mapping no-break space and other special characters

[ptc-957266]

Hello,

We use Epic 4.3 and want to visualize (not replace!) characters like
U+00A0 (non-break space), U+2009 (thin space), ... in xml-documents,
UTF-8 encoded.

The result should be something like:

Hello[nbsp]world[thinsp]: I have a question[thinsp]!

At this moment it looks like:
Hello world : I have a question !

So it looks like all the spaces are normal spaces.


Kind regards for any info.

[bibach]

Michiel,
Creating a custom version of the charent.cf file for your
doctype should allow you to map these characters to different glyphs,
such as something in a font like Symbol or Wingdings. Search the help
for "charent.cf" to find the details. I don't have access to the Epic
4.3 help file, at the moment, but in 5.2, it's covered in a topic called
"How character sets are supported".

-Brandon 🙂

[naglists]

Consider, too, whether or not you're using the content processing pipeline.
charent.cf resolution may fail in your final output if you pass through the
pipeline (multiple parsings and whatnot). We use elements when we have to
pass troublesome special characters from authored XML through the pipeline
to final output. DCAM/DLM and profiling are two examples of functionality
that require the processing pipeline.

[ptc-957266]

Hello,

The charent.cf file specifies how XML or SGML character entities are to
be handled in Epic, but we don't use character entities. All characters
are UTF-8 encoded and not like &somechar;
So I guess that file is not usable for me.

Regards,
Michiel