lynx-dev
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV Bug in AC111 with tables and ¨

From: T.E.Dickey
Subject: Re: LYNX-DEV Bug in AC111 with tables and ¨
Date: Sun, 22 Feb 1998 15:34:25 -0500 (EST) 
> the following HTML-file, reduced from the home pages of the german
> Bundestag, leads to problems concerning text attributes and the
> presentation of ¨ characters. I didn't find differences
> between the djgpp and solaris version:
I looked at this one today, and don't like it either.  The difference
between the 2.7.2 and development versions is that the latter is stricter
in its interpretation than the 2.7.2 version:  the <b> and <blockquote>
tags are not properly nested (as noted by Larry Virden).  This is done in
the development version as part of the 'extended dtd' processing, so I
tried turning _that_ feature off to compare, and it does show the umlauts
-- but the line breaks are lost.

You can see what's going on, of course, by turning on the trace.
 
> <html>
> <body>
> <table><tr><td>
> n&auml;chste1
> <blockquote>
> <b>
> D&uuml;bel
> </blockquote>
> </b>
> n&auml;chste2
> <blockquote>
> <b>
> D&uuml;bel
> </blockquote>
> </b>
> n&auml;chste3
> <blockquote>
> <b>
> D&uuml;bel
> </blockquote>
> </b>
> n&auml;chste4
> <blockquote>
> <b>
> D&uuml;bel
> </blockquote>
> </b>
> n&auml;chste5
> <blockquote>
> <b>
> D&uuml;bel
> </blockquote>
> </b>
> </td></tr></table>
> </body></html>
> 
> Title1 the following blockquote, title2 and the following blockquote
> are OK. In all other titles, the &auml; is not interpreted but
> directly displayed as n&auml;chste3. The uml's in blockquote 3 and
> latter are displayed correctly. But the bold attribute is ignored.
> 
> Replacing blockquote by <p> </p>, the same effect will occur.
> Characterset is set to DosLatin1 in the DJGPP and to IsoLatin1 on
> solaris.
> In any case, the problems occur behind the second quotebolock,
> no matter, one ore more are following. The line or rowposition
> in the table doesn't change this behaviour. Reordering the </b> tags
> leads most time to a good result.
> 
> Any ideas?
> 
> Klaus-Peter
> 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey
reply via email to
[Prev in Thread] Current Thread [Next in Thread]