You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by sv...@apache.org on 2020/07/02 03:00:57 UTC
svn commit: r1879424 [2/3] - in /maven/doxia/website/content: ./ book/
developers/ doxia-example-book/ issues/ macros/ modules/ references/
Modified: maven/doxia/website/content/doxia-example-book/transport-and-channel-api.html
==============================================================================
--- maven/doxia/website/content/doxia-example-book/transport-and-channel-api.html (original)
+++ maven/doxia/website/content/doxia-example-book/transport-and-channel-api.html Thu Jul 2 03:00:56 2020
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from target/generated-site/xdoc/doxia-example-book/transport-and-channel-api.xml at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from target/generated-site/xdoc/doxia-example-book/transport-and-channel-api.xml at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -8,7 +8,7 @@
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="XFire User's Guide" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Transport and Channel API</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.7.min.css" />
@@ -41,7 +41,7 @@
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="../index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Transport and Channel API <a href="https://github.com/apache/maven-doxia-site/tree/master/target/generated-site/xdoc/doxia-example-book/transport-and-channel-api.xml"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="../scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -108,14 +108,13 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2></h2>
<table class="table table-striped" width="100%" align="center" border="0">
<tr class="a">
<td align="left">Previous: <a href="transports.html">Transports</a></td>
<td align="center">Up: <a href="transports.html">Transports</a></td>
-<td align="right">Next: <a href="http-transport.html">HTTP Transport</a></td></tr></table><hr /></div>
-<div class="section">
+<td align="right">Next: <a href="http-transport.html">HTTP Transport</a></td></tr></table><hr /></section><section>
<h2><a name="Transports_and_Channels"></a>Transports and Channels</h2>
<p>Channels and Transports provide the basic unit of communication in XFire. A Channel simply sends messages (via send()) and listens for messages (via receive()). If you want to send a message to a particular URL you do:</p>
<div class="source"><pre class="prettyprint linenums">TransportManager tm = ...;
@@ -125,35 +124,27 @@ OutMessage msg = ...; // create an outme
Channel c = t.createChannel(); // create an anonymous endpoint
MessageContext context = new MessageContext();
c.send(msg, context);</pre></div>
-<p>Each transport is responsible for creating its own protocol specific listener, for example a servlet in the case of HTTP. This listener then passes whatever messages it receives to the channel via Channel.receive(MessageContext, InMessage). Channels simply delegate their receive() to a ChannelEndpoint which application specific handling of what to do with the message. The default endpoint is aptly named DefaultEndpoint and will be covered in the next section.</p>
-<div class="section">
-<h3><a name="InMessage_and_OutMessage"></a>InMessage and OutMessage</h3></div>
-<div class="section">
+<p>Each transport is responsible for creating its own protocol specific listener, for example a servlet in the case of HTTP. This listener then passes whatever messages it receives to the channel via Channel.receive(MessageContext, InMessage). Channels simply delegate their receive() to a ChannelEndpoint which application specific handling of what to do with the message. The default endpoint is aptly named DefaultEndpoint and will be covered in the next section.</p><section>
+<h3><a name="InMessage_and_OutMessage"></a>InMessage and OutMessage</h3></section><section>
<h3><a name="MessageSerializer"></a>MessageSerializer</h3>
-<p>Each OutMessage has a MessageSerializer. A message serializer takes the message body (message.getBody()) and writes it to an XMLStreamWriter that the Channel provides. The semantics of MessageSerializers should be such that they can be invoked multiple times.</p></div>
-<div class="section">
+<p>Each OutMessage has a MessageSerializer. A message serializer takes the message body (message.getBody()) and writes it to an XMLStreamWriter that the Channel provides. The semantics of MessageSerializers should be such that they can be invoked multiple times.</p></section><section>
<h3><a name="Channels.2FTransports_without_Services"></a>Channels/Transports without Services</h3>
-<p>Its important to note that Channels and transports are completely independent of XFire's Services. So I can use a channel to send a receive messages and never even create a service. I simply need to provide my own ChannelEndpoint.</p></div>
-<div class="section">
+<p>Its important to note that Channels and transports are completely independent of XFire's Services. So I can use a channel to send a receive messages and never even create a service. I simply need to provide my own ChannelEndpoint.</p></section><section>
<h3><a name="DefaultEndpoint_and_the_processing_flow"></a>DefaultEndpoint and the processing flow</h3>
-<p>DefaultEndpoint takes a message, creates a default message exchange called InMessageExchange and creates a message pipeline. The message pipeline at first consists of the global in handlers from XFire.getInHandlers() and the transport handlers from Transport.getInHandlers. Later on when the service is resolved, the service's handlers get added into the pipeline. Once the operation is resolved, if there is an out message to be set an Out pipeline is created and added to the MessageContext.</p></div>
-<div class="section">
+<p>DefaultEndpoint takes a message, creates a default message exchange called InMessageExchange and creates a message pipeline. The message pipeline at first consists of the global in handlers from XFire.getInHandlers() and the transport handlers from Transport.getInHandlers. Later on when the service is resolved, the service's handlers get added into the pipeline. Once the operation is resolved, if there is an out message to be set an Out pipeline is created and added to the MessageContext.</p></section><section>
<h3><a name="Phases_and_Handlers"></a>Phases and Handlers</h3>
-<p>See Processing Pipeline for now.</p></div>
-<div class="section">
+<p>See Processing Pipeline for now.</p></section><section>
<h3><a name="SOAP_Processing"></a>SOAP Processing</h3>
<p>SOAPTransport.createTransport() adds SOAP support to a particular transport. It does so by adding three additional handlers:</p>
<ol style="list-style-type: decimal">
-<li>ReadHeaderHandler - this handler reads in the soap headers. It stops reading the XML stream the moment the whitespace stops after the <i>Body</i> tag. If it encounters a <i>Fault</i> in the Body, an XFireFault is thrown. [[1]] ValidateHeadersHandler - Ensure that all the necessary headers are understood by the receiving handlers. [[1]] SoapSerializerHandler - Services provide a MessageSerializer of their own which is responsible for serializing the soap body. But what about the message headers? This is written out by the SoapSerializer. What the SoapSerializerHandler does is replace the outMessage.MessageSerializer with new SoapSerializer(outMsg.getMessageSerializer()).</li></ol></div>
-<div class="section">
-<h3><a name="MessageExchanges"></a>MessageExchanges</h3></div></div>
-<div class="section">
+<li>ReadHeaderHandler - this handler reads in the soap headers. It stops reading the XML stream the moment the whitespace stops after the <i>Body</i> tag. If it encounters a <i>Fault</i> in the Body, an XFireFault is thrown. [[1]] ValidateHeadersHandler - Ensure that all the necessary headers are understood by the receiving handlers. [[1]] SoapSerializerHandler - Services provide a MessageSerializer of their own which is responsible for serializing the soap body. But what about the message headers? This is written out by the SoapSerializer. What the SoapSerializerHandler does is replace the outMessage.MessageSerializer with new SoapSerializer(outMsg.getMessageSerializer()).</li></ol></section><section>
+<h3><a name="MessageExchanges"></a>MessageExchanges</h3></section></section><section>
<h2></h2><hr />
<table class="table table-striped" width="100%" align="center" border="0">
<tr class="a">
<td align="left">Previous: <a href="transports.html">Transports</a></td>
<td align="center">Up: <a href="transports.html">Transports</a></td>
-<td align="right">Next: <a href="http-transport.html">HTTP Transport</a></td></tr></table></div>
+<td align="right">Next: <a href="http-transport.html">HTTP Transport</a></td></tr></table></section>
</div>
</div>
</div>
Modified: maven/doxia/website/content/doxia-example-book/transports.html
==============================================================================
--- maven/doxia/website/content/doxia-example-book/transports.html (original)
+++ maven/doxia/website/content/doxia-example-book/transports.html Thu Jul 2 03:00:56 2020
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from target/generated-site/xdoc/doxia-example-book/transports.xml at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from target/generated-site/xdoc/doxia-example-book/transports.xml at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Transports</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.7.min.css" />
@@ -40,7 +40,7 @@
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="../index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Transports <a href="https://github.com/apache/maven-doxia-site/tree/master/target/generated-site/xdoc/doxia-example-book/transports.xml"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="../scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -107,7 +107,7 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2></h2>
<table border="0" class="table table-striped" width="100%" align="center">
<tr class="a">
@@ -116,8 +116,7 @@
<td>
<div align="center">Up: <a href="index.html">Table Of Content</a></div></td>
<td>
-<div align="right">Next: <a href="transport-and-channel-api.html">Transport and Channel API</a></div></td></tr></table><hr /></div>
-<div class="section">
+<div align="right">Next: <a href="transport-and-channel-api.html">Transport and Channel API</a></div></td></tr></table><hr /></section><section>
<h2><a name="Transports"></a>Transports</h2>
<ul>
<li><a href="transport-and-channel-api.html">Transport and Channel API</a>
@@ -131,8 +130,7 @@
<li><a href="jms-transport.html#JMS_Transport">JMS Transport</a></li></ul></li>
<li><a href="local-transport.html">Local Transport</a>
<ul>
-<li><a href="local-transport.html#Local_Transport">Local Transport</a></li></ul></li></ul></div>
-<div class="section">
+<li><a href="local-transport.html#Local_Transport">Local Transport</a></li></ul></li></ul></section><section>
<h2></h2><hr />
<table border="0" class="table table-striped" width="100%" align="center">
<tr class="a">
@@ -141,7 +139,7 @@
<td>
<div align="center">Up: <a href="index.html">Table Of Content</a></div></td>
<td>
-<div align="right">Next: <a href="transport-and-channel-api.html">Transport and Channel API</a></div></td></tr></table></div>
+<div align="right">Next: <a href="transport-and-channel-api.html">Transport and Channel API</a></div></td></tr></table></section>
</div>
</div>
</div>
Modified: maven/doxia/website/content/faq.html
==============================================================================
--- maven/doxia/website/content/faq.html (original)
+++ maven/doxia/website/content/faq.html Thu Jul 2 03:00:56 2020
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/fml/faq.fml at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/fml/faq.fml at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Frequently Asked Questions</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.7.min.css" />
@@ -40,7 +40,7 @@
<li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Frequently Asked Questions <a href="https://github.com/apache/maven-doxia-site/tree/master/content/fml/faq.fml"><img src="./images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -107,7 +107,7 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Frequently_Asked_Questions"></a><a name="top">Frequently Asked Questions</a></h2>
<ol style="list-style-type: decimal">
<li><a href="#How_to_handle_style_in_the_APT_markup_language">How to handle style in the APT markup language?</a></li>
@@ -115,7 +115,7 @@
<li><a href="#Is_it_possible_to_create_a_book">Is it possible to create a book?</a></li>
<li><a href="#Why_XML_based_sinks_don_t_generate_nicely_formatted_documents">Why XML based sinks don't generate nicely formatted documents?</a></li>
<li><a href="#doxia-xsd">Where are the Maven Doxia XSD schemas files?</a></li>
-<li><a href="#doxia-character-entities">How to define character entities in Doxia XML files with XSD?</a></li></ol></div>
+<li><a href="#doxia-character-entities">How to define character entities in Doxia XML files with XSD?</a></li></ol></section>
<dl>
<dt><a name="How_to_handle_style_in_the_APT_markup_language">How to handle style in the APT markup language?</a></dt>
<dd>
Modified: maven/doxia/website/content/index.html
==============================================================================
--- maven/doxia/website/content/index.html (original)
+++ maven/doxia/website/content/index.html Thu Jul 2 03:00:56 2020
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/index.apt.vm at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/apt/index.apt.vm at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -10,7 +10,7 @@
<meta name="author" content="Jason van Zyl
Vincent Siveton" />
<meta name="Date-Creation-yyyymmdd" content="20100528" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Introduction</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.7.min.css" />
@@ -43,7 +43,7 @@ Vincent Siveton" />
<li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Introduction <a href="https://github.com/apache/maven-doxia-site/tree/master/content/apt/index.apt.vm"><img src="./images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -119,16 +119,14 @@ Vincent Siveton" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Maven_Doxia"></a>Maven Doxia</h2>
<p>Doxia is a content generation framework which aims to provide its users with powerful techniques for generating static and dynamic content: Doxia can be used in web-based publishing context to generate static sites, in addition to being incorporated into dynamic content generation systems like blogs, wikis and content management systems.</p>
<p>Doxia supports <a href="./references/index.html">markup languages with simple syntaxes</a>. Lightweight markup languages are used by people who might be expected to read the document source as well as the rendered output.</p>
<p>Doxia is used extensively by <a class="externalLink" href="http://maven.apache.org">Maven</a> and it powers the entire documentation system of Maven. It gives Maven the ability to take any document that Doxia supports and output it any format.</p>
-<p>The current version of <a href="./doxia/">Doxia base framework</a> is 1.9.1.</p>
-<div class="section">
+<p>The current version of <a href="./doxia/">Doxia base framework</a> is 1.9.1.</p><section>
<h3><a name="Brief_History"></a>Brief History</h3>
-<p>Based on the (now defunct) Aptconvert project developed by <a class="externalLink" href="http://www.xmlmind.com/">Xmlmind</a>, Doxia was initially hosted by <a class="externalLink" href="http://codehaus.org/">Codehaus</a>, to become a sub-project of Maven early in 2006.</p></div>
-<div class="section">
+<p>Based on the (now defunct) Aptconvert project developed by <a class="externalLink" href="http://www.xmlmind.com/">Xmlmind</a>, Doxia was initially hosted by <a class="externalLink" href="http://codehaus.org/">Codehaus</a>, to become a sub-project of Maven early in 2006.</p></section><section>
<h3><a name="Main_Features"></a>Main Features</h3>
<ul>
<li>Developed in Java</li>
@@ -138,10 +136,9 @@ Vincent Siveton" />
<li>No need to have a corporate infrastructure (like wiki) to host your documentation</li>
<li>Extensible framework</li>
<li><a href="./doxia-sitetools/">Site Tools extension</a> for site or document rendering</li>
-<li><a href="./doxia-tools/">Additional Tools</a> like <a href="./doxia-tools/doxia-converter/index.html">Doxia Converter</a></li></ul></div>
-<div class="section">
+<li><a href="./doxia-tools/">Additional Tools</a> like <a href="./doxia-tools/doxia-converter/index.html">Doxia Converter</a></li></ul></section><section>
<h3><a name="Doxia_Reference_Pages"></a>Doxia Reference Pages</h3>
-<p>See <a href="./references/index.html">Doxia Markup Languages References</a> page for a listing of all supported markups for each format.</p></div></div>
+<p>See <a href="./references/index.html">Doxia Markup Languages References</a> page for a listing of all supported markups for each format.</p></section></section>
</div>
</div>
</div>
Modified: maven/doxia/website/content/issue-management.html
==============================================================================
--- maven/doxia/website/content/issue-management.html (original)
+++ maven/doxia/website/content/issue-management.html Thu Jul 2 03:00:56 2020
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.1.0:issue-management at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.1.0:issue-management at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Issue Management</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.7.min.css" />
@@ -40,7 +40,7 @@
<li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Issue Management</li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -116,13 +116,12 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Overview"></a>Overview</h2><a name="Overview"></a>
-<p>This project uses <a class="externalLink" href="http://www.atlassian.com/software/jira">JIRA</a>.</p></div>
-<div class="section">
+<p>This project uses <a class="externalLink" href="http://www.atlassian.com/software/jira">JIRA</a>.</p></section><section>
<h2><a name="Issue_Management"></a>Issue Management</h2><a name="Issue_Management"></a>
<p>Issues, bugs, and feature requests should be submitted to the following issue management system for this project.</p>
-<div class="source"><pre class="prettyprint linenums"><a class="externalLink" href="https://issues.apache.org/jira/browse/DOXIA">https://issues.apache.org/jira/browse/DOXIA</a></pre></div></div>
+<div class="source"><pre class="prettyprint linenums"><a class="externalLink" href="https://issues.apache.org/jira/browse/DOXIA">https://issues.apache.org/jira/browse/DOXIA</a></pre></div></section>
</div>
</div>
</div>
Modified: maven/doxia/website/content/issues/index.html
==============================================================================
--- maven/doxia/website/content/issues/index.html (original)
+++ maven/doxia/website/content/issues/index.html Thu Jul 2 03:00:56 2020
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/issues/index.apt at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/apt/issues/index.apt at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -9,7 +9,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="Lukas Theussl" />
<meta name="Date-Creation-yyyymmdd" content="20090302" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Doxia Issues</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.7.min.css" />
@@ -42,7 +42,7 @@
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="../index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Doxia Issues <a href="https://github.com/apache/maven-doxia-site/tree/master/content/apt/issues/index.apt"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="../scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -109,22 +109,20 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Doxia_Issues_.26_Gotchas"></a>Doxia Issues & Gotchas</h2>
<p>This document collects some infos about specific issues and 'gotchas' when working with Doxia. Please check also the <a href="../faq.html">Frequently Asked Questions</a>.</p>
<ul>
<li><a href="#Apt_anchors_and_links">Apt anchors and links</a></li>
<li><a href="#Figure_sink_events">Figure sink events</a></li>
-<li><a href="#Empty_Generated_Page">Empty Generated Page</a></li></ul>
-<div class="section">
+<li><a href="#Empty_Generated_Page">Empty Generated Page</a></li></ul><section>
<h3><a name="Apt_anchors_and_links">Apt anchors and links</a></h3>
<p>Using <b>Doxia 1.1</b> you may see a lot of warnings when processing old Apt source files:</p>
<div class="source"><pre class="prettyprint linenums">[WARNING] [Apt Parser] Ambiguous link: 'doxia-apt.html'. If this is a local link, prepend "./"!</pre></div>
<p>and</p>
<div class="source"><pre class="prettyprint linenums">[WARNING] [Apt Parser] Modified invalid link: references/doxia-apt.html</pre></div>
-<p>The reason is that in Apt, links to other source documents have to start with either <tt>./</tt> or <tt>../</tt> to distinguish them from internal links. Please read the sections on <a href="../references/doxia-apt.html#Anchors">anchors</a> and <a href="../references/doxia-apt.html#Links">links</a> in our Apt guide. Note in particular that internal links in Apt do <b>not</b> start with '#'.</p>
-<p><b>You should pay attention to these warnings since your links will most likely be broken.</b> Unfortunately, the warning message cannot indicate the source file with the broken link (see eg <a class="externalLink" href="https://issues.apache.org/jira/browse/MPDF-11">MPDF-11</a>), however, if you run in <tt>DEBUG</tt> mode, eg invoke maven with the <tt>-X</tt> switch, you can see which source document is being parsed when the warning is emitted.</p></div>
-<div class="section">
+<p>The reason is that in Apt, links to other source documents have to start with either <code>./</code> or <code>../</code> to distinguish them from internal links. Please read the sections on <a href="../references/doxia-apt.html#Anchors">anchors</a> and <a href="../references/doxia-apt.html#Links">links</a> in our Apt guide. Note in particular that internal links in Apt do <b>not</b> start with '#'.</p>
+<p><b>You should pay attention to these warnings since your links will most likely be broken.</b> Unfortunately, the warning message cannot indicate the source file with the broken link (see eg <a class="externalLink" href="https://issues.apache.org/jira/browse/MPDF-11">MPDF-11</a>), however, if you run in <code>DEBUG</code> mode, eg invoke maven with the <code>-X</code> switch, you can see which source document is being parsed when the warning is emitted.</p></section><section>
<h3><a name="Figure_sink_events">Figure sink events</a></h3>
<p>Doxia distinguishes between figures, which are block-level elements, and images (or icons), which are in-line elements. For instance, the following sequence of sink events</p>
<div class="source"><pre class="prettyprint linenums">sink.figure( null );
@@ -141,12 +139,11 @@ sink.figure_();</pre></div>
<p><img src="figure.png"/></p>
<p>Figure caption</p>
</div></pre></div>
-<p>while the <tt>figureGraphics( ... );</tt> event alone can be used to generate an in-line image, i.e. just the <tt><img></tt> tag in case of html.</p>
-<p><b>Note</b> that we are using the forms that take a <tt>SinkEventAttributeSet</tt> above, even though we are just passing in null values. The reason is that the alternative forms (without <tt>SinkEventAttributeSet</tt>) have a different behavior, which is kept for backward compatibility (but the methods have been deprecated). Using the same sequence of sink events as above, but omitting the <tt>null</tt> method parameters, will generate</p>
-<div class="source"><pre class="prettyprint linenums"><img src="figure.png" alt="Figure caption"/></pre></div></div>
-<div class="section">
+<p>while the <code>figureGraphics( ... );</code> event alone can be used to generate an in-line image, i.e. just the <code><img></code> tag in case of html.</p>
+<p><b>Note</b> that we are using the forms that take a <code>SinkEventAttributeSet</code> above, even though we are just passing in null values. The reason is that the alternative forms (without <code>SinkEventAttributeSet</code>) have a different behavior, which is kept for backward compatibility (but the methods have been deprecated). Using the same sequence of sink events as above, but omitting the <code>null</code> method parameters, will generate</p>
+<div class="source"><pre class="prettyprint linenums"><img src="figure.png" alt="Figure caption"/></pre></div></section><section>
<h3><a name="Empty_Generated_Page">Empty Generated Page</a></h3>
-<p>After running <tt>mvn site</tt> using your Maven reporting plugin, you see that the generated page is empty. Be sure that the the code calls <tt>sink.close()</tt>.</p></div></div>
+<p>After running <code>mvn site</code> using your Maven reporting plugin, you see that the generated page is empty. Be sure that the the code calls <code>sink.close()</code>.</p></section></section>
</div>
</div>
</div>
Modified: maven/doxia/website/content/macros/index.html
==============================================================================
--- maven/doxia/website/content/macros/index.html (original)
+++ maven/doxia/website/content/macros/index.html Thu Jul 2 03:00:56 2020
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/macros/index.apt at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/apt/macros/index.apt at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -9,7 +9,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="Vincent Siveton" />
<meta name="Date-Creation-yyyymmdd" content="20090302" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Doxia Macros Guide</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.7.min.css" />
@@ -42,7 +42,7 @@
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="../index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Doxia Macros Guide <a href="https://github.com/apache/maven-doxia-site/tree/master/content/apt/macros/index.apt"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="../scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -109,7 +109,7 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Doxia_Macros_Guide"></a>Doxia Macros Guide</h2>
<p>The Doxia <i>Core</i> includes macro mechanisms to facilitate the documentation writing.</p>
<p>Macros are currently only supported for APT, Xdoc and FML formats. Starting with Doxia 1.7 (maven-site-plugin 3.5), macros are also supported for XHTML and Markdown. Macros are not (and probably will never be) supported by Confluence, Docbook and Twiki modules.</p>
@@ -129,8 +129,7 @@
<li><a href="#Snippet_Macro">Snippet Macro</a></li>
<li><a href="#TOC_Macro">TOC Macro</a></li>
<li><a href="#SWF_Macro">SWF Macro</a></li>
-<li><a href="#SSI_Macro">SSI Macro</a></li></ul>
-<div class="section">
+<li><a href="#SSI_Macro">SSI Macro</a></li></ul><section>
<h3><a name="Echo_Macro">Echo Macro</a></h3>
<p>The <i>Echo</i> macro is a very simple macro: it prints out the key and value of any supplied parameters. For instance, in an APT file, you could write:</p>
<div class="source"><pre class="prettyprint linenums">%{echo|param1=value1|param2=value2}</pre></div>
@@ -141,8 +140,7 @@
</macro></pre></div>
<p>and it will output</p>
<div class="source"><pre class="prettyprint linenums"> param1 ---> value1
- param2 ---> value2</pre></div></div>
-<div class="section">
+ param2 ---> value2</pre></div></section><section>
<h3><a name="Snippet_Macro">Snippet Macro</a></h3>
<p>The <i>Snippet</i> macro is a very useful macro: it prints out the content of a file or a URL. For instance, in an APT file, you could write:</p>
<div class="source"><pre class="prettyprint linenums">%{snippet|id=myid|url=http://myserver/path/to/file.txt}</pre></div>
@@ -151,7 +149,7 @@
<param name="id" value="myid"/>
<param name="url" value="http://myserver/path/to/file.txt"/>
</macro></pre></div>
-<p>The <tt>id</tt> parameter is not required if you want to include the entire file. If you want to include only a part of a file, you should add start and end demarcators: any line (typically a comment) that contains the strings "<tt>START</tt>", "<tt>SNIPPET</tt>" and "<tt>myid</tt>" (where <tt>myid</tt> is the <tt>id</tt> of the snippet) is a start demarcator, and similarly "<tt>END SNIPPET myid</tt>" denotes the end of the snippet to include. For example:</p>
+<p>The <code>id</code> parameter is not required if you want to include the entire file. If you want to include only a part of a file, you should add start and end demarcators: any line (typically a comment) that contains the strings "<code>START</code>", "<code>SNIPPET</code>" and "<code>myid</code>" (where <code>myid</code> is the <code>id</code> of the snippet) is a start demarcator, and similarly "<code>END SNIPPET myid</code>" denotes the end of the snippet to include. For example:</p>
<ul>
<li>Start and end snippets in a Java file
<div class="source"><pre class="prettyprint linenums">public class MyClass
@@ -191,11 +189,10 @@
<td align="left">The path of the file to include (since doxia-1.0-alpha-9).</td></tr>
<tr class="a">
<td align="left">verbatim</td>
-<td align="left">If the content should be output as verbatim escaped text. If this is set to <tt>false</tt> then the content of the snippet will not be escaped. This means that you can use it like Server-Side Includes on a webserver. Default value is <tt>true</tt>.</td></tr>
+<td align="left">If the content should be output as verbatim escaped text. If this is set to <code>false</code> then the content of the snippet will not be escaped. This means that you can use it like Server-Side Includes on a webserver. Default value is <code>true</code>.</td></tr>
<tr class="b">
<td align="left">encoding</td>
-<td align="left">The encoding of the file to read (since Doxia 1.6). If omitted the default JVM encoding will be used.</td></tr></table></div>
-<div class="section">
+<td align="left">The encoding of the file to read (since Doxia 1.6). If omitted the default JVM encoding will be used.</td></tr></table></section><section>
<h3><a name="TOC_Macro">TOC Macro</a></h3>
<p>The <i>TOC</i> macro prints a Table Of Content of a document. It is useful if you have several sections and subsections in your document. For instance, in an APT file, you could write:</p>
<div class="source"><pre class="prettyprint linenums">%{toc|section=2|fromDepth=2|toDepth=3}</pre></div>
@@ -220,10 +217,9 @@
<tr class="b">
<td align="left">toDepth</td>
<td align="left">Maximum section depth to include in the TOC. Positive int, not mandatory, 5 by default.</td></tr></table>
-<p>From <b>Doxia 1.1.1</b> on you may also specify any of the html base attributes (<i>i.e.</i> any of <tt>id</tt>, <tt>class</tt>, <tt>style</tt>, <tt>lang</tt>, <tt>title</tt>) as parameters, e.g.:</p>
+<p>From <b>Doxia 1.1.1</b> on you may also specify any of the html base attributes (<i>i.e.</i> any of <code>id</code>, <code>class</code>, <code>style</code>, <code>lang</code>, <code>title</code>) as parameters, e.g.:</p>
<div class="source"><pre class="prettyprint linenums">%{toc|class=myTOC}</pre></div>
-<p>This can be used for styling the TOC via css.</p></div>
-<div class="section">
+<p>This can be used for styling the TOC via css.</p></section><section>
<h3><a name="SWF_Macro">SWF Macro</a></h3>
<p>The <i>Swf</i> macro prints Shockwave Flash assets in the documentation. For instance, in an APT file, you could write:</p>
<div class="source"><pre class="prettyprint linenums">%{swf|src=swf/myfile.swf|id=MyMovie|width=600|height=200}</pre></div>
@@ -268,8 +264,7 @@
<tr class="a">
<td align="left">allowScript</td>
<td align="left">Specifies the width of the movie in either pixels or percentage of browser window.</td></tr></table>
-<p>For more information, see the <a href="./swf-macro.html">SWF Macro</a> page.</p></div>
-<div class="section">
+<p>For more information, see the <a href="./swf-macro.html">SWF Macro</a> page.</p></section><section>
<h3><a name="SSI_Macro">SSI Macro</a></h3>
<p>Since Doxia 1.7, the <i>SSI</i> macro prints a server side include. For instance, in an APT file, you could write:</p>
<div class="source"><pre class="prettyprint linenums">%{ssi|function=include|file=included-file.html}</pre></div>
@@ -287,7 +282,7 @@
<td align="left">The SSI function to insert.</td></tr>
<tr class="a">
<td align="left"><i>any</i></td>
-<td align="left">Parameter that will be added to the SSI directive.</td></tr></table></div></div>
+<td align="left">Parameter that will be added to the SSI directive.</td></tr></table></section></section>
</div>
</div>
</div>
Modified: maven/doxia/website/content/macros/swf-macro.html
==============================================================================
--- maven/doxia/website/content/macros/swf-macro.html (original)
+++ maven/doxia/website/content/macros/swf-macro.html Thu Jul 2 03:00:56 2020
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/macros/swf-macro.apt at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/apt/macros/swf-macro.apt at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -9,7 +9,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="The Maven Team" />
<meta name="Date-Creation-yyyymmdd" content="20070517" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Doxia - SWF Macro</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.7.min.css" />
@@ -42,7 +42,7 @@
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="../index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Doxia - SWF Macro <a href="https://github.com/apache/maven-doxia-site/tree/master/content/apt/macros/swf-macro.apt"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="../scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -109,10 +109,10 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="SWF_Macro"></a>SWF Macro</h2>
<p>The SWF macro enables users of APT to put SWF (Flash) assets in their documentation.</p>
-<p>Flash assets typically need to be wrappered in <tt>object</tt> and <tt>embed</tt> tags and can have a variety of parameters. Below is a typical example:</p>
+<p>Flash assets typically need to be wrappered in <code>object</code> and <code>embed</code> tags and can have a variety of parameters. Below is a typical example:</p>
<div class="source"><pre class="prettyprint linenums"><object classid='clsid:D27CDB6E-AE6D-11cf-96B8-444553540000'
codebase='http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,29,0'
width='400' height='400' id='MyMovie'>
@@ -126,12 +126,11 @@
</object></pre></div>
<p>In order to use a *.swf in your APT file, use the basic syntax:</p>
<div class="source"><pre class="prettyprint linenums">%{swf|src=swf/myfile.swf|id=MyMovie|width=600|height=200}</pre></div>
-<p>For which <tt>src</tt> is the required parameter. Make sure to put your *.swf file into the <b>/resources</b> folder so that it will get copied to /target when running the <tt>mvn site</tt> task.</p>
+<p>For which <code>src</code> is the required parameter. Make sure to put your *.swf file into the <b>/resources</b> folder so that it will get copied to /target when running the <code>mvn site</code> task.</p>
<p>You can use more advanced parameters to control the output, as per below:</p>
<div class="source"><pre class="prettyprint linenums">%{swf|src=swf/myfile.swf|id=MyMovie|width=600|height=200|version=9|allowScript=always}</pre></div>
<p>For a full listing of parameters and their values see the Adobe knowledge base:</p>
-<p><a class="externalLink" href="http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_12701">http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_12701</a></p>
-<div class="section">
+<p><a class="externalLink" href="http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_12701">http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_12701</a></p><section>
<h3><a name="Parameters_and_Defaults"></a>Parameters and Defaults</h3>
<p>Currently the following parameters are available through the macro. If no value is placed within a parameter, the value will default to the following:</p>
<ul>
@@ -145,7 +144,7 @@
<li>version = "9,0,45,0"</li>
<li>allowScript = "sameDomain"</li></ul>
<p>Note: There is some provided shorthand for versions, i.e. - version=6 - becomes version=6,0,29,0.</p>
-<p><i>TODO:</i> only shorthand for 6 and 9 are functional. Need to find standard long version for other types.</p></div></div>
+<p><i>TODO:</i> only shorthand for 6 and 9 are functional. Need to find standard long version for other types.</p></section></section>
</div>
</div>
</div>
Modified: maven/doxia/website/content/mailing-lists.html
==============================================================================
--- maven/doxia/website/content/mailing-lists.html (original)
+++ maven/doxia/website/content/mailing-lists.html Thu Jul 2 03:00:56 2020
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.1.0:mailing-lists at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.1.0:mailing-lists at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Project Mailing Lists</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.7.min.css" />
@@ -40,7 +40,7 @@
<li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Project Mailing Lists</li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -116,7 +116,7 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Project_Mailing_Lists"></a>Project Mailing Lists</h2><a name="Project_Mailing_Lists"></a>
<p>These are the mailing lists that have been established for this project. For each list, there is a subscribe, unsubscribe, and an archive link.</p>
<table border="0" class="table table-striped">
@@ -266,7 +266,7 @@
<td>-</td>
<td>-</td>
<td>-</td>
-<td><a class="externalLink" href="https://markmail.org/list/org.apache.maven.notifications">markmail.org</a></td></tr></table></div>
+<td><a class="externalLink" href="https://markmail.org/list/org.apache.maven.notifications">markmail.org</a></td></tr></table></section>
</div>
</div>
</div>
Modified: maven/doxia/website/content/modules/index.html
==============================================================================
--- maven/doxia/website/content/modules/index.html (original)
+++ maven/doxia/website/content/modules/index.html Thu Jul 2 03:00:56 2020
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/modules/index.apt at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/apt/modules/index.apt at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -9,7 +9,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="Vincent Siveton" />
<meta name="Date-Creation-yyyymmdd" content="20090615" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Doxia Modules Guide</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.7.min.css" />
@@ -42,7 +42,7 @@
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="../index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Doxia Modules Guide <a href="https://github.com/apache/maven-doxia-site/tree/master/content/apt/modules/index.apt"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="../scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -109,7 +109,7 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Doxia_Modules_Guide"></a>Doxia Modules Guide</h2>
<p>Doxia has several built-in modules that support some standard markup languages, see the <a href="../references/index.html">References</a> page for an overview. The following is just a collection of reference links for the individual formats.</p>
<ul>
@@ -124,86 +124,74 @@
<li><a href="#RTF">RTF</a></li>
<li><a href="#TWiki">TWiki</a></li>
<li><a href="#XDoc">XDoc</a></li>
-<li><a href="#XHTML">XHTML</a></li></ul>
-<div class="section">
+<li><a href="#XHTML">XHTML</a></li></ul><section>
<h3><a name="APT">APT</a></h3>
<p>APT (Almost Plain Text) is a simple text format.</p>
<p><b>References</b>:</p>
<ul>
-<li><a href="../references/apt-format.html">Apt Reference</a></li></ul></div>
-<div class="section">
+<li><a href="../references/apt-format.html">Apt Reference</a></li></ul></section><section>
<h3><a name="Confluence">Confluence</a></h3>
<p><a class="externalLink" href="http://confluence.atlassian.com">Confluence</a> is an Enterprise wiki from <a class="externalLink" href="http://www.atlassian.com">Atlassian</a>. It uses <a class="externalLink" href="http://textism.com/tools/textile/">Textile</a> inside as an APT language.</p>
<p><b>References</b>:</p>
<ul>
<li><a class="externalLink" href="http://confluence.atlassian.com/display/CONF25/Confluence+Notation+Guide+Overview">Confluence Notation Guide Overview</a></li>
-<li><a class="externalLink" href="http://confluence.atlassian.com/renderer/notationhelp.action?section=all">Confluence Element Reference</a></li></ul></div>
-<div class="section">
+<li><a class="externalLink" href="http://confluence.atlassian.com/renderer/notationhelp.action?section=all">Confluence Element Reference</a></li></ul></section><section>
<h3><a name="Simplified_DocBook">Simplified DocBook</a></h3>
<p><a class="externalLink" href="http://docbook.org/">DocBook</a> is a markup language for technical documentation. <a class="externalLink" href="http://www.docbook.org/schemas/simplified">Simplified DocBook</a> is a simpler subset.</p>
<p><b>References</b>:</p>
<ul>
<li><a class="externalLink" href="https://www.docbook.org/schemas/simplified">Simplified DocBook Introduction</a></li>
-<li><a class="externalLink" href="http://www.docbook.org/xml/simple/sdocbook/elements.html">Simplified DocBook Element Reference</a></li></ul></div>
-<div class="section">
+<li><a class="externalLink" href="http://www.docbook.org/xml/simple/sdocbook/elements.html">Simplified DocBook Element Reference</a></li></ul></section><section>
<h3><a name="FML">FML</a></h3>
<p>FML (FAQ Markup Language) is a FAQ markup language.</p>
<p><b>References</b>:</p>
<ul>
-<li><a href="../references/fml-format.html">FML Reference</a></li></ul></div>
-<div class="section">
+<li><a href="../references/fml-format.html">FML Reference</a></li></ul></section><section>
<h3><a name="iText">iText</a></h3>
<p><a class="externalLink" href="http://www.lowagie.com/iText/">iText</a> is a free Java/PDF library.</p>
<p><b>References</b>:</p>
<ul>
-<li><a class="externalLink" href="http://itextdocs.lowagie.com/tutorial/">iText tutorial</a></li></ul></div>
-<div class="section">
+<li><a class="externalLink" href="http://itextdocs.lowagie.com/tutorial/">iText tutorial</a></li></ul></section><section>
<h3><a name="FO">FO</a></h3>
<p>XSL formatting objects (XSL-FO)</p>
<p><b>References</b>:</p>
<ul>
<li><a class="externalLink" href="https://www.w3.org/TR/xsl11/">XSL-FO Recommendation (05 December 2006)</a></li>
<li><a class="externalLink" href="https://zvon.org/xxl/xslfoReference/Output/index.html">XSL FO reference</a></li>
-<li><a class="externalLink" href="https://xmlgraphics.apache.org/fop/">Apache FOP</a></li></ul></div>
-<div class="section">
+<li><a class="externalLink" href="https://xmlgraphics.apache.org/fop/">Apache FOP</a></li></ul></section><section>
<h3><a name="LaTeX">LaTeX</a></h3>
<p><a class="externalLink" href="https://www.latex-project.org/">LaTeX</a> is a popular document markup language.</p>
<p><b>References</b>:</p>
<ul>
<li><a class="externalLink" href="https://www.latex-project.org/guides/usrguide.pdf">LaTeX2e for authors</a></li>
-<li><a class="externalLink" href="http://www.stdout.org/~winston/latex/latexsheet.pdf">Latex reference sheet</a></li></ul></div>
-<div class="section">
+<li><a class="externalLink" href="http://www.stdout.org/~winston/latex/latexsheet.pdf">Latex reference sheet</a></li></ul></section><section>
<h3><a name="Markdown">Markdown</a></h3>
<p><a class="externalLink" href="http://en.wikipedia.org/wiki/Markdown">Markdown</a> is a widespread Markup language.</p>
<p><b>References</b>:</p>
<ul>
-<li><a class="externalLink" href="https://daringfireball.net/projects/markdown/">Official Markdown project at Daring Fireball</a></li></ul></div>
-<div class="section">
+<li><a class="externalLink" href="https://daringfireball.net/projects/markdown/">Official Markdown project at Daring Fireball</a></li></ul></section><section>
<h3><a name="RTF">RTF</a></h3>
<p><a class="externalLink" href="http://www.microsoft.com/downloads/details.aspx?FamilyId=DD422B8D-FF06-4207-B476-6B5396A18A2B&displaylang=en">RTF</a> is a proprietary document file format.</p>
<p><b>References</b>:</p>
<ul>
<li><a class="externalLink" href="http://www.microsoft.com/downloads/info.aspx?na=46&p=1&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=dd422b8d-ff06-4207-b476-6b5396a18a2b&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f2%2ff%2f5%2f2f599e18-07ee-4ec5-a1e7-f4e6a9423592%2fWord2007RTFSpec9.doc&oRef=http%3a%2f%2fmsdn2.microsoft.com%2fen-us%2foffice%2faa905482.aspx">Microsoft Office Word 2007 Rich Text Format (RTF) Specification</a></li>
-<li><a class="externalLink" href="http://search.cpan.org/~sburke/RTF-Writer/lib/RTF/Cookbook.pod">RTF Cookbook</a></li></ul></div>
-<div class="section">
+<li><a class="externalLink" href="http://search.cpan.org/~sburke/RTF-Writer/lib/RTF/Cookbook.pod">RTF Cookbook</a></li></ul></section><section>
<h3><a name="TWiki">TWiki</a></h3>
<p><a class="externalLink" href="https://twiki.org/">TWiki</a> is a structured wiki.</p>
<p><b>References</b>:</p>
<ul>
-<li><a class="externalLink" href="https://twiki.org/cgi-bin/view/TWiki04x01/TextFormattingRules"> TWiki Text Formatting</a></li></ul></div>
-<div class="section">
+<li><a class="externalLink" href="https://twiki.org/cgi-bin/view/TWiki04x01/TextFormattingRules"> TWiki Text Formatting</a></li></ul></section><section>
<h3><a name="XDoc">XDoc</a></h3>
<p>XDoc is a generic format for document into a styled HTML document.</p>
<p><b>References</b>:</p>
<ul>
-<li><a href="../references/xdoc-format.html">XDoc Reference</a></li></ul></div>
-<div class="section">
+<li><a href="../references/xdoc-format.html">XDoc Reference</a></li></ul></section><section>
<h3><a name="XHTML">XHTML</a></h3>
<p><a class="externalLink" href="https://www.w3.org/MarkUp/">XHTML</a> is a markup language with the same expressions as HTML, but also conforms to XML syntax.</p>
<p><b>References</b>:</p>
<ul>
<li><a class="externalLink" href="http://www.iangraham.org/books/xhtml1/extras/html-7nov2000.pdf">HTML and XHTML Quick Reference Charts: Head and Body Markup</a></li>
-<li><a class="externalLink" href="https://www.w3.org/TR/xhtml1/">XHTML 1.0 Specification</a></li></ul></div></div>
+<li><a class="externalLink" href="https://www.w3.org/TR/xhtml1/">XHTML 1.0 Specification</a></li></ul></section></section>
</div>
</div>
</div>
Modified: maven/doxia/website/content/overview.html
==============================================================================
--- maven/doxia/website/content/overview.html (original)
+++ maven/doxia/website/content/overview.html Thu Jul 2 03:00:56 2020
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/xdoc/overview.xml at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/xdoc/overview.xml at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -9,7 +9,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="Vincent Siveton" />
<meta name="Date-Creation-yyyymmdd" content="20090302" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Overview Of The Doxia Framework</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.7.min.css" />
@@ -42,7 +42,7 @@
<li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Overview Of The Doxia Framework <a href="https://github.com/apache/maven-doxia-site/tree/master/content/xdoc/overview.xml"><img src="./images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -111,7 +111,7 @@
<div id="bodyColumn" class="span10" >
- <div class="section">
+ <section>
<h2><a name="Overview_Of_The_Doxia_Framework"></a>Overview Of The Doxia Framework</h2>
<p>
@@ -143,8 +143,7 @@
<a class="externalLink" href="http://plexus.codehaus.org/">Plexus</a> extensively.
</p>
-
-<div class="section">
+ <section>
<h3><a name="Sink_API"></a>Sink API</h3>
<p>
@@ -172,10 +171,9 @@ sink.paragraph_(); </pre></div>
<p>To find out more about the Sink API, you could read the Javadoc
<a class="externalLink" href="http://maven.apache.org/doxia/doxia/doxia-sink-api/apidocs/org/apache/maven/doxia/sink/Sink.html">here</a>.
</p>
- </div>
+ </section>
-
-<div class="section">
+ <section>
<h3><a name="Doxia_Core"></a>Doxia Core</h3>
<p>
@@ -204,10 +202,9 @@ void parse( Reader source, Sink sink )
provides main definitions of a given Doxia module and it is used by the
<i>doxia-site-renderer</i> site tools.
</p>
- </div>
+ </section>
-
-<div class="section">
+ <section>
<h3><a name="Doxia_Modules"></a>Doxia Modules</h3>
<p>
@@ -231,10 +228,9 @@ void parse( Reader source, Sink sink )
For more information on modules, read the <a href="./modules/index.html">Doxia
Module Guide</a>.
</p>
- </div>
+ </section>
-
-<div class="section">
+ <section>
<h3><a name="Doxia_Site_Tools"></a>Doxia Site Tools</h3>
<p>
@@ -254,8 +250,8 @@ void parse( Reader source, Sink sink )
The <i>doxia-doc-renderer</i> tool is used to renderer any document in another
document.
</p>
- </div>
- </div>
+ </section>
+ </section>
</div>
Modified: maven/doxia/website/content/project-info.html
==============================================================================
--- maven/doxia/website/content/project-info.html (original)
+++ maven/doxia/website/content/project-info.html Thu Jul 2 03:00:56 2020
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from org.apache.maven.plugins:maven-site-plugin:3.7.1:CategorySummaryDocumentRenderer at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from org.apache.maven.plugins:maven-site-plugin:3.9.1:CategorySummaryDocumentRenderer at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – Project Information</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.7.min.css" />
@@ -40,7 +40,7 @@
<li class=""><a href="../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">Project Information</li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -116,10 +116,9 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Project_Information"></a>Project Information</h2>
-<p>This document provides an overview of the various documents and links that are part of this project's general information. All of this content is automatically generated by <a class="externalLink" href="http://maven.apache.org">Maven</a> on behalf of the project.</p>
-<div class="section">
+<p>This document provides an overview of the various documents and links that are part of this project's general information. All of this content is automatically generated by <a class="externalLink" href="http://maven.apache.org">Maven</a> on behalf of the project.</p><section>
<h3><a name="Overview"></a>Overview</h3>
<table border="0" class="table table-striped">
<tr class="a">
@@ -142,7 +141,7 @@
<td>This document provides information on the issue management system used in this project.</td></tr>
<tr class="a">
<td><a href="ci-management.html">CI Management</a></td>
-<td>This document lists the continuous integration management system of this project for building and testing code on a frequent, regular basis.</td></tr></table></div></div>
+<td>This document lists the continuous integration management system of this project for building and testing code on a frequent, regular basis.</td></tr></table></section></section>
</div>
</div>
</div>
Modified: maven/doxia/website/content/references/apt-format.html
==============================================================================
--- maven/doxia/website/content/references/apt-format.html (original)
+++ maven/doxia/website/content/references/apt-format.html Thu Jul 2 03:00:56 2020
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/references/apt-format.apt at 2020-06-19
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/apt/references/apt-format.apt at 2020-07-02
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -9,7 +9,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="author" content="Jason van Zyl" />
<meta name="Date-Creation-yyyymmdd" content="20090302" />
- <meta name="Date-Revision-yyyymmdd" content="20200619" />
+ <meta name="Date-Revision-yyyymmdd" content="20200702" />
<meta http-equiv="Content-Language" content="en" />
<title>Doxia – The APT format</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.7.min.css" />
@@ -42,7 +42,7 @@
<li class=""><a href="../../index.html" title="Maven">Maven</a><span class="divider">/</span></li>
<li class=""><a href="../index.html" title="Doxia">Doxia</a><span class="divider">/</span></li>
<li class="active ">The APT format <a href="https://github.com/apache/maven-doxia-site/tree/master/content/apt/references/apt-format.apt"><img src="../images/accessories-text-editor.png" title="Edit" /></a></li>
- <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-06-19</li>
+ <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2020-07-02</li>
<li class="pull-right"><a href="../scm.html" title="Get Sources">Get Sources</a></li>
</ul>
</div>
@@ -119,15 +119,13 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="The_APT_format"></a>The APT format</h2>
<p>APT stands for "Almost Plain Text". APT is a markup language that takes the hassle out of documentation writing by striving for simplicity. Its syntax resembles plain-text more than it resembles most other markup formats (such as HTML).</p>
-<p>This document provides some examples of available APT formatting.</p>
-<div class="section">
+<p>This document provides some examples of available APT formatting.</p><section>
<h3><a name="Important_Notice"></a>Important Notice</h3>
<p>The information contained in this document corresponds to the original APT format as published by <a class="externalLink" href="http://www.xmlmind.com/">Xmlmind</a>. In version 1.1 Maven Doxia has applied several modifications to this original format, see this separate <a href="./doxia-apt.html">document</a> for a detailed description. Notable differences are highlighted below with a <a href="./doxia-apt.html">[Change]</a> link.</p>
-<p>The following sections contain formatted text that demonstrates the use of APT to create paragraphs, headers, sections, lists, code samples, figures, tables, rules, breaks, and text level elements such as font styles, anchors, and special characters. Boxes containing text in typewriter-like font are examples of APT source.</p></div>
-<div class="section">
+<p>The following sections contain formatted text that demonstrates the use of APT to create paragraphs, headers, sections, lists, code samples, figures, tables, rules, breaks, and text level elements such as font styles, anchors, and special characters. Boxes containing text in typewriter-like font are examples of APT source.</p></section><section>
<h3><a name="Document_structure">Document structure</a></h3>
<p>A short APT document is contained in a single text file. A longer document may be contained in a ordered list of text files. For instance, first text file contains section 1, second text file contains section 2, and so on.</p>
<dl>
@@ -154,12 +152,9 @@ other lines of the paragraph.
Second paragraph contains several lines which are all
indented by two spaces. This style is much nicer than
the one used for the previous paragraph.</pre></div>
-<p>Note that tabs are expanded with a tab width set to 8.</p></div>
-<div class="section">
-<h3><a name="Document_elements"></a>Document elements</h3>
-<div class="section">
-<h4><a name="Block_level_elements"></a>Block level elements</h4>
-<div class="section">
+<p>Note that tabs are expanded with a tab width set to 8.</p></section><section>
+<h3><a name="Document_elements"></a>Document elements</h3><section>
+<h4><a name="Block_level_elements"></a>Block level elements</h4><section>
<h5><a name="Title"></a>Title</h5>
<p>A title is optional. If used, it must appear as the first block of the document.</p>
<div class="source"><pre class="prettyprint linenums"> ------
@@ -168,9 +163,9 @@ other lines of the paragraph.
Author
------
Date</pre></div>
-<p>A title block is indented (centering it is nicer). It begins with a line containing at least 3 dashes (<tt>---</tt>).</p>
-<p>After the first <tt>---</tt> line, one or several consecutive lines of text (implicit line break after each line) specify the title of the document.</p>
-<p>This text may immediately be followed by another <tt>---</tt> line and one or several consecutive lines of text which specifies the author of the document.</p>
+<p>A title block is indented (centering it is nicer). It begins with a line containing at least 3 dashes (<code>---</code>).</p>
+<p>After the first <code>---</code> line, one or several consecutive lines of text (implicit line break after each line) specify the title of the document.</p>
+<p>This text may immediately be followed by another <code>---</code> line and one or several consecutive lines of text which specifies the author of the document.</p>
<p>The author sub-block may optionally be followed by a date sub-block using the same syntax.</p>
<p>The following example is used for a document with an title and a date but with no declared author.</p>
<div class="source"><pre class="prettyprint linenums"> ------
@@ -182,8 +177,7 @@ other lines of the paragraph.
<p>The last line is ignored. It is just there to make the block nicer.</p>
<p><b>Note</b>: the date has no specific format and will be parsed as string. But we recommend to use the ISO-8601 standard, since formatting a date varies around the world:</p>
<p><b>YYYY-MM-DD</b></p>
-<p>where <b>YYYY</b> is the year in the Gregorian calendar, <b>MM</b> is the month of the year between 01 (January) and 12 (December), and <b>DD</b> is the day of the month between 01 and 31.</p></div>
-<div class="section">
+<p>where <b>YYYY</b> is the year in the Gregorian calendar, <b>MM</b> is the month of the year between 01 (January) and 12 (December), and <b>DD</b> is the day of the month between 01 and 31.</p></section><section>
<h5><a name="Paragraph"></a>Paragraph</h5>
<p>Paragraphs other than the title block may appear before the first section.</p>
<div class="source"><pre class="prettyprint linenums"> Paragraph 1, line 1.
@@ -191,8 +185,7 @@ other lines of the paragraph.
Paragraph 2, line 1.
Paragraph 2, line 2.</pre></div>
-<p>Paragraphs are indented. They have already been described in the <a href="#Document_structure">Document structure</a> section.</p></div>
-<div class="section">
+<p>Paragraphs are indented. They have already been described in the <a href="#Document_structure">Document structure</a> section.</p></section><section>
<h5><a name="Section"></a>Section</h5>
<p>Sections are created by inserting section titles into the document. Simple documents need not contain sections.</p>
<div class="source"><pre class="prettyprint linenums">Section title
@@ -204,8 +197,7 @@ other lines of the paragraph.
*** Sub-sub-sub-section title
**** Sub-sub-sub-sub-section title</pre></div>
-<p>Section titles are not indented. A sub-section title begins with one asterisk (<tt>*</tt>), a sub-sub-section title begins with two asterisks (<tt>**</tt>), and so forth up to four sub-section levels.</p></div>
-<div class="section">
+<p>Section titles are not indented. A sub-section title begins with one asterisk (<code>*</code>), a sub-sub-section title begins with two asterisks (<code>**</code>), and so forth up to four sub-section levels.</p></section><section>
<h5><a name="List"></a>List</h5>
<div class="source"><pre class="prettyprint linenums"> * List item 1.
@@ -218,10 +210,10 @@ other lines of the paragraph.
* Sub-list item 2.
* List item 3.</pre></div>
-<p>List items are indented and begin with a asterisk (<tt>*</tt>).</p>
+<p>List items are indented and begin with a asterisk (<code>*</code>).</p>
<p>Plain paragraphs more indented than the first list item are nested in that list. Displays such as tables (not indented) are always nested in the current list.</p>
<p>To nest a list inside a list, indent its first item more than its parent list. To end a list, add a paragraph or list item less indented than the current list.</p>
-<p>Section titles always end a list. Displays cannot end a list but the <tt>[]</tt> pseudo-element may be used to force the end of a list.</p>
+<p>Section titles always end a list. Displays cannot end a list but the <code>[]</code> pseudo-element may be used to force the end of a list.</p>
<div class="source"><pre class="prettyprint linenums"> * List item 3.
Force end of list:
@@ -230,8 +222,8 @@ other lines of the paragraph.
--------------------------------------------
Verbatim text not contained in list item 3
--------------------------------------------</pre></div>
-<p>In the previous example, without the <tt>[]</tt>, the verbatim text (not indented as all displays) would have been contained in list item 3.</p>
-<p>A single <tt>[]</tt> may be used to end several nested lists at the same time. The indentation of <tt>[]</tt> may be used to specify exactly which lists should be ended. Example:</p>
+<p>In the previous example, without the <code>[]</code>, the verbatim text (not indented as all displays) would have been contained in list item 3.</p>
+<p>A single <code>[]</code> may be used to end several nested lists at the same time. The indentation of <code>[]</code> may be used to specify exactly which lists should be ended. Example:</p>
<div class="source"><pre class="prettyprint linenums"> * List item 1.
* List item 2.
@@ -255,22 +247,21 @@ Verbatim text contained in list item 2,
[[2]] Numbered item 2.</pre></div>
<p>A numbered list item begins with a label between two square brackets. The label of the first item establishes the numbering scheme for the whole list:</p>
<dl>
-<dt><tt>[[1]]</tt></dt>
+<dt><code>[[1]]</code></dt>
<dd>Decimal numbering: 1, 2, 3, 4, etc.</dd>
-<dt><tt>[[a]]</tt></dt>
+<dt><code>[[a]]</code></dt>
<dd>Lower-alpha numbering: a, b, c, d, etc.</dd>
-<dt><tt>[[A]]</tt></dt>
+<dt><code>[[A]]</code></dt>
<dd>Upper-alpha numbering: A, B, C, D, etc.</dd>
-<dt><tt>[[i]]</tt></dt>
+<dt><code>[[i]]</code></dt>
<dd>Lower-roman numbering: i, ii, iii, iv, etc.</dd>
-<dt><tt>[[I]]</tt></dt>
+<dt><code>[[I]]</code></dt>
<dd>Upper-roman numbering: I, II, III, IV, etc.</dd></dl>
<p>The labels of the items other than the first one are ignored. It is recommended to take the time to type the correct label for each item in order to keep the APT source document readable.</p>
<div class="source"><pre class="prettyprint linenums"> [Defined term 1] of definition list 2.
[Defined term 2] of definition list 2.</pre></div>
-<p>A definition list item begins with a defined term: text between square brackets.</p></div>
-<div class="section">
+<p>A definition list item begins with a defined term: text between square brackets.</p></section><section>
<h5><a name="Verbatim_text"></a>Verbatim text</h5>
<div class="source"><pre class="prettyprint linenums">----------------------------------------
Verbatim
@@ -278,24 +269,22 @@ Verbatim
preformatted,
escaped.
----------------------------------------</pre></div>
-<p>A verbatim block is not indented. It begins with a non indented line containing at least 3 dashes (<tt>---</tt>). It ends with a similar line.</p>
-<p><tt>+--</tt> instead of <tt>---</tt> draws a box around verbatim text.</p>
-<p>Like in HTML, verbatim text is preformatted. Unlike HTML, verbatim text is escaped: inside a verbatim display, markup is not interpreted by the APT processor.</p></div>
-<div class="section">
+<p>A verbatim block is not indented. It begins with a non indented line containing at least 3 dashes (<code>---</code>). It ends with a similar line.</p>
+<p><code>+--</code> instead of <code>---</code> draws a box around verbatim text.</p>
+<p>Like in HTML, verbatim text is preformatted. Unlike HTML, verbatim text is escaped: inside a verbatim display, markup is not interpreted by the APT processor.</p></section><section>
<h5><a name="Figure"></a>Figure</h5>
<div class="source"><pre class="prettyprint linenums">[Figure name] Figure caption</pre></div>
<p>A figure block is not indented. It begins with the figure name between square brackets. The figure name is optionally followed by some text: the figure caption.</p>
-<p>The figure name is the pathname of the file containing the figure but without an extension. Example: if your figure is contained in <tt>/home/joe/docs/mylogo.jpeg</tt>, the figure name is <tt>/home/joe/docs/mylogo</tt>. <a href="./doxia-apt.html#Figure_extensions">[Change]</a></p>
+<p>The figure name is the pathname of the file containing the figure but without an extension. Example: if your figure is contained in <code>/home/joe/docs/mylogo.jpeg</code>, the figure name is <code>/home/joe/docs/mylogo</code>. <a href="./doxia-apt.html#Figure_extensions">[Change]</a></p>
<p>If the figure name comes from a relative pathname (recommended practice) rather than from an absolute pathname, this relative pathname is taken to be relative to the directory of the current APT document (a la HTML) rather than relative to the current working directory.</p>
-<p>Why not leave the file extension in the figure name? This is better explained by an example. You need to convert an APT document to PostScript and your figure name is <tt>/home/joe/docs/mylogo</tt>. An APT processor will first try to load <tt>/home/joe/docs/mylogo.eps</tt>. When the desired format is not found, a APT processor tries to convert one of the existing formats. In our example, the APT processor tries to convert <tt>/home/joe/docs/mylogo.jpeg</tt> to encapsulated PostScript.</p></div>
-<div class="section">
+<p>Why not leave the file extension in the figure name? This is better explained by an example. You need to convert an APT document to PostScript and your figure name is <code>/home/joe/docs/mylogo</code>. An APT processor will first try to load <code>/home/joe/docs/mylogo.eps</code>. When the desired format is not found, a APT processor tries to convert one of the existing formats. In our example, the APT processor tries to convert <code>/home/joe/docs/mylogo.jpeg</code> to encapsulated PostScript.</p></section><section>
<h5><a name="Table"></a>Table</h5>
-<p>A table block is not indented. It begins with a non indented line containing an asterisk and at least 2 dashes (<tt>*--</tt>). It ends with a similar line.</p>
+<p>A table block is not indented. It begins with a non indented line containing an asterisk and at least 2 dashes (<code>*--</code>). It ends with a similar line.</p>
<p>The first line is not only used to recognize a table but also to specify column justification. In the following example,</p>
<ul>
-<li>the second asterisk (<tt>*</tt>) is used to specify that column 1 is centered,</li>
-<li>the plus sign (<tt>+</tt>) specifies that column 2 is left aligned,</li>
-<li>the colon (<tt>:</tt>) specifies that column 3 is right aligned.</li></ul>
+<li>the second asterisk (<code>*</code>) is used to specify that column 1 is centered,</li>
+<li>the plus sign (<code>+</code>) specifies that column 2 is left aligned,</li>
+<li>the colon (<code>:</code>) specifies that column 3 is right aligned.</li></ul>
<div class="source"><pre class="prettyprint linenums">*----------*--------------+----------------:
| Centered | Left-aligned | Right-aligned |
| cell 1,1 | cell 1,2 | cell 1,3 |
@@ -303,66 +292,57 @@ Verbatim
| cell 2,1 | cell 2,2 | cell 2,3 |
*----------*--------------+----------------:
Table caption</pre></div>
-<p>Rows are separated by a non indented line beginning with <tt>*--</tt>.</p>
+<p>Rows are separated by a non indented line beginning with <code>*--</code>.</p>
<p>An optional table caption (non indented text) may immediately follow the table.</p>
-<p>Rows may contain single line or multiple line cells. Each line of cell text is separated from the adjacent cell by the pipe character (<tt>|</tt>). (<tt>|</tt> may be used in the cell text if quoted: <tt>\|</tt>.)</p>
-<p>The last <tt>|</tt> is only used to make the table nicer. The first <tt>|</tt> is not only used to make the table nicer, but also to specify that a grid is to be drawn around table cells.</p>
+<p>Rows may contain single line or multiple line cells. Each line of cell text is separated from the adjacent cell by the pipe character (<code>|</code>). (<code>|</code> may be used in the cell text if quoted: <code>\|</code>.)</p>
+<p>The last <code>|</code> is only used to make the table nicer. The first <code>|</code> is not only used to make the table nicer, but also to specify that a grid is to be drawn around table cells.</p>
<p>The following example shows a simple table with no grid and no caption.</p>
<div class="source"><pre class="prettyprint linenums">*-----*------*
cell | cell
*-----*------*
cell | cell
-*-----*------*</pre></div></div>
-<div class="section">
+*-----*------*</pre></div></section><section>
<h5><a name="Horizontal_rule"></a>Horizontal rule</h5>
<div class="source"><pre class="prettyprint linenums">=====================</pre></div>
-<p>A non indented line containing at least 3 equal signs (<tt>===</tt>).</p></div>
-<div class="section">
+<p>A non indented line containing at least 3 equal signs (<code>===</code>).</p></section><section>
<h5><a name="Page_break"></a>Page break</h5>
<div class="source"><pre class="prettyprint linenums">^L</pre></div>
-<p>A non indented line containing a single form feed character (Control-L).</p></div></div>
-<div class="section">
-<h4><a name="Text_level_elements"></a>Text level elements</h4>
-<div class="section">
+<p>A non indented line containing a single form feed character (Control-L).</p></section></section><section>
+<h4><a name="Text_level_elements"></a>Text level elements</h4><section>
<h5><a name="Font"></a>Font</h5>
<div class="source"><pre class="prettyprint linenums"> <Italic> font. <<Bold>> font. <<<Monospaced>>> font.</pre></div>
<p>Text between < and > must be rendered in italic. Text between << and >> must be rendered in bold. Text between <<< and >>> must be rendered using a monospaced, typewriter-like font.</p>
<p>Font elements may appear anywhere except inside other font elements.</p>
-<p>It is not recommended to use font elements inside titles, section titles, links and defined terms because an APT processor automatically applies appropriate font styles to these elements.</p></div>
-<div class="section">
+<p>It is not recommended to use font elements inside titles, section titles, links and defined terms because an APT processor automatically applies appropriate font styles to these elements.</p></section><section>
<h5><a name="Anchor_and_link"></a>Anchor and link</h5>
<div class="source"><pre class="prettyprint linenums"> {Anchor}. Link to {{anchor}}. Link to {{http://www.pixware.fr}}.
Link to {{{anchor}showing alternate text}}.
Link to {{{http://www.pixware.fr}Pixware home page}}.</pre></div>
-<p>Text between curly braces (<tt>{}</tt>) specifies an anchor. Text between double curly braces (<tt>{{}}</tt>) specifies a link.</p>
+<p>Text between curly braces (<code>{}</code>) specifies an anchor. Text between double curly braces (<code>{{}}</code>) specifies a link.</p>
<p>It is an error to create a link element that does not refer to an anchor of the same name. The name of an anchor/link is its text with all non alphanumeric characters stripped. <a href="./doxia-apt.html#Anchor_construction">[Change]</a></p>
-<p>This rule does not apply to links to <i>external</i> anchors. Text beginning with <tt>http:/</tt>, <tt>https:/</tt>, <tt>ftp:/</tt>, <tt>file:/</tt>, <tt>mailto:</tt>, <tt>../</tt>, <tt>./</tt> (<tt>..\</tt> and <tt>.\</tt> on Windows) is recognized as an external anchor name.</p>
+<p>This rule does not apply to links to <i>external</i> anchors. Text beginning with <code>http:/</code>, <code>https:/</code>, <code>ftp:/</code>, <code>file:/</code>, <code>mailto:</code>, <code>../</code>, <code>./</code> (<code>..\</code> and <code>.\</code> on Windows) is recognized as an external anchor name.</p>
<p>When the construct <b>{{{</b><i>name</i><b>}</b><i>text</i><b>}}</b> is used, the link text <i>text</i> may differ from the link name <i>name</i>.</p>
<p>Anchor/link elements may appear anywhere except inside other anchor/link elements.</p>
-<p>Section titles are implicitly defined anchors. <a href="./doxia-apt.html#Anchors_for_section_titles">[Change]</a></p></div>
-<div class="section">
+<p>Section titles are implicitly defined anchors. <a href="./doxia-apt.html#Anchors_for_section_titles">[Change]</a></p></section><section>
<h5><a name="Line_break"></a>Line break</h5>
<div class="source"><pre class="prettyprint linenums"> Force line\
break.</pre></div>
-<p>A backslash character (<tt>\</tt>) followed by a newline character.</p>
-<p>Line breaks must not be used inside titles and tables (which are line oriented blocks with implicit line breaks).</p></div>
-<div class="section">
+<p>A backslash character (<code>\</code>) followed by a newline character.</p>
+<p>Line breaks must not be used inside titles and tables (which are line oriented blocks with implicit line breaks).</p></section><section>
<h5><a name="Non_breaking_space"></a>Non breaking space</h5>
<div class="source"><pre class="prettyprint linenums"> Non\ breaking\ space.</pre></div>
-<p>A backslash character (<tt>\</tt>) followed by a space character.</p></div>
-<div class="section">
+<p>A backslash character (<code>\</code>) followed by a space character.</p></section><section>
<h5><a name="Special_character"></a>Special character</h5>
<div class="source"><pre class="prettyprint linenums"> Escaped special characters: \~, \=, \-, \+, \*, \[, \], \<, \>, \{, \}, \\.</pre></div>
<p>In certain contexts, these characters have a special meaning and therefore must be escaped if needed as is. They are escaped by adding a backslash in front of them. The backslash may itself be escaped by adding another backslash in front of it.</p>
-<p>Note that an asterisk, for example, needs to be escaped only if its begins a paragraph. (<tt>*</tt> has no special meaning in the middle of a paragraph.)</p>
+<p>Note that an asterisk, for example, needs to be escaped only if its begins a paragraph. (<code>*</code> has no special meaning in the middle of a paragraph.)</p>
<div class="source"><pre class="prettyprint linenums"> Copyright symbol: \251, \xA9, \u00a9.</pre></div>
-<p>Latin-1 characters (whatever is the encoding of the APT document) may be specified by their codes using a backslash followed by one to three octal digits or by using the <tt>\x</tt><i>NN</i> notation, where <i>NN</i> are two hexadecimal digits.</p>
-<p>Unicode characters may be specified by their codes using the <tt>\u</tt><i>NNNN</i> notation, where <i>NNNN</i> are four hexadecimal digits.</p></div>
-<div class="section">
+<p>Latin-1 characters (whatever is the encoding of the APT document) may be specified by their codes using a backslash followed by one to three octal digits or by using the <code>\x</code><i>NN</i> notation, where <i>NN</i> are two hexadecimal digits.</p>
+<p>Unicode characters may be specified by their codes using the <code>\u</code><i>NNNN</i> notation, where <i>NNNN</i> are four hexadecimal digits.</p></section><section>
<h5><a name="Comment"></a>Comment</h5>
<div class="source"><pre class="prettyprint linenums">~~Commented out.</pre></div>
-<p>Text found after two tildes (<tt>~~</tt>) is ignored up to the end of line.</p>
-<p>A line of <tt>~</tt> is often used to ``underline'' section titles in order to make them stand out of other paragraphs.</p><!-- PB -->
+<p>Text found after two tildes (<code>~~</code>) is ignored up to the end of line.</p>
+<p>A line of <code>~</code> is often used to ``underline'' section titles in order to make them stand out of other paragraphs.</p><!-- PB -->
<div>
<pre> ------
Title
@@ -468,7 +448,7 @@ Table caption
Copyright symbol: \251, \xA9, \u00a9.
~~Commented out.
-</pre></div></div></div></div></div>
+</pre></div></section></section></section></section>
</div>
</div>
</div>