From: Kenichi Handa <handa@m17n.org>
Cc: eliz@elta.co.il, jas@extundo.com, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: MML charset tag regression
Date: Thu, 5 Jun 2003 10:16:34 +0900 (JST) [thread overview]
Message-ID: <200306050116.KAA02388@etlken.m17n.org> (raw)
In-Reply-To: <rzqwug1ec3p.fsf@albion.dl.ac.uk> (message from Dave Love on Wed, 04 Jun 2003 23:01:30 +0100)
In article <rzqwug1ec3p.fsf@albion.dl.ac.uk>, Dave Love <d.love@dl.ac.uk> writes:
> Kenichi Handa <handa@m17n.org> writes:
>> But, ctext itself doesn't have to support it, i.e., decode it as the
>> sender's intention.
> But then you might as well ignore extended segments entirely, and I
> assume it must decode it if the name for the segment is registered.
> However, the CTEXT spec says that you must use extended segments
> for private charsets.
>> It's impossible to know about all possible
>> encoding names that will be used in the extended segment.
> Sure. I was holding off changes in this area until I convinced myself
> what is the best way to do the heuristic conversion between external
> charset names and Emacs names. (Sorry, I could have saved you the
> work.) At least you have a chance of interpreting the names, but you
> can't know anything about private charset definitions, even if they
> were allowed. Extended segment names are supposed to be registered
> and follow font encoding names, of course.
I'm sorry but I can't see how, you think, the current ctext
and ctext-with-extensions should be changed. Could you
give me a concrete proposal?
>> Surely it's not. ctext and compound-text-with-extensions
>> encode text differently. But, I don't think
>> compound-text-with-extensions implies an extended version of
>> ctext.
> It does to me, and that was clearly intended.
Perhaps the last words "-with-extentions" was wrong. I
thought it can mean "-using-extended-segment". But, of
course I'm not a native English speaker, thus ...
> It has been changed recently, but in my Emacs it says:
> x -- compound-text-with-extensions (alias: x-ctext-with-extensions ctext-with-extensions)
> Compound text encoding with ICCCM Extended Segment extensions.
This is already changed to;
Compound text encoding with extended segments.
> and the NEWS entry says only some versions of X use extended segments.
Isn't it correct?
> Giving the impression of not following the CTEXT spec can't help with
> trying to persuade someone else to fix their problems, as I hope you
> can do.
> Anyhow the point is that whatever's called compound-text should deal
> with extended segments.
If "deal with" means "correctly decode as senders
intention", it's impossible. If "deal with" just means
"at least don't collapse", now they do.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-06-05 1:16 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 15:28 Simon Josefsson
2003-04-24 15:50 ` Jesper Harder
2003-04-24 21:15 ` Kai Großjohann
2003-04-24 23:04 ` Simon Josefsson
2003-04-25 0:11 ` Jesper Harder
2003-04-25 9:09 ` Manoj Srivastava
2003-04-25 0:03 ` Jesper Harder
2003-04-25 13:38 ` Kai Großjohann
2003-04-24 16:23 ` Kai Großjohann
2003-04-24 23:00 ` Simon Josefsson
2003-04-25 13:24 ` Kai Großjohann
2003-04-25 13:46 ` Simon Josefsson
2003-04-25 14:19 ` Jesper Harder
2003-04-25 15:43 ` Simon Josefsson
2003-04-25 16:31 ` Simon Josefsson
2003-04-25 19:39 ` Jesper Harder
2003-04-26 0:37 ` Simon Josefsson
2003-04-26 10:50 ` James H. Cloos Jr.
2003-04-28 11:58 ` Kenichi Handa
2003-04-28 12:43 ` Stephen J. Turnbull
2003-04-28 12:59 ` Kenichi Handa
2003-04-28 23:05 ` Simon Josefsson
2003-04-29 7:12 ` Stephen J. Turnbull
2003-04-29 5:38 ` Richard Stallman
2003-05-20 12:47 ` Kenichi Handa
2003-05-20 19:42 ` Jan D.
2003-05-21 15:31 ` Richard Stallman
2003-05-21 16:23 ` Jan D.
2003-05-22 0:58 ` Kenichi Handa
2003-05-22 16:25 ` Jan D.
2003-05-23 1:33 ` Kenichi Handa
2003-05-23 7:45 ` David Kastrup
2003-05-23 22:48 ` Richard Stallman
2003-05-23 23:41 ` Jan D.
2003-05-24 0:31 ` Miles Bader
2003-05-25 16:40 ` Dave Love
2003-05-25 18:01 ` Richard Stallman
2003-05-25 16:38 ` Dave Love
2003-05-25 17:25 ` Eli Zaretskii
2003-05-30 8:39 ` Kenichi Handa
2003-05-30 9:23 ` Dave Love
2003-05-30 11:36 ` Kenichi Handa
2003-06-04 22:01 ` Dave Love
2003-06-05 1:16 ` Kenichi Handa [this message]
2003-06-11 12:33 ` Stephen J. Turnbull
2003-06-01 15:40 ` Eli Zaretskii
2003-06-04 22:04 ` Dave Love
2003-06-06 10:55 ` Eli Zaretskii
2003-05-26 13:49 ` Richard Stallman
2003-05-30 9:28 ` Dave Love
2003-05-25 16:32 ` Dave Love
2003-05-25 19:14 ` Jan D.
2003-05-30 9:23 ` Dave Love
2003-05-23 12:05 ` Richard Stallman
2003-05-25 16:31 ` Dave Love
2003-05-30 12:03 ` Kenichi Handa
2003-06-04 21:52 ` Dave Love
2003-06-05 1:36 ` Kenichi Handa
2003-05-25 16:27 ` Dave Love
2003-05-24 0:51 ` Kenichi Handa
2003-05-23 12:03 ` Richard Stallman
2003-05-23 12:21 ` Kenichi Handa
2003-05-24 23:18 ` Richard Stallman
2003-06-13 8:37 ` Kenichi Handa
2003-06-15 15:59 ` Richard Stallman
2003-06-17 11:06 ` Kenichi Handa
2003-04-25 16:43 ` Michael Teichgräber
2003-04-25 17:14 ` Simon Josefsson
2003-04-25 18:14 ` Jesper Harder
2003-04-25 23:40 ` Michael Teichgräber
2003-04-26 0:32 ` Simon Josefsson
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=200306050116.KAA02388@etlken.m17n.org \
--to=handa@m17n.org \
--cc=ding@gnus.org \
--cc=eliz@elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=jas@extundo.com \
/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 NNTP newsgroup(s).