Menu
▾
▴
[Plplot-cvs] SF.net SVN: plplot:[12580] trunk/doc/docbook/src/advanced.xml
|
From: <ai...@us...> - 2013-10-05 19:38:29
|
Revision: 12580
http://sourceforge.net/p/plplot/code/12580
Author: airwin
Date: 2013-10-05 19:38:25 +0000 (Sat, 05 Oct 2013)
Log Message:
-----------
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 <ai...@us...> for
-DBUILD_DOC=ON and the following targets:
man (results not affected since the man pages ignore the advanced
chapter.)
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.)
Modified Paths:
--------------
trunk/doc/docbook/src/advanced.xml
Modified: trunk/doc/docbook/src/advanced.xml
===================================================================
--- trunk/doc/docbook/src/advanced.xml 2013-10-05 19:00:37 UTC (rev 12579)
+++ trunk/doc/docbook/src/advanced.xml 2013-10-05 19:38:25 UTC (rev 12580)
@@ -2106,7 +2106,7 @@
<para>
Sections of text can have an underline or overline appended. For
- example, the string &over-under; is obtained by specifying
+ example, the string S̅(f̲r̲e̲q̲) is obtained by specifying
<literal>"#+S#+(#-freq#-)"</literal>.
</para>
@@ -2274,6 +2274,85 @@
STRING/></literal> as appropriate.
</para>
+ <para>
+ It should be emphasized that the unicode escape sequences
+ above only work properly for modern unicode-aware devices such as the
+ svg device or the very large set of cairo and qt devices. And for
+ those devices the alternative of simply specifying the unicode symbols
+ using UTF-8 encoding of PLplot input strings is much more convenient
+ for users than using the above escape sequences. For example, we
+ use UTF-8 strings rather than escape sequences in example 24
+ to render the word "Peace" in several different languages.
+ </para>
+
+ <table frame="all" id="peace">
+ <title>The word "peace" expressed in several different languages in example 24 using UTF-8</title>
+ <tgroup align="center" cols="2">
+ <colspec align="center" colnum="1" colwidth="2*"/>
+ <tbody valign="top">
+ <row>
+ <entry>Hebrew</entry>
+ <entry>שלום</entry>
+ </row>
+ <row>
+ <entry>French</entry>
+ <entry>Paix</entry>
+ </row>
+ <row>
+ <entry>Kurdish</entry>
+ <entry>Hasîtî</entry>
+ </row>
+ <row>
+ <entry>English</entry>
+ <entry>Peace</entry>
+ </row>
+ <row>
+ <entry>Korean</entry>
+ <entry>평화</entry>
+ </row>
+ <row>
+ <entry>Turkish</entry>
+ <entry>Barış</entry>
+ </row>
+ <row>
+ <entry>Hindi</entry>
+ <entry>शांति</entry>
+ </row>
+ <row>
+ <entry>German</entry>
+ <entry>Friede</entry>
+ </row>
+ <row>
+ <entry>Arabic</entry>
+ <entry>ﺳﻼم</entry>
+ </row>
+ <row>
+ <entry>Mandarin</entry>
+ <entry>和平</entry>
+ </row>
+ <row>
+ <entry>Russian</entry>
+ <entry>Мир</entry>
+ </row>
+ <row>
+ <entry>Spanish</entry>
+ <entry>Paz</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <para>
+ For unicode-aware devices it is possible as well to specify
+ mathematical glyphs (such as ∂, ∇, ∑, ∫, and ∰) using UTF-8 encoding
+ of PLplot input strings. A typical input method in this case is
+ simply to cut and paste the desired mathematical glyph from, e.g.,
+ gucharmap to source code being edited by a unicode-aware editor such
+ as emacs. Such input methods may be conveniently used, for example,
+ to specify the very wide range of mathematical symbols that are
+ typically desired for scentific plots.
+ </para>
+
</sect2>
<sect2 id="character-size">
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|