summaryrefslogtreecommitdiff
path: root/misc/README
diff options
context:
space:
mode:
authorAlbrecht Schlosser <albrechts.fltk@online.de>2010-04-16 14:25:20 +0000
committerAlbrecht Schlosser <albrechts.fltk@online.de>2010-04-16 14:25:20 +0000
commitead526760fc98a1b47365358fe810eb9cc5efd96 (patch)
tree1dc80a679559fed7371a99564cdb2fb63a50f222 /misc/README
parente0c889087430fcbd990d8edb33643369b2e13cc3 (diff)
Added test files for UTF-8 character testing (use test/editor).
See the README file for more info. git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@7514 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'misc/README')
-rw-r--r--misc/README72
1 files changed, 72 insertions, 0 deletions
diff --git a/misc/README b/misc/README
new file mode 100644
index 000000000..f36f6ae02
--- /dev/null
+++ b/misc/README
@@ -0,0 +1,72 @@
+// $Id$
+//
+// Miscellaneous files for developers:
+//
+
+Developer files for testing UTF-8 character sets and functions:
+================================================================================
+
+Open these files in test/editor and compare the contents.
+
+Test scrolling, move the cursor over the "special" characters (> U+007F),
+watch cursor movement, drawing artefacts, etc..
+
+CAUTION: Do not 'cat' these files unless you know what you're doing.
+Especially the cp1252* files can contain control characters that may freeze
+your screen (xterm etc.).
+
+
+The "native" encoded files contain 8-bit characters with binary values that
+can be seen at the top and left borders, resp. (add both). They should look
+like the image file (cp1252.png) on Windows only (if the current codepage is
+"Western, CP 1252", a superset of ISO-8859-1). They will look different with
+other codepages or on Linux, Unix, or Mac OS X. Use these files with FLTK 1.1
+or an editor with the corresponding codepage or locale.
+
+The UTF-8 encoded files should be usable with FLTK 1.3, FLTK 2, or FLTK 3
+(future). They contain UTF-8 encoded characters at the table positions,
+where the corresponding ISO-8859-1 or Windows copepage 1252 characters would
+be. They should look identical as the image file (cp1252.png) on all UTF-8
+capable systems.
+
+The files with names iso-8859-1_* contain only the ISO-8859-1 subset, i.e.
+the colums with character codes x'80' - x'9F' (U+0080 - U+009F) are empty.
+
+References:
+
+ http://unicode.org/Public/MAPPINGS/ISO8859/8859-1.TXT
+ http://unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP1252.TXT
+
+Files:
+
+The first file is an image of how it should look:
+
+ cp1252.png full Windows Codepage 1252 (Western)
+
+The following two files contain the full Windows Codepage 1252:
+
+ cp1252.txt native (Windows) encoding, suitable for FLTK 1.1
+ cp1252_utf-8.txt UTF-8 encoding, suitable for FLTK 1.3 and greater
+
+The following two files contain only the ISO-8859-1 characters:
+
+ iso-8859-1.txt
+ iso-8859-1_utf-8.txt
+
+
+
+Other developer support files:
+================================================================================
+
+ doxystar.cxx Use this to reformat doxygen comments (test only).
+
+ Compile with: g++ -o doxystar doxystar.cxx
+
+ Usage: cat file | doxystar
+
+ DO NOT USE this for current code development!
+ It is intended for testing of for future code reformatting !
+
+//
+// End of $Id$.
+//