[
https://issues.apache.org/jira/browse/TIKA-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899528#action_12899528
]
Ken Krugler commented on TIKA-463:
----------------------------------
Hi Julien,
As per Jukka's suggestion, the XHTMLContentHandler puts everything it finds in
metadata into the <head> block as <meta> elements. This way it also helps out
non-HTML parsers.
One issue this causes, though, is that it exposes an existing issue with how
HtmlHandler treats the http-equiv meta tag. This gets mapped to a <meta
name="Content-Type" xxx> element, but you can also have an existing <meta
name="content-type" xxx> element. Makes me think we should treat metadata keys
as case-insensitive, to avoid this issue. And/or remap "well-known" keys to
their correct capitalization.
-- Ken
> HtmlParser doesn't extract links from img, map, object, frame, iframe, area,
> link
> ---------------------------------------------------------------------------------
>
> Key: TIKA-463
> URL: https://issues.apache.org/jira/browse/TIKA-463
> Project: Tika
> Issue Type: Bug
> Components: parser
> Reporter: Ken Krugler
> Assignee: Ken Krugler
> Fix For: 0.8
>
> Attachments: TIKA-463-1.patch, TIKA-463-2.patch, TIKA-463-3.patch,
> TIKA-463.patch
>
>
> All of the listed HTML elements can have URLs as attributes, and thus we'd
> want to extract those links, if possible.
> For elements that aren't valid as XHTML 1.0, there might be some challenges
> in the right way to handle this.
> But if XHTML 1.0 means the union of "transitional and frameset" variants,
> then all of the above are valid, and thus should be emitted by the parser,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
