You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have build scripts or container images that drop in just the jar, update them to unpack the zip and run from inside it.
42
42
43
+
== Default content handler: XHTML/XML -> Markdown
44
+
45
+
In 3.x the default content handler produced XHTML/XML. In 4.x the default is **Markdown** everywhere:
46
+
47
+
* `tika-app` outputs Markdown by default (was XHTML). Pass `-x`/`--xml`, `-h`/`--html`, or `-t`/`--text` to choose another format.
48
+
* `tika-server` — the `/tika` and `/rmeta` endpoints return Markdown content by default (was XHTML/XML). Use an explicit handler path (`/tika/xml`, `/rmeta/xml`, ...) or the `X-Tika-Handler` header to choose another format.
49
+
* The async/pipes CLI emits Markdown by default (was plain text). Use `--handler x` (etc.) to choose another format.
50
+
51
+
If you parse the extracted content programmatically and expect XHTML/XML, request it explicitly as shown above (TIKA-4663).
52
+
43
53
== Configuration: XML to JSON
44
54
45
55
Tika 4.x uses JSON configuration files instead of XML. The legacy `tika-config.xml` format
0 commit comments