From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: mew-int@mew.org, kazu@iijlab.net, emacs-devel@gnu.org
Subject: Re: [mew-int 01596] Re: windows 1252
Date: Thu, 13 Nov 2003 21:49:31 +0200 [thread overview]
Message-ID: <9003-Thu13Nov2003214931+0200-eliz@elta.co.il> (raw)
In-Reply-To: <200311130101.KAA04554@etlken.m17n.org> (message from Kenichi Handa on Thu, 13 Nov 2003 10:01:57 +0900 (JST))
> Date: Thu, 13 Nov 2003 10:01:57 +0900 (JST)
> From: Kenichi Handa <handa@m17n.org>
>
> (defvar ctext-non-standard-designations-alist
> '(("$(0" . (big5 "big5-0" 2))
> ("$(1" . (big5 "big5-0" 2))
> ;; The following are actually standard; generating extended
> ;; segments for them is wrong and screws e.g. Latin-9 users.
> ;; 8859-{10,13,16} aren't Emacs charsets anyhow. -- fx
> ;; ("-V" . (t "iso8859-10" 1))
> ;; ("-Y" . (t "iso8859-13" 1))
> ;; ("-_" . (t "iso8859-14" 1))
> ;; ("-b" . (t "iso8859-15" 1))
> ;; ("-f" . (t "iso8859-16" 1))
>
> I think Dave is correct because CTEXT spec has this
> paragraph.
>
> Extended segments are not to be used for any character set
> encoding that can be constructed from a GL/GR pair of
> approved standard encodings. For example, it is incorrect to
> use an extended segment for any of the ISO 8859 family of
> encodings.
For the record, when I worked on this code, I added the ISO 8859
charsets mentioned above because the then official version of the
CTEXT spec did not include them in the list of approved standard
encodings. So, as far as that CTEXT spec was concerned, these
charsets were not members of the ISO 8859 family.
next prev parent reply other threads:[~2003-11-13 19:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031029.160819.120233945.kazu@iijlab.net>
[not found] ` <20031029.082403.193886873.wl@gnu.org>
[not found] ` <20031030.175736.39971315.kazu@iijlab.net>
2003-10-30 14:41 ` [mew-int 01581] Re: windows 1252 Werner LEMBERG
2003-10-31 11:04 ` [mew-int 01579] " Kenichi Handa
2003-10-31 12:39 ` [mew-int 01583] " Kazu Yamamoto
2003-11-01 15:36 ` [mew-int 01584] " Eli Zaretskii
2003-11-02 6:41 ` [mew-int 01582] " Stephen J. Turnbull
2003-11-04 2:13 ` [mew-int 01586] " Kazu Yamamoto
2003-11-04 5:55 ` [mew-int 01585] " Eli Zaretskii
2003-11-04 6:13 ` [mew-int 01587] " Kazu Yamamoto
2003-11-04 6:23 ` [mew-int 01589] " Stephen J. Turnbull
2003-11-04 15:13 ` [mew-int 01590] " Stefan Monnier
2003-11-04 15:55 ` [mew-int 01591] " Kazu Yamamoto
2003-11-04 17:04 ` [mew-int 01590] " Stefan Monnier
2003-11-04 18:45 ` Stephen J. Turnbull
2003-11-05 1:59 ` [mew-int 01594] " Kazu Yamamoto
2003-11-05 5:00 ` [mew-int 01593] " Stephen J. Turnbull
2003-11-07 7:30 ` Kenichi Handa
2003-11-07 7:28 ` [mew-int 01597] " Kenichi Handa
2003-11-07 8:21 ` [mew-int 01599] " Kazu Yamamoto
2003-11-07 7:13 ` [mew-int 01596] " Kenichi Handa
2003-11-10 7:11 ` [mew-int 01607] " Kazu Yamamoto
2003-11-10 7:42 ` [mew-int 01608] " Kenichi Handa
2003-11-12 16:36 ` [mew-int 01596] " Stephen J. Turnbull
2003-11-13 1:01 ` Kenichi Handa
2003-11-13 16:32 ` Stephen J. Turnbull
2003-11-14 2:57 ` Kenichi Handa
2003-11-14 11:20 ` Stephen J. Turnbull
2003-11-14 12:02 ` Kenichi Handa
2003-11-13 19:49 ` Eli Zaretskii [this message]
2003-11-14 3:39 ` [mew-int 01621] " Kenichi Handa
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=9003-Thu13Nov2003214931+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=kazu@iijlab.net \
--cc=mew-int@mew.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).