Given a document (DITA topic or XHTML) with the following lines:
* Hebrew: מנס
* Basic Latin: øĀÅ
* Latin-1 Supplement: ÑÐÃÊŻƀ
* Latin Extended-A: ĘśƒLjljNJNJǕǿǾ
* Latin Extended-B: DžDžDŽƘƍȟɁɣɸDžDŽ
* Greek: ΚΤццѦЀЀΞΟΠΡυφιθ
* Cyrillic: КХцкҩҴӡӶЍщопр
Then, when converting the above document (be it a XHTML document or a
DITA topic) to PDF, I get this output:
* Hebrew: ###
* Basic Latin: ø#Å
* Latin-1 Supplement: ÑÐÃÊ##
* Latin Extended-A: ##ƒ#######
* Latin Extended-B: ###########
* Greek: ###############
* Cyrillic: #############
One can solve this issue by, in the settings for FOP, selecting (on
one’s computer) a font (such as DejaVu Sans) which contains those
characters, for embedding.
However, according to Apple’s Font Book app, the Times New Roman font,
which is one of the Windows standard fonts, does contain all of the
above characters. And so, my initial attempts to solve this was by
editing the font settings of the conversion stylesheet. That, however,
had no effect.
Question: So, after all, since Times New Roman contains those letters,
why is it not enough to rely on the standard Windows fonts (for which
there is a button in the FOP settings)?
Further: If - for PDF - rendering of characters outside the Latin and
Basic Latin group of characters requires that the user manually selects
a font, there ought to be somewhere an alert about this. Or - another
variant - why not insert a warning about this in the interface for
editing the conversion style sheet? When the user points to a font which
is not as well embedded via the FOP settings, the alert could simply
tell the user to remember to also embed that font in the FOP settings.
Leif Halvard Silli
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
