How can I get Unicode characters instead of hex entities in target XML

[Manuel Souto Pico]

Dear all, 

I'm having a problem with a XML file, perhaps someone has a tip.

When including a non-breaking space in the translation in OmegaT, the target file has instead the hex entity, namely   , which is perfectly fine in XML of course.

However, due to a problem with markup in the final product, we have been asked to wrap the text content of the translatable node in <![CDATA[ .... ]]>

When I do that, HTML markup is correct in the application but the &#x00a0; entity is displayed literally rather than being interpreted as the no-break character.

Is there any option in the XML filter parameters that I can use to have Unicode characters in the target XML file instead of their equivalent hex character?

Or perhaps you could help me understand why a translation like "Exécuter" looks like that in the target file (rather than "Ex&#x00E9;cuter") whereas "Programme :" becomes "Programme&#x00a0;:".

Thanks a lot.

Cheers, Manuel

[yves.s...@gmail.com]

Hi Manuel,

 

See here : https://okapiframework.org/wiki/index.php/XML_Filter#escapeNbsp

 

-ys

--
You received this message because you are subscribed to the Google Groups "okapi-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-users/CABm46bb3gRgbp%3DNiDoFoxHSaVXau_0Y74Kzpb6XKOQyuFYZzuw%40mail.gmail.com.

[Manuel Souto Pico]

Dear Yves,

Thank you so much for that fast-lightning reply! Indeed, escapeNbsp is the option that was missing, it works now.

It didn't cross my mind that the problem was linked to that specific character. Thanks again.

Cheers, Manuel