| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
| |
specify characters to 'confuse' is to just put them on the command
line in the system multibyte encoding! In a UTF-8 terminal environment
this may very well be the easiest thing.
[originally from svn r9584]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Unicode values (typically two of them), and it finds cases in which
the provided characters are all encoded as the same thing in different
charsets and prints those charsets. So if you encounter, for example,
some piece of text which has U+0153 LATIN SMALL LIGATURE OE where you
might have expected U+00A3 POUND SIGN, simply run 'confuse 153 a3' and
it'll tell you which character sets the sender and receiver of the
text might have got confused between.
[originally from svn r9581]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r9580]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
| |
and a long int. Spotted by Ubuntu 12.04's gcc, and probably would have
caused trouble on 64-bit machines.
[originally from svn r9489]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I had wrongly believed my TYPECHECK macro double-evaluated one of its
arguments and hence would cause side effects to happen twice. But in
fact I've just realised that although it double-_expands_ the
argument, it doesn't double-_evaluate_ it: the two expansions occur in
mutually exclusive branches of a ?:, and hence cannot both be
executed.
So I've removed the comment that says my macro is rubbish. My macro is
in fact great :-)
[originally from svn r9328]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
| |
[originally from svn r9327]
[r9326 == c72d4b413f024e3c50645caceaddbb65401fb06a in putty repository]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
the list.
[originally from svn r8498]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
| |
unsigned char. On platforms were char is signed, passing plain char won't
cut it. Make sure we case chars to unsigned char before passing them to
tolower().
[originally from svn r8404]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
initialisers, so that gcc stops whining.
[originally from svn r8311]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
support for it.
[originally from svn r8151]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
endings, remove \r from input lines.
[originally from svn r8113]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
| |
output length to charset_{to,from}_unicode, permitting convenient
dry-running of conversions to determine the required output length
and/or test for the presence of difficult characters.
[originally from svn r7677]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r7495]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
| |
used by GNU Emacs. This is likely to be useful for generating or
interpreting "coding:" entries in file local variables.
[originally from svn r7455]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
| |
commit it. Add `-i' option to cstable, which causes charset names to
be output as CS_* constants where meaningful. (Doesn't apply to MBCS
base charsets, because CS_* constants identify _encodings_.)
[originally from svn r6728]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
of this file!
[originally from svn r6705]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
| |
where two SBCS code points mapped to a single Unicode point.
Changed so that by default it favours the lower SBCS code point.
On ixion, this highlighted ambiguities in CS_MAC_THAI, CS_MAC_SYMBOL, and
CS_VISCII. Guessed at a preference for the first two and added "sortpriority"
directives. (No idea about VISCII.)
[originally from svn r6641]
[this svn revision also touched charset,filter,putty,timber]
|
| |
|
|
|
|
|
|
| |
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,putty,timber]
|
| |
|
|
|
|
|
|
|
| |
genuinely portable form. (Thanks to IWJ for ideas.) While I'm here,
add a couple of explicit `unsigned' casts and U suffixes to prevent
more pedantic compilers from warning.
[originally from svn r6463]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
| |
auto-type-checking DEPLANARISE and REPLANARISE macros have turned
out to only work in gcc, which is a shame.
[originally from svn r6455]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
| |
(Fixes a warning in iso2022.c. There are lots more.)
[originally from svn r6424]
[r6378 == 41e50e9f2e3e67da805c5d9037cc650f363e5279]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
what that's useful for but it seemed a pity not to do it) and
compound text.
I've completely removed the compound text implementation from
iso2022s.c in favour of using the more flexible iso2022.c, meaning
we can cope with nastiness such as DOCS.
This is largely untested: I've checked it on small examples as I
went along, but it lacks anything resembling a proper test suite.
[originally from svn r6378]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
I'm here, I've updated the URL to the Adobe Glyph List.
[originally from svn r6376]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
works (unlike our old one).
[originally from svn r6358]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6357]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6354]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6353]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RO data size in cns11643.o from 400k to 240k. Relies on there being
at most seven planes (7*94*94 <= 64k) and on the character set not
encoding any Unicode code point above U+40000; if either of these
becomes untrue later on we can always fall back to the previous
approach, or to somewhere between that and here.
The new version passes all the same tests as the old one did, and
generates the same output under the new `cstable -v'. I'm confident
that I haven't broken it.
[originally from svn r6351]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6350]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
point in every charset.
[originally from svn r6349]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6348]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6347]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
characters". We now filter out the latter from our mapping table.
[originally from svn r6345]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
| |
account when checking the reverse mapping for every potentially
relevant Unicode character.
[originally from svn r6343]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
uses it yet.
[originally from svn r6342]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
| |
Big5 in COMPOUND_TEXT. Emacs does lots of other rude things to
COMPOUND_TEXT, but this one is supported by XLib as well.
[originally from svn r6336]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
ISO 8859-15, and BIG5.
[originally from svn r6335]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
| |
line-drawing). I think this means that libcharset supports all the character
sets that PuTTY supports, which is nice.
[originally from svn r6330]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6329]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
| |
2: Minimal write_iso2022(): it can't encode anything, but promises not to
segfault.
[originally from svn r6328]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
| |
_bottom_ half of JIS X 0201 (the one that's almost identical to
ASCII, equivalent to the bottom half of Shift-JIS), not the top
half.
[originally from svn r6327]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
so it can be used directly in iso2022.c.
[originally from svn r6326]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6325]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6324]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6323]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6321]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
largely work. It might even be useful for something.
[originally from svn r6320]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6319]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6318]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
the usual X fonts.
[originally from svn r6317]
[this svn revision also touched charset,filter,timber]
|