From: Christoph Päper (email@example.com)
Date: Mon May 23 2011 - 04:44:52 CDT
Martin J. Dürst:
> On 2011/05/19 19:35, Christoph Päper wrote:
>> I believe it would help if input immediately was transformed to and text was saved in NFD, because this would make the need for uniform treatment more obvious.
> It might help in theory, but in practice, NFC is much, much closer to what's out there in the real world (in particular the Web).
My remark, in fact, was less about the real world and data interchange, but more about how technologic constrains can and do pave thought patterns.
> So please use NFD for internal processing if you think that helps you, but please use NFC for all cases where it may be seen by other programs.
You imply that some programs have problems with decomposed characters – exactly my point, they must not have.
>> It would be cool if there was an ASCII-compatible encoding with variable length like UTF-8 that supported only NFD (…) and was optimized for a small storage footprint,
> We don't need any more character encodings.
I phrased that badly. I’m fine with the existing UTFs, I just think it would have been cool for usability if the most prevalent of them, i.e. UTF-8, was an encoding like that, because font and software developers would think differently about characters then. Here and now many still consider precomposed ones the norm and combining diacritics an exotic oddity.
This archive was generated by hypermail 2.1.5 : Mon May 23 2011 - 04:48:30 CDT