Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


Commit [r12580] Maximize Restore History

Add some explanatory text concerning UTF-8 encoded input strings. This

explanation includes a wide variety of UTF-8 glyphs (all the "peace"
words in Example 24 and a number of mathematical symbols). Thus, this
additional explanatory text is also a good test of how our
documentation build system handles UTF-8 glyphs in general.

Tested by Alan W. Irwin <airwin@users.sourceforge.net> for
-DBUILD_DOC=ON and the following targets:

man (results not affected since the man pages ignore the advanced

info (good results; all math glyphs and all but the glyphs occurring
in the Korean, Hindi, and Mandarin "peace" words came through fine.
That's exactly the same set of missing glyphs that occurs when I use
"less" on advanced.xml so it is possible some configuration adjustment
for my system will fix the missing glyphs that occur both for the info
form of our documentation and when using "less".)

html (outstanding results; all math glyphs and all the glyphs occurring
in the set of "peace" words render without issues including the CTL
languages like Hebrew, Arabic, and Hindi.)

pdf (good results; all math glyphs and all but the glyphs occurring in
the Korean and Mandarin "peace" words come through fine. I attribute
these issues to missing Korean and Mandarin glyphs in the chosen
FreeSans, FreeSerif, and FreeMono fonts. The order of the glyphs in
the Hindi peace word is not correct (last two glyphs switched) which
is a common complex text layout (CTL) issue when using unsophisticated
software to render Hindi. More comments on these PDF results are
forthcoming on the plplot-devel list.)

airwin 2013-10-05

changed /trunk/doc/docbook/src/advanced.xml
/trunk/doc/docbook/src/advanced.xml Diff Switch to side-by-side view