all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jürgen Hartmann" <juergen_hartmann_@hotmail.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: Automatic recognition of some specific coding systems
Date: Tue, 24 Feb 2015 23:30:49 +0100	[thread overview]
Message-ID: <DUB124-W90938708558C1FBE7E95BA8160@phx.gbl> (raw)
In-Reply-To: <83fv9v6u5o.fsf@gnu.org>

Thank you, Eli Zaretskii, for your speedy answer:

>> Is this conclusion correct?
> 
> No, I don't think so.  There's no direct relation between categories
> and recognition of encoding.

I am very glad to hear that.

> If you have specific problems, i.e. if Emacs doesn't recognize the
> encoding of some file(s), please post the details.  (I'd suggest to
> try in "emacs -Q" first, because some problems might be caused by your
> customizations that need to be removed or adapted to the new version.)
> Then people here could review the problems and advise you about
> possible solutions, or ask you to file a bug report.
> 
> But in general, there shouldn't be any regressions in recognizing
> encodings.

OK. I will try to give a specific example - it is rather artificial
but representative:

Consider an utf-8-unix encoded text file, meaningfully named
utf-8-unix, that just contains the seven German special characters

   äöüßÄÖÜ   ("a"o"u"s"A"O"U)

in one single line followed by a newline character. Now we make two
copies of this file and recode them to the other coding systems of
interest:

   cp utf-8-unix latin-9-unix
   recode ..l9 latin-9-unix

   cp utf-8-unix cp850-dos
   recode ..pc cp850-dos

Visiting all tree files in an Emacs session that was freshly started
by means of

   emacs -Q

- thank you for that important hint - yields a perfect recognition of
the respective coding in the case of

   utf-8-unix
   latin-9-unix   (recognized as latin-1-unix, equivalent here)

but the recognition fails tor the cp850-dos encoded file, as it is
recognized as

   raw-text-dos

encoded and its contents is displayed as

   \204\224\201\341\216\231\232

Looking on the contents of the variable coding-category-list, it has
the form

   (coding-category-utf-8 coding-category-charset ...
    coding-category-raw-text ...)

where the values of the variables coding-category-utf-8 and
coding-category-charset are utf-8 and iso-latin-1 respectively.

If I start again with a new Emacs session (emacs -Q), but this time
performing the commands

   prefer-coding-system cp850
   prefer-coding-system utf-8

prior to visiting the files, the codings of

   utf-8-unix
   cp850-dos

are recognized correctly, while the file latin-9-unix is recognized as
cp850-unix encoded and its contents is displayed as some cryptic symbols.

The coding-category-list and the variable coding-category-utf-8 have
the same values as before, but the variable coding-category-charset
contains cp850 this time.

So my problem is to find a configuration of Emacs 24.4 that yields a
correct automatic recognition of all tree coding systems

   utf-8-unix
   latin-9-unix or
   cp850-dos

when the files of the example above are visited. One has to keep in
mind that this was perfectly possible with Emacs 22.3, as I just
verified again.

Sorry for the rather long post, but I hope that I could state my
problem more precisely.

Juergen

 		 	   		  


  reply	other threads:[~2015-02-24 22:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 15:31 Automatic recognition of some specific coding systems Jürgen Hartmann
2015-02-24 18:28 ` Eli Zaretskii
2015-02-24 22:30   ` Jürgen Hartmann [this message]
2015-02-25 16:19     ` Eli Zaretskii
2015-02-25 17:53       ` Jürgen Hartmann
2015-02-25 20:29         ` Eli Zaretskii
2015-02-25 23:23           ` Jürgen Hartmann
2015-02-26 16:36             ` Eli Zaretskii
2015-02-26 22:34               ` Jürgen Hartmann
2015-02-28 16:55                 ` Eli Zaretskii
2015-03-03 22:58                   ` Jürgen Hartmann
2015-02-27  1:50 ` Yuri Khan
2015-02-27 12:12   ` Jürgen Hartmann
2015-02-27 12:25     ` Jürgen Hartmann

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=DUB124-W90938708558C1FBE7E95BA8160@phx.gbl \
    --to=juergen_hartmann_@hotmail.com \
    --cc=help-gnu-emacs@gnu.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 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.