unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: schwab@linux-m68k.org, ezander@valkyrie.sc.cs.tu-bs.de,
	4712@emacsbugs.donarmstrong.com
Subject: bug#4712: File encoding
Date: Thu, 15 Oct 2009 03:20:11 -0400	[thread overview]
Message-ID: <E1MyKd9-0001mg-Tr@fencepost.gnu.org> (raw)
In-Reply-To: <jwvoco94abh.fsf-monnier+emacsbugreports@gnu.org> (message from Stefan Monnier on Wed, 14 Oct 2009 23:16:32 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 4712@emacsbugs.donarmstrong.com,  schwab@linux-m68k.org,  ezander@valkyrie.sc.cs.tu-bs.de
> Date: Wed, 14 Oct 2009 23:16:32 -0400
> 
> >> > Maybe so, but this part of the OP's report:
> >> 
> >> >   value of $LANG: en_AU.UTF-8
> >> >   locale-coding-system: utf-8
> >> 
> >> > indicates that UTF-8 is the "native" encoding on the OP's machine, and
> >> > there is an overwhelming user demand for silently and transparently
> >> > switch to such a native encoding when we need to select an encoding.
> >> 
> >> The `coding' cookie trumps any such setting, since when we read the
> >> file, we will blindly obey the cookie without paying any attention to
> >> the user's locale.
> 
> > Right, and we did:
> 
> >   Selected encoding mule-utf-8-unix disagrees with iso-8859-1-unix
> >   specified by file contents.
> 
> The fact that we even consider utf-8 is the bug, it means that the
> coding cookie didn't actually "trump" the locale setting.

Sigh...  In case it wasn't clear, I didn't mean to say this is not a
problem.  I tried to explain why it happens, so that someone who cares
could find the proper fix faster and without disrupting other
important features while at that.  But if no one wants to hear, I
guess I'll crawl back under my rock...





  reply	other threads:[~2009-10-15  7:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13  9:12 bug#4712: File encoding Elmar Zander
2009-10-14  9:07 ` Andreas Schwab
2009-10-14 13:27   ` Stefan Monnier
2009-10-14 14:04     ` Eli Zaretskii
2009-10-14 14:33       ` Andreas Schwab
2009-10-14 18:11         ` Eli Zaretskii
2009-10-14 15:19       ` Stefan Monnier
2009-10-14 18:15         ` Eli Zaretskii
2009-10-15  3:16           ` Stefan Monnier
2009-10-15  7:20             ` Eli Zaretskii [this message]
2009-10-15  9:38             ` Andreas Schwab
2009-10-17  4:01               ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=E1MyKd9-0001mg-Tr@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=4712@emacsbugs.donarmstrong.com \
    --cc=ezander@valkyrie.sc.cs.tu-bs.de \
    --cc=monnier@iro.umontreal.ca \
    --cc=schwab@linux-m68k.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).