1
0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-09 17:38:00 +00:00
putty-source/charset
Jacob Nevins 0f602f0368 CP866 is popular and small. Add it to both the general and PuTTY
implementations of libcharset, since we've had at least one request for
it in PuTTY.

[originally from svn r6499]
[this svn revision also touched charset,filter,halibut,timber]
2005-12-18 16:57:00 +00:00
..
charset.h CP866 is popular and small. Add it to both the general and PuTTY 2005-12-18 16:57:00 +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
localenc.c CP866 is popular and small. Add it to both the general and PuTTY 2005-12-18 16:57:00 +00:00
macenc.c Don't pass NULL to strcmp. Instead, if the user passes a font of NULL, 2003-01-25 19:21:56 +00:00
mimeenc.c CP866 is popular and small. Add it to both the general and PuTTY 2005-12-18 16:57:00 +00:00
README First draft of Unicode support in pterm. It's pretty complete: it 2002-12-31 12:20:34 +00:00
sbcs.c Having painstakingly generated those reverse mapping tables in 2003-01-01 17:03:27 +00:00
sbcs.dat CP866 is popular and small. Add it to both the general and PuTTY 2005-12-18 16:57:00 +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 CP866 is popular and small. Add it to both the general and PuTTY 2005-12-18 16:57:00 +00:00

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.