From: robin_listas@es.invalid   
      
   On 2023-07-16 14:10, bad sector wrote:   
   > On 7/16/23 07:30, Carlos E.R. wrote:   
   >> On 2023-07-16 05:00, bad sector wrote:   
   >>>   
   >>> I was using such characters to name guitar chord   
   >>> diagrams but since some upgrade or config change I   
   >>> can no longer save files with these in their name.   
   >>   
   >> Using what software?   
   >   
   > Gimp, and it's in Gimp that I get the first hint like:   
   >   
   > "Execution error for procedure   
   > 'gimp-image-set-filename':   
   > Invalid byte sequence in conversion input."   
      
   I just created a file named "¡ ×  ⁋  º ¦.xcf" in gimp, on Leap 15.5.   
      
   >   
   > Another possibly UNRELATED errrr (don't remember   
   > the conditiion but not in Suse) message is:   
   >   
   > "System locale charset is ANSI_X3.4-1968   
   > Your system's locale charset (i.e. the charset   
   > used to encode filenames) is set to ANSI_X3.4-1968.   
   > It is highly unlikely that this has been done   
   > intentionally. Most likely the locale is not   
   > set at all. An invalid setting will result in   
   > problems when creating data projects.   
   > Solution: To properly set the locale charset   
   > make sure the LC_* environment variables are set.   
   > Normally the distribution setup tools take care   
   > of this."   
   >   
   >   
   >   
   >>> Existing files still display OK in dolphin but no   
   >>> new ones can be saved. Where did I go wrong (this   
   >>> worked before and I have tons of such files, still   
   >>> works in Artix).   
   >>   
   >>   
   >> And what openSUSE release are you using?   
   >   
   > Only Leap-15.5 & TW seem to be affected   
   >   
   > The "^" up-arrow, circumflex or caret is not problemantic.   
   > The BAD characters are  ¡ ×  ⁋  º ¦   
   >   
   >   
   > At first I thought it might be a "locale" issue but a   
   > check of my distros coughed up the following   
   >   
   > Artix           no filename issue  charmap="ANSI_X3.4-1968"   
   > Devuan          no filename issue  charmap="UTF-8"   
   > Slackware       no filename issue  charmap="UTF-8"   
   > Suse-Leap-15.5  BAD                charmap="UTF-8"   
   > Suse TW         BAD                charmap="UTF-8"   
   > Ubuntu-Studio   no filename issue  charmap="UTF-8"   
   > AvLinux         no filename issue  charmap="ANSI_X3.4-1968"   
   >   
   > So it don't seem to be a charmap issue.   
   >   
   > BTW while kicking this around, in all cases except   
   > Devuan & Slackware, I noticed one or more of the   
   > following error messages in response to the   
   > "locale -k LC_CTYPE" comand:   
   >   
   > locale: Cannot set LC_CTYPE to default locale:   
   > No such file or directory   
      
      
           -k, --keyword-name   
      
                  For  each  keyword  whose  value is being displayed,   
   include also the name of that keyword, so that the output has the   
                  format:   
      
                      keyword="value"   
      
      
   >   
   > locale: Cannot set LC_MESSAGES to default locale:   
   > No such file or directory   
   >   
   > locale: Cannot set LC_ALL to default locale:   
   > No such file or directory   
   >   
   > Exactly WHAT does not exist?   
      
   Your locale.   
      
   In a terminal as that user, just do "locale" and paste that here.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)