[PATCH 2/6] Add unicode support for commonly used characters like copyright.

Chris Johns chrisj at rtems.org
Sun Feb 24 21:38:18 UTC 2019

On 22/2/19 5:48 pm, Sebastian Huber wrote:
> On 21/02/2019 22:10, Chris Johns wrote:
>> On 21/2/19 5:35 pm, Sebastian Huber wrote:
>>> On 21/02/2019 07:24, Chris Johns wrote:
>>>> On 21/2/19 5:07 pm, Sebastian Huber wrote:
>>>>> On 21/02/2019 03:43, chrisj at rtems.org wrote:
>>>>>> From: Chris Johns<chrisj at rtems.org>
>>>>>> - This change makes the copyright character easier to see on editors
>>>>>>      lacking good unicode rendering support, ie terminals.
>>>>> I am not in favour of this change. Unicode support should be standard even for
>>>>> terminals for a couple of years now.
>>>> Can you see it on a standard non-gui terminal that does not have the character
>>>> set? I do not use _any_ GUI tools for editing, debugging etc. Everything is a
>>>> basic terminal run in tmux. Not allowing this type change exposes me to making
>>>> mistakes.
>>> What do you see if you open testsuites/fstests/fsdosfsname01/create_files.cs for
>>> example? I see all characters even in the "less" command line tool.
>> With `less` ..
>>                  "this is a long filename",
>>                  "<C4><91><C3><A2>y l<C3><A0> m<E1><BB><99>t t<C3><AA>n
>> t<E1><BA><AD>p tin d<C3><A0>i",
>> and in emacs ..
>>                  "this is a long filename",
>>                   "??y l? m?t t?n t?p tin d?i",
> Maybe you should use a hex editor and not emacs.

No need I use hexl-mode. ;)

>>>> Note, I am not asking all unicode characters be implemented in way. Just common
>>>> ones we may need to support.
>>> Ok, good.
>> OK to push?
> Ok, but it would be nice if we don't need this for every non-English character.


More information about the devel mailing list