* Re: emacs-unicode: different encoding of iso-2022-7bit? [not found] ` <buowtyc1u26.fsf@mctpc71.ucom.lsi.nec.co.jp> @ 2004-10-13 0:52 ` Miles Bader 2004-10-13 2:07 ` Kenichi Handa 0 siblings, 1 reply; 4+ messages in thread From: Miles Bader @ 2004-10-13 0:52 UTC (permalink / raw) Cc: emacs-devel 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: emacs-unicode: different encoding of iso-2022-7bit? 2004-10-13 0:52 ` emacs-unicode: different encoding of iso-2022-7bit? Miles Bader @ 2004-10-13 2:07 ` Kenichi Handa 2004-10-13 2:42 ` Kenichi Handa 0 siblings, 1 reply; 4+ messages in thread From: Kenichi Handa @ 2004-10-13 2:07 UTC (permalink / raw) Cc: emacs-unicode, emacs-devel 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: emacs-unicode: different encoding of iso-2022-7bit? 2004-10-13 2:07 ` Kenichi Handa @ 2004-10-13 2:42 ` Kenichi Handa 2004-10-13 3:09 ` Miles Bader 0 siblings, 1 reply; 4+ messages in thread From: Kenichi Handa @ 2004-10-13 2:42 UTC (permalink / raw) Cc: emacs-unicode, emacs-devel, miles 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: emacs-unicode: different encoding of iso-2022-7bit? 2004-10-13 2:42 ` Kenichi Handa @ 2004-10-13 3:09 ` Miles Bader 0 siblings, 0 replies; 4+ messages in thread From: Miles Bader @ 2004-10-13 3:09 UTC (permalink / raw) Cc: emacs-unicode, emacs-devel 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] ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-10-13 3:09 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [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 2004-10-13 2:42 ` Kenichi Handa 2004-10-13 3:09 ` Miles Bader
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.