From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: getting out of raw-text encoding
Date: Sat, 10 May 2003 22:06:21 +0200 [thread overview]
Message-ID: <84of2a8t36.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: mailman.5938.1052592339.21513.help-gnu-emacs@gnu.org
"Eli Zaretskii" <eliz@elta.co.il> writes:
>> From: kai.grossjohann@gmx.net (=?iso-8859-1?q?Kai_Gro=DFjohann?=)
>> Newsgroups: gnu.emacs.help
>> Date: Sat, 10 May 2003 19:06:36 +0200
>>
>> (codepage-setup "1252") might have done something useful, but it seems
>> that my Emacs knows 1250 and 1251 but not 1252. Why?
>
> Because codepage 1252's target charset is latin-iso8859-1, and where
> cp1252 and latin-1 intersect, they are identical, while the few
> non-Latin-1 characters there cannot be expressed as latin-iso8859-1.
>
> I'd like to remind you that until now, cpNNN encodings could only
> express characters of a single charset. This makes support of
> Microsoft's abominations impossible. (The CVS version of Emacs fixes
> that in code-pages.el.)
Hm?
It would have been possible to introduce another charset for cp1252.
Then in addition to Latin-1 ä and Latin-2 ä and Latin-9 ä we'd also
have cp1252 ä. That would be in the spirit of current Mule, wouldn't
it?
And then unify-8859-on-{de,en}coding-mode could unify them...
--
This line is not blank.
next prev parent reply other threads:[~2003-05-10 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 15:21 getting out of raw-text encoding David Madore
2003-05-10 17:06 ` Kai Großjohann
2003-05-10 18:40 ` Eli Zaretskii
[not found] ` <mailman.5938.1052592339.21513.help-gnu-emacs@gnu.org>
2003-05-10 20:06 ` Kai Großjohann [this message]
2003-05-10 21:11 ` Eli Zaretskii
[not found] ` <mailman.5950.1052601438.21513.help-gnu-emacs@gnu.org>
2003-05-12 15:53 ` Kai Großjohann
2003-05-10 17:52 ` Eli Zaretskii
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=84of2a8t36.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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.