xml output problem

Teamsite 6.7.1 /Solaris-10

I am generating xml output from a DCR which contains french characters.
When i generate the output xml its containing the html entities used for the french charater.

Votre voiture achet&ampeacute;e neuve est rembours&ampeacute;e &ampagrave; sa valeur d&amprsquo;achat pendant 12 mois

But i need exactly the french character to be placed in output xml like the following.

Votre voiture achetée neuve est remboursée à sa valeur d’achat pendant 12 mois

I tried with html:entities encode and decode. But still the problem has not solved.I am using TinyMCE (richtext) in my DCT.Please advice

Find more posts tagged with

Comments

kaalraa

Teamsite 6.7.1 /Solaris-10

I am generating xml output from a DCR which contains french characters.
When i generate the output xml its containing the html entities used for the french charater.

Votre voiture achetée neuve est remboursée à sa valeur d’achat pendant 12 mois

But i need exactly the french character to be placed in output xml like the following.

Votre voiture achetée neuve est remboursée à sa valeur d’achat pendant 12 mois

I tried with html:entities encode and decode. But still the problem has not solved.I am using TinyMCE (richtext) in my DCT.Please advice

What you have written as your XML declaration as DocType and have you tried to encapsulate your french characters with CDATA tag??

Please attach your generated XML to have a more clear picture on it?

Adam Stoller

Teamsite 6.7.1 /Solaris-10

I am generating xml output from a DCR which contains french characters.
When i generate the output xml its containing the html entities used for the french charater.

Votre voiture achet&ampeacute;e neuve est rembours&ampeacute;e &ampagrave; sa valeur d&amprsquo;achat pendant 12 mois

But i need exactly the french character to be placed in output xml like the following.

Votre voiture achetée neuve est remboursée à sa valeur d’achat pendant 12 mois

I tried with html:entities encode and decode. But still the problem has not solved.I am using TinyMCE (richtext) in my DCT.Please advice

Not sure, but I think the entities are more portable and thus more correct - and it's the application that consumes the XML you're generating that should take care of processing the entities...

Frederik

@ghoti: personally, I disagree... I think that clean xml UTF-8, without entities, is more portable. It just requires to have good encoding conf in the whole flow

baskar, how are the DCR files? do they have the HTML entities, or proper UTF-8 characters? And how do you get XML out of the DCR? Maybe you should show the PT ?

baskar

The output xml will be used by a flash application to display dynamic content .
But as the ouput xml contains html entities the pages with flash contains display text with HTML entities.

I attached the 2 xml files one with french characters(home_orig.xml) and the other with html entities for the french character(home.xml).

baskar

I can see french characters in DCR.But ofcourse when i try to open the DCR in editplus its showing the values with html entities.

Please find the tpl used to generate XML in attachment.

Frederik

But ofcourse when i try to open the DCR in editplus its showing the values with html entities.

you mean that in the DCR *file* the entities are already there? then you need to fix the rich text editor settings.

I have limited experience with TinyMCE configuration, but I would hope there is a setting to tell it not to output entities. I have to say that my impression thus far of TinyMCE as implemented in TS 6.7.1 is very bad :-(

off-topic: for convenience you could concatenate the 2 endCDATA parts in the perl snippet of your TP

--
EDIT: I had a deeper look at that, and it doesn't seem like this setting is exposed, although the TinyMCE editor does have a setting for it. cfr http://TEAMSITE671.HOST/iw/tinymce/docs/reference_configuration.html and entity related options. If you want, you could change the js files deep in Teamsite, I think it is $IWHOME/httpd/iw/tinymce/jscripts/tiny_mce/tiny_mce_src.js (probably just a one word change in there - but it will have global effect). Or better, you can reverse engineer the wrapper objects that IWOV created and find a nice FormAPI call to change the setting on the fly for just the editor that needs it. See for instance $IWHOME/httpd/webapps/content_center/datacapture/dc_editor.js

Good luck. And tell us what you did, too! ;-)

Adam Stoller

you mean that in the DCR *file* the entities are already there? then you need to fix the rich text editor settings.

I have limited experience with TinyMCE configuration, but I would hope there is a setting to tell it not to output entities. I have to say that my impression thus far of TinyMCE as implemented in TS 6.7.1 is very bad :-(

off-topic: for convenience you could concatenate the 2 endCDATA parts in the perl snippet of your TP

--
EDIT: I had a deeper look at that, and it doesn't seem like this setting is exposed, although the TinyMCE editor does have a setting for it. cfr http://TEAMSITE671.HOST/iw/tinymce/docs/reference_configuration.html and entity related options. If you want, you could change the js files deep in Teamsite, I think it is $IWHOME/httpd/iw/tinymce/jscripts/tiny_mce/tiny_mce_src.js (probably just a one word change in there - but it will have global effect). Or better, you can reverse engineer the wrapper objects that IWOV created and find a nice FormAPI call to change the setting on the fly for just the editor that needs it. See for instance $IWHOME/httpd/webapps/content_center/datacapture/dc_editor.js

Good luck. And tell us what you did, too! ;-)

Why go to all the trouble of trying to implement an unsupported hack? (I do agree that the TinyMCE implementation could/should be improved, but ...) - If the process already involves using a PT to generate XML output (as distinct from the DCR which is the source XML input) - then you should be able to handle the resolution of entities in the PT code - at least I'd think you could do so - and it would probably be more supportable (IMO)