Modified: tika/site/src/site/apt/1.1/formats.apt URL: http://svn.apache.org/viewvc/tika/site/src/site/apt/1.1/formats.apt?rev=1381198&r1=1381197&r2=1381198&view=diff ============================================================================== --- tika/site/src/site/apt/1.1/formats.apt (original) +++ tika/site/src/site/apt/1.1/formats.apt Wed Sep 5 14:31:06 2012 @@ -31,7 +31,7 @@ Supported Document Formats 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 + {{{./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. @@ -41,7 +41,7 @@ Supported Document 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}} + {{{./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. @@ -53,9 +53,9 @@ Supported Document Formats 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}} + {{{./api/org/apache/tika/parser/microsoft/OfficeParser.html}OfficeParser}} and - {{{api/org/apache/tika/parser/microsoft/ooxml/OOXMLParser.html}OOXMLParser}} + {{{./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. @@ -63,25 +63,25 @@ Supported Document Formats 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}} + {{{./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 + 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 + 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 + 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. @@ -89,7 +89,7 @@ Supported Document 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}} + {{{./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 @@ -99,7 +99,7 @@ Supported Document 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 + {{{./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. @@ -108,20 +108,20 @@ Supported Document 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}} + {{{./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 + {{{./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}} + 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 + {{{./api/org/apache/tika/parser/jpeg/JpegParser.html}JpegParser}} class that uses the metadata-extractor library to supports Exif metadata extraction from Jpeg images. @@ -129,17 +129,17 @@ Supported Document 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. + {{{./api/org/apache/tika/parser/flv/FLVParser}FLVParser}} class. * {Java class files and archives} - The {{{api/org/apache/tika/parser/asm/ClassParser}ClassParser}} class + 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 + 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 + 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.
Modified: tika/site/src/site/apt/1.1/index.apt URL: http://svn.apache.org/viewvc/tika/site/src/site/apt/1.1/index.apt?rev=1381198&r1=1381197&r2=1381198&view=diff ============================================================================== --- tika/site/src/site/apt/1.1/index.apt (original) +++ tika/site/src/site/apt/1.1/index.apt Wed Sep 5 14:31:06 2012 @@ -127,7 +127,7 @@ Apache Tika 1.1 * Geoff Jarrad - * Jan H¿ydahl + * Jan H\u00F8ydahl * Jerome Lacoste @@ -163,7 +163,7 @@ Apache Tika 1.1 * Ray Gauss II - * Stephan Mhlstrasser + * Stephan M\u00FChlstrasser * Swapna Vuppala Modified: tika/site/src/site/apt/1.1/parser.apt URL: http://svn.apache.org/viewvc/tika/site/src/site/apt/1.1/parser.apt?rev=1381198&r1=1381197&r2=1381198&view=diff ============================================================================== --- tika/site/src/site/apt/1.1/parser.apt (original) +++ tika/site/src/site/apt/1.1/parser.apt Wed Sep 5 14:31:06 2012 @@ -20,7 +20,7 @@ The Parser interface The - {{{api/org/apache/tika/parser/Parser.html}org.apache.tika.parser.Parser}} + {{{./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 @@ -79,7 +79,7 @@ void parse( {{{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}}. + 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 @@ -134,7 +134,7 @@ try { --- Parser implementations typically use the - {{{apidocs/org/apache/tika/sax/XHTMLContentHandler.html}XHTMLContentHandler}} + {{{./api/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 @@ -142,7 +142,7 @@ try { convert the event stream to other representations. For example, the - {{{api/org/apache/tika/sax/BodyContentHandler.html}BodyContentHandler}} + {{{./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 @@ -155,7 +155,7 @@ parser.parse(System.in, handler, ...); --- Another useful class is - {{{api/org/apache/tika/parser/ParsingReader.html}ParsingReader}} that + {{{./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: @@ -173,7 +173,7 @@ try { 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. + as an {{{./api/org/apache/tika/metadata/Metadata.html}Metadata}} object. The following are some of the more interesting metadata properties: @@ -220,14 +220,14 @@ try { 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. + {{{./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 + {{{./formats.html}various document formats}}. You can also extend Tika with your own parsers, and of course any contributions to Tika are warmly welcome. @@ -238,7 +238,7 @@ try { 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}} + is the {{{./api/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 Modified: tika/site/src/site/apt/1.1/parser_guide.apt URL: http://svn.apache.org/viewvc/tika/site/src/site/apt/1.1/parser_guide.apt?rev=1381198&r1=1381197&r2=1381198&view=diff ============================================================================== --- tika/site/src/site/apt/1.1/parser_guide.apt (original) +++ tika/site/src/site/apt/1.1/parser_guide.apt Wed Sep 5 14:31:06 2012 @@ -28,7 +28,7 @@ Get Tika parsing up and running in 5 min * {Getting Started} - The {{{gettingstarted.html}Getting Started}} document describes how to + 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. Modified: tika/site/src/site/apt/1.2/formats.apt URL: http://svn.apache.org/viewvc/tika/site/src/site/apt/1.2/formats.apt?rev=1381198&r1=1381197&r2=1381198&view=diff ============================================================================== --- tika/site/src/site/apt/1.2/formats.apt (original) +++ tika/site/src/site/apt/1.2/formats.apt Wed Sep 5 14:31:06 2012 @@ -31,7 +31,7 @@ Supported Document Formats 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 + {{{./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. @@ -41,7 +41,7 @@ Supported Document 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}} + {{{./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. @@ -53,9 +53,9 @@ Supported Document Formats 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}} + {{{./api/org/apache/tika/parser/microsoft/OfficeParser.html}OfficeParser}} and - {{{api/org/apache/tika/parser/microsoft/ooxml/OOXMLParser.html}OOXMLParser}} + {{{./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. @@ -63,25 +63,25 @@ Supported Document Formats 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}} + {{{./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 + 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 + 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 + 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. @@ -89,7 +89,7 @@ Supported Document 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}} + {{{./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 @@ -99,7 +99,7 @@ Supported Document 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 + {{{./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. @@ -108,20 +108,20 @@ Supported Document 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}} + {{{./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 + {{{./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}} + 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 + {{{./api/org/apache/tika/parser/jpeg/JpegParser.html}JpegParser}} class that uses the metadata-extractor library to supports Exif metadata extraction from Jpeg images. @@ -129,17 +129,17 @@ Supported Document 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. + {{{./api/org/apache/tika/parser/flv/FLVParser}FLVParser}} class. * {Java class files and archives} - The {{{api/org/apache/tika/parser/asm/ClassParser}ClassParser}} class + 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 + 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 + 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. Modified: tika/site/src/site/apt/1.2/index.apt URL: http://svn.apache.org/viewvc/tika/site/src/site/apt/1.2/index.apt?rev=1381198&r1=1381197&r2=1381198&view=diff ============================================================================== --- tika/site/src/site/apt/1.2/index.apt (original) +++ tika/site/src/site/apt/1.2/index.apt Wed Sep 5 14:31:06 2012 @@ -126,7 +126,7 @@ Apache Tika 1.2 * Ingo Renner - * Jan Høydahl + * Jan H\u00F8ydahl * Jeremy Anderson @@ -134,7 +134,7 @@ Apache Tika 1.2 * John Mastarone - * Jörg Ehrlich + * J\u00F6rg Ehrlich * Jukka Zitting @@ -165,3 +165,4 @@ Apache Tika 1.2 * Torsten Krah See {{http://s.apache.org/PSE}} for more details on these contributions. + Modified: tika/site/src/site/apt/1.2/parser.apt URL: http://svn.apache.org/viewvc/tika/site/src/site/apt/1.2/parser.apt?rev=1381198&r1=1381197&r2=1381198&view=diff ============================================================================== --- tika/site/src/site/apt/1.2/parser.apt (original) +++ tika/site/src/site/apt/1.2/parser.apt Wed Sep 5 14:31:06 2012 @@ -20,7 +20,7 @@ The Parser interface The - {{{api/org/apache/tika/parser/Parser.html}org.apache.tika.parser.Parser}} + {{{./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 @@ -79,7 +79,7 @@ void parse( {{{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}}. + 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 @@ -134,7 +134,7 @@ try { --- Parser implementations typically use the - {{{apidocs/org/apache/tika/sax/XHTMLContentHandler.html}XHTMLContentHandler}} + {{{./api/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 @@ -142,7 +142,7 @@ try { convert the event stream to other representations. For example, the - {{{api/org/apache/tika/sax/BodyContentHandler.html}BodyContentHandler}} + {{{./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 @@ -155,7 +155,7 @@ parser.parse(System.in, handler, ...); --- Another useful class is - {{{api/org/apache/tika/parser/ParsingReader.html}ParsingReader}} that + {{{./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: @@ -173,7 +173,7 @@ try { 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. + as an {{{./api/org/apache/tika/metadata/Metadata.html}Metadata}} object. The following are some of the more interesting metadata properties: @@ -220,14 +220,14 @@ try { 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. + {{{./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 + {{{./formats.html}various document formats}}. You can also extend Tika with your own parsers, and of course any contributions to Tika are warmly welcome. @@ -238,7 +238,7 @@ try { 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}} + is the {{{./api/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 Modified: tika/site/src/site/apt/1.2/parser_guide.apt URL: http://svn.apache.org/viewvc/tika/site/src/site/apt/1.2/parser_guide.apt?rev=1381198&r1=1381197&r2=1381198&view=diff ============================================================================== --- tika/site/src/site/apt/1.2/parser_guide.apt (original) +++ tika/site/src/site/apt/1.2/parser_guide.apt Wed Sep 5 14:31:06 2012 @@ -28,7 +28,7 @@ Get Tika parsing up and running in 5 min * {Getting Started} - The {{{gettingstarted.html}Getting Started}} document describes how to + 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.
