Re: 8859 unification and Emacs' ChangeLog files

[kai.grossjohann@gmx.net (Kai Großjohann)]

Jason Rumney <jasonr@gnu.org> writes:

> kai.grossjohann@gmx.net (Kai Großjohann) writes:
>
>> But if all Emacs developers enable unify-8859-on-decoding-mode, then
>> this is not a problem anymore.
>
> It is still a problem, because some users will end up saving all
> Latin characters unified to Latin-1 while others will save all
> unified to Latin-2 etc. So there will be a lot of unnecessary changed
> lines in each checkin.

Oh, I didn't know that the preferred encoding is influenced by the
language environment.  Hm.

>>  Or the ChangeLog files could be stored as UTF-8.
>
> This could certainly work, if we think UTF-8 support in Emacs now is
> good enough to handle it reliably.

OK.

>> Of course, there might be other files where iso-8859 characters might
>> be present in different encodings.  Is it right to say that these
>> files must be encoded in iso-2022 or in emacs-mule, because no other
>> encodings distinguish between Latin-1 ä and Latin-2 ä, say?
>
> Yes, many of the files in leim, lisp/international and lisp/language
> need to make the distinction between different Latin charsets.

Really?  Why?  If *all* of Emacs treats all `ä's as the same, why do
these files then need to make the distinction?

But I guess that even with unify-8859-on-decoding-mode, maybe Emacs
does not treat all `ä's as the same.  Hm.
-- 
A preposition is not a good thing to end a sentence with.