GNU bug report logs - #57531
28.1; Character encoding missing for "eo"

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gregory Heytings <gregory <at> heytings.org>
Cc: jonathan <at> jonreeve.com, larsi <at> gnus.org, schwab <at> linux-m68k.org, 57531 <at> debbugs.gnu.org
Subject: bug#57531: 28.1; Character encoding missing for "eo"
Date: Thu, 06 Oct 2022 19:05:57 +0300

> Date: Thu, 06 Oct 2022 15:15:51 +0000
> From: Gregory Heytings <gregory <at> heytings.org>
> cc: jonathan <at> jonreeve.com, larsi <at> gnus.org, schwab <at> linux-m68k.org, 
>     57531 <at> debbugs.gnu.org
> 
> 
> >> To avoid such bugs, the most reasonable thing to do for users is to 
> >> always specify the encoding.
> >
> > Should we perhaps have an entry in PROBLEMS with that information?
> >
> 
> Would it not be better if Emacs checked the LANG environment variable on 
> startup and warned the user when LANG does not specify an encoding?  Like 
> this:

We could do that, but:

 . issuing a warning doesn't solve the problem
 . experience shows that warnings shown at startup time frequently go
   unnoticed, since they might "drown in the sea" of the many messages
   shown by startup (for example, I use desktop, which emits gobs of
   messages when it restores a session)

So I'm not objected to having a warning, but an entry in PROBLEMS
would still be good.

Also:

> +                       (format "%s%s%s"
> +                               "The LANG environment variable, set to `"
> +                               (getenv "LANG")
> +                               "', does not specify an encoding.")

I believe the accepted terminology for that is "codeset".

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.