svn commit: r1152446 - /james/mime4j/trunk/src/site/apt/usage.apt

[ba...@apache.org]

Author: bago
Date: Sat Jul 30 10:35:14 2011
New Revision: 1152446

URL: http://svn.apache.org/viewvc?rev=1152446&view=rev
Log:
fix apt syntax for anchors (they don't need the starting #) and relative urls (the have to start with ./).

Modified:
    james/mime4j/trunk/src/site/apt/usage.apt

Modified: james/mime4j/trunk/src/site/apt/usage.apt
URL: http://svn.apache.org/viewvc/james/mime4j/trunk/src/site/apt/usage.apt?rev=1152446&r1=1152445&r2=1152446&view=diff
==============================================================================
--- james/mime4j/trunk/src/site/apt/usage.apt (original)
+++ james/mime4j/trunk/src/site/apt/usage.apt Sat Jul 30 10:35:14 2011
@@ -23,25 +23,25 @@
 {Usage}
 
   Mime4j provides two different API's: An event based API by using
-  the {{{apidocs/org/apache/james/mime4j/parser/MimeStreamParser.html}
+  the {{{./apidocs/org/apache/james/mime4j/parser/MimeStreamParser.html}
   MimeStreamParser}}. Alternatively, you may use the iterative
   API, which is available through the
-  {{{apidocs/org/apache/james/mime4j/parser/MimeTokenStream.html}
+  {{{./apidocs/org/apache/james/mime4j/parser/MimeTokenStream.html}
   MimeTokenStream}}. In terms of speed, you should not note
   any differences.
 
-  * {{{#Token Streams}Token Streams}}
+  * {{{Token Streams}Token Streams}}
 
-  * {{{#Sample Token Stream}Sample Token Stream}}
+  * {{{Sample Token Stream}Sample Token Stream}}
 
-  * {{{#Event Handlers}Event Handlers}}
+  * {{{Event Handlers}Event Handlers}}
 
-  * {{{#Sample Event Stream}Sample Event Stream}}
+  * {{{Sample Event Stream}Sample Event Stream}}
 
 {Token Streams}
 
   The iterative approach is using the class
-  {{{apidocs/org/apache/james/mime4j/parser/MimeTokenStream.html}
+  {{{./apidocs/org/apache/james/mime4j/parser/MimeTokenStream.html}
   MimeTokenStream}}. Here's an example, how you could use
   the token stream:
 
@@ -121,7 +121,7 @@
 
   The event based API requires, that you provide an event handler,
   which receives events. The event handler is an object, which
-  implements the {{{apidocs/org/apache/james/mime4j/parser/ContentHandler.html}
+  implements the {{{./apidocs/org/apache/james/mime4j/parser/ContentHandler.html}
   ContentHandler}} interface. Here's an example, how you could
   implement an event handler:
 
@@ -146,7 +146,7 @@
 
   A little bit of additional code allows us to create an example, which
   is functionally equivalent to the example from the section on
-  {{{#Token Streams}Token Streams}}:
+  {{{Token Streams}Token Streams}}:
 
 --------------------------------------------------------------------  
   ContentHandler handler = new MyContentHandler();