🚀 go-pugleaf

In <paul.4cbx@serena.iaehv.nl>, paul@serena.iaehv.nl (Paul Kolenbrander) wrote:
> On Fri, 29 Mar 96, Mike Meyer typed the following line(s):
> > There is at least one bug in AWeb's HTML 2.0 support. It will
> > sometimes format this ugly construct:
> > <FONT SIZE=+1>G</Font>et <FONT SIZE=+1>O</Font>ur <FONT SIZE=+1>G</Font>reat
> > <FONT SIZE=+1>P</Font>roduct <FONT SIZE=+1>N</Font>ow
> I disagree with you here. There is nothing wrong with AWeb's HTML 2.0
> support. Especially as the <FONT></FONT> tag pair is NOT a part of the
> HTML 2.0 standard. But is one of the NetScape custom tags. BTW, have
> youtried putting that construct on one line instead of two...

Ok, change the <FONT SIZE=+1> to <B>, and the </FONT> to </B>. AWeb
still gets it wrong - I used FONT (with invalid SGML in it as well)
because the people who like this kind of ugly construct tend to do it
that way. A more realistic example would be something like
"<i>this</i>.", which follows typographic conventions. AWeb will
sometimes put a line break before the period, which looks VERY
strange.

That AWeb lets tags create a word break when the tag is either
unrecognized or NOT a tag that creates a line break is a bug in it's
HTML 2.0 handling. I reported this to Yvon during the beta, and he
said he would see how painfull it was to fix.

If AWeb changes it's formatting because I replace a space with newline
outside of a preformatted text area, that's a bug as well.

	<mike