(no subject) [entries|reading|network|archive]
simont

[ userinfo | dreamwidth userinfo ]
[ archive | journal archive ]

Sun 2004-09-26 10:59
LinkReply
[identity profile] brad.livejournal.comSun 2004-09-26 08:26
Well, it works fine pasting into another Emacs, it must be a bug in your code.

Put it in the FAQ. Hell, link this post in the FAQ. Then when people bitch at you, just reply with "See FAQ".

Do any other applications besides emacs do emacs' style of broken ISO 2022?

I'd strongly avoid implementing this garbage. If you make Putty only support the newer utf-8 copy/paste you refered to, will a modern Emacs (perhaps in the future) negotiate with the other app to agree on a compatible copy/paste protocol? I'd put the onus on emacs to conform to standards, even if they weren't out yet when they went astray.
Link Reply to this | Thread
[personal profile] simontMon 2004-09-27 02:13
It's not quite as bad as I'd previously feared; it turns out that Emacs's bizarre character set definitions are within the ISO 2022 private use section (which I hadn't realised there was one of). So they probably aren't technically doing anything wrong, although it's still not very pleasant.

Some more investigation reveals that the Xutf8 functions do actually understand (even if they don't generate) some of Emacs's private character sets. I have a feeling I'm probably going to need to take a conservative/liberal approach: be ready to understand any bizarre crud fed to me by Emacs or XFree86 or anyone else, but only generate standards-compliant niceness myself...
Link Reply to this | Parent
navigation
[ go | Previous Entry | Next Entry ]
[ add | to Memories ]