unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Automatic recognition of some specific coding systems
Date: Tue, 24 Feb 2015 20:28:35 +0200	[thread overview]
Message-ID: <83fv9v6u5o.fsf@gnu.org> (raw)
In-Reply-To: <DUB124-W49AED29A1D7C3F12F34889A8160@phx.gbl>

> From: Jürgen Hartmann <juergen_hartmann_@hotmail.com>
> Date: Tue, 24 Feb 2015 16:31:46 +0100
> 
> Most of the text files that I have to work with are encoded with one
> of the coding systems
> 
>    utf-8-unix
>    latin-9-unix
>    cp850-dos
> 
> Therefore, it was very convenient for me that the version 22.3 of
> Emacs was (after some minor configuration) perfectly able to
> automatically recognize these coding systems from the contents of the
> respective files. As I understand, this was possible because in that
> old Emacs version these tree systems were associated with three
> different coding categories, i.e.
> 
>    coding-category-utf-8
>    coding-category-iso-8-1   (meanwhile depreciated)
>    coding-category-ccl
> 
> respectively.
> 
> Now switching to Emacs 24.4, I found that two of these coding systems,
> 
>    latin-9-unix
>    cp850-dos
> 
> were bunched together into the category
> 
>    coding-category-charset
> 
> presumably with the consequence that I have to choose which one of
> these two systems will not be automatically recognized any more.
> 
> Is this conclusion correct?

No, I don't think so.  There's no direct relation between categories
and recognition of encoding.

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.




  reply	other threads:[~2015-02-24 18:28 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 [this message]
2015-02-24 22:30   ` Jürgen Hartmann
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

  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=83fv9v6u5o.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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.
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).