Re:The History and rationale of the Python 3 Unicode model f...
by lidavidm on Wednesday December 14, 2022 @06:09PM
(#33992146)
I'm curious, what does 'broken' mean? Is this about the CJK merger, or something else?
[ Parent
| on HN ]
Re:The History and rationale of the Python 3 Unicode model f...
by lmm on Wednesday December 14, 2022 @06:24PM
(#33992334)
Yes, CJK unification. Characters will be rendered differently from how they should be (e.g. with missing or extra strokes).
Re:The History and rationale of the Python 3 Unicode model f...
by hnfong on Wednesday December 14, 2022 @10:37PM
(#33994859)
Why is that a filesystem issue or a "utf8only=on" issue? If the renderer doesn't have sufficient context, it will pick one glyph to render anyway, and it could be "wrong".
PS: unless your take is to say that we should just assume everything is ascii and don't ever render codepoints > 127?
Re:The History and rationale of the Python 3 Unicode model f...
by lmm on Wednesday December 14, 2022 @10:54PM
(#33995009)
If the filesystem can't allow parts to be in different encodings then it can't ever possibly work right. With current filesystems at least I can do "ls ~/chinese-files; LANG=ja_JP.SJIS ls ~/japanese-files". Which is not a great way of working, but it's better than a utf8only filesystem where it's physically impossible to make even that much work.