Author: nick
Date: Sat May 28 11:41:48 2016
New Revision: 1745868

URL: http://svn.apache.org/viewvc?rev=1745868&view=rev
Log:
Republish

Modified:
    tika/site/publish/1.10/configuring.html
    tika/site/publish/1.11/configuring.html
    tika/site/publish/1.12/configuring.html
    tika/site/publish/1.13/configuring.html

Modified: tika/site/publish/1.10/configuring.html
URL: 
http://svn.apache.org/viewvc/tika/site/publish/1.10/configuring.html?rev=1745868&r1=1745867&r2=1745868&view=diff
==============================================================================
--- tika/site/publish/1.10/configuring.html (original)
+++ tika/site/publish/1.10/configuring.html Sat May 28 11:41:48 2016
@@ -106,7 +106,7 @@
 <h3><a name="Configuring_Parsers">Configuring Parsers</a></h3>
 <p>Through the Tika Config xml, it is possible to have a high degree of 
control over which parsers are or aren't used, in what order of preferences 
etc. It is also possible to override just certain parts, to (for example) have 
&quot;default except for PDF&quot;.</p>
 <p>Currently, it is only possible to have a single parser run against a 
document. There is on-going discussion around fallback parsers and combining 
the output of multiple parsers running on a document, but none of these are 
available yet.</p>
-<p>To override some parser certain default behaviours, include the <a 
href="#DefaultParser"></a> in your configuration, with excludes, then add other 
parser definitions in. To prevent the <a href="#DefaultParser"></a> (with its 
auto-discovery) being used, simply omit it from your config, and list all other 
parsers you want instead.</p>
+<p>To override some parser certain default behaviours, include the <tt> 
DefaultParser </tt> in your configuration, with excludes, then add other parser 
definitions in. To prevent the <tt> DefaultParser </tt> (with its 
auto-discovery) being used, simply omit it from your config, and list all other 
parsers you want instead.</p>
 <p>To override just some default behaviour, you can use a Tika Config 
something like this:</p>
 <div>
 <pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
@@ -129,7 +129,7 @@
 <div class="section">
 <h3><a name="Configuring_Detectors">Configuring Detectors</a></h3>
 <p>Through the Tika Config xml, it is possible to have a high degree of 
control over which detectors are or aren't used, in what order of preferences 
etc. It is also possible to override just certain parts, to (for example) have 
&quot;default except for no POIFS Container Detction&quot;.</p>
-<p>To override some detector certain default behaviours, include the <a 
href="#DefaultDetector"></a>, with any <a href="#detector-exclude"></a> entries 
you need, in your configuration, then add other detectors definitions in. To 
prevent the <a href="#DefaultParser"></a> (with its auto-discovery) being used, 
simply omit it from your config, and list all other detectors you want 
instead.</p>
+<p>To override some detector certain default behaviours, include the <tt> 
DefaultDetector </tt>, with any <tt> detector-exclude </tt> entries you need, 
in your configuration, then add other detectors definitions in. To prevent the 
<tt> DefaultParser </tt> (with its auto-discovery) being used, simply omit it 
from your config, and list all other detectors you want instead.</p>
 <p>To override just some default behaviour, you can use a Tika Config 
something like this:</p>
 <div>
 <pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;

Modified: tika/site/publish/1.11/configuring.html
URL: 
http://svn.apache.org/viewvc/tika/site/publish/1.11/configuring.html?rev=1745868&r1=1745867&r2=1745868&view=diff
==============================================================================
--- tika/site/publish/1.11/configuring.html (original)
+++ tika/site/publish/1.11/configuring.html Sat May 28 11:41:48 2016
@@ -106,7 +106,7 @@
 <h3><a name="Configuring_Parsers">Configuring Parsers</a></h3>
 <p>Through the Tika Config xml, it is possible to have a high degree of 
control over which parsers are or aren't used, in what order of preferences 
etc. It is also possible to override just certain parts, to (for example) have 
&quot;default except for PDF&quot;.</p>
 <p>Currently, it is only possible to have a single parser run against a 
