Re: [dev] Bringing together OS'es terminals and their codepages

From: patrick295767 patrick295767 <patrick295767_AT_gmail.com>
Date: Tue, 3 Dec 2013 15:09:17 +0100

The UTF-8 is sure the one to adopt. Luckily it exists ;)

"Unicode also has all the weird line-drawing characters you could ever
want, if you find them important."
Indeed. You have a good compatibility, however a limited number of
"weid" characters.

However, if you would like to show nice effects, you may use extended
one: CP437, for instance, and the windows one is a "standard".
This is likely not installed or you may have some "porting" problems.


2013/12/3 Ismael Luceno <ismael.luceno_AT_gmail.com>:
> On Tue, 03 Dec 2013 12:59:59 +0100
> Troels Henriksen <athas_AT_sigkill.dk> wrote:
>> patrick295767 patrick295767 <patrick295767_AT_gmail.com> writes:
>>
>> > Would you know a technique to have a way that your application looks
>> > the same on whatever system (Linux, Mac, OS/2, Windows,..)?
>>
>> Use UTF-8. Seriously, different character sets are such an incredibly
>> sucky thing that nobody should consider re-introducing them, unless
>> necessary to interact with legacy systems. (Of course, one should
>> consider Windows to be legacy...) Unicode also has all the weird
>> line-drawing characters you could ever want, if you find them
>> important.
>>
>> On which systems are the Latin-set of code pages still necessary?
>>
>
> Have you heard of UTF-8? Try using luit for legacy applications.
>
Received on Tue Dec 03 2013 - 15:09:17 CET