[
https://issues.apache.org/jira/browse/TIKA-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899465#action_12899465
]
Julien Nioche commented on TIKA-463:
------------------------------------
Look good. I must be missing something obvious but I can't work out where an
element like META is sent to the XHTML output. Wasn't the case before as far as
I can remember and this can't be in HtmlHandler as it imposes the constraints I
described earlier i.e. it used to simply put the info in the metadata. Ken,
would you mind giving me a hint?
> 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.
