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/
_______________________________________________
Help-gnu-emacs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
