Posted Mar 12, 2007 16:14 UTC (Mon) by branden (guest, #7029)
[Link]
Or just use proper HTML character entities instead of inlining 8-bit characters...
Or maybe that doesn't work? Let's see... à la piñata...
It works, but you have to use HTML-formatted comments.
OpenOffice.org sends Dell a letter
Posted Mar 12, 2007 16:53 UTC (Mon) by sveinrn (guest, #2827)
[Link]
That's a hack from an ancient time when the Internet used 7-bit ASCII... And it works only for a limited number of characters. I think specifying a proper character set (like UTF-8) is a much better long term solution.
OpenOffice.org sends Dell a letter
Posted Mar 12, 2007 19:59 UTC (Mon) by ajross (subscriber, #4563)
[Link]
HTML has numeric entities that can encode any unicode character. And 7 bit ASCII is still a very useful interchange and storage format, guaranteed to display robustly on all devices.
But yeah: Latin-1 as a web page encoding needs to die a fast death. UTF-8 would be much cleaner.
OpenOffice.org sends Dell a letter
Posted Mar 13, 2007 13:39 UTC (Tue) by xanni (subscriber, #361)
[Link]
As it turns out, the character encoding *is* UTF-8; it's just wrongly specified as ISO-8859-1 in the headers. Manually override to UTF-8 in your browser and everything displays correctly. Looks like someone at LWN needs to fix their HTML headers!
Encodings
Posted Mar 13, 2007 14:05 UTC (Tue) by corbet (editor, #1)
[Link]
LWN needs to fix its handling of encodings in general. It's very much on my list to deal with this issue...but the list remains long...
Encodings
Posted Mar 13, 2007 15:17 UTC (Tue) by nix (subscriber, #2304)
[Link]
If you opened the source up someone else could fix it for you!