Details
-
Improvement
-
Status: Reopened
-
Minor
-
Resolution: Unresolved
-
0.8, 0.9, 0.10
-
None
Description
if the encoding in the meta tag is wrong, this encoding is detected,
even if there is the right encoding set in metadata before(which can be from http response header).
test code to reproduce:
static String content = "<html><head>\n"
+ "<meta http-equiv=\"content-type\" content=\"application/xhtml+xml; charset=iso-8859-1\" />"
+ "</head><body>Über den Wolken\n</body></html>";
/**
- @param args
- @throws IOException
- @throws TikaException
- @throws SAXException
*/
public static void main(String[] args) throws IOException, SAXException,
TikaException { Metadata metadata = new Metadata(); metadata.set(Metadata.CONTENT_TYPE, "text/html"); metadata.set(Metadata.CONTENT_ENCODING, "UTF-8"); System.out.println(metadata.get(Metadata.CONTENT_ENCODING)); InputStream in = new ByteArrayInputStream(content.getBytes("UTF-8")); AutoDetectParser parser = new AutoDetectParser(); BodyContentHandler h = new BodyContentHandler(10000); parser.parse(in, h, metadata, new ParseContext()); System.out.print(h.toString()); System.out.println(metadata.get(Metadata.CONTENT_ENCODING)); }
Attachments
Attachments
Issue Links
- is related to
-
TIKA-431 Tika currently misuses the HTTP Content-Encoding header, and does not seem to use the charset part of the Content-Type header properly.
-
- Resolved
-
-
-
- Open
-
- relates to
-
-
- Closed
-