svn commit: r1416409 - /xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext

[ps...@apache.org]

Author: psancho
Date: Mon Dec  3 10:00:25 2012
New Revision: 1416409

URL: http://svn.apache.org/viewvc?rev=1416409&view=rev
Log:
Titles Hierarchy

Modified:
    xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext

Modified: xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext?rev=1416409&r1=1416408&r2=1416409&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/hyphenation.mdtext Mon Dec  3 10:00:25 2012
@@ -49,7 +49,7 @@ and run Ant with build target `jar-hyphe
 - Put the pattern source file(s) into a directory of your choice and configure FOP to look for custom patterns in this directory, by setting the [<hyphenation-base>](configuration.html) configuration option.
 
 <warning>Either of these three options will ensure hyphenation is working when using FOP from the command-line. If FOP is being embedded, remember to add the location(s) of the hyphenation JAR(s) to the CLASSPATH (option 1 and 2) or to set the [<hyphenation-dir>](configuration.html#hyphenation-dir) configuration option programmatically (option 3).</warning>
-# Hyphenation Patterns <a id="patterns"></a>
+## Hyphenation Patterns <a id="patterns"></a>
 
 If you would like to build your own hyphenation pattern files, or modify existing ones, this section will help you understand how to do so. Even when creating a pattern file from scratch, it may be beneficial to start with an existing file and modify it. See [OFFO's Hyphenation page](http://offo.sourceforge.net/hyphenation/index.html) for examples. Here is a brief explanation of the contents of FOP's hyphenation patterns:
 <warning>The remaining content of this section should be considered "draft" quality. It was drafted from theoretical literature, and has not been tested against actual FOP behavior. It may contain errors or omissions. Do not rely on these instructions without testing everything stated here. If you use these instructions, please provide feedback on the [FOP User mailing list](../maillist.html#fop-user) , either confirming their accuracy, or raising specific problems that we can address.</warning>



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org