4 Commits

Author	SHA1	Message	Date
Simon Tatham	a2afc03bdb	A better solution to the problem of duplicated positions in ... CS_ISO8859_1_X11: where two SBCS positions map to the same Unicode code point, we now have a `sortpriority' hint which can tell sbcsgen.pl which one it should preferentially generate when converting back to SBCS. [originally from svn r2427]	2003-01-02 16:56:29 +00:00
Ben Harris	f8e3eee673	Add all the Mac OS simple single-byte character sets from ftp.unicode.org. ... Also add the older variants described there, and the character set used by the "VT100" font (old and new). Since RFC 1345 defines "macintosh" to refer to the currency-sign variant of Mac OS Roman, update our table to match. [originally from svn r2403]	2003-01-01 16:24:01 +00:00
Simon Tatham	548555ded4	Better, I think, to avoid mapping 0x00 -> U+0020 in the X11 ... nonstandard font encoding. 0x20 maps to it, so it's not as if it's in short supply. [originally from svn r2396]	2002-12-31 15:42:07 +00:00
Simon Tatham	ad2bbc52a4	First draft of Unicode support in pterm. It's pretty complete: it ... does UTF-8 copy and paste (falling back to normal strings if necessary), it understands X font encodings and translates things accordingly so that if you have a Unicode font you can ask for virtually any single-byte encoding and get it (Mac-Roman pterm, anyone?), and so on. There's work left to be done (wide fonts for CJK spring to mind), but I reckon this is a pretty good start. [originally from svn r2395]	2002-12-31 12:20:34 +00:00