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

2013-12-04 Thread Alexander Huemer
On Tue, Dec 03, 2013 at 12:56:08PM +0100, patrick295767 patrick295767 wrote: If you are developing C/C++ programs in a terminal environment, you may know the problem of the codepages. Sometimes in Putty, SSH,... you may have some problems with characters. What about this Portability of your

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

2013-12-03 Thread patrick295767 patrick295767
Hello, If you are developing C/C++ programs in a terminal environment, you may know the problem of the codepages. Sometimes in Putty, SSH,... you may have some problems with characters. What about this Portability of your terminal applications? - Not great, isn't it? If you would like to have

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

2013-12-03 Thread Troels Henriksen
patrick295767 patrick295767 patrick295...@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

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

2013-12-03 Thread Ismael Luceno
On Tue, 03 Dec 2013 12:59:59 +0100 Troels Henriksen at...@sigkill.dk wrote: patrick295767 patrick295767 patrick295...@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,

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

2013-12-03 Thread patrick295767 patrick295767
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,

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

2013-12-03 Thread patrick295767 patrick295767
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:

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

2013-12-03 Thread Troels Henriksen
patrick295767 patrick295767 patrick295...@gmail.com writes: 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.

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

2013-12-03 Thread Christoph Lohmann
Greetings. On Tue, 03 Dec 2013 16:00:14 +0100 patrick295767 patrick295767 patrick295...@gmail.com wrote: Hello, If you are developing C/C++ programs in a terminal environment, you may know the problem of the codepages. Sometimes in Putty, SSH,... you may have some problems with characters.

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

2013-12-03 Thread Troels Henriksen
patrick295767 patrick295767 patrick295...@gmail.com writes: Let's take an example: Let's take a well-known program: vim compiled for Windows. If you use gvim.exe in Windows, you have a perfect result. No simple problem with characters. However, if you take vim.exe (from the same directory

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

2013-12-03 Thread Christoph Lohmann
Greetings. On Tue, 03 Dec 2013 18:53:04 +0100 Noah Birnel nbir...@gmail.com wrote: On Tue, Dec 03, 2013 at 04:00:14PM +0100, Christoph Lohmann wrote: Windows has to adapt to Open Source and not the other way around. Hahahahaha. You live in a wonderful world. Please read up on software

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

2013-12-03 Thread patrick295767 patrick295767
You are completely right. Windows is important. Another point... what about colors? You never know what the user using your program will get. Linux terminal, Windows Terminal, xterm,... e.g: http://invisible-island.net/xterm/images/contrast.jpg 2013/12/3 Noah Birnel nbir...@gmail.com: On

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

2013-12-03 Thread Troels Henriksen
patrick295767 patrick295767 patrick295...@gmail.com writes: You are completely right. Windows is important. Another point... what about colors? You never know what the user using your program will get. Linux terminal, Windows Terminal, xterm,... e.g:

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

2013-12-03 Thread Dmitrij D. Czarkoff
Troels Henriksen said: You really shouldn't write terminal programs that require precise colours. FWIW as a rule you really shouldn't write terminal programs that use colours. -- Dmitrij D. Czarkoff

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

2013-12-03 Thread Thorsten Glaser
patrick295767 patrick295767 dixit: I think about various possible POSIX and non-POSIX platforms, which allow compiling with gcc or g++: You missed MirBSD, which incidentally is UTF-8 only (with the known issue that you need to run “script -lns” or GNU screen on the text console, but for Unicode

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

2013-12-03 Thread Carlos Torres
Hello Thorsten, On 12/3/13, Thorsten Glaser t...@mirbsd.de wrote: I did suggest banning them, didn’t I? ☺ here we go again... bye, //mirabilos -- „Also irgendwie hast du IMMER recht. Hier zuckelte gerade ein Triebwagen mit der Aufschrift Ostdeutsche Eisenbahn durch Wuppertal. Ich

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

2013-12-03 Thread Thorsten Glaser
Carlos Torres dixit: here we go again... Sure… googlemail user ;) should they ban people that use fortune in their signatures too? You’d be amazed to hear that I have a collection of individual sig files and select one manually when I don’t want to use the default one, which I rotate