Greetings.
On Tue, 03 Dec 2013 16:00:14 +0100 patrick295767 patrick295767 <patrick295767_AT_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.
I had that problem 15 years ago. Then I forced everyone to use UTF‐8.
Now I am living in a world without that problem of the past.
> What about this "Portability" of your terminal applications? - Not
> great, isn't it?
You are coming from 15 years ago?
> If you would like to have your code portable and also looking the same
> on each operating system, it will not be so easy.
Of course it is in 2013: Use UTF‐8.
> For instance, Latin,... codes are necessary depending on the country.
> One which is cool is the CP437. I like the CP437 on Linux for xterm
> for nice terminal images, but the problem is that users have not
> necessarily all installed. CP437 remains also portable with windows
> PDcurses dll (I mean the pdc34dll.zip one, without 'w').
> http://dmr.ath.cx/misc/cp437/
People still using Windows in 2013 deserve their misery. Windows has to
adapt to Open Source and not the other way around. So stop using Win‐
dows.
> Would you know a technique to have a way that your application looks
> the same on whatever system (Linux, Mac, OS/2, Windows,..)?
For Linux use st and UTF‐8 and for Windows Putty and UTF‐8. On Android
you have a Terminal too.
Applications do not need to look all the same. That’s a farce. They have
to be usable everywhere.
Sincerely,
Christoph Lohmann
Received on Tue Dec 03 2013 - 16:00:14 CET