fltk/misc
Albrecht Schlosser 0aa28e28b4 Minor corrections and additions to misc UTF-8 test files.
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@7515 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
2010-04-16 14:49:08 +00:00
..
cp1252_utf-8.txt Minor corrections and additions to misc UTF-8 test files. 2010-04-16 14:49:08 +00:00
cp1252.png Added test files for UTF-8 character testing (use test/editor). 2010-04-16 14:25:20 +00:00
cp1252.txt Added test files for UTF-8 character testing (use test/editor). 2010-04-16 14:25:20 +00:00
doxystar.cxx Added test files for UTF-8 character testing (use test/editor). 2010-04-16 14:25:20 +00:00
iso-8859-1_utf-8.txt Added test files for UTF-8 character testing (use test/editor). 2010-04-16 14:25:20 +00:00
iso-8859-1.txt Added test files for UTF-8 character testing (use test/editor). 2010-04-16 14:25:20 +00:00
README Minor corrections and additions to misc UTF-8 test files. 2010-04-16 14:49:08 +00:00

//
// $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.).

Detailed file description:

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.

Special Notes:

  U+0022 ("quotation mark") is doubled intentionally. This has been done for
  better results in test/editor, because otherwise the rest of the file would
  be shown in blue color (as a comment).

  U+0098 ("small tilde") may not display correctly on Windows systems. I saw
  the same effect with other Windows editors as well. The following characters
  may be display "shifted left" by one position. Seems to work correctly on
  Linux (with UTF-8 encoding).
  
  There may currently be drawing artefacts when moving the cursor forwards
  and/or backwards over some "special" characters.


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		native (Windows) encoding, suitable for FLTK 1.1
 iso-8859-1_utf-8.txt	UTF-8 encoding, suitable for FLTK 1.3 and greater



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 future code reformatting !

//
// End of $Id$.
//