Subject: Re: bug#104: devuan-i18n: Utf8 problems in X vs console for file names and others

From: PICCORO McKAY Lenz <[email-masked]>
Date: Mon, 6 Feb 2023 16:55:18 -0400

in the current devuan i dont know were such key raised. the `locale
charmap` command outputs
the same that is another name for USAS X3.4-1968, a revision of ASCII that
is distinguished first revision
to allow a linefeed (LF) to occur on its own (i.e. not preceded by or
followed by a carriage return (CR)).

 iguess is something related to windosers, my current env have mixed
russian and english maybe
due that i have such locale charmap due that revision introduced the common
name of (US-)ASCII.

This is basically ASCII as we think of it, although there were two minor
revisions that followed it.
also desktop in devuan when i set to russian with spanish as default just
dont follow the encoding

On Fri, Feb 3, 2023 at 11:25 AM Mark Hindley <[email-masked]> wrote:

>
> On Tue, Jun 06, 2017 at 11:57:22AM -0400, PICCORO McKAY Lenz wrote:
> > Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=ANSI_X3.4-1968)
>
> You appear to have a mismatched locale setting. Where is the ANSI_X3.4-1968
> charmap coming from? What is the output of `locale' and `locale charmap'?
>
> I have no problems with this either in the console or GUI:
>
> /tmp% touch últimos
> /tmp% ls -l últimos
> -rw-r--r-- 1 mark mark 0 Feb  3 15:12 últimos
> /tmp% locale
> LANG=en_GB.UTF-8
> LANGUAGE=en_GB:en
> LC_CTYPE="en_GB.UTF-8"
> LC_NUMERIC="en_GB.UTF-8"
> LC_TIME="en_GB.UTF-8"
> LC_COLLATE="en_GB.UTF-8"
> LC_MONETARY="en_GB.UTF-8"
> LC_MESSAGES="en_GB.UTF-8"
> LC_PAPER="en_GB.UTF-8"
> LC_NAME="en_GB.UTF-8"
> LC_ADDRESS="en_GB.UTF-8"
> LC_TELEPHONE="en_GB.UTF-8"
> LC_MEASUREMENT="en_GB.UTF-8"
> LC_IDENTIFICATION="en_GB.UTF-8"
> LC_ALL=
> /tmp% locale charmap
> UTF-8
>
> Mark
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

-- 
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com