all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jonathan Reeve <jonathan@jonreeve.com>
Cc: 57531@debbugs.gnu.org
Subject: bug#57531: 28.1; Character encoding missing for "eo"
Date: Sun, 04 Sep 2022 08:37:21 +0300	[thread overview]
Message-ID: <831qsrn1im.fsf@gnu.org> (raw)
In-Reply-To: <875yi4p6se.fsf@jonreeve.com> (message from Jonathan Reeve on Sat, 03 Sep 2022 20:00:41 +0000)

> Date: Sat, 03 Sep 2022 20:00:41 +0000
> From: Jonathan Reeve <jonathan@jonreeve.com>
> Cc: 57531@debbugs.gnu.org
> 
> > I believe this is due to the fact that the text was saved in UTF-8,
> > and Emacs was trying to decode it as if it were in Latin-3.
> 
> That’s the problem. Emacs should decode UTF-8 as UTF-8, not Latin-3.

It tries, but it isn't always 100% successful.

> > Using the prefer-coding-system customization should fix that.
> 
> The user shouldn’t have to customize an encoding system to have a UTF-8 locale be interpreted as UTF-8. A UTF-8 locale should be encoded as such, without needing to be told otherwise.

Ideally, I agree.  But in practice, we've found that goal unreachable
in some cases.

> > I disagree.  I think your system doesn’t tell Emacs enough to guess
> > correctly.
> 
> It does, though. The locale data is already there, which is why I only have this problem in Emacs, and nowhere else on my whole system. The problem is in this line from `locale-language-names'. Here’s what it says:
> 
> `("eo" . "Esperanto")'
> 
> Here’s what it should say:
> 
> `("eo" "Esperanto" utf-8)'

That's only correct for glibc systems, though, as I already explained.
I found no authoritative place on the Internet which would mandate
that the Esperanto locale should use or prefer UTF-8 as its encoding.
Once again, glibc is just one C library on just one OS.

If you can show me some authoritative source of information about this
locale which says it should use UTF-8, that could be a reason good
enough to make such an incompatible change.  And we need good reasons
for such incompatible changes, because some users out there could have
configurations or applications that depend on previous behavior.

> The system says that it’s a UTF-8 locale.

How does it say so?

> > Please try the solution I proposed, and if it doesn’t work, let’s see
> > what else is needed.  If you keep insisting on defaulting Esperanto to
> > UTF-8, I see now way to make any progress here.
> 
> You’re not proposing a solution, you’re proposing a workaround.

Would you please try it nonetheless?

> There’s no reason at all why Esperanto should be encoded in latin-3. It never has been, as far as I can tell, and it never well be, in latin-3, with the eo locale. If you can find any good reason why it should be in latin-3, I’m all ears, but as far as I can tell, this is a mistake.

No, it isn't a mistake.  Latin-3 was introduced to cover Esperanto
(and some other languages).  That's why the Emacs Esperanto locale
was configured to use it.  It wasn't a random choice.

> Please keep in mind that /I’m trying to help improve emacs,/

Please keep in mind that so am I.  For many years, as a matter of
fact.





  reply	other threads:[~2022-09-04  5:37 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 18:47 bug#57531: 28.1; Character encoding missing for "eo" Jonathan Reeve
2022-09-02  5:52 ` Eli Zaretskii
2022-09-03  1:28   ` Jonathan Reeve
2022-09-03 14:47     ` Eli Zaretskii
2022-09-03 16:54       ` Jonathan Reeve
2022-09-03 17:12         ` Eli Zaretskii
2022-09-03 17:32           ` Andreas Schwab
2022-09-03 17:58             ` Eli Zaretskii
2022-09-03 20:13               ` Andreas Schwab
2022-09-04  5:02                 ` Eli Zaretskii
2022-09-04  6:32                   ` Andreas Schwab
2022-09-04  6:54                     ` Eli Zaretskii
2022-09-04  7:33                       ` Andreas Schwab
2022-09-03 20:00           ` Jonathan Reeve
2022-09-04  5:37             ` Eli Zaretskii [this message]
2022-09-04  7:03               ` Andreas Schwab
2022-09-04  7:20                 ` Eli Zaretskii
2022-09-04  7:34                   ` Andreas Schwab
2022-09-04  7:46                     ` Eli Zaretskii
2022-09-04  8:28                       ` Eli Zaretskii
2022-10-04 11:44                         ` Lars Ingebrigtsen
2022-10-04 12:39                           ` Eli Zaretskii
2022-10-04 13:13                             ` Lars Ingebrigtsen
2022-10-06 10:51                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-06 11:28                               ` Gregory Heytings
2022-10-06 12:13                                 ` Lars Ingebrigtsen
2022-10-06 14:20                                 ` Eli Zaretskii
2022-10-06 15:15                                   ` Gregory Heytings
2022-10-06 16:05                                     ` Eli Zaretskii
2022-10-04 13:16                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-05  0:00                     ` Gregory Heytings
2022-09-05  8:16                       ` Gregory Heytings
2022-09-05  8:58                         ` Lars Ingebrigtsen
2022-09-05  9:10                           ` Gregory Heytings
2022-09-05  9:39                             ` Andreas Schwab
2022-09-05 11:46                               ` Gregory Heytings
2022-09-05  9:24                           ` Andreas Schwab
2022-09-05  9:30                             ` Gregory Heytings
2022-09-05 11:44                           ` Eli Zaretskii
2022-09-05 14:15                             ` Lars Ingebrigtsen
2022-09-05 11:40                         ` Eli Zaretskii
2022-09-05 12:00                           ` Gregory Heytings
2022-09-05 12:24                             ` Eli Zaretskii
2022-09-05 12:38                               ` Gregory Heytings
2022-09-05 13:04                                 ` Eli Zaretskii
2022-09-05 13:26                                   ` Gregory Heytings
2022-09-05 16:56                               ` Andreas Schwab
2022-09-05 17:50                                 ` Jonathan Reeve
2022-09-05 18:20                                   ` Gregory Heytings
2022-09-05 22:41                                     ` Jonathan Reeve
2022-09-05 23:14                                       ` Gregory Heytings
     [not found]                                       ` <57ffb073-c4ea-da56-18c0-661b9d8ab929@heytings.org>
2022-09-05 23:21                                         ` Gregory Heytings
2022-10-04 13:09                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 13:05                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-04 23:35               ` Gregory Heytings
2022-09-05 11:29                 ` Eli Zaretskii
2022-09-05 12:07                   ` Gregory Heytings
2022-09-05 12:25                     ` Eli Zaretskii
2022-09-05 12:59                       ` Gregory Heytings
2022-09-05 13:11                         ` Eli Zaretskii
2022-09-05 13:33                           ` Gregory Heytings
2022-09-04  8:39 ` Andreas Schwab
2022-09-04  8:48   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=831qsrn1im.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57531@debbugs.gnu.org \
    --cc=jonathan@jonreeve.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.