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

From: patrick295767 patrick295767 <patrick295767_AT_gmail.com>
Date: Tue, 3 Dec 2013 16:01:01 +0100

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 as gvim.exe) and
use it in the windows console (execute: cmd then type vim), you end up
with strange chars if you are using special accents, and so on.
(with a well configured terminal).

I just would like to point that problems, even on well known programs,
may still today be present (and quite annoying for some users).
Vim has more than 20 years existence, but still, some problems may
still exist with characters, although Unicode/utf-8,.. are there to
make it easier.
(It is a bug).


2013/12/3 Troels Henriksen <athas_AT_sigkill.dk>:
> patrick295767 patrick295767 <patrick295767_AT_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.
>
> No, but it's more likely than any other encoding (apart from plain
> ASCII), and it will only improve, given that almost every platform has
> adopted at least Unicode (and often UTF-8 specifically) as the preferred
> way to deal with text.
>
> I'm not saying UTF-8 is perfect, just that it's the best choice. But
> yeah, stay away from the weirdest characters. For example, '💩', which I
> often find useful when discussing software, is missing in many fonts.
>
> --
> \ Troels
> /\ Henriksen
>
Received on Tue Dec 03 2013 - 16:01:01 CET

This archive was generated by hypermail 2.3.0 : Tue Dec 03 2013 - 16:12:07 CET