tj_edit - email - url
Site won't work properly with the output as utf-16. That's because utf-16 doesn't really exist --at least not for the web.
That's not a dis [insult]. I have the Unicode Standard Version 3.0 right here at my elbow.
For example, here's the ampersand in either Latin 1 or utf-8: & [or &]. Otherwise, a CO control.
Okay? Now here's the unicode 16 version: 0026. It's use right now for HTML/XTHML documents is only theoretical.
For example, with the Unicode Standard 3.0, I can look up any character I want --but then I have to use a formula to convert it back to utf-8.
(Had I known that in advance, I might not have bought the book!).
You can definitely use utf-8 to desplay multiple languages on the same page. But not with utf-16.
This page has problems with display because the browser has trouble with the encoding.
Again, too many mixed charsets | mixed signals.
It also won't validate. Let's remove the utf-16 experiment, and see what happens.
20011216 @ 22:33:15
tj_edit - email - url
Got It!!
Edit | Correct the above.
The page only works properly | validates if the charset is windows-1252 (western europe).
If you change to
Everything works | displays fine. Otherwise, The viewer gets blocks or question marks (?) where there should be single quotes in the Textism section.
So your actual input encoding is windows-1252 (western europe).
Interesting. How to solve this problem? To make sure that the default input is really utf-8, and not some other charset?
I'll work on it. But you'll probably get the answer first.
20011216 @ 22:48:08
michel v - email - url
if you display code, please use [ instead of
20011216 @ 22:53:18
michel v - email - url
gah. instead of < >
20011216 @ 22:55:44
tj_edit - email - url
The missing line above is:
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252" /> [Most HTML tags turned off, I guess].
Forget the utf-16 error. Although I'd love to know what's really going on there.
The output [all the text/encoding] is clean, fine and valid as windows-1252.
But the browser picks up the unicode tag, and so displays with errors.
Solution (1): change the charset.
Solution (2): change the input encoding.
utf-16 has nothing to do with anything here, error|display and validation-wise.
Just a false alarm due to my own unicode obsessions.
20011216 @ 22:58:06
tj_edit - email - url
Opps. Sorry Michel. Posted when your comment was not on the screen!
[meta http-equiv="Content-Type" content=
"text/html; charset=windows-1252" /]
20011216 @ 22:59:52
[powered by b2.]