Re: [dev] [st] Stuck in ISO 2022 locking escapes and Evil escape sequences

From: Pickfire <pickfire_AT_riseup.net>
Date: Tue, 1 Sep 2015 14:07:23 +0800

on tue, sep 01, 2015 at 08:52:26am +0300, otto modinos wrote:
>>
>> It's not a locking escape. "ESC ( 0" switches your character
>> set to VT100 Special Graphics (see [0]).
>> Of course, if a given terminal like mosh doesn't have the
>> translation-tables, nothing gets "messed" up.
>
>mosh mentions some "UTF8 terminal mode", which is different
>from "ISO 2022" and doesn't even have G0-3. It's all mentioned
>in the link[1].
>
>[1]: https://www.cl.cam.ac.uk/~mgk25/unicode.html#term

In st.suckless.org:
> Current state:
> See the TODO file for what needs to be implemented or fixed.
> What has been implemented:
> ...
> * utf8

I thought suckless uses UTF-8? Most applications[1] are already using UTF8
now, so does suckless need to use 'ISO 2022' or 'utf8'?

[1]: https://www.cl.cam.ac.uk/~mgk25/unicode.html#apps

-- 
 _____________________________________
< Do what you like, like what you do. >
 -------------------------------------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||
Received on Tue Sep 01 2015 - 08:07:23 CEST

This archive was generated by hypermail 2.3.0 : Tue Sep 01 2015 - 08:12:08 CEST