On 2/18/07, Drew Adams <[EMAIL PROTECTED]> wrote:
[...] so I did not change my browser
encoding - after all, this is code, which displays as plain text.
That assumption is just wrong, and more and more with each passing
day. elisp is not the only language where you can have source that
contains non-ASCII chars (it is perfectly legal in Ada, for example,
and Perl).
Yes, I know you're arguing that buff-menu.el contains just one
non-ASCII char and it would be friendlier to use an escape (It's me
who added the comment line just above the one which is causing you so
much grief.) Perhaps you're right. But you said yourself your fix
wouldn't work for packages with lots of Unicode chars. Where do you
intend to put the line? At ten chars? A thousand? And how do you
propose to inform the user, used to "code which displays as plain
text", that suddenly this other code isn't downloadable with broken
tools anymore?
I don't care about buff-menu.el, and won't argue for or against
changing one character; but the fix for the problem you're struggling
with is educating the users, and pointing them to non-broken tools.
Obviously, we can't (nor should) force anyone to change their ways;
but I don't see why should we make extraordinary efforts to suit them,
either.
Juanma
_______________________________________________
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
