From: Kenichi Handa <handa@m17n.org>
Cc: emacs-unicode@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs-unicode: different encoding of iso-2022-7bit?
Date: Wed, 13 Oct 2004 11:07:20 +0900 (JST) [thread overview]
Message-ID: <200410130207.LAA08910@etlken.m17n.org> (raw)
In-Reply-To: <buomzyrfnhu.fsf@mctpc71.ucom.lsi.nec.co.jp> (message from Miles Bader on Wed, 13 Oct 2004 09:52:29 +0900)
In article <buomzyrfnhu.fsf@mctpc71.ucom.lsi.nec.co.jp>, Miles Bader <miles@lsi.nec.co.jp> writes:
> I wrote:
>>> I've attached a diff showing the changes -- if you visit it in emacs,
>>> you'll see that it looks like the inserted and deleted lines are all
>>> equal (except for my addition at the top of course)! But if you use
>>> `find-file-literally', you can see that the file encodings are actually
>>> different.
>>
>> An update: actually the lines only look the same if you view it in
>> emacs-unicode -- if you view the diff file in the CVS trunk emacs, in
>> fact the `rewritten' characters generated by emacs-unicode are rendered
>> as double-width characters.
> Hi, does anybody have any idea about this bug, or a work-around?
Sorry for not responding on this matter earlier. I remember
that I implemented a code to preserve the original
desigination information of iso-2022 fairly long ago and
assured that it worked at that time. It seems that some
changes later broke it. I'll invetigate it soon.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2004-10-13 2:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <buok6ud33sd.fsf@mctpc71.ucom.lsi.nec.co.jp>
[not found] ` <buowtyc1u26.fsf@mctpc71.ucom.lsi.nec.co.jp>
2004-10-13 0:52 ` emacs-unicode: different encoding of iso-2022-7bit? Miles Bader
2004-10-13 2:07 ` Kenichi Handa [this message]
2004-10-13 2:42 ` Kenichi Handa
2004-10-13 3:09 ` Miles Bader
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=200410130207.LAA08910@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-unicode@gnu.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).