putty/charset
Simon Tatham e5012fa846 ... of course, that would be better still if I remembered to update
`nvalid'. Ahem.

[originally from svn r2428]
2003-01-02 17:07:24 +00:00
..
.cvsignore First draft of Unicode support in pterm. It's pretty complete: it 2002-12-31 12:20:34 +00:00
README First draft of Unicode support in pterm. It's pretty complete: it 2002-12-31 12:20:34 +00:00
charset.h Add a mechanism for determining which charset to use for a given Mac OS font, 2003-01-01 19:51:13 +00:00
enum.c First draft of Unicode support in pterm. It's pretty complete: it 2002-12-31 12:20:34 +00:00
fromucs.c First draft of Unicode support in pterm. It's pretty complete: it 2002-12-31 12:20:34 +00:00
internal.h First draft of Unicode support in pterm. It's pretty complete: it 2002-12-31 12:20:34 +00:00
macenc.c Add a mechanism for determining which charset to use for a given Mac OS font, 2003-01-01 19:51:13 +00:00
mimeenc.c Add all the Mac OS simple single-byte character sets from ftp.unicode.org. 2003-01-01 16:24:01 +00:00
sbcs.c Having painstakingly generated those reverse mapping tables in 2003-01-01 17:03:27 +00:00
sbcs.dat A better solution to the problem of duplicated positions in 2003-01-02 16:56:29 +00:00
sbcsgen.pl ... of course, that would be better still if I remembered to update 2003-01-02 17:07:24 +00:00
slookup.c First draft of Unicode support in pterm. It's pretty complete: it 2002-12-31 12:20:34 +00:00
toucs.c First draft of Unicode support in pterm. It's pretty complete: it 2002-12-31 12:20:34 +00:00
utf8.c Add internal prototypes to keep my compiler from complaining. 2002-12-31 21:12:29 +00:00
xenc.c First draft of Unicode support in pterm. It's pretty complete: it 2002-12-31 12:20:34 +00:00

README

This subdirectory contains a general character-set conversion
library, used in the Unix port of PuTTY, and available for use in
other ports if it should happen to be useful.

I intend to use this same library in other programs at some future
date. It is therefore a _strong_ design goal that this library
should remain perfectly general, and not tied to particulars of
PuTTY. It must not reference any code outside its own subdirectory;
it should not have PuTTY-specific helper routines added to it unless
they can be documented in a general manner which might make them
useful in other circumstances as well.