diff options
author | Rich Felker <dalias@aerifal.cx> | 2013-08-05 13:14:17 -0400 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2013-08-05 13:14:17 -0400 |
commit | 734062b298e129a8f8bdae299f8d2b7b19419867 (patch) | |
tree | 328aa8e11d1391ba5d02515c1ed1c96fa473f687 /src/string/x86_64 | |
parent | a7f18a55298ffaa287336fd0c81dcd3fe45e16b6 (diff) | |
download | musl-734062b298e129a8f8bdae299f8d2b7b19419867.tar.gz musl-734062b298e129a8f8bdae299f8d2b7b19419867.tar.xz musl-734062b298e129a8f8bdae299f8d2b7b19419867.zip |
iconv support for legacy Korean encodings
like for other character sets, stateful iso-2022 form is not supported yet but everything else should work. all charset aliases are treated the same, as Windows codepage 949, because reportedly the EUC-KR charset name is in widespread (mis?)usage in email and on the web for data which actually uses the extended characters outside the standard 93x94 grid. this could easily be changed if desired. the principle of this converter for handling the giant bulk of rare Hangul syllables outside of the standard KS X 1001 93x94 grid is the same as the GB18030 converter's treatment of non-explicitly-coded Unicode codepoints: sequences in the extension range are mapped to an integer index N, and the converter explicitly computes the Nth Hangul syllable not explicitly encoded in the character map. empirically, this requires at most 7 passes over the grid. this approach reduces the table size required for Korean legacy encodings from roughly 44k to 17k and should have minimal performance impact on real-world text conversions since the "slow" characters are rare. where it does have impact, the cost is merely a large constant time factor.
Diffstat (limited to 'src/string/x86_64')
0 files changed, 0 insertions, 0 deletions