Re: LYNX-DEV problem page

[Foteos Macrides]

Klaus Weide <address@hidden> wrote:
>[...]
>Btw. the same kind of problem seems to exist for all kinds of tags with an
>ID attribute if they appear within Anchor text... (not dependent on "which
>parser" etc.)

        Yes, I noticed that too when I was checking out the MARQUEE
problem.  Things as innocuous as:

        <A HREF="foo">Blah <EM ID="yuk">yuk</EM> foo</A>
        
break the Anchor, because the named link is technically embedded.
I tried all day yesterday to come up with a safe workaround, but
didn't succeed.  I haven't given up, though.



>[...]
>> Finally, this page, and other pages at this site, are sprinkled with
>> &#145; and &#146; strings.  Shouldn't these be translated into something
>> else?
>
>Yes, of course.  By the authors or authoring tools. 
>[...]

        Why not mention to Laura and others who got involved in that
(in conjunction with a discussion about whether an investment of $24
at Walden Books would be worthwhile), that just a few days ago, you
posted (free of charge) a lengthy, scholarly discussion of 8-bit control
character (as far as the "document character set" for an "HTML
document" is concerned) handling, and the workarounds used in Lynx
due to its not first converting the input stream to an "HTML document",
but instead doing that and everything else in one, byte-by-byte pass
through it?  Note, though, that "document" is not an everyday, "you
know what I mean" word in this context.  You don't have an "HTML
document" until the input stream has been converted to the "document
character set", which means, with the current Lynx API, that Lynx
doesn't ever parse an "HTML document", even when the input stream is
text/html[;charset="MicroSoft keeps this a secret"].

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;