DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2378 Version: 1.3.0 That's a *great* first step! Thanks. I was considering a combination of your changes and Markus Kuhn's utf2ps.c, but I was still in the learning and investigation phase, and you beat me. ;-) My general plan was to use the utf2ps.c way, but also to set the encoding to ISOLatin1Encoding to avoid replacing all standard ISO-8859-1 characters. This would make the tables much shorter (I removed the area 0xA1-0xFF in my tests), and thus reduce searching time and have shorter PS output (escaping characters outside the ASCII range notwithstanding, see below). Another way I thought about was to use a simple replacement table for all characters that are in the ISOLatin1Encoding *and* StandardEncoding, but leave the font encoding in its default. Things to consider: (1) Minor change: I suggest to use the reversed question mark (U+00BF) as the undefined character instead of the normal question mark. (2) I'm not sure if it is okay to use bytes in the range 0x80-0xFF (or more precise: 0xA0-0xFF) in PS files. We should verify whether we need to escape them (\nnn) for better compatibility, since I seem to remember that PostScript files are recommended to contain ASCII (<0x80) only. (3) The Euro sign is important, but still missing. (4) There are a lot more characters in the Mac Roman character set that are undefined with this solution (according to Markus Kuhn's uniset 46 or 48, depending on the Mac encoding file used [1][2], including Euro). Some of them are probably rarely used punctuation and accent characters. (5) Greek, Cyrillic, and CJK character sets - but I wouldn't mind leaving them away for now. They would all need non-standard fonts, and that's another story. [1] http://en.wikipedia.org/wiki/Mac_OS_Roman [2] http://www.unicode.org/Public/MAPPINGS/VENDORS/APPLE/ROMAN.TXT Link: http://www.fltk.org/str.php?L2378 Version: 1.3.0 _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
