summaryrefslogtreecommitdiff
path: root/documentation/src/unicode.dox
diff options
context:
space:
mode:
authorAlbrecht Schlosser <albrechts.fltk@online.de>2016-03-23 14:02:25 +0000
committerAlbrecht Schlosser <albrechts.fltk@online.de>2016-03-23 14:02:25 +0000
commit979740ce91525cc301a9173731d6aaf3004a6c88 (patch)
treed312c7f444b758163bf3e1b13a7bf6da28d13b26 /documentation/src/unicode.dox
parent8d89d760fa2d01b7f6e38067793d1b480817ae78 (diff)
Enable definition of Unicode conv. options on compiler command line.
Three documented pre-processor variables can now be defined on the compiler command line to avoid editing the FLTK src code. The default values still apply unchanged. Port of branch-1.3, svn r11404. git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3-porting@11406 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'documentation/src/unicode.dox')
-rw-r--r--documentation/src/unicode.dox12
1 files changed, 8 insertions, 4 deletions
diff --git a/documentation/src/unicode.dox b/documentation/src/unicode.dox
index 818d22b49..ecd9074bd 100644
--- a/documentation/src/unicode.dox
+++ b/documentation/src/unicode.dox
@@ -191,14 +191,14 @@ the following limitations:
\section unicode_illegals Illegal Unicode and UTF-8 sequences
-Three pre-processor variables are defined in the source code that
+Three pre-processor variables are defined in the source code [1] that
determine how %fl_utf8decode() handles illegal UTF-8 sequences:
- if ERRORS_TO_CP1252 is set to 1 (the default), %fl_utf8decode() will
assume that a byte sequence starting with a byte in the range 0x80
- to 0x9f represents a Microsoft CP1252 character, and will instead
- return the value of an equivalent UCS character. Otherwise, it
- will be processed as an illegal byte value as described below.
+ to 0x9f represents a Microsoft CP1252 character, and will return
+ the value of an equivalent UCS character. Otherwise, it will be
+ processed as an illegal byte value as described below.
- if STRICT_RFC3629 is set to 1 (not the default!) then UTF-8
sequences that correspond to illegal UCS values are treated as
@@ -210,6 +210,10 @@ determine how %fl_utf8decode() handles illegal UTF-8 sequences:
byte value is returned unchanged, otherwise 0xFFFD, the Unicode
REPLACEMENT CHARACTER, is returned instead.
+[1] Since FLTK 1.3.4 you may set these three pre-processor variables on
+ your compile command line with -D"variable=value" (value: 0 or 1)
+ to avoid editing the source code.
+
%fl_utf8encode() is less strict, and only generates the UTF-8
sequence for 0xFFFD, the Unicode REPLACEMENT CHARACTER, if it is
asked to encode a UCS value above U+10FFFF.