[jira] Created: (TIKA-349) HtmlParser's http-equiv code needs to be more flexible

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (TIKA-349) HtmlParser's http-equiv code needs to be more flexible

JIRA jira@apache.org
HtmlParser's http-equiv code needs to be more flexible
------------------------------------------------------

                 Key: TIKA-349
                 URL: https://issues.apache.org/jira/browse/TIKA-349
             Project: Tika
          Issue Type: Improvement
    Affects Versions: 0.6
            Reporter: Ken Krugler
            Priority: Minor


Some http-equiv meta tags in HTML documents have charset attributes that currently aren't handled properly.

For example, <meta http-equiv="content-type" content="text/html; charset=utf-8; charset=UTF-8">

Or where content="text/html;; charset="utf-8" (note double semi-colons)

The parsing code needs to be more flexible to handle these edge cases.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (TIKA-349) HtmlParser's http-equiv code needs to be more flexible

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/TIKA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ken Krugler updated TIKA-349:
-----------------------------

    Attachment: TIKA-349.patch

> HtmlParser's http-equiv code needs to be more flexible
> ------------------------------------------------------
>
>                 Key: TIKA-349
>                 URL: https://issues.apache.org/jira/browse/TIKA-349
>             Project: Tika
>          Issue Type: Improvement
>    Affects Versions: 0.6
>            Reporter: Ken Krugler
>            Priority: Minor
>         Attachments: TIKA-349.patch
>
>
> Some http-equiv meta tags in HTML documents have charset attributes that currently aren't handled properly.
> For example, <meta http-equiv="content-type" content="text/html; charset=utf-8; charset=UTF-8">
> Or where content="text/html;; charset="utf-8" (note double semi-colons)
> The parsing code needs to be more flexible to handle these edge cases.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (TIKA-349) HtmlParser's http-equiv code needs to be more flexible

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/TIKA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved TIKA-349.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.6
         Assignee: Jukka Zitting

Patch committed in revision 891074.

> HtmlParser's http-equiv code needs to be more flexible
> ------------------------------------------------------
>
>                 Key: TIKA-349
>                 URL: https://issues.apache.org/jira/browse/TIKA-349
>             Project: Tika
>          Issue Type: Improvement
>    Affects Versions: 0.6
>            Reporter: Ken Krugler
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.6
>
>         Attachments: TIKA-349.patch
>
>
> Some http-equiv meta tags in HTML documents have charset attributes that currently aren't handled properly.
> For example, <meta http-equiv="content-type" content="text/html; charset=utf-8; charset=UTF-8">
> Or where content="text/html;; charset="utf-8" (note double semi-colons)
> The parsing code needs to be more flexible to handle these edge cases.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.