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; } } }

Encoding of DCR

Amit_LnT

Hi,
I want to know, how can we change the encoding of DCR's. The DCR's which i m creating is getting saved in UTF-8 format.
i searched in interwoven pdf's, but was not able to locate related content.
it was saying about change in one file, file_encoding.cfg to give the encoding for the contents.
but that is for the one which do not specify encoding. correct me if i m wrong. Smiley Happy

even i tried to change in datacapture.cfg. but it’s not reflecting in DCR.
anyone knowing abt it, help is appreciated.

i m using teamsite 6.5.0 sp2 on windows server 2003 sp1

thanks
amit

Find more posts tagged with

Comments

Amit_LnT

It looks like DCR will be always created in UTF-8 format.
Any expert advice on this?

moonkhanna

It looks like DCR will be always created in UTF-8 format.
Any expert advice on this?

you can configure this is templating.cfg .. check the templating guide

ISCBorisB

Hi,
I want to know, how can we change the encoding of DCR's. The DCR's which i m creating is getting saved in UTF-8 format.
i searched in interwoven pdf's, but was not able to locate related content.
it was saying about change in one file, file_encoding.cfg to give the encoding for the contents.
but that is for the one which do not specify encoding. correct me if i m wrong.
even i tried to change in datacapture.cfg. but it’s not reflecting in DCR.
anyone knowing abt it, help is appreciated.

i m using teamsite 6.5.0 sp2 on windows server 2003 sp1

thanks
amit

"file_encoding.cfg" is a configuration to control "Source Difference/Merge" Java Applet GUI encoding (in 6.5 see Administration Guide,
Appendix C). It has nothing to do to *real* Files Encoding, DCRs or otherwise.

There are several supported/certified Data Capture Templates (DCT) encodings, see Appendix "Internationalization" in the
Forms Publisher Developer Guide. Supported Data Capture Records (DCR) encoding though is limited to UTF-8.

That said, there are numerous mechanisms to help you to generate what you want out of this UTF-8 encoded DCR. You can have a DCT
created in Shift_JIS to capture data in UTF-8 to generate an output in Windows-1256 if that's what you want.

Amit_LnT

Hi Boris,
I want to have the DCR by default to be saved in Latin-1 instead of UTF-8. I do not want to change the encoding of DCT.

As you mentioned about the encoding of DCR only in UTF-8, I got the same
in one of the PDF, tst.650.dev.pdf.
"There is no restricted binding between encoding of a data capture template, encoding of a
presentation template, and encoding of page generation. Data capture templates can be in
one encoding, while presentation templates be in a different encoding, and HTML output in
yet another encoding. For example, you could have a data capture template created/edited
in Shift_JIS. The data records can then be combined with an UTF-8 encoded presentation
template, to generate an EUC-JP encoded HTML file. The only constraint is that data
records are encoded in UTF-8. "

Adam Stoller

Hi Boris,
I want to have the DCR by default to be saved in Latin-1 instead of UTF-8. I do not want to change the encoding of DCT.

As you mentioned about the encoding of DCR only in UTF-8, I got the same
in one of the PDF, tst.650.dev.pdf.
".... The only constraint is that data records are encoded in UTF-8. "

Well given the documented constraint - your "want" is just that - a "want". If you need the DCR's XML in Latin-1 in order to deploy it (as a file or via DD or something) you could use a PT to generate a different XML file in the desired encoding, and then process that file.

Frederik

I agree... to my knowledge you cannot control the encoding of the DCR. It is and always will be UTF-8.
If you need something else, produce it out of the DCR with presentation templates.

Care to explain WHY you want DCR's in Latin1? Given that they are XML files, and all XML parsers should be more than happy with XML in UTF-8, I can't see the reason for your Latin1 preference.

sample.rptdesign

Amit_LnT

Hi All, Thanks for your input.

Care to explain WHY you want DCR's in Latin1? Given that they are XML files, and all XML parsers should be more than happy with XML in UTF-8, I can't see the reason for your Latin1 preference.

Our client has sites for European languages. The DB is also set to Latin-1 character code. Previously, it was inserting junk characters in the database in place of some french characters from DCR. So, we encoded the content in Latin-1 before insertion and it worked properly.

Migrateduser

I work in Europe with all kinds of content languages (including double byte like chinese etc.) and from experiance I find that alligning everything to UTF-8 (inluding the database) never results in encoding issues.

Is changing the database to UTF-8 a better option? You will be allowed to handle a wider range of characters.

Ron

TESTSONY_PickList.doc

Amit_LnT

I work in Europe with all kinds of content languages (including double byte like chinese etc.) and from experiance I find that alligning everything to UTF-8 (inluding the database) never results in encoding issues.

Is changing the database to UTF-8 a better option? You will be allowed to handle a wider range of characters.

Ron

Yes Ron, I agree.
But, the website application is not managed by us. Client has its own tech team which has design the website and database.