Re: strange behaviour of utf-8 files

[Georg Bauhaus <rm.dash-bauhaus@futureapps.de>]

On 16.11.13 16:55, Dmitry A. Kazakov wrote:
> As I said in order to avoid troubles, don't use anything but ASCII.

ASCII-ism is the soil in which dangerous bugs keep many things
from working.(*)

With an attitude of denial towards encoding basics, would anyone
ever approach *numbers* in the same way?  I doubt it.

The best medication against chronic character FUD is to

(a) see how some unambiguous encoding does work everywhere
     (e.g. the universally supported UTF-16)  (**),
(b) understand that single units of text and single octets
     are not in general isomorphic; this leads to bugs just
     as harmless or harmful as erroneous execution in the
     presence of not 'Valid,
(c) understand that maybe wasting 9 bits of 16 bit characters
     (or a few bits per octet sequence in UTF-8)
     is not worth mentioning these days, considering source text.

Part (b) will not come to be as long as most programmers are
fine thinking that text is always 7bit characters in real life.
If, instead, programmers start learning about further bits---
that Character is a type, not an encoding---integrating software
will start working better.

__
(*) A big one of these ASCII bugs yields Google's infrastructure
     stuck with Python 2.7.
(**) I understand that even the US Navy has officially started
     using more characters than ASCII. So, can I maintains hopes
     that GNAT will one day read source files that use UTF-NN, which
     GNAT does support?