> However, running the script with that doesn't produce exactly what we
> have in utf8_to_sjis.map, either. It's otherwise same, but we have
> some extra mappings:
>
> - {0xc2a5, 0x5c},
0xc2a5 is U+00a5. The glyph is "YEN SIGN" which is corresponding to
0x5c in SJIS. So this is a valid mapping.
Hello,
At Fri, 7 Oct 2016 23:58:45 +0300, Heikki Linnakangas wrote
in <9c544547-7214-aebe-9b04-57624aedd...@iki.fi>
> > So, I wonder how the mappings related to SJIS (and/or EUC-JP) are
> > maintained. If no authoritative information is available, the
> > generating script no longer usable. If a
On 09/07/2016 09:50 AM, Kyotaro HORIGUCHI wrote:
Hi,
I found an useless entry in utf8_to_sjis.map
{0xc19c, 0x815f},
which is apparently illegal as UTF-8 which postgresql
deliberately refuses. So it should be removed and the attached
patch does that. 0x815f(SJIS) is also mapped from 0xefbcbc
Hi,
I found an useless entry in utf8_to_sjis.map
> {0xc19c, 0x815f},
which is apparently illegal as UTF-8 which postgresql
deliberately refuses. So it should be removed and the attached
patch does that. 0x815f(SJIS) is also mapped from 0xefbcbc(U+FF3C
FULLWIDTH REVERSE SOLIDUS) and it is a righ
