At 16:39 2003-05-27 -0400, David Goodger wrote:
>I haven't had any trouble.
Where have you been then? In a pure MacOS and BeOS land of
milk and honey? Please show me where that is! :)
>(I assume you mean UTF-8 or something; no
>such thing as Unicode files.)
You obviously knew what I mean. I could live with *any* UTF encoding
that's consistently supported by the environments I use. It's not long
ago that it was deep magic to get ISO 8859-1 to work on a Linux box,
and I'm not sure it still works smoothly if you set up cygwin X11 on
a Windows box. :(
>I've made this message UTF-8 encoded.
>Here's a hyphen (-), an en-dash (b
>with spaces between (- b
That was how your mail looked when it came through the mailing list.
The one sent directly looked somewhat better, as does the web archive at
>I haven't had any trouble. (I assume you mean UTF-8 or something; no
>such thing as Unicode files.) I've made this message UTF-8 encoded.
>Here's a hyphen (-), an en-dash (=AD), an em-dash (=97), and all three
>with spaces between (- =AD =97). Some accented e's: =C3=A9=C3=A8=C3=AB=C3=
=AA. Can you read
It doesn't look right to me: A with ~, copyright, A with ~, dieresis,
A with ~, is << called a chevron?, A with ~, a raised little 2. That's
not what you planned, is it? Actually, the dashes look right to me, so
it's partially correct. In Mozilla and Opera I can get the mail archive
to look right for your message if I force the browser to UTF-8, in MS IE
ndash and mdash looks like little black boxes, and UTF-8 is certainly not
activated automagically by any of the browsers for that we page.
You see? The current computer environment is sadly not quite ready for
For instance, mailing list software that places archives on web pages or
makes digests would need to convert all messages to UTF-8 and give a correct
header to the message. Each page can only have one encoding.
Not all email clients grok UTF. I use Eudora, and obviously it managed to
show the dashes but failed with the little e's. (They were little e's=
Or were they just spoiled on the way?
Sigh. I hope UTF works with email in a few years. With text editors, it's
probably a similar time span.
The PythonWin editor, which I *like* (Scintilla based I think) will say
that I'm in col 41 if I have a line of 20 =E5 before the cursor. It counts
bytes, not characters! It will still save the file as latin1. It will also
remove one *byte* on backspace so if you backspace over =E5 it's not=
but replaced with =C0. Also, it you copy and paste, it will paste UTF-8 into
other apps without declaring that.
If your native languange had been another than those three that can get
along with US ASCII, you would have known that these kinds of problems
Magnus Lycka (It's really Lyckå), magnus@...
Thinkware AB, Sweden, http://www.thinkware.se
I code Python ~ The shortest path from thought to working program=20