From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: coding system
Date: Sun, 27 Mar 2005 17:54:50 +0200 [thread overview]
Message-ID: <v9eke1krsl.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: mailman.321.1111924417.28103.help-gnu-emacs@gnu.org
On Sun, Mar 27 2005, Eli Zaretskii wrote:
> That is precisely so: Emacs 21.x treats Latin-N character sets as
> disjoint, so they are represented by different codes internally.
>
> The CVS version introduces features (unification on en- and decoding)
> that make this distinction less visible, and work is under way on a
> Unicode-based Emacs where the distinction will go away entirely.
In case you refer to `unify-8859-on-{en,de}coding-mode', those are
already included in Emacs 21.3 and 21.4 (but not in 21.1 and 21.2):
,----[ NEWS ]
| ** Translation tables are available between equivalent characters in
| different Emacs charsets -- for instance `e with acute' coming from the
| Latin-1 and Latin-2 charsets. User options `unify-8859-on-encoding-mode'
| and `unify-8859-on-decoding-mode' respectively turn on translation
| between ISO 8859 character sets (`unification') on encoding
| (e.g. writing a file) and decoding (e.g. reading a file). Note that
| `unify-8859-on-encoding-mode' is useful and safe, but
| `unify-8859-on-decoding-mode' can cause text to change when you read
| it and write it out again without edits, so it is not generally advisable.
| By default `unify-8859-on-encoding-mode' is turned on.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-03-27 15:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 12:47 coding system Olive
2005-03-22 13:57 ` Joe Corneli
[not found] ` <mailman.4714.1111501237.32256.help-gnu-emacs@gnu.org>
2005-03-22 14:32 ` Olive
2005-03-23 0:43 ` Miles Bader
2005-03-22 19:08 ` Peter Dyballa
2005-03-26 23:46 ` Stefan Monnier
2005-03-27 6:56 ` B.T. Raven
2005-03-27 10:50 ` Eli Zaretskii
[not found] ` <mailman.321.1111924417.28103.help-gnu-emacs@gnu.org>
2005-03-27 15:54 ` Reiner Steib [this message]
2005-03-27 20:03 ` B.T. Raven
2005-03-29 14:54 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2003-05-26 9:58 Stein A. Stromme
2003-05-26 11:05 ` lawrence mitchell
2003-05-26 11:52 ` Stein A. Stromme
2003-05-26 11:58 ` Stein A. Stromme
2003-05-26 13:47 ` Oliver Scholz
2003-05-26 13:55 ` Kai Großjohann
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=v9eke1krsl.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+from-uce@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).