[fpc-devel] Unicode support (yet again)
Hans-Peter Diettrich
DrDiettrich1 at aol.com
Wed Sep 14 19:17:16 CEST 2011
Graeme Geldenhuys schrieb:
> As for the text-to-braille functionality, that is outside the scope of
> the FPC and RTL. But common sense should prevail, use RTL string
> functions to implement your conversion - don't assume 1 byte = 1
> character. A unicode aware string iterator could be implemented to help
> you step through the characters one at a time. Such a string iterator
> could even become part of the RTL as it will probably be used often for
> many parsers.
How many users will have to deal with chars outside the Unicode BMP?
IMO UTF-16 can make 99% of the (current) users happy with simple string
handling, while the rest would prefer UTF-32 instead of UTF-8, because
outside the BMP UTF-8 is a waste of space, and lacks indexed char access
in any case.
DoDi
More information about the fpc-devel
mailing list