Re: [Lynx-dev] rendering (0x97)

2020-06-30 Thread Mouse
> I thought the HTML5 principle is that every browser should produce
> the same output regardless of whether the document was syntactically
> valid, and that is why they define error cases in such detail.

Then is "error" really an appropriate word?  If an interpretation is
defined for something, how much sense does it make to call it an error?

And, of course, it's completely impossible for every browser to produce
the same output, unless "the same" is taken in a ludicrously relaxed
sense.

/~\ The ASCII Mouse
\ / Ribbon Campaign
 X  Against HTMLmo...@rodents-montreal.org
/ \ Email!   7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] rendering (0x97)

2020-06-30 Thread David Woolley

On 30/06/2020 14:49, Halaasz Saandor via Lynx-dev wrote:
say text between  and , with the webbrowser free to make any 
interpretation of it.


Are you sure that the browser is given free reign?  I thought the HTML5 
principle is that every browser should produce the same output 
regardless of whether the document was syntactically valid, and that is 
why they define error cases in such detail.


I think there is also a principle that pre-HTML5 invalid pages should 
produce results similar to those on mainstream pre-HTML5 browsers.


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] rendering (0x97)

2020-06-30 Thread Halaasz Saandor via Lynx-dev

2020/06/28 13:34 ... Thomas Dickey:

but in the meantime, the html5 crowd declared that iso-8859-1 is
identical to cp1252


I, too, think the crowd crazie, for other reasons besides: when I heard 
of this crowd I glanced at the website, and found great effort exerted 
on the meaning of strings that had been considered bad HTML, say text 
between  and , with the webbrowser free to make any 
interpretation of it. Furthermore, I looked for limitless nesting, as 
the deprecated  is allowed within , to the webbrowser s 
limits, and found that such limitless nesting is not and never shall be 
part of HTML, right after claims that the element structure allows 
that--but only in style!
Sounds as if one has to use something like MSoft Word to generate it, 
because Word well fakes nesting by means of indenting. Ugh.


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] rendering (0x97)

2020-06-30 Thread Halaasz Saandor via Lynx-dev

2020/06/29 14:43 ... Mouse:

I hav seen that, and , in Microsoft HTML from Word.

That means little.  Just because a Microsoft program generates
something does not mean it's compatible with non-Microsoft software,
and sometimes does not even mean it's compatible with other Microsoft
software, and certainly does not mean it's correct.


My point was the perversity of Microsoft software. HT is almost useless 
in HTML, it is only another space.


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev