Re: emacs-unicode: different encoding of iso-2022-7bit?

Re: emacs-unicode: different encoding of iso-2022-7bit?

[Miles Bader]

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?

I think it's a fairly serious problem -- I've stopped using Emacs 22
because I can't edit Emacs' ChangeLogs with it (they're encoded using
iso-2022-7bit).

Thanks,

-Miles
-- 
Is it true that nothing can be known?  If so how do we know this?  -Woody Allen

Re: emacs-unicode: different encoding of iso-2022-7bit?

[Kenichi Handa]

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

Re: emacs-unicode: different encoding of iso-2022-7bit?

[Kenichi Handa]

In article <200410130207.LAA08910@etlken.m17n.org>, Kenichi Handa <handa@m17n.org> writes:

> 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.

I've just installed a fix.  Could you try again?

---
Ken'ichi HANDA
handa@m17n.org

Re: emacs-unicode: different encoding of iso-2022-7bit?

[Miles Bader]

Kenichi Handa <handa@m17n.org> writes:
> I've just installed a fix.  Could you try again?

A quick test shows that it now seems to work correctly on Emacs'
lisp/ChangeLog.

Thanks!

-Miles
-- 
If you can't beat them, arrange to have them beaten.  [George Carlin]