nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DCR encoding issue - new encoding in DCT not reflecting in DCR

gauri

Hi,
I have changed encoding in a DCT from 'UTF-8' to 'ISO-8859-1'.
When I edit any existing DCR (which was created when encoding was UTF-8) and save it, I am expecting that DCR should now have encoding 'ISO-8859-1'. But, this is not happening.
Even when I create a new DCR or edit and existing one, I am still getting old encoding ('UTF-8'). It is not reflecting ISO-8859-1.
Pl. let me know if you have an idea why this is happening. Not sure whether am I missing anything.
Reagrds,
Gauri

Find more posts tagged with

Comments

retesh

Hi,
I have changed encoding in a DCT from 'UTF-8' to 'ISO-8859-1'.
When I edit any existing DCR (which was created when encoding was UTF-8) and save it, I am expecting that DCR should now have encoding 'ISO-8859-1'. But, this is not happening.
Even when I create a new DCR or edit and existing one, I am still getting old encoding ('UTF-8'). It is not reflecting ISO-8859-1.
Pl. let me know if you have an idea why this is happening. Not sure whether am I missing anything.
Reagrds,
Gauri

I think default UTF-8 encoding cannot be changed using teamsite provided configuration. You would need to write some script to take care of it in the output file. It would be interesting to know why ISO-8859-1 encoding is required in dcr.

-Retesh

gauri

FormsPublisher developer guide mentions that any of the listed encodings can be used in the DCT (list of supported encodings is provided, which has ISO-8859-1 also). So, expecting it to work.

I have a DCR containing French characters. With UTF-8, I am getting some junk character issues.

Based on what I have tried so far:
Earlier when I tried editing the DCR, it gave me parse error due to junk character (encoding was UTF-8).
I downloaded an existing DCR that was having junk character issue.
Modified the encoding to ISO-8859-1 manually. Imported the DCR to TeamSite and set the required EA's.
After setting the encoding manually to ISO-8859-1, I was able to edit DCR successfully.

I do not need it for output file. I need the DCRs with encoding as ISO-8859-1.
Am I missing any setting/configuration?

regards,
gauri

retesh

By default UTF-8 supports all the languages. we have produced korean characters OOTB without issues.
Are you trying to call inline or callserver scripts which could create issue.
You could check if french language font is installed at OS level in teamsite server.

Post your dct for further analysis and also share which version of teamsite you are using.

gauri

Thanks for response.
This is not happening for all the DCRs that have French contnet.
This is happening for only few DCRs (may be some french characters are creating problem with UTF-8). When I imported the same DCR by changing the encoding to ISO-8859-1, i was able to edit it successfully. It gave no error.
Attaching DCT for reference.
Regards,
Gauri

ISCBorisB

Thanks for response.
This is not happening for all the DCRs that have French contnet.
This is happening for only few DCRs (may be some french characters are creating problem with UTF-8). When I imported the same DCR by changing the encoding to ISO-8859-1, i was able to edit it successfully. It gave no error.
Attaching DCT for reference.
Regards,
Gauri

There seems to be a misunderstanding here. Yes, you can indeed use Xerces encodings for DCT.
That affects DCTs Names, Labels, Descriptions and nothing else. Regardless of DCT Encoding though,
default DCR Encoding is always UTF-8.

Sure, with some efforts it is possible to store DCRs in an encoding other than UTF-8 (unless it is in IWOV DTD).
I would recommend against it. You will create numerous problems starting with compromised GUI preview/generation
and will need yet more coding to overcome it. It is IMO much easier to keep DCRs in UTF-8 and encode (or re-code)your
generated assets the way you need it.

Your "junk character" issue is a typical manifestation of mismatch between Page's encoding declaration ("Content-Type"
HTTP Reply Header) and actual page encoding, page encoding errors or both. There are few good threads in the Forum
discussing all that. So, to rephrase what I already said, fixing the real cause of garbled symbols rendition is much easier
than mangle DCR and fight consequences.

Topic_39613__Image URI.rptdesign

gauri

Thanks ISCBorisB for the response.

Following are details of the scenario where I am facing junk character issue. Your comments on this will help me decide the next steps.

Scenario:
- I have a source system (oracle database) that stores information about persons in the system
This data keeps refreshing based on some other integrated system.
- I have a batch program that runs everyday. It reads data in Oracle database and updates the latest values to respective DCRs.
This content is French.

Issue:
- Batch program runs and updates French DCR.
- When i try editing the updated DCR from TeamSite, it give me parse error due to junk character.
This is not happening everytime. This issue is seen intermittently.

In your response, you have mentioned that "That affects DCTs Names, Labels, Descriptions and nothing else."
Does it not impact the content? Just wanted to clarify.

I have changed encoding in a DCT from 'UTF-8' to 'ISO-8859-1' (have removed the brackets just to display it correctly in the post).
Before:
?xml version="1.0" encoding="UTF-8"?
Now:
?xml version="1.0" encoding="ISO-8859-1"?

When I update any existing DCR or create a new one, expecting it to have ISO-8859-1.
Why is it not reflecting in DCR? Is it b'cos of TeamSite's default behavior that irrespective of the encoding mentioned in DCT, it will always consider it to be UTF-8?
Do I need to write some custom code (not sure whether it will be thro' FormAPI) to save the DCR in ISO-8859-1?

I want to check what issues it may give when the encoding changes. But, it is not reflecting at all in the DCRs.

Pl. let me know your comments.

Regards,
Gauri

ISCBorisB

In your response, you have mentioned that "That affects DCTs Names, Labels, Descriptions and nothing else."
Does it not impact the content? Just wanted to clarify.

No it does not. DCT does not have any content to impact. Only DCR does and DCR is a different XML
with completely different DTD.

Batch program runs and updates French DCR...

That's what I would modify if I were you. Leave DCRs in their native UTF-8 encoding. Your code should
take care of maintaining it and encoding DCRs' Data to UTF-8 if needed. You can use true UTF-8 encoding
or you can find/substitute diacritical characters with XML numeric entities (considering both upper and
lower cases, there are perhaps about two dozens diacriticals in French).

Take a look at [thread=21037]this old thread[/thread]. It discusses few ways to do all that in Perl,
you'll do it in whatever language your batch is written.