document. There is on-going discussion around fallback parsers and combining 
the output of multiple parsers running on a document, but none of these are 
available yet.</p>
-<p>To override some parser certain default behaviours, include the <a 
href="#DefaultParser"></a> in your configuration, with excludes, then add other 
parser definitions in. To prevent the <a href="#DefaultParser"></a> (with its 
auto-discovery) being used, simply omit it from your config, and list all other 
parsers you want instead.</p>
+<p>To override some parser certain default behaviours, include the <tt> 
DefaultParser </tt> in your configuration, with excludes, then add other parser 
definitions in. To prevent the <tt> DefaultParser </tt> (with its 
auto-discovery) being used, simply omit it from your config, and list all other 
parsers you want instead.</p>
 <p>To override just some default behaviour, you can use a Tika Config 
something like this:</p>
 <div>
 <pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
@@ -129,7 +129,7 @@
 <div class="section">
 <h3><a name="Configuring_Detectors">Configuring Detectors</a></h3>
 <p>Through the Tika Config xml, it is possible to have a high degree of 
control over which detectors are or aren't used, in what order of preferences 
etc. It is also possible to override just certain parts, to (for example) have 
&quot;default except for no POIFS Container Detction&quot;.</p>
-<p>To override some detector certain default behaviours, include the <a 
href="#DefaultDetector"></a>, with any <a href="#detector-exclude"></a> entries 
you need, in your configuration, then add other detectors definitions in. To 
prevent the <a href="#DefaultParser"></a> (with its auto-discovery) being used, 
simply omit it from your config, and list all other detectors you want 
instead.</p>
+<p>To override some detector certain default behaviours, include the <tt> 
DefaultDetector </tt>, with any <tt> detector-exclude </tt> entries you need, 
in your configuration, then add other detectors definitions in. To prevent the 
<tt> DefaultParser </tt> (with its auto-discovery) being used, simply omit it 
from your config, and list all other detectors you want instead.</p>
 <p>To override just some default behaviour, you can use a Tika Config 
something like this:</p>
 <div>
 <pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;

Modified: tika/site/publish/1.12/configuring.html
URL: 
http://svn.apache.org/viewvc/tika/site/publish/1.12/configuring.html?rev=1745868&r1=1745867&r2=1745868&view=diff
==============================================================================
--- tika/site/publish/1.12/configuring.html (original)
+++ tika/site/publish/1.12/configuring.html Sat May 28 11:41:48 2016
@@ -106,7 +106,7 @@
 <h3><a name="Configuring_Parsers">Configuring Parsers</a></h3>
 <p>Through the Tika Config xml, it is possible to have a high degree of 
control over which parsers are or aren't used, in what order of preferences 
etc. It is also possible to override just certain parts, to (for example) have 
&quot;default except for PDF&quot;.</p>
 <p>Currently, it is only possible to have a single parser run against a 
document. There is on-going discussion around fallback parsers and combining 
the output of multiple parsers running on a document, but none of these are 
available yet.</p>
-<p>To override some parser certain default behaviours, include the <a 
href="#DefaultParser"></a> in your configuration, with excludes, then add other 
parser definitions in. To prevent the <a href="#DefaultParser"></a> (with its 
auto-discovery) being used, simply omit it from your config, and list all other 
parsers you want instead.</p>
+<p>To override some parser certain default behaviours, include the <tt> 
DefaultParser </tt> in your configuration, with excludes, then add other parser 
definitions in. To prevent the <tt> DefaultParser </tt> (with its 
auto-discovery) being used, simply omit it from your config, and list all other 
parsers you want instead.</p>
 <p>To override just some default behaviour, you can use a Tika Config 
something like this:</p>
 <div>
 <pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
@@ -129,7 +129,7 @@
 <div class="section">
 <h3><a name="Configuring_Detectors">Configuring Detectors</a></h3>
 <p>Through the Tika Config xml, it is possible to have a high degree of 
