Torsten Neuer wrote:
> Depends on what ht://Dig is developing towards. ;-)
>
> I'd rather split things up for correct HTML 4.0 and language support.
> <LINK> is somewhat more complex than <AREA> with reagards to language
> support. <LINK> adds the "hreflang" attribute to denote the language
> of the referred document whereas such an attribute is unknown to <AREA>.
The <LINK> tag is even more complex than that. From the HTML 4.0 DTD (in
the META section)
Note. When a property specified by a META element takes a value that is
a URI, some authors prefer to specify the meta data via the LINK
element. Thus, the following meta data declaration:
<META name="DC.identifier"
content="ftp://ds.internic.net/rfc/rfc1866.txt">
might also be written:
<LINK rel="DC.identifier"
type="text/plain"
href="ftp://ds.internic.net/rfc/rfc1866.txt">
In other words, we have to worry about <META> tags masquerading as
<LINK> tags!
> To ease the task of automatically switching between multiple languages
> (i.e. stopword lists, dictionaries etc.) in the future it probably will
> be better to handle both DTD elements separately.
The change isn't *that* hard--you'd just separate the case statements
and duplcate the current code. I'm going to leave the change as-is, with
the <AREA> and <LINK> tags parsed by the same code. But patches for more
involved HTML parsing are welcome. ;-) This will get a little easier
when the Transport object is more robust and the HTML parser can fetch
the linked meta-data.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
