Re: [Q] Handle bytes in the range 0x80-0xC0 better when dealing with ISO-IR 196.
Ar an cúigiú lá is fiche de mí na Samhain, scríobh Stephen J. Turnbull:
> If you have a less warty proposal, I doubt people will complain
about
> implementing that.
If Aidan wants to put his broken-Unicode coding system in a package, I
have no objection to that.
Our Unicode coding systems are in C. The packages have no support for
including C.
I just object strongly to putting it in core and promising to support
it
in the future.
You’re not giving an alternative. You’ve said yourself that adding support
for passing through errors from Lstreams is almost impossible. The present
behaviour is not acceptable.
The issue is that pretty much anything that doesn't involve
rewriting
our file-coding mechanism is going to be warty, and if it's in core it
will involve making promises that I sure don't want to keep (cf.
latin-unity, which is a hack that I wrote and am pleased with, but
nevertheless I am the most determined opponent of putting it in core).
And as a result of it not being in core, every time a European installs
XEmacs for the first time, and tries writing the Euro sign to an iso-8859-1
file, only to have it silently trashed, that European is a chunk less likely
to continue using XEmacs.
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta