diff options
| -rw-r--r-- | doc/ScintillaDoc.html | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/doc/ScintillaDoc.html b/doc/ScintillaDoc.html index cf68e1d69..f4c0e93c6 100644 --- a/doc/ScintillaDoc.html +++ b/doc/ScintillaDoc.html @@ -38,7 +38,7 @@ <h1>Scintilla Documentation</h1> - <p>Last edited 7/August/2009 NH</p> + <p>Last edited 1/September/2009 NH</p> <p>There is <a class="jump" href="Design.html">an overview of the internal design of Scintilla</a>.<br /> @@ -2933,16 +2933,17 @@ struct TextToFind { normal Unicode encoding before being drawn by the OS and thus can display Hebrew, Arabic, Cyrillic, and Han characters. Languages which can use two characters stacked vertically in one horizontal space, such as Thai, will mostly work but there are some issues where the characters - are drawn separately leading to visual glitches. Bi-directional text is not supported. Characters outside the - Basic Multilingual Plane are unlikely to work.</p> + are drawn separately leading to visual glitches. Bi-directional text is not supported. </p> <p>On Windows, code page can be set to 932 (Japanese Shift-JIS), 936 (Simplified Chinese GBK), 949 (Korean Unified Hangul Code), 950 (Traditional Chinese Big5), or 1361 (Korean Johab) although these may require installation of language specific support.</p> - <p>On GTK+, code page <code>SC_CP_DBCS</code> (1) sets Scintilla into - multi byte character mode as is required for Japanese language processing with - the EUC encoding.</p> + <p>On GTK+, code page can be set to 932 (Japanese Shift-JIS), 936 (Simplified Chinese GBK), + or 950 (Traditional Chinese Big5). + The code page may also be set to <code>SC_CP_DBCS</code> (1) + which uses the current locale to handle multi byte characters which may work for otherwise unsupported + code pages.</p> <p>For GTK+ 1.x, the locale should be set to a Unicode locale with a call similar to <code>setlocale(LC_CTYPE, "en_US.UTF-8")</code>. Fonts with an <code>"iso10646"</code> registry |