Skip to content
Commits on Source (2)
Expand all Show whitespace changes
Inline Side-by-side
.gitignore
View file @ efa85c97
.svn
target
.idea
.classpath
......@@ -6,3 +7,5 @@ target
*.iml
*.ipr
*.iws
nbactions.xml
nb-configuration.xml
\ No newline at end of file
CHANGES.txt
View file @ efa85c97
Release 1.8 - 4/13/2015
* Fix null pointer when processing ODT footer styles (TIKA-1600).
* Upgrade to com.drewnoakes' metadata-extractor to 2.0 and
add parser for webp metadata (TIKA-1594).
* Duration extracted from MP3s with no ID3 tags (TIKA-1589).
* Upgraded to PDFBox 1.8.9 (TIKA-1575).
* Tika now supports the IsaTab data standard for bioinformatics
both in terms of MIME identification and in terms of parsing
(TIKA-1580).
* Tika server can now enable CORS requests with the command line
"--cors" or "-C" option (TIKA-1586).
* Update jhighlight dependency to avoid using LGPL license. Thank
@kkrugler for his great contribution (TIKA-1581).
* Updated HDF and NetCDF parsers to output file version in
metadata (TIKA-1578 and TIKA-1579).
* Upgraded to POI 3.12-beta1 (TIKA-1531).
* Added tika-batch module for directory to directory batch
processing. This is a new, experimental capability, and the API will
likely change in future releases (TIKA-1330).
* Translator.translate() Exceptions are now restricted to
TikaException and IOException (TIKA-1416).
* Tika now supports MIME detection for Microsoft Extended
Makefiles (EMF) (TIKA-1554).
* Tika has improved delineation in XML and HTML MIME detection
(TIKA-1365).
* Upgraded the Drew Noakes metadata-extractor to version 2.7.2
(TIKA-1576).
* Added basic style support for ODF documents, contributed by
Axel Dörfler (TIKA-1063).
* Move Tika server resources and writers to separate
org.apache.tika.server.resource and writer packages (TIKA-1564).
* Upgrade UCAR dependencies to 4.5.5 (TIKA-1571).
* Fix Paths in Tika server welcome page (TIKA-1567).
* Fixed infinite recursion while parsing some PDFs (TIKA-1038).
* XHTMLContentHandler now properly passes along body attributes,
contributed by Markus Jelsma (TIKA-995).
* TikaCLI option --compare-file-magic to report mime types known to
the file(1) tool but not known / fully known to Tika.
* MediaTypeRegistry support for returning known child types.
* Support for excluding (blacklisting) certain Parsers from being
used by DefaultParser via the Tika Config file, using the new
parser-exclude tag (TIKA-1558).
* Detect Global Change Master Directory (GCMD) Directory
Interchange Format (DIF) files (TIKA-1561).
* Tika's JAX-RS server can now return stacktraces for
parse exceptions (TIKA-1323).
* Added MockParser for testing handling of exceptions, errors
and hangs in code that uses parsers (TIKA-1553).
* The ForkParser service removed from Activator. Rollback of (TIKA-1354).
* Increased the speed of language identification by
a factor of two -- contributed by Toke Eskildsen (TIKA-1549).
* Added parser for Sqlite3 db files. BEWARE: the org.xerial
dependency includes native libs. Some users may need to
exclude this dependency or configure it specially for
their environment (TIKA-1511).
* Use POST instead of PUT for tika-server form methods
(TIKA-1547).
* A basic wrapper around the UNIX file command was
added to extract Strings. In addition a parse to
handle Strings parsing from octet-streams using Latin1
charsets as added (TIKA-1541, TIKA-1483).
* Add test files and detection mechanism for Gridded
Binary (GRIB) files (TIKA-1539).
* The RAR parser was updated to handle Chinese characters
using the functionality provided by allowing encoding to
be used within ZipArchiveInputStream (TIKA-936).
* Fix out of memory error in surefire plugin (TIKA-1537).
* Build a parser to extract data from GRIB formats (TIKA-1423).
* Upgrade to Commons Compress 1.9 (TIKA-1534).
* Include media duration in metadata parsed by MP4Parser (TIKA-1530).
* Support password protected 7zip files (using a PasswordProvider,
in keeping with the other password supporting formats) (TIKA-1521).
* Password protected Zip files should not trigger an exception (TIKA-1028).
Release 1.7 - 1/9/2015
* Fixed resource leak in OutlookPSTParser that caused TikaException
when invoked via AutoDetectParser on Windows (TIKA-1506).
* HTML tags are properly stripped from content by FeedParser
(TIKA-1500).
* Tika Server support for selecting a single metadata key;
wrapped MetadataEP into MetadataResource (TIKA-1499).
* Tika Server support for JSON and XMP views of metadata (TIKA-1497).
* Tika Parent uses dependency management to keep duplicate
dependencies in different modules the same version (TIKA-1384).
* Upgraded slf4j to version 1.7.7 (TIKA-1496).
* Tika Server support for RecursiveParserWrapper's JSON output
(endpoint=rmeta) equivalent to (TIKA-1451's) -J option
in tika-app (TIKA-1498).
* Tika Server support for providing the password for files on a
per-request basis through the Password http header (TIKA-1494).
* Simple support for the BPG (Better Portable Graphics) image format
(TIKA-1491, TIKA-1495).
* Prevent exceptions from being thrown for some malformed
mp3 files (TIKA-1218).
* Reformat pom.xml files to use two spaces per indent (TIKA-1475).
* Fix warning of slf4j logger on Tika Server startup (TIKA-1472).
* Tika CLI and GUI now have option to view JSON rendering of output
of RecursiveParserWrapper (TIKA-1451).
* Tika now integrates the Geospatial Data Abstraction Library
(GDAL) for parsing hundreds of geospatial formats (TIKA-605,
TIKA-1503).
* ExternalParsers can now use Regexs to specify dynamic keys
(TIKA-1441).
* Thread safety issues in ImageMetadataExtractor were resolved
(TIKA-1369).
* The ForkParser service is now registered in Activator
(TIKA-1354).
* The Rome Library was upgraded to version 1.5 (TIKA-1435).
* Add markup for files embedded in PDFs (TIKA-1427).
* Extract files embedded in annotations in PDFS (TIKA-1433).
* Upgrade to PDFBox 1.8.8 (TIKA-1419, TIKA-1442).
* Add RecursiveParserWrapper (aka Jukka's and Nick's)
RecursiveMetadataParser (TIKA-1329)
* Add example for how to dump TikaConfig to XML (TIKA-1418).
* Allow users to specify a tika config file for tika-app (TIKA-1426).
* PackageParser includes the last-modified date from the archive
in the metadata, when handling embedded entries (TIKA-1246)
* Created a new Tesseract OCR Parser to extract text from images.
Requires installation of Tesseract before use (TIKA-93).
* Basic parser for older Excel formats, such as Excel 4, 5 and 95,
which can get simple text, and metadata for Excel 5+95 (TIKA-1490)
Release 1.6 - 08/31/2014
* Parse output should indicate which Parser was actually used
(TIKA-674).
* Use the forbidden-apis Maven plugin to check for unsafe Java
operations (TIKA-1387).
* Created an ExternalTranslator class to interface with command
line Translators (TIKA-1385).
* Created a MosesTranslator as a subclass of ExternalTranslator
that calls the Moses Decoder machine translation program (TIKA-1385).
* Created the tika-example module. It will have examples of how to
use the main Tika interfaces (TIKA-1390).
* Upgraded to Commons Compress 1.8.1 (TIKA-1275).
* Upgraded to POI 3.11-beta1 (TIKA-1380).
* Tika now extracts SDTCell content from tables in .docx files (TIKA-1317).
* Tika now supports detection of the Persian/Farsi language.
(TIKA-1337)
* The Tika Detector interface is now exposed through the JAX-RS
server (TIKA-1336, TIKA-1336).
* Tika now has support for parsing binary Matlab files as part of
our larger effort to increase the number of scientific data formats
supported. (TIKA-1327)
* The Tika Server URLs for the unpacker resources have been changed,
to bring them under a common prefix (TIKA-1324). The mapping is
/unpacker/{id} -> /unpack/{id}
/all/{id} -> /unpack/all/{id}
* Added module and core Tika interface for translating text between
languages and added a default implementation that call's Microsoft's
translate service (TIKA-1319)
* Added an Translator implementation that calls Lingo24's Premium
Machine Translation API (TIKA-1381)
* Made RTFParser's list handling slightly more robust against corrupt
list metadata (TIKA-1305)
* Fixed bug in CLI json output (TIKA-1291/TIKA-1310)
* Added ability to turn off image extraction from PDFs (TIKA-1294).
Users must now turn on this capability via the PDFParserConfig.
* Upgrade to PDFBox 1.8.6 (TIKA-1290, TIKA-1231, TIKA-1233, TIKA-1352)
* Zip Container Detection for DWFX and XPS formats, which are OPC
based (TIKA-1204, TIKA-1221)
* Added a user facing welcome page to the Tika Server, which
says what it is, and a very brief summary of what is available.
(TIKA-1269)
* Added Tika Server endpoints to list the available mime types,
Parsers and Detectors, similar to the --list-<foo> methods on
the Tika CLI App (TIKA-1270)
* Improvements to NetCDF and HDF parsing to mimic the output of
ncdump and extract text dimensions and spatial and variable
information from scientific data files (TIKA-1265)
* Extract attachments from RTF files (TIKA-1010)
* Support Outlook Personal Folders File Format *.pst (TIKA-623)
* Added mime entries for additional Ogg based formats (TIKA-1259)
* Updated the Ogg Vorbis plugin to v0.4, which adds detection for a wider
range of Ogg formats, and parsers for more Ogg Audio ones (TIKA-1113)
* PDF: Images in PDF documents can now be extracted as embedded resources.
(TIKA-1268)
* Fixed RuntimeException thrown for certain Word Documents (TIKA-1251).
* CLI: TikaCLI now has another option: --list-parser-details-apt, which outputs
the list of supported parsers in APT format. This is used to generate the list
on the formats page (TIKA-411).
Release 1.5 - 02/04/2014
* Fixed bug in handling of embedded file processing in PDFs (TIKA-1228).
......
KEYS
View file @ efa85c97
......@@ -230,7 +230,7 @@ uid David Meikle (CODE SIGNING KEY) <dmeikle@apache.org>
sub 4096R/84C15C40 2014-02-04
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1
Version: GnuPG v1.4.11 (GNU/Linux)
mQINBFLxaSYBEADUywK+vv9sbxjLrW5aAM5bSxyZdPLgv8xUphG40XEGQPAamGiL
aDg9cgob1eZNcxmzMmp/O4vHdcdjzHN0iRMUpsYaSlm9YjqbK3sYynrXqahmHJFa
......@@ -256,28 +256,89 @@ yTpZZplU3QS7sMrAPDGrTP7A0pHkcMxLu+EKfnAYgtWKcPHmwdpWEHwcJaaYD5LU
U3+oNL01iP7fdTp+Nu6eHqCg3GXIkCEwN88Vr9IbAkoQD3DrRWerh35X9zOeb56i
GT+UulAJayBWIgypp6j+uiDqOtDWysOQBn1wQxkERSHzsHtKJ4OXTqXudZ+gNhAK
cQPDzrm1vaT/WoGLxL/hvjf1jo0UD/UtCKnFbCphjKXifuXiRFmr0MkI12ui79rk
uQINBFLxaSYBEACoQN98rA1Nj2shfaWDe3Pjhpd7f6qin86ziKbw8Eu/AxdiG5Xh
PpZbYm63+GKOinAwP0T4V1Fln+j+XH650Ysee1dexa8gXufChf85FKq/rDGjTPG0
RFvI6DkGDP+u4sJJdyAjkZjoZrUOR6ai3kSLIcVAsBRT/NLnlDnfljVfK1hbrE1Y
pLVxKmeTbJsvZOjQA1MgCigAlH3AAXcfZE9UY9HlPHrNDBNazvc89fzktgyUBS7b
H99J9DxmtWIn/XqpsFF/lQ86zeirWSSofJvfk6G66yxS5ApKB7O15GZ1AyqWkAzD
KfsLfd4gAfezRfKDJcWrY8/DyjsyRfbqF6HoBnV0UOLpzqZ8UbjP5+64WDGqajUc
6pUoW0lBJUxu1ZYvjCy7O/m1GNQD/v5Atoi0M2MUOLui30yN1AxC9qhbKFZB8vb1
F4cMuTuCtfF+GeOk8Ib2gl8RhSVmIlrbek7p5wk6pPR8Jf/9ngwySr4dhQBs3GdJ
Hh8fBge4zkg6kFo1pCo99bFzinB3hSbCV3hTnf2uLAb2LCizr125uAc5UML/jeHq
SXSZtHwfcy1wYKKmaynLcz8iMMM+CaCuNTUVLS2VI4P0p5eHUH1SAL1qT9T2S3gp
gM+5pyZmeDOWigtbUOJ79QBM17lbqlexvNQ/t1TcyWPHk9bXXvdAjoNBnwARAQAB
iQIfBBgBCgAJBQJS8WkmAhsMAAoJEFJBSwsOswsHJUAQAKslPy2ZNJwMvFyKaHfk
F0ki+tGDy3Zy/qYW8aQFxnzsR4fTl/BJNXBCh2EpYTGpSESfdvZeMXk8+jUVatq/
C8tLfFoDzwrPudwAemwynEJ+MqK8kJKbmMvmXddzqLJKrHXjzZCmi706ssAkioqI
XSJYZt+d93tTcZsmVrWwoyXUE+ZBbQfmds32HqeziepmfGXasWnRj1/fhdY5XZWJ
rCIZnwCadpxKlPj74XxfEastcKVsI+EWr7Sj83B7RsGS1IPjclY77PBNTCBSB1U3
kBTD7l/dYDLXpiJZ5OAyRO9MrXW7A876XhaBsRdcRxUqEe98NFLVhWuJO6RTb89L
if3LGxsvuaHpIQD0NgkNNTYL9PfIbRjTZpJPQtWErt+eRK4QuZRA1HYKT/htYVH6
/oqsMKlrIh9AoVXPQ+ExCw8TqNo0jTSh0Kdy4Sj0vASLDzckpzFVz2cMoPBfgsjr
U1h+Fc3lMPTjWW/YZUaPt7V+m1jrI4ikm+EC4TIWKtgE+VvHAXHnUPKm2G4a2a0Y
+a5Hwbtz+6hSCxpa2WMIV4wBhaoEeoRrgfllqfovNJ2BJHpZAvGqavFf/yqnqXst
JN4T06+JEcezrCUTDyZ/M0GNGVNq/cdNApc1XIl+tukUCYS/mg6uUWhVzfWenukM
WDWdnyjxFv/9quOxHM976hkg
=CmKg
iQQcBBABCAAGBQJTMWqBAAoJEIqviNbYTkGu/ZkgAJuXfdwRbvhuodF8f944sRN1
7dMDEBf2Uu07zIWR/zXw/ivduf89/5pOXKTjxWFtOqkxPNPPobc8qwAJ8RvnG8fJ
Wz5GP4X3b4Li56U+jSeIuMQqAPivnQQZAykKHwwZcjKrJK0zhpMwITbuQ9ng/tMk
kuV5S3twt73CrIcet2rd7VztesmD2cheNupwlal7tImMwOboE9lF6l4gln48dxzt
huW8h2jo2mWHqzGradcDLlFsecBFFYute3O5gVVweNG0p9/k7GtBTlcKga8ukhuK
nIKzcxGN2wDdMD/xXH0cSGhcDaxHPFvRcX5Og3bAVvdIdkrZueBoV7pd9BWpFA54
ArTBPkK9WUd0JVRMN1yDZqpel7JHAgKgQ1YiTT41RKj2XFvjN6S4kYJ3elRvDX8f
W4kZ4XOKzmqagGfJV061wFRI4sx1Vp3H1vZiF4NkVxdXApBlCdKtO4tyCZiqqSKZ
MaDDPYBiBp1WaNvwmP9zhLw6ZLoO8/0XMKjpguUWzIJh4D4lqw1pN690Dcvfm05r
gKnJUBH8KCq2XgPg8pgAsjuJ6EzIjHLxmvXffiQQ1jgvRT1yU/XM4glSqRnaTVXB
ymg6KrKDTf6iZE94TpmRkZu1lxvg8bKGo9T+otAVq44Ns/qKPaZ/pgZZi+Ip9v80
GQo4KHGaObjwYbZgHurwlZu59FRRTbm1iU0nt/h49xXOwGZuNM3LRO5gC3usvvL3
BYv18jSX9RZnsA0MAVLv9AcjtHMhAYoYZlmogA8Y6S/dIUuEEqTcQMG76GP8hRRL
RUXIViQ7aaOw7y61xVL65OFrfJcuJ0VSB7tuUVFffK6sijRtxu93JOmigq7/IlHy
vatCv6UW+NXaCg1gKezwBFjUQqwQc8ECNt8cq9A8VqhIk5w3xhu/oQpTarUuVJ9H
ZygV5sD/qamJ015fm9lePA7FgNwS0Jf9Bn/BO70IP72/s4bUWvDHGd2a7w0PM9fd
eXt5xTFxNuJJ2BOpO4XIFCiT7igSz5aEC9HoSBv6P+LEqDjoqp/Wize61iWJ9DVP
pZoFQUF3UMH5WajQ/wZxF7YZJsJX+YNiV+cYahO/6bJ6/nMMo1vLtRYLoliujXXQ
K92x7au66cDKUvc/5F1HbpuJ8ZkLtzUERcOdncU5hMeJjTxBH6wmqmBGYUvcqXgY
IfYYGv/J3z/Fai66q2fDuHFV1cIBtdR8wM00XuprMYLDmS0capQc3s7Ft8jsJVGt
y4hhM/zNzltkM7UB3XeEJNDwMHFZi2+yY49H9sPFrzh8izOFrYW670YFLhBTVNCw
C2i2rESxDs13do8UvuxK4qPnQTN2pAh21lUGrzGTm/NUqRJlpuK+NZYJ1EqjIoSI
nAQQAQIABgUCUwOEzQAKCRDurUz9SaVj2UUQA/9rfy/wgwWejyiei60Fnn4H7bfO
FRuNj3etXWOGksF+KciFY+TwKEmtC+Sxgzfq4jqLZCcTJWIVpAv+xD+bU0wXbU83
dv9BrYfuT1Q9O2r4m4YGGLROoaUU75/CKbyeKxUJZdulvB5DjxWPOVADUGV9k7Ct
2Xlpcxt0owafAWMa8rkCDQRS8WkmARAAqEDffKwNTY9rIX2lg3tz44aXe3+qop/O
s4im8PBLvwMXYhuV4T6WW2Jut/hijopwMD9E+FdRZZ/o/lx+udGLHntXXsWvIF7n
woX/ORSqv6wxo0zxtERbyOg5Bgz/ruLCSXcgI5GY6Ga1Dkemot5EiyHFQLAUU/zS
55Q535Y1XytYW6xNWKS1cSpnk2ybL2To0ANTIAooAJR9wAF3H2RPVGPR5Tx6zQwT
Ws73PPX85LYMlAUu2x/fSfQ8ZrViJ/16qbBRf5UPOs3oq1kkqHyb35OhuussUuQK
SgezteRmdQMqlpAMwyn7C33eIAH3s0XygyXFq2PPw8o7MkX26heh6AZ1dFDi6c6m
fFG4z+fuuFgxqmo1HOqVKFtJQSVMbtWWL4wsuzv5tRjUA/7+QLaItDNjFDi7ot9M
jdQMQvaoWyhWQfL29ReHDLk7grXxfhnjpPCG9oJfEYUlZiJa23pO6ecJOqT0fCX/
/Z4MMkq+HYUAbNxnSR4fHwYHuM5IOpBaNaQqPfWxc4pwd4Umwld4U539riwG9iwo
s69dubgHOVDC/43h6kl0mbR8H3MtcGCipmspy3M/IjDDPgmgrjU1FS0tlSOD9KeX
h1B9UgC9ak/U9kt4KYDPuacmZngzlooLW1Die/UATNe5W6pXsbzUP7dU3Mljx5PW
1173QI6DQZ8AEQEAAYkCHwQYAQoACQUCUvFpJgIbDAAKCRBSQUsLDrMLByVAEACr
JT8tmTScDLxcimh35BdJIvrRg8t2cv6mFvGkBcZ87EeH05fwSTVwQodhKWExqUhE
n3b2XjF5PPo1FWravwvLS3xaA88Kz7ncAHpsMpxCfjKivJCSm5jL5l3Xc6iySqx1
482Qpou9OrLAJIqKiF0iWGbfnfd7U3GbJla1sKMl1BPmQW0H5nbN9h6ns4nqZnxl
2rFp0Y9f34XWOV2ViawiGZ8AmnacSpT4++F8XxGrLXClbCPhFq+0o/Nwe0bBktSD
43JWO+zwTUwgUgdVN5AUw+5f3WAy16YiWeTgMkTvTK11uwPO+l4WgbEXXEcVKhHv
fDRS1YVriTukU2/PS4n9yxsbL7mh6SEA9DYJDTU2C/T3yG0Y02aST0LVhK7fnkSu
ELmUQNR2Ck/4bWFR+v6KrDCpayIfQKFVz0PhMQsPE6jaNI00odCncuEo9LwEiw83
JKcxVc9nDKDwX4LI61NYfhXN5TD041lv2GVGj7e1fptY6yOIpJvhAuEyFirYBPlb
xwFx51DypthuGtmtGPmuR8G7c/uoUgsaWtljCFeMAYWqBHqEa4H5Zan6LzSdgSR6
WQLxqmrxX/8qp6l7LSTeE9OviRHHs6wlEw8mfzNBjRlTav3HTQKXNVyJfrbpFAmE
v5oOrlFoVc31np7pDFg1nZ8o8Rb//arjsRzPe+oZIA==
=wanG
-----END PGP PUBLIC KEY BLOCK-----
pub 2048R/D4F10117 2015-01-01
uid Tyler Palsulich <tpalsulich@apache.org>
sig 3 D4F10117 2015-01-01 Tyler Palsulich <tpalsulich@apache.org>
sub 2048R/6137D1E6 2015-01-01
sig D4F10117 2015-01-01 Tyler Palsulich <tpalsulich@apache.org>
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1
mQENBFSlspUBCADJfADZ0ep3o/wo5sUSHDcFvmcuTRsHZDgsoHrdk83oqsQtHBZK
EQ4KeTbPTONgyNSU13kQDT6BYX3CA4AB9rqSBCI/Gghi56+I4d8mjZODY5bpnILC
vU9FyLsJNdbV8J48+oDF/5LToo5VB8QYslZ8ZZ7DJZvNmh4EovlnP9bVVS4Txk7d
mywSr1MTy5u6lb71oczK95pxO2dRwvJzLcQNTAgh3nrqk1JCLMxJoGGaKKLiGZgF
psn5nusGzOoRHeUa33V3/ms3ZYM6mS/9MmyU5P1zOUZ2Exc9C6Tps0bYbB/oztgM
4bx9NFwpeuILi4OJ/wEIJNp809CXXoYFuWlNABEBAAG0J1R5bGVyIFBhbHN1bGlj
aCA8dHBhbHN1bGljaEBhcGFjaGUub3JnPokBOAQTAQIAIgUCVKWylQIbAwYLCQgH
AwIGFQgCCQoLBBYCAwECHgECF4AACgkQiBC7GdTxARd0nQf/S2yLJ8U7P/Hix5zR
3idwrAmfDtYhUJXuEedKCw9RFnq9Q45hs1zIHVsOtnYaPvyQqSF8rY/E5LR6KJ1W
I1reFc5wKJLfmCWPAJ0Og8U4N1DOwwxESesugUT16iAXQL58xbSAzGJ1/v4L8eTj
P7maZcEdW7FLLTqJFuSfJsu8VowU8pD+v2DGHehARhDyJhhQxrX1Zb1t8vffspXw
bND1CbdB87VZJOj1apRL47nG6Qev7On+XKEXR9tHz/MWdJ/0kyNju6OLcjPJ2QFb
Q/Dwj6VYblvKq5eIYuhSNzbaI2AayZGpC9/PpFSPPWPhqa+eukUoPd3rGEG2PGBh
1shjYLkBDQRUpbKVAQgAsHL1+04Um1nOQJyeBhZ6tIa5VBPvhwk+Gccy3rWFZ66W
4byZ16Hc4tM9mU2CcPpdLYITPJaAEi+T7frXuiJwmVeAe1o9LElVAOGwbDlybv6s
wJvQqnrbwRBQLmblXeSqffAE4bpz4iU4haD2LpyjKNs5D/YS9QfhjuTKh9gGu+uP
DhXmD1hGn0UvDy9GuX6PgWijeOIUlvuZaiN8cZjsG87MLXcLLxbvCZIfrmyheF22
zSYMEvNB3r8dLTnCIt7SqbdGGyyV0kBMQWic2Epk7WzQWNsshCVPhZNkJ4oQN4Yo
AMdGyLHTJ8HvH6L8trDFQEdJrt1lIcLn43lv1AzF9QARAQABiQEfBBgBAgAJBQJU
pbKVAhsMAAoJEIgQuxnU8QEX4+oIALw2qD3KyAKKwHGK8X93woHY19tDH4zCKsQa
r2qXy7aoAsNhERkg24OUkJu0T/c/HzAQPs0RbEZUxqhzsezmJKwey+9TmNsmTcM6
52nVMa5fl7+38A54dqLOtK965ZggSroM6Qyk9lrfsJRQ/4BbNfagsXPP7Fvs1DDe
JcWAy7md7XR9MiVgSQuw040wqSzcSA5M6RCFZ9gN+G0kP1CNZ5vDz+JktV4nJZzh
/i/wH25qTePHz6Clp6mye68cqtCTKX2RF5cTlFCWIqyFYFCfrKCi3LF0bhpWqq7S
JF8xV9E4P/Msl8hqmOOocZ4LDJdw/nt1UWlUmattMLBVWdSeuu0=
=pYQ7
-----END PGP PUBLIC KEY BLOCK-----
LICENSE.txt
View file @ efa85c97
......@@ -322,3 +322,51 @@ Council.
14. This Specifications License Agreement reflects the entire agreement of the parties regarding the subject matter hereof and supersedes all prior agreements or representations regarding such matters, whether written or oral. To the extent any portion or provision of this Specifications License Agreement is found to be illegal or unenforceable, then the remaining provisions of this Specifications License Agreement will remain in full force and effect and the illegal or unenforceable provision will be construed to give it such effect as it may properly have that is consistent with the intentions of the parties.
15. This Specifications License Agreement may only be modified in writing signed by an authorized representative of the IPTC.
16. This Specifications License Agreement is governed by the law of United Kingdom, as such law is applied to contracts made and fully performed in the United Kingdom. Any disputes arising from or relating to this Specifications License Agreement will be resolved in the courts of the United Kingdom. You consent to the jurisdiction of such courts over you and covenant not to assert before such courts any objection to proceeding in such forums.
JUnRAR (https://github.com/edmund-wagner/junrar/)
JUnRAR is based on the UnRAR tool, and covered by the same license
It was formerly available from http://java-unrar.svn.sourceforge.net/
****** ***** ****** UnRAR - free utility for RAR archives
** ** ** ** ** ** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
****** ******* ****** License for use and distribution of
** ** ** ** ** ** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
** ** ** ** ** ** FREE portable version
~~~~~~~~~~~~~~~~~~~~~
The source code of UnRAR utility is freeware. This means:
1. All copyrights to RAR and the utility UnRAR are exclusively
owned by the author - Alexander Roshal.
2. The UnRAR sources may be used in any software to handle RAR
archives without limitations free of charge, but cannot be used
to re-create the RAR compression algorithm, which is proprietary.
Distribution of modified UnRAR sources in separate form or as a
part of other software is permitted, provided that it is clearly
stated in the documentation and source comments that the code may
not be used to develop a RAR (WinRAR) compatible archiver.
3. The UnRAR utility may be freely distributed. It is allowed
to distribute UnRAR inside of other software packages.
4. THE RAR ARCHIVER AND THE UnRAR UTILITY ARE DISTRIBUTED "AS IS".
NO WARRANTY OF ANY KIND IS EXPRESSED OR IMPLIED. YOU USE AT
YOUR OWN RISK. THE AUTHOR WILL NOT BE LIABLE FOR DATA LOSS,
DAMAGES, LOSS OF PROFITS OR ANY OTHER KIND OF LOSS WHILE USING
OR MISUSING THIS SOFTWARE.
5. Installing and using the UnRAR utility signifies acceptance of
these terms and conditions of the license.
6. If you don't agree with terms of the license you must remove
UnRAR files from your storage devices and cease to use the
utility.
Thank you for your interest in RAR and UnRAR. Alexander L. Roshal
Sqlite (bundled in org.xerial's sqlite-jdbc)
This product bundles Sqlite, which is in the Public Domain. For details
see: https://www.sqlite.org/copyright.html
NOTICE.txt
View file @ efa85c97
Apache Tika
Copyright 2011 The Apache Software Foundation
Copyright 2015 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
......@@ -7,9 +7,11 @@ The Apache Software Foundation (http://www.apache.org/).
Copyright 1993-2010 University Corporation for Atmospheric Research/Unidata
This software contains code derived from UCAR/Unidata's NetCDF library.
Tika-server compoment uses CDDL-licensed dependencies: jersey (http://jersey.java.net/) and
Tika-server component uses CDDL-licensed dependencies: jersey (http://jersey.java.net/) and
Grizzly (http://grizzly.java.net/)
Tika-parsers component uses CDDL/LGPL dual-licensed dependency: jhighlight (https://github.com/codelibs/jhighlight)
OpenCSV: Copyright 2005 Bytecode Pty Ltd. Licensed under the Apache License, Version 2.0
IPTC Photo Metadata descriptions Copyright 2010 International Press Telecommunications Council.
README.md 0 → 100644
View file @ efa85c97
Welcome to Apache Tika <http://tika.apache.org/>
=================================================
Apache Tika(TM) is a toolkit for detecting and extracting metadata and structured text content from various documents using existing parser libraries.
Tika is a project of the [Apache Software Foundation](http://www.apache.org).
Apache Tika, Tika, Apache, the Apache feather logo, and the Apache Tika project logo are trademarks of The Apache Software Foundation.
Getting Started
---------------
Tika is based on Java 6 and uses the [Maven 3](http://maven.apache.org) build system. To build Tika, use the following command in this directory:
mvn clean install
The build consists of a number of components, including a standalone runnable jar that you can use to try out Tika features. You can run it like this:
java -jar tika-app/target/tika-app-*.jar --help
Contributing via Github
=======================
To contribute a patch, follow these instructions (note that installing
[Hub](http://hub.github.com) is not strictly required, but is recommended).
```
0. Download and install hub.github.com
1. File JIRA issue for your fix at https://issues.apache.org/jira/browse/TIKA
- you will get issue id TIKA-xxx where xxx is the issue ID.
2. git clone http://github.com/apache/tika.git
3. cd tika
4. git checkout -b TIKA-xxx
5. edit files
6. git status (make sure it shows what files you expected to edit)
7. git add <files>
8. git commit -m “fix for TIKA-xxx contributed by <your username>”
9. git fork
10. git push -u <your git username> TIKA-xxx
11. git pull-request
```
License (see also LICENSE.txt)
------------------------------
Collective work: Copyright 2011 The Apache Software Foundation.
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
<http://www.apache.org/licenses/LICENSE-2.0>
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Apache Tika includes a number of subcomponents with separate copyright notices and license terms. Your use of these subcomponents is subject to the terms and conditions of the licenses listed in the LICENSE.txt file.
Export control
--------------
This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See <http://www.wassenaar.org/> for more information.
The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code.
The following provides more details on the included cryptographic software:
Apache Tika uses the Bouncy Castle generic encryption libraries for extracting text content and metadata from encrypted PDF files. See <http://www.bouncycastle.org/> for more details on Bouncy Castle.
Mailing Lists
-------------
Discussion about Tika takes place on the following mailing lists:
* user@tika.apache.org - About using Tika
* dev@tika.apache.org - About developing Tika
Notification on all code changes are sent to the following mailing list:
* commits@tika.apache.org
The mailing lists are open to anyone and publicly archived.
You can subscribe the mailing lists by sending a message to [LIST]-subscribe@tika.apache.org (for example user-subscribe@...). To unsubscribe, send a message to [LIST]-unsubscribe@tika.apache.org. For more instructions, send a message to [LIST]-help@tika.apache.org.
Issue Tracker
-------------
If you encounter errors in Tika or want to suggest an improvement or a new feature, please visit the [Tika issue tracker](https://issues.apache.org/jira/browse/TIKA). There you can also find the latest information on known issues and recent bug fixes and enhancements.
README.txt deleted 100644 → 0
View file @ 5be09601
=================================================
Welcome to Apache Tika <http://tika.apache.org/>
=================================================
Apache Tika(TM) is a toolkit for detecting and extracting metadata and
structured text content from various documents using existing parser
libraries.
Tika is a project of the Apache Software Foundation <http://www.apache.org/>.
Apache Tika, Tika, Apache, the Apache feather logo, and the Apache Tika
project logo are trademarks of The Apache Software Foundation.
Getting Started
===============
Tika is based on Java 5 and uses the Maven 2 <http://maven.apache.org/>
build system. To build Tika, use the following command in this directory:
mvn clean install
The build consists of a number of components, including a standalone runnable
jar that you can use to try out Tika features. You can run it like this:
java -jar tika-app/target/tika-app-*.jar --help
License (see also LICENSE.txt)
==============================
Collective work: Copyright 2011 The Apache Software Foundation.
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Apache Tika includes a number of subcomponents with separate copyright
notices and license terms. Your use of these subcomponents is subject to
the terms and conditions of the licenses listed in the LICENSE.txt file.
Export control
==============
This distribution includes cryptographic software. The country in which
you currently reside may have restrictions on the import, possession, use,
and/or re-export to another country, of encryption software. BEFORE using
any encryption software, please check your country's laws, regulations and
policies concerning the import, possession, or use, and re-export of
encryption software, to see if this is permitted. See
<http://www.wassenaar.org/> for more information.
The U.S. Government Department of Commerce, Bureau of Industry and
Security (BIS), has classified this software as Export Commodity Control
Number (ECCN) 5D002.C.1, which includes information security software using
or performing cryptographic functions with asymmetric algorithms. The form
and manner of this Apache Software Foundation distribution makes it eligible
for export under the License Exception ENC Technology Software Unrestricted
(TSU) exception (see the BIS Export Administration Regulations, Section
740.13) for both object code and source code.
The following provides more details on the included cryptographic software:
Apache Tika uses the Bouncy Castle generic encryption libraries for
extracting text content and metadata from encrypted PDF files.
See http://www.bouncycastle.org/ for more details on Bouncy Castle.
Mailing Lists
=============
Discussion about Tika takes place on the following mailing lists:
user@tika.apache.org - About using Tika
dev@tika.apache.org - About developing Tika
Notification on all code changes are sent to the following mailing list:
commits@tika.apache.org
The mailing lists are open to anyone and publicly archived.
You can subscribe the mailing lists by sending a message to
<LIST>-subscribe@tika.apache.org (for example user-subscribe@...).
To unsubscribe, send a message to <LIST>-unsubscribe@tika.apache.org.
For more instructions, send a message to <LIST>-help@tika.apache.org.
Issue Tracker
=============
If you encounter errors in Tika or want to suggest an improvement or
a new feature, please visit the Tika issue tracker at
https://issues.apache.org/jira/browse/TIKA. There you can also find the
latest information on known issues and recent bug fixes and enhancements.
pom.xml
View file @ efa85c97
......@@ -25,7 +25,7 @@
<parent>
<groupId>org.apache.tika</groupId>
<artifactId>tika-parent</artifactId>
<version>1.5</version>
<version>1.8</version>
<relativePath>tika-parent/pom.xml</relativePath>
</parent>
......@@ -36,12 +36,12 @@
<scm>
<connection>
scm:svn:http://svn.apache.org/repos/asf/tika/tags/1.5/
scm:svn:http://svn.apache.org/repos/asf/tika/tags/1.8-rc2
</connection>
<developerConnection>
scm:svn:https://svn.apache.org/repos/asf/tika/tags/1.5/
scm:svn:https://svn.apache.org/repos/asf/tika/tags/1.8-rc2
</developerConnection>
<url>http://svn.apache.org/viewvc/tika/tags/1.5/</url>
<url>http://svn.apache.org/viewvc/tika/tags/1.8-rc2</url>
</scm>
<modules>
......@@ -49,45 +49,15 @@
<module>tika-core</module>
<module>tika-parsers</module>
<module>tika-xmp</module>
<module>tika-serialization</module>
<module>tika-batch</module>
<module>tika-app</module>
<module>tika-bundle</module>
<module>tika-server</module>
<module>tika-translate</module>
<module>tika-example</module>
</modules>
<build>
<plugins>
<plugin>
<artifactId>maven-deploy-plugin</artifactId>
<configuration>
<skip>true</skip> <!-- No need to deploy the reactor -->
</configuration>
</plugin>
<plugin>
<artifactId>maven-site-plugin</artifactId>
<configuration>
<templateDirectory>src/site</templateDirectory>
<template>site.vm</template>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.rat</groupId>
<artifactId>apache-rat-plugin</artifactId>
<configuration>
<excludes>
<exclude>.*/**</exclude>
<exclude>CHANGES.txt</exclude>
<exclude>tika-dotnet/AssemblyInfo.cs</exclude>
<exclude>tika-dotnet/Tika.csproj</exclude>
<exclude>tika-dotnet/Tika.sln</exclude>
<exclude>tika-dotnet/Tika.sln.cache</exclude>
<exclude>tika-dotnet/obj/**</exclude>
<exclude>tika-dotnet/target/**</exclude>
</excludes>
</configuration>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<id>apache-release</id>
......@@ -134,7 +104,8 @@
<fileset dir="${basedir}">
<include name="CHANGES.txt" />
<include name="target/*-src.zip*" />
<include name="tika-app/target/*-${project.version}.jar*" />
<include name="tika-app/target/tika-app-${project.version}.jar*" />
<include name="tika-server/target/tika-server-${project.version}.jar*" />
</fileset>
</copy>
<checksum algorithm="MD5" fileext=".md5">
......@@ -153,17 +124,20 @@
<echo file="${basedir}/target/vote.txt">
From: ${username}@apache.org
To: dev@tika.apache.org
Subject: [VOTE] Release Apache Tika ${project.version}
user@tika.apache.org
Subject: [VOTE] Release Apache Tika ${project.version} Candidate #N
A candidate for the Tika ${project.version} release is available at:
http://people.apache.org/~${username}/tika/${project.version}/
https://dist.apache.org/repos/dist/dev/tika/
The release candidate is a zip archive of the sources in:
http://svn.apache.org/repos/asf/tika/tags/${project.version}-rcN/
http://svn.apache.org/repos/asf/tika/tags/${project.version}/
The SHA1 checksum of the archive is
${checksum}.
The SHA1 checksum of the archive is ${checksum}.
In addition, a staged maven repository is available here:
https://repository.apache.org/content/repositories/orgapachetika-.../org/apache/tika
Please vote on releasing this package as Apache Tika ${project.version}.
The vote is open for the next 72 hours and passes if a majority of at
......@@ -213,7 +187,9 @@ A release vote template has been generated for you:
</profile>
</profiles>
<description>The Apache Tika™ toolkit detects and extracts metadata and structured text content from various documents using existing parser libraries. </description>
<description>The Apache Tika™ toolkit detects and extracts metadata and structured text content from various documents
using existing parser libraries.
</description>
<organization>
<name>The Apache Software Foundation</name>
<url>http://www.apache.org</url>
......
src/site/apt/detection.apt deleted 100644 → 0
View file @ 5be09601
-----------------
Content Detection
-----------------
~~ Licensed to the Apache Software Foundation (ASF) under one or more
~~ contributor license agreements. See the NOTICE file distributed with
~~ this work for additional information regarding copyright ownership.
~~ The ASF licenses this file to You under the Apache License, Version 2.0
~~ (the "License"); you may not use this file except in compliance with
~~ the License. You may obtain a copy of the License at
~~
~~ http://www.apache.org/licenses/LICENSE-2.0
~~
~~ Unless required by applicable law or agreed to in writing, software
~~ distributed under the License is distributed on an "AS IS" BASIS,
~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~~ See the License for the specific language governing permissions and
~~ limitations under the License.
Content Detection
This page gives you information on how content and language detection
works with Apache Tika, and how to tune the behaviour of Tika.
%{toc|section=1|fromDepth=1}
* {The Detector Interface}
The
{{{./api/org/apache/tika/detect/Detector.html}org.apache.tika.detect.Detector}}
interface is the basis for most of the content type detection in Apache
Tika. All the different ways of detecting content all implement the
same common method:
---
MediaType detect(java.io.InputStream input,
Metadata metadata) throws java.io.IOException
---
The <<<detect>>> method takes the stream to inspect, and a
<<<Metadata>>> object that holds any additional information on
the content. The detector will return a
{{{./api/org/apache/tika/mime/MediaType.html}MediaType}} object describing
its best guess as to the type of the file.
In general, only two keys on the Metadata object are used by Detectors.
These are <<<Metadata.RESOURCE_NAME_KEY>>> which should hold the name
of the file (where known), and <<<Metadata.CONTENT_TYPE>>> which should
hold the advertised content type of the file (eg from a webserver or
a content repository).
* {Mime Magic Detction}
By looking for special ("magic") patterns of bytes near the start of
the file, it is often possible to detect the type of the file. For
some file types, this is a simple process. For others, typically
container based formats, the magic detection may not be enough. (More
detail on detecting container formats below)
Tika is able to make use of a a mime magic info file, in the
{{{http://www.freedesktop.org/standards/shared-mime-info}Freedesktop MIME-info}}
format to peform mime magic detection.
This is provided within Tika by
{{{./api/org/apache/tika/detect/MagicDetector.html}org.apache.tika.detect.MagicDetector}}. It is most commonly access via
{{{./api/org/apache/tika/mime/MimeTypes.html}org.apache.tika.mime.MimeTypes}},
normally sourced from the <<<tika-mimetypes.xml>>> file.
* {Resource Name Based Detection}
Where the name of the file is known, it is sometimes possible to guess
the file type from the name or extension. Within the
<<<tika-mimetypes.xml>>> file is a list of patterns which are used to
identify the type from the filename.
However, because files may be renamed, this method of detection is quick
but not always as accurate.
This is provided within Tika by
{{{./api/org/apache/tika/detect/NameDetector.html}org.apache.tika.detect.NameDetector}}.
* {Known Content Type "Detection}
Sometimes, the mime type for a file is already known, such as when
downloading from a webserver, or when retrieving from a content store.
This information can be used by detectors, such as
{{{./api/org/apache/tika/mime/MimeTypes.html}org.apache.tika.mime.MimeTypes}},
* {The default Mime Types Detector}
By default, the mime type detection in Tika is provided by
{{{./api/org/apache/tika/mime/MimeTypes.html}org.apache.tika.mime.MimeTypes}}.
This detector makes use of <<<tika-mimetypes.xml>>> to power
magic based and filename based detection.
Firstly, magic based detection is used on the start of the file.
If the file is an XML file, then the start of the XML is processed
to look for root elements. Next, if available, the filename
(from <<<Metadata.RESOURCE_NAME_KEY>>>) is
then used to improve the detail of the detection, such as when magic
detects a text file, and the filename hints it's really a CSV. Finally,
if available, the supplied content type (from <<<Metadata.CONTENT_TYPE>>>)
is used to further refine the type.
* {Container Aware Detection}
Several common file formats are actually held within a common container
format. One example is the PowerPoint .ppt and Word .doc formats, which
are both held within an OLE2 container. Another is Apple iWork formats,
which are actually a series of XML files within a Zip file.
Using magic detection, it is easy to spot that a given file is an OLE2
document, or a Zip file. Using magic detection alone, it is very difficult
(and often impossible) to tell what kind of file lives inside the container.
For some use cases, speed is important, so having a quick way to know the
container type is sufficient. For other cases however, you don't mind
spending a bit of time (and memory!) processing the container to get a
more accurate answer on its contents. For these cases, a container
aware detector should be used.
Tika provides a wrapping detector in the parsers bundle, of
{{{./api/org/apache/tika/detect/ContainerAwareDetector.html}org.apache.tika.detect.ContainerAwareDetector}}.
This detector will check for certain known containers, and if found,
will open them and detect the appropriate type based on the contents.
If the file isn't a known container, it will fall back to another
detector for the answer (most commonly the default
<<<MimeTypes>>> detector)
Because this detector needs to read the whole file to process the
container, it must be used with a
{{{./api/org/apache/tika/io/TikaInputStream.html}org.apache.tika.io.TikaInputStream}}.
If called with a regular <<<InputStream>>>, then all work will be done
by the fallback detector.
For more information on container formats and Tika, see
{{{http://wiki.apache.org/tika/MetadataDiscussion}}}
* {Language Detection}
Tika is able to help identify the language of a piece of text, which
is useful when extracting text from document formats which do not include
language information in their metadata.
The language detection is provided by
{{{./api/org/apache/tika/language/LanguageIdentifier.html}org.apache.tika.language.LanguageIdentifier}}
src/site/apt/formats.apt deleted 100644 → 0
View file @ 5be09601
--------------------------
Supported Document Formats
--------------------------
~~ Licensed to the Apache Software Foundation (ASF) under one or more
~~ contributor license agreements. See the NOTICE file distributed with
~~ this work for additional information regarding copyright ownership.
~~ The ASF licenses this file to You under the Apache License, Version 2.0
~~ (the "License"); you may not use this file except in compliance with
~~ the License. You may obtain a copy of the License at
~~
~~ http://www.apache.org/licenses/LICENSE-2.0
~~
~~ Unless required by applicable law or agreed to in writing, software
~~ distributed under the License is distributed on an "AS IS" BASIS,
~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~~ See the License for the specific language governing permissions and
~~ limitations under the License.
Supported Document Formats
This page lists all the document formats supported by Apache Tika 0.6.
Follow the links to the various parser class javadocs for more detailed
information about each document format and how it is parsed by Tika.
%{toc|section=1|fromDepth=1}
* {HyperText Markup Language}
The HyperText Markup Language (HTML) is the lingua franca of the web.
Tika uses the {{{http://home.ccil.org/~cowan/XML/tagsoup/}TagSoup}}
library to support virtually any kind of HTML found on the web.
The output from the
{{{api/org/apache/tika/parser/html/HtmlParser.html}HtmlParser}} class
is guaranteed to be well-formed and valid XHTML, and various heuristics
are used to prevent things like inline scripts from cluttering the
extracted text content.
* {XML and derived formats}
The Extensible Markup Language (XML) format is a generic format that can
be used for all kinds of content. Tika has custom parsers for some widely
used XML vocabularies like XHTML, OOXML and ODF, but the default
{{{api/org/apache/tika/parser/xml/DcXMLParser.html}DcXMLParser}}
class simply extracts the text content of the document and ignores any XML
structure. The only exception to this rule are Dublin Core metadata
elements that are used for the document metadata.
* {Microsoft Office document formats}
Microsoft Office and some related applications produce documents in the
generic OLE 2 Compound Document and Office Open XML (OOXML) formats. The
older OLE 2 format was introduced in Microsoft Office version 97 and was
the default format until Office version 2007 and the new XML-based
OOXML format. The
{{{api/org/apache/tika/parser/microsoft/OfficeParser.html}OfficeParser}}
and
{{{api/org/apache/tika/parser/microsoft/ooxml/OOXMLParser.html}OOXMLParser}}
classes use {{{http://poi.apache.org/}Apache POI}} libraries to support
text and metadata extraction from both OLE2 and OOXML documents.
* {OpenDocument Format}
The OpenDocument format (ODF) is used most notably as the default format
of the OpenOffice.org office suite. The
{{{api/org/apache/tika/parser/odf/OpenDocumentParser.html}OpenDocumentParser}}
class supports this format and the earlier OpenOffice 1.0 format on which
ODF is based.
* {Portable Document Format}
The {{{api/org/apache/tika/parser/pdf/PDFParser.html}PDFParser}} class
parsers Portable Document Format (PDF) documents using the
{{{http://pdfbox.apache.org/}Apache PDFBox}} library.
* {Electronic Publication Format}
The {{{api/org/apache/tika/parser/epub/EpubParser.html}EpubParser}} class
supports the Electronic Publication Format (EPUB) used for many digital
books.
* {Rich Text Format}
The {{{api/org/apache/tika/parser/rtf/RTFParser.html}RTFParser}} class
uses the standard javax.swing.text.rtf feature to extract text content
from Rich Text Format (RTF) documents.
* {Compression and packaging formats}
Tika uses the {{{http://commons.apache.org/compress/}Commons Compress}}
library to support various compression and packaging formats. The
{{{api/org/apache/tika/parser/pkg/PackageParser.html}PackageParser}}
class and its subclasses first parse the top level compression or
packaging format and then pass the unpacked document streams to a
second parsing stage using the parser instance specified in the
parse context.
* {Text formats}
Extracting text content from plain text files seems like a simple task
until you start thinking of all the possible character encodings. The
{{{api/org/apache/tika/parser/txt/TXTParser.html}TXTParser}} class uses
encoding detection code from the {{{http://site.icu-project.org/}ICU}}
project to automatically detect the character encoding of a text document.
* {Audio formats}
Tika can detect several common audio formats and extract metadata
from them. Even text extraction is supported for some audio files that
contain lyrics or other textual content. The
{{{api/org/apache/tika/parser/audio/AudioParser.html}AudioParser}}
and {{{api/org/apache/tika/parser/audio/MidiParser.html}MidiParser}}
classes use standard javax.sound features to process simple audio
formats, and the
{{{api/org/apache/tika/parser/mp3/Mp3Parser.html}Mp3Parser}} class
adds support for the widely used MP3 format.
* {Image formats}
The {{{api/org/apache/tika/parser/image/ImageParser.html}ImageParser}}
class uses the standard javax.imageio feature to extract simple metadata
from image formats supported by the Java platform. More complex image
metadata is available through the
{{{api/org/apache/tika/parser/jpeg/JpegParser.html}JpegParser}} class
that uses the metadata-extractor library to supports Exif metadata
extraction from Jpeg images.
* {Video formats}
Currently Tika only supports the Flash video format using a simple
parsing algorithm implemented in the
{{{api/org/apache/tika/parser/flv/FLVParser}FLVParser}} class.
* {Java class files and archives}
The {{{api/org/apache/tika/parser/asm/ClassParser}ClassParser}} class
extracts class names and method signatures from Java class files, and
the {{{api/org/apache/tika/parser/pkg/ZipParser.html}ZipParser}} class
supports also jar archives.
* {The mbox format}
The {{{api/org/apache/tika/parser/mbox/MboxParser.html}MboxParser}} can
extract email messages from the mbox format used by many email archives
and Unix-style mailboxes.
src/site/apt/gettingstarted.apt deleted 100644 → 0
View file @ 5be09601
--------------------------------
Getting Started with Apache Tika
--------------------------------
~~ Licensed to the Apache Software Foundation (ASF) under one or more
~~ contributor license agreements. See the NOTICE file distributed with
~~ this work for additional information regarding copyright ownership.
~~ The ASF licenses this file to You under the Apache License, Version 2.0
~~ (the "License"); you may not use this file except in compliance with
~~ the License. You may obtain a copy of the License at
~~
~~ http://www.apache.org/licenses/LICENSE-2.0
~~
~~ Unless required by applicable law or agreed to in writing, software
~~ distributed under the License is distributed on an "AS IS" BASIS,
~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~~ See the License for the specific language governing permissions and
~~ limitations under the License.
Getting Started with Apache Tika
This document describes how to build Apache Tika from sources and
how to start using Tika in an application.
Getting and building the sources
To build Tika from sources you first need to either
{{{../download.html}download}} a source release or
{{{../source-repository.html}checkout}} the latest sources from
version control.
Once you have the sources, you can build them using the
{{{http://maven.apache.org/}Maven 2}} build system. Executing the
following command in the base directory will build the sources
and install the resulting artifacts in your local Maven repository.
---
mvn install
---
See the Maven documentation for more information about the available
build options.
Note that you need Java 5 or higher to build Tika.
Build artifacts
The Tika build consists of a number of components and produces
the following main binaries:
[tika-core/target/tika-core-*.jar]
Tika core library. Contains the core interfaces and classes of Tika,
but none of the parser implementations. Depends only on Java 5.
[tika-parsers/target/tika-parsers-*.jar]
Tika parsers. Collection of classes that implement the Tika Parser
interface based on various external parser libraries.
[tika-app/target/tika-app-*.jar]
Tika application. Combines the above components and all the external
parser libraries into a single runnable jar with a GUI and a command
line interface.
[tika-bundle/target/tika-bundle-*.jar]
Tika bundle. An OSGi bundle that combines tika-parsers with non-OSGified
parser libraries to make them easy to deploy in an OSGi environment.
Using Tika as a Maven dependency
The core library, tika-core, contains the key interfaces and classes of Tika
and can be used by itself if you don't need the full set of parsers from
the tika-parsers component. The tika-core dependency looks like this:
---
<dependency>
<groupId>org.apache.tika</groupId>
<artifactId>tika-core</artifactId>
<version>...</version>
</dependency>
---
If you want to use Tika to parse documents (instead of simply detecting
document types, etc.), you'll want to depend on tika-parsers instead:
---
<dependency>
<groupId>org.apache.tika</groupId>
<artifactId>tika-parsers</artifactId>
<version>...</version>
</dependency>
---
Note that adding this dependency will introduce a number of
transitive dependencies to your project, including one on tika-core.
You need to make sure that these dependencies won't conflict with your
existing project dependencies. You can use the following command in
the tika-parsers directory to get a full listing of all the dependencies.
---
$ mvn dependency:tree | grep :compile
---
Using Tika in an Ant project
Unless you use a dependency manager tool like
{{{http://ant.apache.org/ivy/}Apache Ivy}}, the easiest way to use
Tika is to include either the tika-core or the tika-app jar in your
classpath, depending on whether you want just the core functionality
or also all the parser implementations.
---
<classpath>
... <!-- your other classpath entries -->
<!-- either: -->
<pathelement location="path/to/tika-core-${tika.version}.jar"/>
<!-- or: -->
<pathelement location="path/to/tika-app-${tika.version}.jar"/>
</classpath>
---
Using Tika as a command line utility
The Tika application jar (tika-app-*.jar) can be used as a command
line utility for extracting text content and metadata from all sorts of
files. This runnable jar contains all the dependencies it needs, so
you don't need to worry about classpath settings to run it.
The usage instructions are shown below.
---
usage: java -jar tika-app.jar [option...] [file|port...]
Options:
-? or --help Print this usage message
-v or --verbose Print debug level messages
-V or --version Print the Apache Tika version number
-g or --gui Start the Apache Tika GUI
-s or --server Start the Apache Tika server
-f or --fork Use Fork Mode for out-of-process extraction
-x or --xml Output XHTML content (default)
-h or --html Output HTML content
-t or --text Output plain text content
-T or --text-main Output plain text content (main content only)
-m or --metadata Output only metadata
-j or --json Output metadata in JSON
-y or --xmp Output metadata in XMP
-l or --language Output only language
-d or --detect Detect document type
-eX or --encoding=X Use output encoding X
-pX or --password=X Use document password X
-z or --extract Extract all attachements into current directory
--extract-dir=<dir> Specify target directory for -z
-r or --pretty-print For XML and XHTML outputs, adds newlines and
whitespace, for better readability
--create-profile=X
Create NGram profile, where X is a profile name
--list-parsers
List the available document parsers
--list-parser-details
List the available document parsers, and their supported mime types
--list-detectors
List the available document detectors
--list-met-models
List the available metadata models, and their supported keys
--list-supported-types
List all known media types and related information
Description:
Apache Tika will parse the file(s) specified on the
command line and output the extracted text content
or metadata to standard output.
Instead of a file name you can also specify the URL
of a document to be parsed.
If no file name or URL is specified (or the special
name "-" is used), then the standard input stream
is parsed. If no arguments were given and no input
data is available, the GUI is started instead.
- GUI mode
Use the "--gui" (or "-g") option to start the
Apache Tika GUI. You can drag and drop files from
a normal file explorer to the GUI window to extract
text content and metadata from the files.
- Server mode
Use the "--server" (or "-s") option to start the
Apache Tika server. The server will listen to the
ports you specify as one or more arguments.
---
You can also use the jar as a component in a Unix pipeline or
as an external tool in many scripting languages.
---
# Check if an Internet resource contains a specific keyword
curl http://.../document.doc \
| java -jar tika-app.jar --text \
| grep -q keyword
---
src/site/apt/index.apt deleted 100644 → 0
View file @ 5be09601
---------------
Apache Tika 1.3
---------------
~~ Licensed to the Apache Software Foundation (ASF) under one or more
~~ contributor license agreements. See the NOTICE file distributed with
~~ this work for additional information regarding copyright ownership.
~~ The ASF licenses this file to You under the Apache License, Version 2.0
~~ (the "License"); you may not use this file except in compliance with
~~ the License. You may obtain a copy of the License at
~~
~~ http://www.apache.org/licenses/LICENSE-2.0
~~
~~ Unless required by applicable law or agreed to in writing, software
~~ distributed under the License is distributed on an "AS IS" BASIS,
~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~~ See the License for the specific language governing permissions and
~~ limitations under the License.
Apache Tika 1.3
The most notable changes in Tika 1.3 over the previous release are:
* TBD
The following people have contributed to Tika 1.3 by submitting or
commenting on the issues resolved in this release:
* TBD
See TBD for more details on these contributions.
src/site/apt/parser.apt deleted 100644 → 0
View file @ 5be09601
--------------------
The Parser interface
--------------------
~~ Licensed to the Apache Software Foundation (ASF) under one or more
~~ contributor license agreements. See the NOTICE file distributed with
~~ this work for additional information regarding copyright ownership.
~~ The ASF licenses this file to You under the Apache License, Version 2.0
~~ (the "License"); you may not use this file except in compliance with
~~ the License. You may obtain a copy of the License at
~~
~~ http://www.apache.org/licenses/LICENSE-2.0
~~
~~ Unless required by applicable law or agreed to in writing, software
~~ distributed under the License is distributed on an "AS IS" BASIS,
~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~~ See the License for the specific language governing permissions and
~~ limitations under the License.
The Parser interface
The
{{{api/org/apache/tika/parser/Parser.html}org.apache.tika.parser.Parser}}
interface is the key concept of Apache Tika. It hides the complexity of
different file formats and parsing libraries while providing a simple and
powerful mechanism for client applications to extract structured text
content and metadata from all sorts of documents. All this is achieved
with a single method:
---
void parse(
InputStream stream, ContentHandler handler, Metadata metadata,
ParseContext context) throws IOException, SAXException, TikaException;
---
The <<<parse>>> method takes the document to be parsed and related metadata
as input and outputs the results as XHTML SAX events and extra metadata.
The parse context argument is used to specify context information (like
the current local) that is not related to any individual document.
The main criteria that lead to this design were:
[Streamed parsing] The interface should require neither the client
application nor the parser implementation to keep the full document
content in memory or spooled to disk. This allows even huge documents
to be parsed without excessive resource requirements.
[Structured content] A parser implementation should be able to
include structural information (headings, links, etc.) in the extracted
content. A client application can use this information for example to
better judge the relevance of different parts of the parsed document.
[Input metadata] A client application should be able to include metadata
like the file name or declared content type with the document to be
parsed. The parser implementation can use this information to better
guide the parsing process.
[Output metadata] A parser implementation should be able to return
document metadata in addition to document content. Many document
formats contain metadata like the name of the author that may be useful
to client applications.
[Context sensitivity] While the default settings and behaviour of Tika
parsers should work well for most use cases, there are still situations
where more fine-grained control over the parsing process is desirable.
It should be easy to inject such context-specific information to the
parsing process without breaking the layers of abstraction.
[]
These criteria are reflected in the arguments of the <<<parse>>> method.
* Document input stream
The first argument is an
{{{http://java.sun.com/j2se/1.5.0/docs/api/java/io/InputStream.html}InputStream}}
for reading the document to be parsed.
If this document stream can not be read, then parsing stops and the thrown
{{{http://java.sun.com/j2se/1.5.0/docs/api/java/io/IOException.html}IOException}}
is passed up to the client application. If the stream can be read but
not parsed (for example if the document is corrupted), then the parser
throws a {{{api/org/apache/tika/exception/TikaException.html}TikaException}}.
The parser implementation will consume this stream but <will not close it>.
Closing the stream is the responsibility of the client application that
opened it in the first place. The recommended pattern for using streams
with the <<<parse>>> method is:
---
InputStream stream = ...; // open the stream
try {
parser.parse(stream, ...); // parse the stream
} finally {
stream.close(); // close the stream
}
---
Some document formats like the OLE2 Compound Document Format used by
Microsoft Office are best parsed as random access files. In such cases the
content of the input stream is automatically spooled to a temporary file
that gets removed once parsed. A future version of Tika may make it possible
to avoid this extra file if the input document is already a file in the
local file system. See
{{{https://issues.apache.org/jira/browse/TIKA-153}TIKA-153}} for the status
of this feature request.
* XHTML SAX events
The parsed content of the document stream is returned to the client
application as a sequence of XHTML SAX events. XHTML is used to express
structured content of the document and SAX events enable streamed
processing. Note that the XHTML format is used here only to convey
structural information, not to render the documents for browsing!
The XHTML SAX events produced by the parser implementation are sent to a
{{{http://java.sun.com/j2se/1.5.0/docs/api/org/xml/sax/ContentHandler.html}ContentHandler}}
instance given to the <<<parse>>> method. If this the content handler
fails to process an event, then parsing stops and the thrown
{{{http://java.sun.com/j2se/1.5.0/docs/api/org/xml/sax/SAXException.html}SAXException}}
is passed up to the client application.
The overall structure of the generated event stream is (with indenting
added for clarity):
---
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>...</title>
</head>
<body>
...
</body>
</html>
---
Parser implementations typically use the
{{{apidocs/org/apache/tika/sax/XHTMLContentHandler.html}XHTMLContentHandler}}
utility class to generate the XHTML output.
Dealing with the raw SAX events can be a bit complex, so Apache Tika
comes with a number of utility classes that can be used to process and
convert the event stream to other representations.
For example, the
{{{api/org/apache/tika/sax/BodyContentHandler.html}BodyContentHandler}}
class can be used to extract just the body part of the XHTML output and
feed it either as SAX events to another content handler or as characters
to an output stream, a writer, or simply a string. The following code
snippet parses a document from the standard input stream and outputs the
extracted text content to standard output:
---
ContentHandler handler = new BodyContentHandler(System.out);
parser.parse(System.in, handler, ...);
---
Another useful class is
{{{api/org/apache/tika/parser/ParsingReader.html}ParsingReader}} that
uses a background thread to parse the document and returns the extracted
text content as a character stream:
---
InputStream stream = ...; // the document to be parsed
Reader reader = new ParsingReader(parser, stream, ...);
try {
...; // read the document text using the reader
} finally {
reader.close(); // the document stream is closed automatically
}
---
* Document metadata
The third argument to the <<<parse>>> method is used to pass document
metadata both in and out of the parser. Document metadata is expressed
as an {{{api/org/apache/tika/metadata/Metadata.html}Metadata}} object.
The following are some of the more interesting metadata properties:
[Metadata.RESOURCE_NAME_KEY] The name of the file or resource that contains
the document.
A client application can set this property to allow the parser to use
file name heuristics to determine the format of the document.
The parser implementation may set this property if the file format
contains the canonical name of the file (for example the Gzip format
has a slot for the file name).
[Metadata.CONTENT_TYPE] The declared content type of the document.
A client application can set this property based on for example a HTTP
Content-Type header. The declared content type may help the parser to
correctly interpret the document.
The parser implementation sets this property to the content type according
to which the document was parsed.
[Metadata.TITLE] The title of the document.
The parser implementation sets this property if the document format
contains an explicit title field.
[Metadata.AUTHOR] The name of the author of the document.
The parser implementation sets this property if the document format
contains an explicit author field.
[]
Note that metadata handling is still being discussed by the Tika development
team, and it is likely that there will be some (backwards incompatible)
changes in metadata handling before Tika 1.0.
* Parse context
The final argument to the <<<parse>>> method is used to inject
context-specific information to the parsing process. This is useful
for example when dealing with locale-specific date and number formats
in Microsoft Excel spreadsheets. Another important use of the parse
context is passing in the delegate parser instance to be used by
two-phase parsers like the
{{{api/org/apache/parser/pkg/PackageParser.html}PackageParser}} subclasses.
Some parser classes allow customization of the parsing process through
strategy objects in the parse context.
* Parser implementations
Apache Tika comes with a number of parser classes for parsing
{{{formats.html}various document formats}}. You can also extend Tika
with your own parsers, and of course any contributions to Tika are
warmly welcome.
The goal of Tika is to reuse existing parser libraries like
{{{http://www.pdfbox.org/}PDFBox}} or
{{{http://poi.apache.org/}Apache POI}} as much as possible, and so most
of the parser classes in Tika are adapters to such external libraries.
Tika also contains some general purpose parser implementations that are
not targeted at any specific document formats. The most notable of these
is the {{{apidocs/org/apache/tika/parser/AutoDetectParser.html}AutoDetectParser}}
class that encapsulates all Tika functionality into a single parser that
can handle any types of documents. This parser will automatically determine
the type of the incoming document based on various heuristics and will then
parse the document accordingly.
src/site/apt/parser_guide.apt deleted 100644 → 0
View file @ 5be09601
--------------------------------------------
Get Tika parsing up and running in 5 minutes
--------------------------------------------
Arturo Beltran
--------------------------------------------
~~ Licensed to the Apache Software Foundation (ASF) under one or more
~~ contributor license agreements. See the NOTICE file distributed with
~~ this work for additional information regarding copyright ownership.
~~ The ASF licenses this file to You under the Apache License, Version 2.0
~~ (the "License"); you may not use this file except in compliance with
~~ the License. You may obtain a copy of the License at
~~
~~ http://www.apache.org/licenses/LICENSE-2.0
~~
~~ Unless required by applicable law or agreed to in writing, software
~~ distributed under the License is distributed on an "AS IS" BASIS,
~~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~~ See the License for the specific language governing permissions and
~~ limitations under the License.
Get Tika parsing up and running in 5 minutes
This page is a quick start guide showing how to add a new parser to Apache Tika.
Following the simple steps listed below your new parser can be running in only 5 minutes.
%{toc|section=1|fromDepth=1}
* {Getting Started}
The {{{gettingstarted.html}Getting Started}} document describes how to
build Apache Tika from sources and how to start using Tika in an application. Pay close attention
and follow the instructions in the "Getting and building the sources" section.
* {Add your MIME-Type}
You first need to modify {{{http://svn.apache.org/repos/asf/tika/trunk/tika-core/src/main/resources/org/apache/tika/mime/tika-mimetypes.xml}tika-core/src/main/resources/org/apache/tika/mime/tika-mimetypes.xml}}
in order to Tika can map the file extension with its MIME-Type. You should add something like this:
---
<mime-type type="application/hello">
<glob pattern="*.hi"/>
</mime-type>
---
* {Create your Parser class}
Now, you need to create your new parser. This is a class that must implement the Parser interface
offered by Tika. A very simple Tika Parser looks like this:
---
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*
* @Author: Arturo Beltran
*/
package org.apache.tika.parser.hello;
import java.io.IOException;
import java.io.InputStream;
import java.util.Collections;
import java.util.Set;
import org.apache.tika.exception.TikaException;
import org.apache.tika.metadata.Metadata;
import org.apache.tika.mime.MediaType;
import org.apache.tika.parser.ParseContext;
import org.apache.tika.parser.Parser;
import org.apache.tika.sax.XHTMLContentHandler;
import org.xml.sax.ContentHandler;
import org.xml.sax.SAXException;
public class HelloParser implements Parser {
private static final Set<MediaType> SUPPORTED_TYPES = Collections.singleton(MediaType.application("hello"));
public static final String HELLO_MIME_TYPE = "application/hello";
public Set<MediaType> getSupportedTypes(ParseContext context) {
return SUPPORTED_TYPES;
}
public void parse(
InputStream stream, ContentHandler handler,
Metadata metadata, ParseContext context)
throws IOException, SAXException, TikaException {
metadata.set(Metadata.CONTENT_TYPE, HELLO_MIME_TYPE);
metadata.set("Hello", "World");
XHTMLContentHandler xhtml = new XHTMLContentHandler(handler, metadata);
xhtml.startDocument();
xhtml.endDocument();
}
/**
* @deprecated This method will be removed in Apache Tika 1.0.
*/
public void parse(
InputStream stream, ContentHandler handler, Metadata metadata)
throws IOException, SAXException, TikaException {
parse(stream, handler, metadata, new ParseContext());
}
}
---
Pay special attention to the definition of the SUPPORTED_TYPES static class
field in the parser class that defines what MIME-Types it supports.
Is in the "parse" method where you will do all your work. This is, extract
the information of the resource and then set the metadata.
* {List the new parser}
Finally, you should explicitly tell the AutoDetectParser to include your new
parser. This step is only needed if you want to use the AutoDetectParser functionality.
If you figure out the correct parser in a different way, it isn't needed.
List your new parser in:
{{{http://svn.apache.org/repos/asf/tika/trunk/tika-parsers/src/main/resources/META-INF/services/org.apache.tika.parser.Parser}tika-parsers/src/main/resources/META-INF/services/org.apache.tika.parser.Parser}}
src/site/resources/css/site.css deleted 100644 → 0
View file @ 5be09601
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*/
#search {
position: relative;
right: 10px;
width: 100%;
font-size: 70%;
white-space: nowrap;
text-align: right;
z-index:0;
bottom: -1px; /* compensate for IE rendering issue */
}
#bookpromo {
position: relative;
top: 35px;
left: 10px;
width: 100%;
white-space: nowrap;
text-align: center;
z-index:0;
bottom: -1px;
}
#searchform {
}
body {
margin: 0px;
padding: 0px 0px 10px 0px;
}
/* From maven-theme.css */
body, td, select, input, li {
font-family: Verdana, Helvetica, Arial, sans-serif;
font-size: 13px;
}
code{
font-family: Courier, monospace;
font-size: 13px;
}
a {
text-decoration: none;
}
a:link {
color:#36a;
}
a:visited {
color:#47a;
}
a:active, a:hover {
color:#69c;
}
#legend li.externalLink {
background: url(../images/external.png) left top no-repeat;
padding-left: 18px;
}
a.externalLink, a.externalLink:link, a.externalLink:visited, a.externalLink:active, a.externalLink:hover {
background: url(../images/external.png) right center no-repeat;
padding-right: 18px;
}
#legend li.newWindow {
background: url(../images/newwindow.png) left top no-repeat;
padding-left: 18px;
}
a.newWindow, a.newWindow:link, a.newWindow:visited, a.newWindow:active, a.newWindow:hover {
background: url(../images/newwindow.png) right center no-repeat;
padding-right: 18px;
}
h2 {
padding: 4px 4px 4px 6px;
border: 1px solid #999;
color: #900;
background-color: #ddd;
font-weight:900;
font-size: x-large;
}
h3 {
padding: 4px 4px 4px 6px;
border: 1px solid #aaa;
color: #900;
background-color: #eee;
font-weight: normal;
font-size: large;
}
h4 {
padding: 4px 4px 4px 6px;
border: 1px solid #bbb;
color: #900;
background-color: #fff;
font-weight: normal;
font-size: large;
}
h5 {
padding: 4px 4px 4px 6px;
color: #900;
font-size: normal;
}
p {
line-height: 1.3em;
font-size: small;
}
#breadcrumbs {
border-top: 1px solid #aaa;
border-bottom: 1px solid #aaa;
background-color: #ccc;
}
#leftColumn {
margin: 10px 0 0 5px;
border: 1px solid #999;
background-color: #eee;
}
#navcolumn h5 {
font-size: smaller;
border-bottom: 1px solid #aaaaaa;
padding-top: 2px;
color: #000;
}
table.bodyTable th {
color: white;
background-color: #bbb;
text-align: left;
font-weight: bold;
}
table.bodyTable th, table.bodyTable td {
font-size: 1em;
}
table.bodyTable tr.a {
background-color: #ddd;
}
table.bodyTable tr.b {
background-color: #eee;
}
.source {
border: 1px solid #999;
}
dl {
padding: 4px 4px 4px 6px;
border: 1px solid #aaa;
background-color: #ffc;
}
dt {
color: #900;
}
#organizationLogo img, #projectLogo img, #projectLogo span{
margin: 8px;
}
#banner {
border-bottom: 1px solid #fff;
}
.errormark, .warningmark, .donemark, .infomark {
background: url(../images/icon_error_sml.gif) no-repeat;
}
.warningmark {
background-image: url(../images/icon_warning_sml.gif);
}
.donemark {
background-image: url(../images/icon_success_sml.gif);
}
.infomark {
background-image: url(../images/icon_info_sml.gif);
}
/* From maven-base.css */
img {
border:none;
}
table {
padding:0px;
width: 100%;
margin-left: -2px;
margin-right: -2px;
}
acronym {
cursor: help;
border-bottom: 1px dotted #feb;
}
table.bodyTable th, table.bodyTable td {
padding: 2px 4px 2px 4px;
vertical-align: top;
}
div.clear{
clear:both;
visibility: hidden;
}
div.clear hr{
display: none;
}
#bannerLeft, #bannerRight {
font-size: xx-large;
font-weight: bold;
}
#bannerLeft img, #bannerRight img {
margin: 0px;
}
.xleft, #bannerLeft img {
float:left;
text-shadow: #7CFC00 1px 1px 1px;
}
.xright, #bannerRight {
float:right;
text-shadow: #7CFC00 1px 1px 1px;
}
#banner {
padding: 0px;
}
#banner img {
border: none;
}
#breadcrumbs {
padding: 3px 10px 3px 10px;
}
#leftColumn {
width: 170px;
float:left;
overflow: auto;
}
#bodyColumn {
margin-right: 1.5em;
margin-left: 197px;
}
#legend {
padding: 8px 0 8px 0;
}
#navcolumn {
padding: 8px 4px 0 8px;
}
#navcolumn h5 {
margin: 0;
padding: 0;
font-size: small;
}
#navcolumn ul {
margin: 0;
padding: 0;
font-size: small;
}
#navcolumn li {
list-style-type: none;
background-image: none;
background-repeat: no-repeat;
background-position: 0 0.4em;
padding-left: 16px;
list-style-position: outside;
line-height: 1.2em;
font-size: smaller;
}
#navcolumn li.expanded {
background-image: url(../images/expanded.gif);
}
#navcolumn li.collapsed {
background-image: url(../images/collapsed.gif);
}
#navcolumn img {
margin-top: 10px;
margin-bottom: 3px;
}
#search img {
margin: 0px;
display: block;
}
#search #q, #search #btnG {
border: 1px solid #999;
margin-bottom:10px;
}
#search form {
margin: 0px;
}
#lastPublished {
font-size: x-small;
}
.navSection {
margin-bottom: 2px;
padding: 8px;
}
.navSectionHead {
font-weight: bold;
font-size: x-small;
}
.section {
padding: 4px;
}
#footer p {
padding: 3px 10px 3px 10px;
font-size: x-small;
text-align: center;
}
.source {
padding: 12px;
margin: 1em 7px 1em 7px;
}
.source pre {
margin: 0px;
padding: 0px;
}
src/site/resources/tika.svg deleted 100644 → 0
View file @ 5be09601
This diff is collapsed.
src/site/resources/tikaNoText.svg deleted 100644 → 0
View file @ 5be09601
This diff is collapsed.