Re: [Lynx-dev] lynx un-renders 

[Thorsten Glaser]

Hi russellbell,

can you please use hexadecimal numbers in threads like this one,
so it is easier for others to find the mentioned character in the
Unicode database? Thanks in advance!

>I think it appears by accident every time I see it.

I’ve only ever seen those used by windows codepage 1252 users…
I usually render the C1 control characters thus:

/* 0x80 */      0x20AC, 0x278A, 0x201A, 0x0192, 0x201E, 0x2026, 0x2020, 0x2021,
/* 0x88 */      0x02C6, 0x2030, 0x0160, 0x2039, 0x0152, 0x278B, 0x017D, 0x278C,
/* 0x90 */      0x278D, 0x2018, 0x2019, 0x201C, 0x201D, 0x2022, 0x2013, 0x2014,
/* 0x98 */      0x02DC, 0x2122, 0x0161, 0x203A, 0x0153, 0x278E, 0x017E, 0x0178,

I’m using 0x278A‥0x278E for those undefined even in cp1252 so
that there’s at least some indication of what went wrong. C1
control characters generally should not be interpreted, or even
sent out as part of text files, so this is the safe way to do
it, and rendering it as if it were miscalculated cp1252 makes
most of its uses legible.

Note that this applies equally for undefined uses of all three
of: bare \x80 in the HTML, bare \xC2\xA0 (U+0080) in the HTML,
and use of entities like € and Ĩ in the HTML. These
all should be rendered the same as € for… acceptance
that the word “web designer” is a curse word denoting idiots.

bye,
//mirabilos
-- 
[...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but
what about xfs, and if only i had waited until reiser4 was ready... in the be-
ginning, there was ffs, and in the middle, there was ffs, and at the end, there
was still ffs, and the sys admins knew it was good. :)  -- Ted Unangst über *fs