On Wed, 1 Dec 2010, Eric Auer wrote:
> Compatible apps would be apps which only display ASCII out
> of themselves and which make no serious assumptions about
> one byte being equal to one character. A good example are
> MORE and TYPE: If you TYPE an UTF8 text with a special CON
> driver which expe
Hi Christian,
>> Should the translation be "accurate" or should it be "useful"?
That depends a lot on which languages we are talking about.
For the DISPLAYING of already existing strings such as file
names on some USB stick made by somebody using Linux, MacOS
or Windows, if your language is "so
Hi Christian,
> Just noticing that this grows quite large. If someone finds this
> unbearable for this list, please speak up to let me know I should cut down
> the off-topic stuff on my public mails!
No problem :-) I would hope that people talk more about the
"big font" approaches - Having eithe
> I think your attitude is not very constructive. We have to keep this
> idea as simple as possible or nobody implements it.
I think some of that is important, even if you only want to implement a
simple translation. Besides, of course it isn't very constructive to
*discuss* an idea. Go use
I think your attitude is not very constructive. We have to keep this idea as
simple as possible or nobody implements it.
I think it is not needed to make tables UNICODE to ASCII.
It is sufficient to make ASCII to UNICODE.
Simple table - on one side 256 bytes - on second side 256 words.
That is al
> UniCode is not the panacea it's purported to be.
No, but you have to give them that it's certainly an improvement.
>> UTF-8 is independent of byte-order. The exact encoding (and byte-order)
>> should always either be implicit (in the interface's or format's
>> definition) or be marked in some w
Christian Masloch wrote:
>
> I think it should be accurate for file systems. Such a "useful"
> translation is a good concept for displaying output (maybe even that of
> the DIR command) but not for actually working with the file system.
> Keyboard input can't map one key to several characters a
> Should the translation be "accurate" or should it be "useful"?
I think it should be accurate for file systems. Such a "useful"
translation is a good concept for displaying output (maybe even that of
the DIR command) but not for actually working with the file system.
Keyboard input can't ma