control over which detectors are or aren't used, in what order of preferences 
etc. It is also possible to override just certain parts, to (for example) have 
&quot;default except for no POIFS Container Detction&quot;.</p>
-<p>To override some detector certain default behaviours, include the <a 
href="#DefaultDetector"></a>, with any <a href="#detector-exclude"></a> entries 
you need, in your configuration, then add other detectors definitions in. To 
prevent the <a href="#DefaultParser"></a> (with its auto-discovery) being used, 
simply omit it from your config, and list all other detectors you want 
instead.</p>
+<p>To override some detector certain default behaviours, include the <tt> 
DefaultDetector </tt>, with any <tt> detector-exclude </tt> entries you need, 
in your configuration, then add other detectors definitions in. To prevent the 
<tt> DefaultParser </tt> (with its auto-discovery) being used, simply omit it 
from your config, and list all other detectors you want instead.</p>
 <p>To override just some default behaviour, you can use a Tika Config 
something like this:</p>
 <div>
 <pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;

Modified: tika/site/publish/1.13/configuring.html
URL: 
http://svn.apache.org/viewvc/tika/site/publish/1.13/configuring.html?rev=1745868&r1=1745867&r2=1745868&view=diff
==============================================================================
--- tika/site/publish/1.13/configuring.html (original)
+++ tika/site/publish/1.13/configuring.html Sat May 28 11:41:48 2016
@@ -106,7 +106,7 @@
 <h3><a name="Configuring_Parsers">Configuring Parsers</a></h3>
 <p>Through the Tika Config xml, it is possible to have a high degree of 
control over which parsers are or aren't used, in what order of preferences 
etc. It is also possible to override just certain parts, to (for example) have 
&quot;default except for PDF&quot;.</p>
 <p>Currently, it is only possible to have a single parser run against a 
document. There is on-going discussion around fallback parsers and combining 
the output of multiple parsers running on a document, but none of these are 
available yet.</p>
-<p>To override some parser certain default behaviours, include the <a 
href="#DefaultParser"></a> in your configuration, with excludes, then add other 
parser definitions in. To prevent the <a href="#DefaultParser"></a> (with its 
auto-discovery) being used, simply omit it from your config, and list all other 
parsers you want instead.</p>
+<p>To override some parser certain default behaviours, include the <tt> 
DefaultParser </tt> in your configuration, with excludes, then add other parser 
definitions in. To prevent the <tt> DefaultParser </tt> (with its 
auto-discovery) being used, simply omit it from your config, and list all other 
parsers you want instead.</p>
 <p>To override just some default behaviour, you can use a Tika Config 
something like this:</p>
 <div>
 <pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
@@ -129,7 +129,7 @@
 <div class="section">
 <h3><a name="Configuring_Detectors">Configuring Detectors</a></h3>
 <p>Through the Tika Config xml, it is possible to have a high degree of 
control over which detectors are or aren't used, in what order of preferences 
etc. It is also possible to override just certain parts, to (for example) have 
&quot;default except for no POIFS Container Detction&quot;.</p>
-<p>To override some detector certain default behaviours, include the <a 
href="#DefaultDetector"></a>, with any <a href="#detector-exclude"></a> entries 
you need, in your configuration, then add other detectors definitions in. To 
prevent the <a href="#DefaultParser"></a> (with its auto-discovery) being used, 
simply omit it from your config, and list all other detectors you want 
instead.</p>
+<p>To override some detector certain default behaviours, include the <tt> 
DefaultDetector </tt>, with any <tt> detector-exclude </tt> entries you need, 
in your configuration, then add other detectors definitions in. To prevent the 
<tt> DefaultParser </tt> (with its auto-discovery) being used, simply omit it 
from your config, and list all other detectors you want instead.</p>
 <p>To override just some default behaviour, you can use a Tika Config 
something like this:</p>
 <div>
 <pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;


Reply via email to