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

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

I am not so sure if you can get all the unicode well displayed on most
terminals.

If you make a nice art / ascii graphic, you are never sure whether it
will end well displayed depending on the system/terminal, that the
user uses.

example of various chars:
http://www.unicode.org/charts/PDF/U2500.pdf

I think about various possible POSIX and non-POSIX platforms, which
allow compiling with gcc or g++:

      BSD variants:
      FreeBSD 9.0, 8.2, 7.0, 6.4, 4.9
      OpenBSD 4.9
      NetBSD 5.1
      GNU/Linux
      Slackware 13.x
      Debian 6.0, 5.0, 3.1
      Fedora 13-16, CentOS 4-6
      Mandrake 2010
      SuSE 11, 12

      AIX 5.3, 5.1 (cc, gcc)
      BeOS R5
      Cygwin
      HPUX 11.23, 11.11, 11.00, 10.20
      IRIX64
      Mac OS X 10.7
      OS/2 EMX 0.9d (gcc 2.7.2)
      QNX 6.1
      SCO OpenServer 5.0.5e (cc/CC, gcc 2.7.2.3)
      Solaris 10, 9, 8, 7, 6, 2.51
      Tru64 (aka OSF1 and Digital Unix) 4.0d, 5.1 (cc)
      Windows 7, using MinGW

2013/12/3 patrick295767 patrick295767 <patrick295767_AT_gmail.com>:
> 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:45:53 CET

This archive was generated by hypermail 2.3.0 : Tue Dec 03 2013 - 15:48:07 CET