From ad41ebb7b2cdcada7b6afed29ddee17690bd5c97 Mon Sep 17 00:00:00 2001
From: nyamatongwe
On Windows, code page can be set to 932 (Japanese Shift-JIS), 936 (Simplified Chinese GBK), +
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.
-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 SC_CP_DBCS (1)
- which uses the current locale to handle multi byte characters which may work for otherwise unsupported
- code pages.
For GTK+ 1.x, the locale should be set to a Unicode locale with a call similar to
- setlocale(LC_CTYPE, "en_US.UTF-8"). Fonts with an "iso10646" registry
- should be used in a font set. Font sets are a comma separated list of partial font
- specifications where each partial font specification can be in the form:
- foundry-fontface-charsetregistry-encoding or
- fontface-charsetregistry-encoding or foundry-fontface or
- fontface. An example is "misc-fixed-iso10646-1,*".
- On GTK+ 2.x, Pango fonts should be used rather than font sets.
Setting codePage to a non-zero value that is not SC_CP_UTF8 is
- operating system dependent.
SCI_SETKEYSUNICODE(bool keysUnicode)
SCI_GETKEYSUNICODE
On Windows, character keys are normally handled differently depending on whether Scintilla is a wide
--
cgit v1.2.3