You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sis.apache.org by de...@apache.org on 2021/05/14 10:28:13 UTC

[sis-site] branch asf-site updated: First web-site generation using Hugo. Should have the same content than previous site.

This is an automated email from the ASF dual-hosted git repository.

desruisseaux pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/sis-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new fd6c987  First web-site generation using Hugo. Should have the same content than previous site.
fd6c987 is described below

commit fd6c987d2aeecf46911374f95ada0d097c0728ab
Author: Martin Desruisseaux <ma...@geomatys.com>
AuthorDate: Fri May 14 12:26:54 2021 +0200

    First web-site generation using Hugo. Should have the same content than previous site.
---
 build.html                             | 291 ++++++------
 code-patterns.html                     | 301 ++++++------
 coding-conventions.html                | 391 +++++++--------
 command-line.html                      | 477 +++++++++----------
 contributor.html                       | 318 +++++++------
 css/syntax.css                         |  70 +++
 downloads.html                         | 290 ++++++------
 epsg.html                              | 407 ++++++++--------
 faq.html                               | 843 ++++++++++++++++++++-------------
 faq_fr.html                            | 785 ++++++++++++++++++------------
 gdal.html                              | 269 ++++++-----
 index.html                             | 236 ++++-----
 index.xml                              | 172 +++++++
 mail-lists.html                        | 229 ++++-----
 openoffice/en/formula.html             |   4 +-
 openoffice/en/install.html             |   2 +-
 openoffice/fr/formula.html             |   4 +-
 openoffice/fr/install.html             |   2 +-
 release-management-setup.html          | 334 ++++++-------
 release-management.html                | 769 +++++++++++++-----------------
 release-notes/0.7.html                 |   2 +-
 robots.txt                             |   6 +
 site-management.html                   | 296 ++++++------
 sitemap.xml                            |  90 ++++
 source.html                            | 361 +++++++-------
 tables/CoordinateOperationMethods.html |   4 +-
 team-list.html                         | 217 +++++----
 27 files changed, 3892 insertions(+), 3278 deletions(-)

diff --git a/build.html b/build.html
index 0f86843..7207ce6 100644
--- a/build.html
+++ b/build.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Build from source</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Build from source</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,87 +37,118 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Build from source</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>Apache SIS is built by Maven.
-For installing the JAR files in the local Maven repository, execute the following command
-from the SIS project root:</p>
-<div class="codehilite"><pre>mvn install
-</pre></div>
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
 
 
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Build from source</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>Apache SIS is built by Maven.
+For installing the JAR files in the local Maven repository, execute the following command
+from the SIS project root:</p>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mvn install</code></pre></div>
 <p>For signing the artifacts and producing distribution files (<code>apache-sis-bin.zip</code> and <code>apache-sis.oxt</code>),
 execute the following command.
 Note that it requires an OpenPGP (<em>Open Pretty Good Privacy</em>) software for cryptography signatures
 (more information on the <a href="release-management-setup.html#generate-key">release management setup</a> page):</p>
-<div class="codehilite"><pre>mvn install --activate-profiles apache-release
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mvn install --activate-profiles apache-release</code></pre></div>
 <p>The remaining of this page provides more advanced tips for SIS developers.</p>
-<div class="toc">
-<ul>
-<li><a href="#dist">Distribution file</a><ul>
-<li><a href="#limitations">Known limitations</a></li>
-</ul>
-</li>
-<li><a href="#build-helper">SIS-specific Maven plugin</a><ul>
-<li><a href="#resources">Localized resources compiler</a></li>
-<li><a href="#jar-collect">JAR files collector</a></li>
-</ul>
-</li>
-</ul>
-</div>
-<h1 id="dist">Distribution file<a class="headerlink" href="#dist" title="Permanent link">&para;</a></h1>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#dist">Distribution file  </a>
+      <ul>
+        <li><a href="#limitations">Known limitations  </a></li>
+      </ul>
+    </li>
+    <li><a href="#build-helper">SIS-specific Maven plugin  </a>
+      <ul>
+        <li><a href="#resources">Localized resources compiler   </a></li>
+        <li><a href="#jar-collect">JAR files collector   </a></li>
+      </ul>
+    </li>
+  </ul>
+</nav>
+<h1 id="dist">Distribution file  </h1>
 <p>The distribution archive is a file with the <code>.zip</code> extension containing most SIS modules except <code>sis-webapp</code>
 (because Web applications use an other packaging) together with their dependencies.
 However for users convenience, we provide a shell script launching the SIS command line tool.
 That shell script, together with other files (<code>README</code>, <code>LICENSE</code>, <i>etc.</i>) are bundled in a ZIP file created as below:</p>
-<div class="codehilite"><pre><span class="nb">cd </span>application/sis-console
-mvn package org.apache.sis.core:sis-build-helper:dist
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> application/sis-console
+mvn package org.apache.sis.core:sis-build-helper:dist</code></pre></div>
 <p>This task is executed automatically if the <code>apache-release</code> profile is activated at build time.
 Above command is for the cases where the developer wants the distribution file without rebuilding the whole project.
 Optionally, the Apache SIS version can be inserted as a 4th element between <code>sis-build-helper:</code> and <code>:dist</code>
 if there is many versions of the plugin in the local repository.</p>
 <p>The result will be created in the <code>target/distribution/apache-sis-&lt;version&gt;.zip</code> file.
 To test, uncompress in any directory and execute <code>apache-sis-&lt;version&gt;/bin/sis</code>.</p>
-<h2 id="limitations">Known limitations<a class="headerlink" href="#limitations" title="Permanent link">&para;</a></h2>
+<h2 id="limitations">Known limitations  </h2>
 <p>The current plugin implementation has some hard-coded values, especially:</p>
 <ul>
 <li>The ZIP file content is copied from the <code>application/sis-console/src/main/artifact</code> directory.</li>
 <li>The final filename is hard-coded to <code>apache-sis-&lt;version&gt;.zip</code>.</li>
 </ul>
-<h1 id="build-helper">SIS-specific Maven plugin<a class="headerlink" href="#build-helper" title="Permanent link">&para;</a></h1>
+<h1 id="build-helper">SIS-specific Maven plugin  </h1>
 <p>Apache SIS uses a <code>sis-build-helper</code> plugin for SIS-specific tasks and Javadoc customization.
 This plugin is used automatically by <code>mvn install</code>. Consequently the remaining of this page
 can be safely ignored. This page is provided only as a reference for developers wanting to
 take a closer look to SIS <code>pom.xml</code> file.</p>
-<h2 id="resources">Localized resources compiler<a class="headerlink" href="#resources" title="Permanent link">&para;</a></h2>
+<h2 id="resources">Localized resources compiler   </h2>
 <p>Localized resources are provided in <code>*.properties</code> files as specified by the <code>java.util.PropertyResourceBundle</code> standard class.
 However SIS does not use those resources files directly. Instead <code>*.properties</code> files are transformed into binary files having
 the same filename but the <code>.utf</code> extension. This conversion is done for efficiency, for convenience (the compiler applies the
@@ -166,7 +160,7 @@ and contains a public static inner class named <code>Keys</code>, then the compi
 with the list of keys found in the <code>Vocabulary*.properties</code> files.</p>
 <p>The resource compiler is executed at Maven build time if the <code>pom.xml</code> file contains the following declaration. Note that current
 implementation looks only for resources in any package ending with the <code>resources</code> name; all other packages are ignored.</p>
-<div class="codehilite"><pre><span class="nt">&lt;build&gt;</span>
+<div class="highlight"><pre class="chroma"><code class="language-xml" data-lang="xml"><span class="nt">&lt;build&gt;</span>
   <span class="nt">&lt;plugins&gt;</span>
     <span class="nt">&lt;plugin&gt;</span>
       <span class="nt">&lt;groupId&gt;</span>org.apache.sis.core<span class="nt">&lt;/groupId&gt;</span>
@@ -181,32 +175,26 @@ implementation looks only for resources in any package ending with the <code>res
       <span class="nt">&lt;/executions&gt;</span>
     <span class="nt">&lt;/plugin&gt;</span>
   <span class="nt">&lt;/plugins&gt;</span>
-<span class="nt">&lt;/build&gt;</span>
-</pre></div>
-
-
+<span class="nt">&lt;/build&gt;</span></code></pre></div>
 <p>The resources compilation is part of the build process and does not need to be run explicitly.
 However, if necessary the resources compiler can be invoked alone by the following command line
 in the module containing the resources to recompile. This is sometime useful for regenerating
 the constants in the <code>Keys</code> inner class in a feaster way than building the project.</p>
-<div class="codehilite"><pre>mvn org.apache.sis.core:sis-build-helper:compile-resources
-</pre></div>
-
-
-<h2 id="jar-collect">JAR files collector<a class="headerlink" href="#jar-collect" title="Permanent link">&para;</a></h2>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mvn org.apache.sis.core:sis-build-helper:compile-resources</code></pre></div>
+<h2 id="jar-collect">JAR files collector   </h2>
 <p>Links or lists all JAR files (including dependencies) in the <code>target/binaries</code> directory of the parent project.
 This plugin performs a work similar to the standard Maven assembly plugin work, with the following differences:</p>
 <ul>
 <li>In multi-modules projects, this plugin does not create anything in the <code>target</code> directory of sub-modules.
-     Instead, this plugin groups everything in the <code>target/binaries</code> directory of the parent module.</li>
+Instead, this plugin groups everything in the <code>target/binaries</code> directory of the parent module.</li>
 <li>This plugin does not create any ZIP file. It only links or lists JAR files.
-     This plugin uses hard links on platforms that support them,
-     so execution of this plugin should be very cheap and consume few disk space.</li>
+This plugin uses hard links on platforms that support them,
+so execution of this plugin should be very cheap and consume few disk space.</li>
 <li>Dependencies already present in the <code>target/binaries</code> directory are presumed stables and
-     are not overwritten. Only artifacts produced by the Maven build are unconditionally overwritten.</li>
+are not overwritten. Only artifacts produced by the Maven build are unconditionally overwritten.</li>
 </ul>
 <p>This plugin can be activated by the following fragment in the parent <code>pom.xml</code> file:</p>
-<div class="codehilite"><pre><span class="nt">&lt;build&gt;</span>
+<div class="highlight"><pre class="chroma"><code class="language-xml" data-lang="xml"><span class="nt">&lt;build&gt;</span>
   <span class="nt">&lt;plugins&gt;</span>
     <span class="nt">&lt;plugin&gt;</span>
       <span class="nt">&lt;groupId&gt;</span>org.apache.sis.core<span class="nt">&lt;/groupId&gt;</span>
@@ -221,33 +209,38 @@ This plugin performs a work similar to the standard Maven assembly plugin work,
       <span class="nt">&lt;/executions&gt;</span>
     <span class="nt">&lt;/plugin&gt;</span>
   <span class="nt">&lt;/plugins&gt;</span>
-<span class="nt">&lt;/build&gt;</span>
-</pre></div>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
+<span class="nt">&lt;/build&gt;</span></code></pre></div>
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
-    </div>
-  </footer>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+        </article>
+      </section>
+    </div>
+  </div>
+</div>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
+
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/code-patterns.html b/code-patterns.html
index 990e8af..6eec4c0 100644
--- a/code-patterns.html
+++ b/code-patterns.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Recommended code patterns</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Recommended code patterns</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,102 +37,140 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Recommended code patterns</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>This page lists some recommended code pattern for developing or using Apache SIS.</p>
-<div class="toc">
-<ul>
-<li><a href="#referencing">Referencing</a><ul>
-<li><a href="#axisOrder">Never explicitely swap ordinates for axis order</a></li>
-</ul>
-</li>
-<li><a href="#coverage">Coverages</a><ul>
-<li><a href="#gridToCRS">Georeference images with affine transforms, not bounding boxes</a></li>
-</ul>
-</li>
-<li><a href="#international">International</a><ul>
-<li><a href="#timezone">Specify timezone</a></li>
-<li><a href="#sort">Replace underscores by spaces before sorting</a></li>
-<li><a href="#unicode-loop">Loop over character sequences using code points</a></li>
-</ul>
-</li>
-<li><a href="#logging">Logging</a></li>
-</ul>
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
 </div>
-<h1 id="referencing">Referencing<a class="headerlink" href="#referencing" title="Permanent link">&para;</a></h1>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Recommended code patterns</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>This page lists some recommended code pattern for developing or using Apache SIS.</p>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#referencing">Referencing   </a>
+      <ul>
+        <li><a href="#axisOrder">Never explicitely swap ordinates for axis order   </a></li>
+      </ul>
+    </li>
+    <li><a href="#coverage">Coverages   </a>
+      <ul>
+        <li><a href="#gridToCRS">Georeference images with affine transforms, <em>not</em> bounding boxes   </a></li>
+      </ul>
+    </li>
+    <li><a href="#international">International   </a>
+      <ul>
+        <li><a href="#timezone">Specify timezone   </a></li>
+        <li><a href="#sort">Replace underscores by spaces before sorting   </a></li>
+        <li><a href="#unicode-loop">Loop over character sequences using code points   </a></li>
+      </ul>
+    </li>
+    <li><a href="#logging">Logging   </a></li>
+  </ul>
+</nav>
+<h1 id="referencing">Referencing   </h1>
 <p>Recommended code pattern when using the <code>sis-referencing</code> module.</p>
-<h2 id="axisOrder">Never explicitely swap ordinates for axis order<a class="headerlink" href="#axisOrder" title="Permanent link">&para;</a></h2>
+<h2 id="axisOrder">Never explicitely swap ordinates for axis order   </h2>
 <p>The <a href="faq.html#axisOrder">axis order issue</a> causes lot of confusion,
 and developers are sometime tempted to swap their ordinate values in order to comply with some expected axis ordering.
 It should never be necessary, since the Apache SIS referencing engine manages axis order transparently — provided that
-the Coordinate Reference System (<abbr title="Coordinate Reference System">CRS</abbr>) definition is accurate. If a code needs to swap ordinates, this is probably an
-indication that the <abbr title="Coordinate Reference System">CRS</abbr> has not been properly defined. Instead than patching the coordinate values, try to make sure
-that the <em>Source <abbr title="Coordinate Reference System">CRS</abbr></em> (associated to the original data) and the <em>Target <abbr title="Coordinate Reference System">CRS</abbr></em> (the coordinate space where to perform the
-work) are properly defined, and let the referencing engine performs the conversion from the source to the target <abbr title="Coordinate Reference System">CRS</abbr>.</p>
-<h1 id="coverage">Coverages<a class="headerlink" href="#coverage" title="Permanent link">&para;</a></h1>
+the Coordinate Reference System (CRS) definition is accurate. If a code needs to swap ordinates, this is probably an
+indication that the CRS has not been properly defined. Instead than patching the coordinate values, try to make sure
+that the <em>Source CRS</em> (associated to the original data) and the <em>Target CRS</em> (the coordinate space where to perform the
+work) are properly defined, and let the referencing engine performs the conversion from the source to the target CRS.</p>
+<h1 id="coverage">Coverages   </h1>
 <p>Recommended code pattern when using the <code>sis-coverage</code> module.</p>
-<h2 id="gridToCRS">Georeference images with affine transforms, <em>not</em> bounding boxes<a class="headerlink" href="#gridToCRS" title="Permanent link">&para;</a></h2>
+<h2 id="gridToCRS">Georeference images with affine transforms, <em>not</em> bounding boxes   </h2>
 <p>Many users define the geographic extent of an image by its corner locations.
 This approach may be ambiguous as it does not specify whether the (<var>x</var>,<var>y</var>) axes are interchanged
 (see the <a href="faq.html#axisOrder">axis order issue</a>) or if the <var>y</var> axis is oriented downward.
 All images in SIS shall be georeferenced by at least an affine transform (more complex transforms are also possible),
 never by a rectangle or bounding box.
 In the two-dimensional case, the standard <code>java.awt.geom.AffineTransform</code> class can be used.</p>
-<h1 id="international">International<a class="headerlink" href="#international" title="Permanent link">&para;</a></h1>
+<h1 id="international">International   </h1>
 <p>Recommended code pattern for internationalization.</p>
-<h2 id="timezone">Specify timezone<a class="headerlink" href="#timezone" title="Permanent link">&para;</a></h2>
+<h2 id="timezone">Specify timezone   </h2>
 <p>Geospatial data often cover a wide geographic area, spanning many time zones.
 Timezone are sometime specified as metadata in the header of data files to be read,
-or is sometime fixed to <abbr title="Universal Time Coordinated">UTC</abbr> by applications managing world-wide data.
+or is sometime fixed to UTC by applications managing world-wide data.
 Some Apache SIS objects have <code>Locale</code> and <code>TimeZone</code> information.
 Such locale and timezone are given to <code>java.text.DateFormat</code> or <code>java.util.Calendar</code> constructors among others.</p>
-<p>When reading dates or timestamps from a <abbr title="Java DataBase Connectivity">JDBC</abbr> database, always use the <code>ResultSet</code> method
+<p>When reading dates or timestamps from a JDBC database, always use the <code>ResultSet</code> method
 accepting a <code>Calendar</code> argument, when such method is available.
 For example prefer the <code>getTimestamp(int, Calendar)</code> method instead than <code>getTimestamp(int)</code>.
 The <code>Calendar</code> object should has been created with the appropriate timezone.</p>
-<h2 id="sort">Replace underscores by spaces before sorting<a class="headerlink" href="#sort" title="Permanent link">&para;</a></h2>
+<h2 id="sort">Replace underscores by spaces before sorting   </h2>
 <p>Before to sort programmatic names for human reading, consider replacing all occurrences of the underscore character
 (<code>'_'</code>) by the space character (<code>' '</code>). The ASCII value of the underscore character is greater than <code>'Z'</code> but lower
 than <code>'a'</code>, which sometime produce unexpected sort results.
-For example <code>"Foo_bar"</code> is sorted <em>between</em> <code>"FooBar"</code> and <code>"Foobar"</code>.
+For example <code>&quot;Foo_bar&quot;</code> is sorted <em>between</em> <code>&quot;FooBar&quot;</code> and <code>&quot;Foobar&quot;</code>.
 The space character produces more consistent sort results because its ASCII value is less than any printable character,
-so <code>"Foo bar"</code> is sorted before both <code>"FooBar"</code> and <code>"Foobar"</code>.</p>
-<h2 id="unicode-loop">Loop over character sequences using code points<a class="headerlink" href="#unicode-loop" title="Permanent link">&para;</a></h2>
+so <code>&quot;Foo bar&quot;</code> is sorted before both <code>&quot;FooBar&quot;</code> and <code>&quot;Foobar&quot;</code>.</p>
+<h2 id="unicode-loop">Loop over character sequences using code points   </h2>
 <p>Since Java 1.5, characters are no longer restricted to 16 bits.
-Some "characters" are actually represented using two consecutive <code>char</code> elements.
-Those "characters" are called <cite>code points</cite>.
+Some &ldquo;characters&rdquo; are actually represented using two consecutive <code>char</code> elements.
+Those &ldquo;characters&rdquo; are called <cite>code points</cite>.
 Consequently, when iterating over characters in a string, the following pattern should be used:</p>
-<div class="codehilite"><pre><span class="k">for</span> <span class="o">(</span><span class="kt">int</span> <span class="n">i</span><span class="o">=</span><span class="mi">0</span><span class="o">;</span> <span class="n">i</span><span class="o">&lt;</span><span class="n">string</span><span class="o">.</span><span class="na">length</span><span class="o">();)</span> <span class="o">{</span>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="k">for</span> <span class="o">(</span><span class="kt">int</span> <span class="n">i</span><span class="o">=</span><span class="n">0</span><span class="o">;</span> <span class="n">i</span><span class="o">&lt;</span><span class="n">string</span><span class="o">.</span><span class="na">length</span><span class="o">();)</span> <span class="o">{</span>
     <span class="kd">final</span> <span class="kt">int</span> <span class="n">c</span> <span class="o">=</span> <span class="n">string</span><span class="o">.</span><span class="na">codePointAt</span><span class="o">(</span><span class="n">i</span><span class="o">);</span>
-    <span class="c1">// ... do some stuff ...</span>
-    <span class="n">i</span> <span class="o">+=</span> <span class="n">Character</span><span class="o">.</span><span class="na">charCount</span><span class="o">(</span><span class="n">c</span><span class="o">);</span>
-<span class="o">}</span>
-</pre></div>
-
-
-<h1 id="logging">Logging<a class="headerlink" href="#logging" title="Permanent link">&para;</a></h1>
+    <span class="c1">// ... do some stuff ...
+</span><span class="c1"></span>    <span class="n">i</span> <span class="o">+=</span> <span class="n">Character</span><span class="o">.</span><span class="na">charCount</span><span class="o">(</span><span class="n">c</span><span class="o">);</span>
+<span class="o">}</span></code></pre></div>
+<h1 id="logging">Logging   </h1>
 <p>Apache SIS uses the <code>java.util.logging</code> framework, but with a <a href="http://sis.apache.org/apidocs/org/apache/sis/util/logging/LoggerFactory.html">mechanism allowing users to redirect
 to another framework</a>.
 The logger names are usually the package name of the class emitting log messages, but not necessarily.
@@ -181,31 +182,41 @@ since developers use them for configuring their logging (verbosity, destination,
 <p>All logging at <code>Level.INFO</code> or above shall be targeted to users or administrators, not to developers.
 In particular <code>Level.SEVERE</code> shall be reserved for critical errors that compromise the application stability —
 it shall not be used for exceptions thrown while parsing user data (file or database).</p>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
+<p>*[CRS]:  Coordinate Reference System
+*[JDBC]: Java DataBase Connectivity
+*[OGC]:  Open Geospatial Consortium
+*[UTC]:  Universal Time Coordinated</p>
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
+
+        </article>
+      </section>
     </div>
-  </footer>
+  </div>
+</div>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/coding-conventions.html b/coding-conventions.html
index 980fbbf..0b5fd90 100644
--- a/coding-conventions.html
+++ b/coding-conventions.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Source code</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Source code</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,90 +37,133 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Source code</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>This page describes some coding conventions applied in Apache SIS development.</p>
-<div class="toc">
-<ul>
-<li><a href="#license">License header</a></li>
-<li><a href="#naming">Naming convention</a><ul>
-<li><a href="#internal">Internal packages</a></li>
-<li><a href="#substitutions">Substitution for non-existent classes</a></li>
-</ul>
-</li>
-<li><a href="#formatting">Code formatting</a><ul>
-<li><a href="#imports">Import statements</a></li>
-<li><a href="#spaces">Spaces and line length</a></li>
-<li><a href="#brackets">Brackets</a></li>
-<li><a href="#declarations">Member declarations</a></li>
-<li><a href="#tabular-formatting">Exceptions to coding conventions</a></li>
-</ul>
-</li>
-<li><a href="#javadoc">Documentation formatting</a><ul>
-<li><a href="#javadoc-tags">Javadoc annotations</a></li>
-<li><a href="#html">HTML elements</a><ul>
-<li><a href="#paragraph">Paragraphs</a></li>
-<li><a href="#css">Javadoc CSS</a></li>
-</ul>
-</li>
-<li><a href="#mathml">MathML elements</a></li>
-</ul>
-</li>
-</ul>
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
 </div>
-<h1 id="license">License header<a class="headerlink" href="#license" title="Permanent link">&para;</a></h1>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Source code</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>This page describes some coding conventions applied in Apache SIS development.</p>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#license">License header   </a></li>
+    <li><a href="#naming">Naming convention   </a>
+      <ul>
+        <li><a href="#internal">Internal packages   </a></li>
+        <li><a href="#substitutions">Substitution for non-existent classes   </a></li>
+      </ul>
+    </li>
+    <li><a href="#formatting">Code formatting   </a>
+      <ul>
+        <li><a href="#imports">Import statements   </a></li>
+        <li><a href="#spaces">Spaces and line length   </a></li>
+        <li><a href="#brackets">Brackets   </a></li>
+        <li><a href="#declarations">Member declarations   </a></li>
+        <li><a href="#tabular-formatting">Exceptions to coding conventions   </a></li>
+      </ul>
+    </li>
+    <li><a href="#javadoc">Documentation formatting   </a>
+      <ul>
+        <li><a href="#javadoc-tags">Javadoc annotations   </a></li>
+        <li><a href="#html">HTML elements   </a>
+          <ul>
+            <li><a href="#paragraph">Paragraphs   </a></li>
+            <li><a href="#css">Javadoc CSS   </a></li>
+          </ul>
+        </li>
+        <li><a href="#mathml">MathML elements   </a></li>
+      </ul>
+    </li>
+  </ul>
+</nav>
+<h1 id="license">License header   </h1>
 <p>All Java source files (<code>*.java</code>) shall begin with the current ASF license header as described in <a href="http://www.apache.org/legal/src-headers.html">ASF Source Header</a>.
 Properties source files (<code>*.properties</code>) used as inputs to some processor (e.g. the resource compiler)
 shall have the same license header, but with lines prefixed by <code>#</code> instead of <code>*</code>.
 Properties files distributed as-is in the JAR files can summarize the license on a single line for saving space,
 as below:</p>
-<div class="codehilite"><pre># Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.
-</pre></div>
-
-
-<h1 id="naming">Naming convention<a class="headerlink" href="#naming" title="Permanent link">&para;</a></h1>
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text"># Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.</code></pre></div>
+<h1 id="naming">Naming convention   </h1>
 <p>Classes that do not implement an interface are usually not prefixed, even if abstract.
 Classes implementing GeoAPI interfaces usually (but not always) begin with <code>Abstract</code>, <code>Default</code>, <code>Simple</code> or <code>General</code> prefix.</p>
 <ul>
-<li>The <code>Abstract</code> prefix is used when a class is abstract according <abbr title="International Organization for Standardization">ISO</abbr> specifications — it may or may not be be abstract in the Java sense.</li>
+<li>The <code>Abstract</code> prefix is used when a class is abstract according 
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+ specifications — it may or may not be be abstract in the Java sense.</li>
 <li>The <code>General</code> prefix is used when an implementation is designed for use in the general case,
-    as opposed to other implementations specialized for a fixed number of dimensions or other conditions.</li>
+as opposed to other implementations specialized for a fixed number of dimensions or other conditions.</li>
 <li>Implementations specialized for a fixed number of dimensions are suffixed with <code>1D</code>, <code>2D</code>, <code>3D</code> or <code>4D</code> rather than being prefixed.</li>
 </ul>
 <p>Example: <code>GeneralEnvelope</code> class is an implementation of <code>Envelope</code> interface for the multi-dimensional case.
 <code>Envelope2D</code> is another implementation of the same interface specialized for the two-dimensional case.</p>
-<h2 id="internal">Internal packages<a class="headerlink" href="#internal" title="Permanent link">&para;</a></h2>
+<h2 id="internal">Internal packages   </h2>
 <p>All classes in <code>org.apache.sis.internal</code> sub-packages are for SIS usage only and may change without warning in any future release.
 Those classes are excluded from Javadoc and will not be exported by SIS Jigsaw modules.
 Those packages may be renamed after SIS upgraded to JDK 9.</p>
-<h2 id="substitutions">Substitution for non-existent classes<a class="headerlink" href="#substitutions" title="Permanent link">&para;</a></h2>
+<h2 id="substitutions">Substitution for non-existent classes   </h2>
 <p>When using a JDK 9 class that does not exist on JDK 8, define a class of the same name in a
 <code>org.apache.sis.internal</code> sub-package with the minimal amount of needed functionalities,
 provided that it can be done with reasonable effort.
 Otherwise just delete the JDK9-dependent code from the development branch.</p>
-<h1 id="formatting">Code formatting<a class="headerlink" href="#formatting" title="Permanent link">&para;</a></h1>
+<h1 id="formatting">Code formatting   </h1>
 <p>Apache SIS uses the standard Java conventions, except for the 80 characters line length restriction.
 The conventions listed below are guidelines. Some exceptions to those conventions can occur but should
 be rare (see <a href="#tabular-formatting">exceptions to coding conventions</a>).</p>
@@ -167,46 +173,54 @@ be rare (see <a href="#tabular-formatting">exceptions to coding conventions</a>)
 <li>or the modified lines are known to be identical on all active branches (merges work well in such cases);</li>
 <li>or the committer is willing to resolve the merge conflicts.</li>
 </ul>
-<h2 id="imports">Import statements<a class="headerlink" href="#imports" title="Permanent link">&para;</a></h2>
+<h2 id="imports">Import statements   </h2>
 <p>Isolate at the end of the imports section any import statements that are specific to a platform.
 This separation allows any branch to re-arrange the common import statements without generating
 conflicts with the platform-dependent import statements. Example:</p>
-<div class="codehilite"><pre><span class="kn">import</span> <span class="nn">java.io.File</span><span class="o">;</span>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="kn">import</span> <span class="nn">java.io.File</span><span class="o">;</span>
 <span class="kn">import</span> <span class="nn">java.util.List</span><span class="o">;</span>
 <span class="kn">import</span> <span class="nn">org.opengis.metadata.Metadata</span><span class="o">;</span>
 
-<span class="c1">// Branch-specific imports</span>
-<span class="kn">import</span> <span class="nn">org.opengis.feature.Feature</span><span class="o">;</span>
-</pre></div>
-
-
-<h2 id="spaces">Spaces and line length<a class="headerlink" href="#spaces" title="Permanent link">&para;</a></h2>
+<span class="c1">// Branch-specific imports
+</span><span class="c1"></span><span class="kn">import</span> <span class="nn">org.opengis.feature.Feature</span><span class="o">;</span></code></pre></div>
+<h2 id="spaces">Spaces and line length   </h2>
+<ul>
+<li><strong>Indentation:</strong> Use a consistent space indents and never use tabs.
 <ul>
-<li><strong>Indentation:</strong> Use a consistent space indents and never use tabs.<ul>
 <li>Use 4 space indents for Java files.</li>
-<li>Use 2 space indents for XML files, because <abbr title="International Organization for Standardization">ISO</abbr>/<abbr title="Open Geospatial Consortium">OGC</abbr> XML schemas tend to have a very deep structure.</li>
+<li>Use 2 space indents for XML files, because 
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+/
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ XML schemas tend to have a very deep structure.</li>
 </ul>
 </li>
 <li><strong>Space after keyword:</strong> Put a space after <code>if</code>, <code>else</code>, <code>for</code>, <code>try</code>, <code>catch</code> and similar keywords
-    (not after method names).</li>
-<li><strong>Trailing Whitespaces:</strong> Remove all trailing whitespaces.<ul>
+(not after method names).</li>
+<li><strong>Trailing Whitespaces:</strong> Remove all trailing whitespaces.
+<ul>
 <li>Eclipse users can use the <em>Source</em> - <em>Cleanup</em> option to accomplish this.</li>
 <li>NetBeans users can use the use the <em>Source</em> - <em>Remove trailing spaces</em> on a file-by-file basis,
-  or set the <em>Preferences</em> - <em>Editor</em> - <em>On Save</em> - <em>Remove trailing whitespaces</em> option.</li>
+or set the <em>Preferences</em> - <em>Editor</em> - <em>On Save</em> - <em>Remove trailing whitespaces</em> option.</li>
 </ul>
 </li>
 <li><strong>Line wrapping:</strong> Use 120-column line width for Java code and Javadoc.
-    Some exceptions to this rule may exist for preserving tabular structures, but should be rare.</li>
+Some exceptions to this rule may exist for preserving tabular structures, but should be rare.</li>
 </ul>
-<h2 id="brackets">Brackets<a class="headerlink" href="#brackets" title="Permanent link">&para;</a></h2>
+<h2 id="brackets">Brackets   </h2>
 <ul>
 <li><strong>Curly brackets:</strong> The <code>{</code> and <code>}</code> brackets are mandatory for <code>if</code>, <code>else</code>, <code>while</code> and other blocks,
-    except if the instruction after the keyword is on the same line (e.g. <code>else if</code>).</li>
+except if the instruction after the keyword is on the same line (e.g. <code>else if</code>).</li>
 </ul>
-<h2 id="declarations">Member declarations<a class="headerlink" href="#declarations" title="Permanent link">&para;</a></h2>
+<h2 id="declarations">Member declarations   </h2>
 <ul>
 <li>Class, method and field declarations shall use the keywords in the following order.
-    This is known as the "customary order" in the <a href="http://docs.oracle.com/javase/specs/jls/se8/html/jls-8.html#jls-8.1.1">Java Language Specification</a>:<ul>
+This is known as the &ldquo;customary order&rdquo; in the <a href="http://docs.oracle.com/javase/specs/jls/se8/html/jls-8.html#jls-8.1.1">Java Language Specification</a>:
+<ul>
 <li><code>public</code>, <code>protected</code> or <code>private</code>,</li>
 <li><code>abstract</code> or <code>static</code>,</li>
 <li><code>final</code>,</li>
@@ -215,35 +229,32 @@ conflicts with the platform-dependent import statements. Example:</p>
 </li>
 <li>Member fields do not have any particular prefix (no <code>m_</code> prefix).</li>
 </ul>
-<h2 id="tabular-formatting">Exceptions to coding conventions<a class="headerlink" href="#tabular-formatting" title="Permanent link">&para;</a></h2>
+<h2 id="tabular-formatting">Exceptions to coding conventions   </h2>
 <p>Many mathematical operations in a two-dimensional space (or more) have symmetry.
 Formatting the code in a way that emphase their symmetrical nature, for example
 aligning identical terms in columns, can help to understand the overall pattern
 and to identify bugs. Example:</p>
-<div class="codehilite"><pre><span class="k">if</span> <span class="o">(</span><span class="n">x</span> <span class="o">&lt;</span> <span class="n">xmin</span><span class="o">)</span> <span class="n">xmin</span> <span class="o">=</span> <span class="n">x</span><span class="o">;</span>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="k">if</span> <span class="o">(</span><span class="n">x</span> <span class="o">&lt;</span> <span class="n">xmin</span><span class="o">)</span> <span class="n">xmin</span> <span class="o">=</span> <span class="n">x</span><span class="o">;</span>
 <span class="k">if</span> <span class="o">(</span><span class="n">x</span> <span class="o">&gt;</span> <span class="n">xmax</span><span class="o">)</span> <span class="n">xmax</span> <span class="o">=</span> <span class="n">x</span><span class="o">;</span>
 <span class="k">if</span> <span class="o">(</span><span class="n">y</span> <span class="o">&lt;</span> <span class="n">ymin</span><span class="o">)</span> <span class="n">ymin</span> <span class="o">=</span> <span class="n">y</span><span class="o">;</span>
-<span class="k">if</span> <span class="o">(</span><span class="n">y</span> <span class="o">&gt;</span> <span class="n">ymax</span><span class="o">)</span> <span class="n">ymax</span> <span class="o">=</span> <span class="n">y</span><span class="o">;</span>
-</pre></div>
-
-
+<span class="k">if</span> <span class="o">(</span><span class="n">y</span> <span class="o">&gt;</span> <span class="n">ymax</span><span class="o">)</span> <span class="n">ymax</span> <span class="o">=</span> <span class="n">y</span><span class="o">;</span></code></pre></div>
 <p>The decision to use standard or tabular format is made on a case-by-case basis.
 Of course, tabular format shall not be abused.</p>
-<h1 id="javadoc">Documentation formatting<a class="headerlink" href="#javadoc" title="Permanent link">&para;</a></h1>
+<h1 id="javadoc">Documentation formatting   </h1>
 <p>Apache SIS uses the standard Javadoc conventions, except for the 80 characters line length restriction.
 Javadoc lines should not exceed 120 characters, but exceptions to this rule may exist for preserving the
 structure of <code>&lt;table&gt;</code> elements.</p>
-<h2 id="javadoc-tags">Javadoc annotations<a class="headerlink" href="#javadoc-tags" title="Permanent link">&para;</a></h2>
+<h2 id="javadoc-tags">Javadoc annotations   </h2>
 <p>SIS uses standard javadoc annotations. The meaning of some tags are refined as below:</p>
 <ul>
 <li><code>@since</code>   - the SIS version when the annotated element (class, method, <i>etc.</i>) was first introduced.</li>
 <li><code>@version</code> - the last SIS version when the code of the annotated class got a significant change.</li>
 <li><code>@author</code>  - developer name in <var>FirstName</var> <var>LastName</var> (<var>Organization</var>) format.
-                 A separated <code>@author</code> tag is added for each developer.
-                 The intent is to allow other developers to know to who to ask questions if needed.</li>
+A separated <code>@author</code> tag is added for each developer.
+The intent is to allow other developers to know to who to ask questions if needed.</li>
 </ul>
 <p>In addition, the <code>sis-build-helper</code> modules provides the following custom javadoc taglets:</p>
-<table class="table">
+<table>
 <thead>
 <tr>
 <th>Javadoc tag</th>
@@ -265,16 +276,16 @@ structure of <code>&lt;table&gt;</code> elements.</p>
 </tr>
 </tbody>
 </table>
-<h2 id="html">HTML elements<a class="headerlink" href="#html" title="Permanent link">&para;</a></h2>
+<h2 id="html">HTML elements   </h2>
 <p>HTML tags and entities shall be used only when there is no equivalent Javadoc tag.
 For example:</p>
 <ul>
-<li>Instead of "<code>&lt;code&gt;✎&lt;/code&gt;</code>", use "<code>{@code ✎}</code>".</li>
-<li>Instead of "<code>a &amp;lt; b &amp;lt; c</code>", use "<code>{@literal a &lt; b &lt; c}</code>".</li>
-<li>Instead of "<code>&lt;pre&gt;✎&lt;/pre&gt;</code>" for a Java listing, use "<code>{@preformat java ✎}</code>"
-     (this Javadoc tag is specific to Apache SIS — see above table).</li>
+<li>Instead of &ldquo;<code>&lt;code&gt;✎&lt;/code&gt;</code>&rdquo;, use &ldquo;<code>{@code ✎}</code>&rdquo;.</li>
+<li>Instead of &ldquo;<code>a &amp;lt; b &amp;lt; c</code>&rdquo;, use &ldquo;<code>{@literal a &lt; b &lt; c}</code>&rdquo;.</li>
+<li>Instead of &ldquo;<code>&lt;pre&gt;✎&lt;/pre&gt;</code>&rdquo; for a Java listing, use &ldquo;<code>{@preformat java ✎}</code>&rdquo;
+(this Javadoc tag is specific to Apache SIS — see above table).</li>
 </ul>
-<h3 id="paragraph">Paragraphs<a class="headerlink" href="#paragraph" title="Permanent link">&para;</a></h3>
+<h3 id="paragraph">Paragraphs   </h3>
 <p>Usages of the <code>&lt;p&gt;</code> tag should be relatively rare, since we use CSS styles (see below)
 as much as possible for controlling the margin between elements like lists and tables.
 Do <strong>not</strong> use <code>&lt;p&gt;</code> for the first paragraph in a package, class or member documentation,
@@ -282,10 +293,10 @@ or for the first paragraph after a <code>&lt;/ul&gt;</code>, <code>&lt;/ol&gt;</
 or <code>{@preformat}</code> element.
 The <code>&lt;p&gt;</code> tag shall be used only for separating a new paragraph from a previous one.
 In such cases, <code>&lt;p&gt;</code> shall have a matching <code>&lt;/p&gt;</code> tag at the paragraph end in order to form valid HTML.</p>
-<h3 id="css">Javadoc CSS<a class="headerlink" href="#css" title="Permanent link">&para;</a></h3>
+<h3 id="css">Javadoc CSS   </h3>
 <p>Avoid using HTML attributes other than <code>class</code> as much as possible.
 Instead, rely on styling. Some HTML tags having a style definition in Apache SIS are:</p>
-<table class="table">
+<table>
 <thead>
 <tr>
 <th>HTML tag</th>
@@ -294,15 +305,15 @@ Instead, rely on styling. Some HTML tags having a style definition in Apache SIS
 </thead>
 <tbody>
 <tr>
-<td><code>&lt;div class="section"&gt;</code></td>
+<td><code>&lt;div class=&quot;section&quot;&gt;</code></td>
 <td>Header of a sub-section in a package, class or member description.</td>
 </tr>
 <tr>
-<td><code>&lt;div class="note"&gt;</code></td>
+<td><code>&lt;div class=&quot;note&quot;&gt;</code></td>
 <td>Indented text with smaller font, used for notes or examples.</td>
 </tr>
 <tr>
-<td><code>&lt;div class="warning"&gt;</code></td>
+<td><code>&lt;div class=&quot;warning&quot;&gt;</code></td>
 <td>Text in red color, used for warning about probable API changes.</td>
 </tr>
 <tr>
@@ -310,32 +321,32 @@ Instead, rely on styling. Some HTML tags having a style definition in Apache SIS
 <td>Default list styles with few space between items (suitable for compact lists).</td>
 </tr>
 <tr>
-<td><code>&lt;ul class="verbose"&gt;</code></td>
+<td><code>&lt;ul class=&quot;verbose&quot;&gt;</code></td>
 <td>A list style with space between items. Used for lists having verbose (multi-lines) items.</td>
 </tr>
 <tr>
-<td><code>&lt;table class="compact"&gt;</code></td>
+<td><code>&lt;table class=&quot;compact&quot;&gt;</code></td>
 <td>Table without border and no space between rows. Used for lists with columns alignment.</td>
 </tr>
 <tr>
-<td><code>&lt;table class="sis"&gt;</code></td>
+<td><code>&lt;table class=&quot;sis&quot;&gt;</code></td>
 <td>Table with a border, blue headers, light background and some space between columns.</td>
 </tr>
 <tr>
-<td><code>&lt;th class="hsep"&gt;</code></td>
+<td><code>&lt;th class=&quot;hsep&quot;&gt;</code></td>
 <td>In SIS tables, draw a line on the top border. Used for drawing table section separators.</td>
 </tr>
 <tr>
-<td><code>&lt;th class="sep"&gt;</code></td>
+<td><code>&lt;th class=&quot;sep&quot;&gt;</code></td>
 <td>In SIS tables, draw a bright line on the left border. Used for drawing column separators.</td>
 </tr>
 <tr>
-<td><code>&lt;td class="sep"&gt;</code></td>
+<td><code>&lt;td class=&quot;sep&quot;&gt;</code></td>
 <td>In SIS tables, draw a bright line on the left border. Used for drawing column separators.</td>
 </tr>
 </tbody>
 </table>
-<h2 id="mathml">MathML elements<a class="headerlink" href="#mathml" title="Permanent link">&para;</a></h2>
+<h2 id="mathml">MathML elements   </h2>
 <p>The source code occasionally uses MathML for formulas that are difficult to render with only Unicode characters.
 PNG images are not extensively used for formulas because they are difficult to edit after creation,
 and their content are invisible to search operations (for example when a variable is renamed).
@@ -348,33 +359,39 @@ For an introduction to MathML, see:</p>
 </ul>
 <p>MathML is supported natively in Firefox, Safari and Opera.
 Internet Explorer users need to <a href="http://www.dessci.com/en/products/mathplayer/download.htm">install a plugin</a>.
-Firefox users can optionally install the <a href="http://developer.mozilla.org/en-US/docs/Mozilla/MathML_Project/Fonts">fonts for Mozilla's MathML engine</a> for better results.
+Firefox users can optionally install the <a href="http://developer.mozilla.org/en-US/docs/Mozilla/MathML_Project/Fonts">fonts for Mozilla&rsquo;s MathML engine</a> for better results.
 Note that a <a href="http://www.mathjax.org/">JavaScript display engine</a> is available for all browsers, but not yet used by SIS.</p>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
+
+        </article>
+      </section>
     </div>
-  </footer>
+  </div>
+</div>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/command-line.html b/command-line.html
index 669fa26..f59bd50 100644
--- a/command-line.html
+++ b/command-line.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Command-line interface</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Command-line interface</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,99 +37,130 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Command-line interface</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>A command-line interface is provided for extracting information from data files or authority codes,
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Command-line interface</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>A command-line interface is provided for extracting information from data files or authority codes,
 and for performing coordinate operations.
 That command-line tool is provided for allowing users to experiment some Apache SIS functionalities
 without writing Java code.
 For each example, key Java APIs are listed for allowing users to reproduce the functionality
 in their own application.</p>
-<div class="toc">
-<ul>
-<li><a href="#install">Installation</a><ul>
-<li><a href="#dependencies">Optional dependencies</a></li>
-</ul>
-</li>
-<li><a href="#usage">Usage</a></li>
-<li><a href="#examples">Examples</a><ul>
-<li><a href="#crs">Print Coordinate Reference Systems (CRS) definition</a></li>
-<li><a href="#identifier">Getting a verified EPSG identifier from a Coordinate Reference System</a></li>
-<li><a href="#coordinateOperation">Performing coordinate conversions or transformations</a></li>
-<li><a href="#metadata">Extracting ISO 19115 Metadata</a></li>
-</ul>
-</li>
-<li><a href="#performance">Performance consideration</a></li>
-</ul>
-</div>
-<h1 id="install">Installation<a class="headerlink" href="#install" title="Permanent link">&para;</a></h1>
-<p>Select "Apache SIS 1.0 binary" from the <a href="downloads.html">downloads page</a> an unzip in any directory.
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#install">Installation   </a>
+      <ul>
+        <li><a href="#dependencies">Optional dependencies   </a></li>
+      </ul>
+    </li>
+    <li><a href="#usage">Usage   </a></li>
+    <li><a href="#examples">Examples   </a>
+      <ul>
+        <li><a href="#crs">Print Coordinate Reference Systems (CRS) definition   </a></li>
+        <li><a href="#identifier">Getting a verified EPSG identifier from a Coordinate Reference System   </a></li>
+        <li><a href="#coordinateOperation">Performing coordinate conversions or transformations   </a></li>
+        <li><a href="#metadata">Extracting ISO 19115 Metadata   </a></li>
+      </ul>
+    </li>
+    <li><a href="#performance">Performance consideration   </a></li>
+  </ul>
+</nav>
+<h1 id="install">Installation   </h1>
+<p>Select &ldquo;Apache SIS 1.0 binary&rdquo; from the <a href="downloads.html">downloads page</a> an unzip in any directory.
 The directory structure will be as below:</p>
-<div class="codehilite"><pre>apache-sis-1.0
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">apache-sis-1.0
 ├─ bin
 ├─ conf
 ├─ data
 ├─ lib
-└─ log
-</pre></div>
-
-
+└─ log</code></pre></div>
 <p>The <code>bin</code> sub-directory contains a <code>sis</code> command for Unix systems (Linux or MacOS — we have not yet done a <code>sis.bat</code> file for Windows).
 The <code>bin</code> sub-directory can be added to the <code>PATH</code> environment variable for convenience, but this is not mandatory.
 Example:</p>
-<div class="codehilite"><pre><span class="nb">export </span><span class="nv">PATH</span><span class="o">=</span><span class="nv">$PWD</span>/apache-sis-1.0/bin:<span class="nv">$PATH</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">export</span> <span class="nv">PATH</span><span class="o">=</span><span class="nv">$PWD</span>/apache-sis-1.0/bin:<span class="nv">$PATH</span></code></pre></div>
 <p>The remaining of this page assumes that the <code>bin</code> directory is on the search path.
 If not, the same examples can still be executed by replacing the <code>sis</code> command by <code>./apache-sis-1.0/bin/sis</code>.</p>
-<h2 id="dependencies">Optional dependencies<a class="headerlink" href="#dependencies" title="Permanent link">&para;</a></h2>
+<h2 id="dependencies">Optional dependencies   </h2>
 <p>Every JAR files present in the <code>lib</code> sub-directory will be included on the classpath during <code>sis</code> command execution.
 By default, the <code>lib</code> directory contains the <code>sis.jar</code> file with only GeoAPI JAXB API dependencies.
 However users can add other JAR files in that directory for the following optional dependencies:</p>
 <ul>
 <li>
 <p><strong>Derby driver —</strong>
-    needed only if Apache SIS can not locate a JavaDB driver in the JDK installation directory.
-    This is not needed on Oracle JDK8 distribution, but needed for all OpenJDK versions and for
-    Oracle JDK more recent than 8.</p>
+needed only if Apache SIS can not locate a JavaDB driver in the JDK installation directory.
+This is not needed on Oracle JDK8 distribution, but needed for all OpenJDK versions and for
+Oracle JDK more recent than 8.</p>
 </li>
 <li>
 <p><strong>UCAR netCDF library —</strong>
-    by default, SIS uses its own embedded netCDF reader which supports only the classical netCDF format, as standardized by OGC.
-    If there is a need to read files encoded in GRID or HDF formats, then one can copy the UCAR netCDF library in the <code>lib</code> sub-directory.
-    If presents, the UCAR library should be detected and used automatically when SIS can not read a netCDF file by itself.</p>
+by default, SIS uses its own embedded netCDF reader which supports only the classical netCDF format, as standardized by OGC.
+If there is a need to read files encoded in GRID or HDF formats, then one can copy the UCAR netCDF library in the <code>lib</code> sub-directory.
+If presents, the UCAR library should be detected and used automatically when SIS can not read a netCDF file by itself.</p>
 </li>
 </ul>
-<h1 id="usage">Usage<a class="headerlink" href="#usage" title="Permanent link">&para;</a></h1>
+<h1 id="usage">Usage   </h1>
 <p>Invoking <code>sis</code> without argument shows a summary of available commands and all options.
 For executing a command, the syntax is:</p>
-<div class="codehilite"><pre>sis &lt;<span class="nb">command</span>&gt; <span class="o">[</span>options<span class="o">]</span> <span class="o">[</span>files<span class="o">]</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">sis &lt;command&gt; <span class="o">[</span>options<span class="o">]</span> <span class="o">[</span>files<span class="o">]</span></code></pre></div>
 <p>Available commands are:</p>
 <table>
   <tr><td><code>help</code></td>       <td>Show a help overview.</td></tr>
@@ -177,7 +171,6 @@ For executing a command, the syntax is:</p>
   <tr><td><code>identifier</code></td> <td>Show identifiers for metadata and referencing systems in the given file.</td></tr>
   <tr><td><code>transform</code></td>  <td>Convert or transform coordinates from given source CRS to target CRS.</td></tr>
 </table>
-
 <p>The set of legal options and the expected number of file arguments depend on the command being executed.
 However all commands support the <code>--help</code> option, which lists the options available for that command.
 Available options will be from the following list:</p>
@@ -194,11 +187,10 @@ Available options will be from the following list:</p>
   <tr><td><code>--debug</code></td>     <td>Prints full stack trace in case of failure.</td></tr>
   <tr><td><code>--help</code></td>      <td>Lists the options available for a specific command.</td></tr>
 </table>
-
 <p>The <code>--locale</code>, <code>--timezone</code> and <code>--encoding</code> options apply to the command output sent to the standard output stream,
 but usually do not apply to the error messages sent to the standard error stream.
 The reason is that command output may be targeted to a client, while the error messages are usually for the operator.</p>
-<h1 id="examples">Examples<a class="headerlink" href="#examples" title="Permanent link">&para;</a></h1>
+<h1 id="examples">Examples   </h1>
 <p>The following examples first show how to get a Coordinate Reference System (CRS) from different kinds of definitions.
 CRS contain necessary information for locating points on Earth.
 Those information include the geodetic datum, the map projection (if any), the axes and their units of measurement.
@@ -206,7 +198,7 @@ When two such CRS are known (the <em>source</em> and the <em>target</em>), it is
 However the coordinate operation depends not only on the source and target CRS, but also on the <em>area of interest</em> as shown
 by the example transforming city coordinates in USA and in Canada.
 Then another example show how to get a wider set of metadata, with the CRS as only one specific element of those metadata.</p>
-<h2 id="crs">Print Coordinate Reference Systems (CRS) definition<a class="headerlink" href="#crs" title="Permanent link">&para;</a></h2>
+<h2 id="crs">Print Coordinate Reference Systems (CRS) definition   </h2>
 <p>Apache SIS can read Coordinate Reference System (CRS) definitions from various sources:</p>
 <ul>
 <li>Codes from the EPSG geodetic dataset</li>
@@ -214,14 +206,11 @@ Then another example show how to get a wider set of metadata, with the CRS as on
 <li>XML files conform to <em>Geographic Markup Language</em> (GML) schema version 3.2</li>
 </ul>
 <p>The easiest way to see a CRS definition is to use an EPSG code.
-The <a href="http://www.epsg.org/">EPSG geodetic dataset</a> is a widely-used source of definitions for thousands of Coordinate Reference Systems.
+The <a href="https://epsg.org/">EPSG geodetic dataset</a> is a widely-used source of definitions for thousands of Coordinate Reference Systems.
 Appache SIS provides a <a href="tables/CoordinateReferenceSystems.html">list of supported codes</a>, which can be queried from the command line.
-For example the following command prints the definition of the <em>"JGD2011 / Japan Plane Rectangular CS VIII"</em> Coordinate Reference System:</p>
-<div class="codehilite"><pre>sis crs EPSG:6676
-</pre></div>
-
-
-<p><details>
+For example the following command prints the definition of the <em>&ldquo;JGD2011 / Japan Plane Rectangular CS VIII&rdquo;</em> Coordinate Reference System:</p>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">sis crs EPSG:6676</code></pre></div>
+<details>
   <summary>Expected output (click to expand):</summary>
 <pre>ProjectedCRS["JGD2011 / Japan Plane Rectangular CS VIII",
   BaseGeodCRS["JGD2011",
@@ -244,7 +233,7 @@ For example the following command prints the definition of the <em>"JGD2011 / Ja
   BBox[34.54, 137.32, 38.58, 139.91],
   Id["EPSG", 6676, "9.7", URI["urn:ogc:def:crs:EPSG:9.7:6676"]],
   Remark["Replaces JGD2000 / Japan Plane Rectangular CS VIII (CRS code 2450) with effect from 21st October 2011."]]</pre>
-</details></p>
+</details>
 <p>The first time that a command requires the EPSG dataset, Apache SIS will propose to download and install a local copy.
 This automatic download happen only when using the command-line tools described in this page.
 Developers who wish to use the EPSG dataset in their applications can use the Maven artifact
@@ -256,199 +245,163 @@ The output format can be controlled as below:</p>
 <ul>
 <li>
 <p>Some applications are restricted to WKT version 1.
-    For an output using the legacy WKT 1 format, one can add the <code>--format wkt1</code> option to the above command-line.</p>
+For an output using the legacy WKT 1 format, one can add the <code>--format wkt1</code> option to the above command-line.</p>
 </li>
 <li>
 <p>The “WKT 2” specification allows some flexibility in keyword names and in the way to specify units of measurement.
-    By default, the command-line uses this flexibility for producing less verbose but still legal WKT 2 output.
-    If an output closer to WKT 2 recommendations is desired, one can add the <code>--format wkt2</code> option to the above command.
-    The result will be slightly more verbose.</p>
+By default, the command-line uses this flexibility for producing less verbose but still legal WKT 2 output.
+If an output closer to WKT 2 recommendations is desired, one can add the <code>--format wkt2</code> option to the above command.
+The result will be slightly more verbose.</p>
 </li>
 <li>
 <p>Apache SIS can also read and write CRS definitions in the <em>Geographic Markup Language</em> (GML) format.
-    For GML output, one can add the <code>--format xml</code> option to the above command.
-    The result will be much more verbose than WKT outputs.</p>
+For GML output, one can add the <code>--format xml</code> option to the above command.
+The result will be much more verbose than WKT outputs.</p>
 </li>
 </ul>
 <p>Java API for accessing functionalities shown in above examples are:</p>
 <ul>
-<li>Convenience static methods in <code>org.apache.sis.referencing</code> package:<ul>
+<li>Convenience static methods in <code>org.apache.sis.referencing</code> package:
+<ul>
 <li><code>CRS.forCode(String)</code></li>
 <li><code>CRS.fromWKT(String)</code></li>
 <li><code>CRS.fromXML(String)</code></li>
 </ul>
 </li>
-<li>Classes in other packages (less convenient but give more control):<ul>
+<li>Classes in other packages (less convenient but give more control):
+<ul>
 <li><code>org.apache.sis.io.wkt.WKTFormat</code> — control WKT version, syntax highlighting, <em>etc.</em></li>
 <li><code>org.apache.sis.xml.MarshallerPool</code> — control GML version, link resolutions,  <em>etc.</em></li>
 </ul>
 </li>
 </ul>
-<h2 id="identifier">Getting a verified EPSG identifier from a Coordinate Reference System<a class="headerlink" href="#identifier" title="Permanent link">&para;</a></h2>
+<h2 id="identifier">Getting a verified EPSG identifier from a Coordinate Reference System   </h2>
 <p>Because the EPSG geodetic dataset is so commonly used,
 a very common practice is to specify a CRS using only its EPSG code instead than its full definition.
 Such codes can be written in different ways. For example all the following strings are for the same code:</p>
 <ul>
-<li><code>"EPSG:4326"</code></li>
-<li><code>"urn:ogc:def:crs:EPSG::4326"</code></li>
-<li><code>"http://www​.opengis​.net/def/crs/epsg/0/4326"</code> (not yet supported on the command-line)</li>
-<li><code>"http://www​.opengis​.net/gml/srs/epsg​.xml#4326"</code> (not yet supported on the command-line)</li>
+<li><code>&quot;EPSG:4326&quot;</code></li>
+<li><code>&quot;urn:ogc:def:crs:EPSG::4326&quot;</code></li>
+<li><code>&quot;http://www​.opengis​.net/def/crs/epsg/0/4326&quot;</code> (not yet supported on the command-line)</li>
+<li><code>&quot;http://www​.opengis​.net/gml/srs/epsg​.xml#4326&quot;</code> (not yet supported on the command-line)</li>
 </ul>
 <p>In a <em>Well Known Text</em> (WKT) string, the code can appear at the bottom of the definition
-in an optional element like <code>ID["EPSG", 4326]</code> or <code>AUTHORITY["EPSG", "4326"]</code>.
+in an optional element like <code>ID[&quot;EPSG&quot;, 4326]</code> or <code>AUTHORITY[&quot;EPSG&quot;, &quot;4326&quot;]</code>.
 However in many cases the code is missing.
 Sometime Apache SIS can find a missing code by comparing a given CRS against the definitions in the EPSG database.
 The following example reads a WKT for the <em>“NTF (Paris) / Lambert zone II”</em> Coordinate Reference System,
-but in which the <code>ID["EPSG", 27572]</code> element has been intentionally omitted.
+but in which the <code>ID[&quot;EPSG&quot;, 27572]</code> element has been intentionally omitted.
 Furthermore, the <em>“NTF (Paris) / Lambert zone II”</em> name has been replaced by <em>“NTF (Paris) / zone to be discovered by the demo”</em> name.
 Executing the following command:</p>
-<div class="codehilite"><pre>sis identifier http://sis.apache.org/examples/crs/MissingIdentifier.wkt
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">sis identifier http://sis.apache.org/examples/crs/MissingIdentifier.wkt</code></pre></div>
 <p>produces an output like below:</p>
-<div class="codehilite"><pre>    urn:ogc:def:crs:EPSG:9.7:27572    | NTF (Paris) / Lambert zone II
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">urn:ogc:def:crs:EPSG:9.7:27572    | NTF (Paris) / Lambert zone II</code></pre></div>
 <p>As we can see, Apache SIS has been able to find back the identifier code and the actual CRS name.</p>
 <p>Sometime a WKT declares wrongly an EPSG code.
 The most frequent case is a WKT that defines a Coordinate Reference System with (<em>longitude</em>, <em>latitude</em>) axes,
 but declare an EPSG code for a CRS with (<em>latitude</em>, <em>longitude</em>) axes.
 Apache SIS can detect such mismatches.
 For example executing the following command:</p>
-<div class="codehilite"><pre>sis identifier http://sis.apache.org/examples/crs/WrongAxisOrder.wkt
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">sis identifier http://sis.apache.org/examples/crs/WrongAxisOrder.wkt</code></pre></div>
 <p>produces an output like below:</p>
-<div class="codehilite"><pre>!   urn:ogc:def:crs:EPSG:8.9:4979    | WGS 84
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">!   urn:ogc:def:crs:EPSG:8.9:4979    | WGS 84
 
 Legend:
-!   Identified object matches definition provided by authority except for coordinate system axes.
-</pre></div>
-
-
+!   Identified object matches definition provided by authority except for coordinate system axes.</code></pre></div>
 <p>Apache SIS can perform such analysis because it “understands” the CRS definition.
 This analysis capability can be tested by altering the CRS definition.
 The next example asks the identifier of a CRS which is normally defined as below:</p>
-<div class="codehilite"><pre>ProjectedCRS[&quot;WGS 84 / Mercator 41&quot;,
-  (... definition omitted for brevity ...)
-    Method[&quot;Mercator (variant B)&quot;],
-    Parameter[&quot;Latitude of 1st standard parallel&quot;, -41.0],
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">ProjectedCRS[&#34;WGS 84 / Mercator 41&#34;,
   (... definition omitted for brevity ...)
-</pre></div>
-
-
+    Method[&#34;Mercator (variant B)&#34;],
+    Parameter[&#34;Latitude of 1st standard parallel&#34;, -41.0],
+  (... definition omitted for brevity ...)</code></pre></div>
 <p>However in this example, we will provide a CRS defined as below:</p>
-<div class="codehilite"><pre>ProjectedCRS[&quot;Scaled Mercator&quot;,
-  (... definition omitted for brevity ...)
-    Method[&quot;Mercator (variant A)&quot;],
-    Parameter[&quot;Scale factor at natural origin&quot;, 0.7557992272019596&quot;],
-    Parameter[&quot;Latitude of natural origin&quot;, -0.0],
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">ProjectedCRS[&#34;Scaled Mercator&#34;,
   (... definition omitted for brevity ...)
-</pre></div>
-
-
+    Method[&#34;Mercator (variant A)&#34;],
+    Parameter[&#34;Scale factor at natural origin&#34;, 0.7557992272019596&#34;],
+    Parameter[&#34;Latitude of natural origin&#34;, -0.0],
+  (... definition omitted for brevity ...)</code></pre></div>
 <p>Executing the following command:</p>
-<div class="codehilite"><pre>sis identifier http://sis.apache.org/examples/crs/EquivalentDefinition.wkt
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">sis identifier http://sis.apache.org/examples/crs/EquivalentDefinition.wkt</code></pre></div>
 <p>produces an output like below:</p>
-<div class="codehilite"><pre>urn:ogc:def:crs:EPSG:9.7:3994    | WGS 84 / Mercator 41
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">urn:ogc:def:crs:EPSG:9.7:3994    | WGS 84 / Mercator 41</code></pre></div>
 <p>In above example, Apache SIS used the fact that a
 <em>“Mercator (variant A)”</em> projection with a <em>“Scale factor at natural origin”</em> parameter value of 0.755799… on the WGS84 datum is numerically equivalent to a
 <em>“Mercator (variant B)”</em> projection with a <em>“Latitude of 1st standard parallel”</em> parameter value of 41° on the same datum.
 This recognition allowed SIS to return the EPSG:3994 code even if it stands for a CRS defined as a <em>“Mercator (variant B)”</em> projection rather than variant A.</p>
 <p>Java API for accessing functionalities shown in above example are:</p>
 <ul>
-<li>Convenience static method in <code>org.apache.sis.referencing</code> package:<ul>
+<li>Convenience static method in <code>org.apache.sis.referencing</code> package:
+<ul>
 <li><code>IdentifiedObjects.lookupURN(IdentifiedObject, Citation)</code></li>
 </ul>
 </li>
-<li>Class in other package (less convenient but give more control):<ul>
+<li>Class in other package (less convenient but give more control):
+<ul>
 <li><code>org.apache.sis.referencing.factory.IdentifiedObjectFinder</code></li>
 </ul>
 </li>
 </ul>
-<h2 id="coordinateOperation">Performing coordinate conversions or transformations<a class="headerlink" href="#coordinateOperation" title="Permanent link">&para;</a></h2>
+<h2 id="coordinateOperation">Performing coordinate conversions or transformations   </h2>
 <p>Coordinates represented in a given CRS can be transformed into coordinates represented in another CRS.
 The coordinate transformations depend mostly on the <em>source</em> and <em>target</em> CRS, but the <em>area of interest</em>
 can also have an influence; while optional, that area should be specified when it is known.</p>
 <p>The following example transform coordinates from the North American Datum 1927 (EPSG:4267) to WGS84 (EPSG:4326).
 The example is run twice: once for cities in USA, then once for cities in Canada:
 (Note: the application may log warnings to the console. Those warnings can be ignored)</p>
-<div class="codehilite"><pre>wget http://sis.apache.org/examples/coordinates/AmericanCities.csv
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">wget http://sis.apache.org/examples/coordinates/AmericanCities.csv
 wget http://sis.apache.org/examples/coordinates/CanadianCities.csv
 sis transform --sourceCRS EPSG:4267 --targetCRS EPSG:4326 AmericanCities.csv
-sis transform --sourceCRS EPSG:4267 --targetCRS EPSG:4326 CanadianCities.csv
-</pre></div>
-
-
+sis transform --sourceCRS EPSG:4267 --targetCRS EPSG:4326 CanadianCities.csv</code></pre></div>
 <p>The first execution should print the following header, followed by transformed coordinate values.
 Note the operation code (EPSG:1173), domain of validity (United State) and accuracy.</p>
-<div class="codehilite"><pre># Source:      NAD27 (EPSG:4267)
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text"># Source:      NAD27 (EPSG:4267)
 # Destination: WGS 84 (EPSG:4326)
 # Operations:  NAD27 to WGS 84 (4) (EPSG:1173)
 # Domain:      United States (USA) - onshore
-# Accuracy:    10.0 metres
-</pre></div>
-
-
+# Accuracy:    10.0 metres</code></pre></div>
 <p>The second execution should print the following header, followed by transformed coordinate values.
 Note that the operation code (EPSG:1172), domain of validity (Canada) and accuracy are not the same
 than in previous example.</p>
-<div class="codehilite"><pre># Source:      NAD27 (EPSG:4267)
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text"># Source:      NAD27 (EPSG:4267)
 # Destination: WGS 84 (EPSG:4326)
 # Operations:  NAD27 to WGS 84 (3) (EPSG:1172)
 # Domain:      Canada - onshore and offshore
-# Accuracy:    20.0 metres
-</pre></div>
-
-
+# Accuracy:    20.0 metres</code></pre></div>
 <p>The difference between those two operations become more visible by adding the <code>--verbose</code> option
 to the above <code>sis transform</code> commands.
 This option shows the coordinate operation in Well Known Text (WKT) or pseudo-WKT format.
 When transforming coordinates in USA, the operation contains the following parameter values:</p>
-<div class="codehilite"><pre>Method[&quot;Geocentric translations (geog2D domain)&quot;],
-  Parameter[&quot;X-axis translation&quot;, -8.0, Unit[&quot;metre&quot;, 1]],
-  Parameter[&quot;Y-axis translation&quot;, 160.0, Unit[&quot;metre&quot;, 1]],
-  Parameter[&quot;Z-axis translation&quot;, 176.0, Unit[&quot;metre&quot;, 1]]
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">Method[&#34;Geocentric translations (geog2D domain)&#34;],
+  Parameter[&#34;X-axis translation&#34;, -8.0, Unit[&#34;metre&#34;, 1]],
+  Parameter[&#34;Y-axis translation&#34;, 160.0, Unit[&#34;metre&#34;, 1]],
+  Parameter[&#34;Z-axis translation&#34;, 176.0, Unit[&#34;metre&#34;, 1]]</code></pre></div>
 <p>But when transforming coordinates in Canada, the operation rather contains the following parameter values:</p>
-<div class="codehilite"><pre>Method[&quot;Geocentric translations (geog2D domain)&quot;],
-  Parameter[&quot;X-axis translation&quot;, -10.0, Unit[&quot;metre&quot;, 1]],
-  Parameter[&quot;Y-axis translation&quot;, 158.0, Unit[&quot;metre&quot;, 1]],
-  Parameter[&quot;Z-axis translation&quot;, 187.0, Unit[&quot;metre&quot;, 1]],
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">Method[&#34;Geocentric translations (geog2D domain)&#34;],
+  Parameter[&#34;X-axis translation&#34;, -10.0, Unit[&#34;metre&#34;, 1]],
+  Parameter[&#34;Y-axis translation&#34;, 158.0, Unit[&#34;metre&#34;, 1]],
+  Parameter[&#34;Z-axis translation&#34;, 187.0, Unit[&#34;metre&#34;, 1]],</code></pre></div>
 <p>As seen in the above examples, the parameter values differ slightly with the geographic area of the coordinates to transform.
 Those parameters could also be different if <em>datum shift grids</em> are available. For example in USA:</p>
-<div class="codehilite"><pre>Method[&quot;NADCON&quot;],
-  Parameter[&quot;Latitude difference file&quot;, &quot;conus.las&quot;],
-  Parameter[&quot;Longitude difference file&quot;, &quot;conus.los&quot;],
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">    Method[&#34;NADCON&#34;],
+      Parameter[&#34;Latitude difference file&#34;, &#34;conus.las&#34;],
+      Parameter[&#34;Longitude difference file&#34;, &#34;conus.los&#34;],\</code></pre></div>
 <p>Java API for accessing functionalities shown in above examples are:</p>
 <ul>
-<li>Convenience static method in <code>org.apache.sis.referencing</code> package:<ul>
+<li>Convenience static method in <code>org.apache.sis.referencing</code> package:
+<ul>
 <li><code>CRS.findOperation(CoordinateReferenceSystem, CoordinateReferenceSystem, GeographicBoundingBox)</code></li>
 </ul>
 </li>
-<li>Class in other package (less convenient but give more control):<ul>
+<li>Class in other package (less convenient but give more control):
+<ul>
 <li><code>org.apache.sis.referencing.operation.DefaultCoordinateOperationFactory</code></li>
 </ul>
 </li>
 </ul>
-<h2 id="metadata">Extracting ISO 19115 Metadata<a class="headerlink" href="#metadata" title="Permanent link">&para;</a></h2>
+<h2 id="metadata">Extracting ISO 19115 Metadata   </h2>
 <p>SIS can read the header of a data file and print the metadata in an ISO 19115 structure.
 The data file given in argument can be a local file or a URL.
 By default, the metadata are shown in a relatively compact tree-table format.
@@ -457,13 +410,9 @@ But the metadata can optionally be exported as an ISO 19139 compliant XML docume
 As of SIS 1.0, only ISO 19139 XML documents, CF-compliant netCDF files, GeoTIFF files, GPX files
 or Moving Features CSV files can be given in argument to this command.
 </blockquote>
-
 <p>The following example show the metadata of a netCDF file accessible from the web:</p>
-<div class="codehilite"><pre>sis metadata https://github.com/opengeospatial/geoapi/raw/master/geoapi-conformance/src/main/resources/org/opengis/test/dataset/Cube4D_projected_float.nc
-</pre></div>
-
-
-<p><details>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">    sis metadata https://github.com/opengeospatial/geoapi/raw/master/geoapi-conformance/src/main/resources/org/opengis/test/dataset/Cube4D_projected_float.nc</code></pre></div>
+<details>
   <summary>Below is an extract of the above command output:</summary>
 <pre>Metadata
   ├─Identification info
@@ -494,51 +443,59 @@ or Moving Features CSV files can be given in argument to this command.
       └─Dimension
           ├─Descriptor………………………………………………………………… Sea temperature
           └─Sequence identifier………………………………………… SST</pre>
-</details></p>
+</details>
 <p>Adding the <code>--format xml</code> option to the above command will format the same metadata in a XML document.
 The output is not shown in this page because of its verbosity.</p>
 <p>Java API for accessing functionalities shown in above examples are:</p>
 <ul>
-<li>Convenience static methods in <code>org.apache.sis.xml</code> package:<ul>
+<li>Convenience static methods in <code>org.apache.sis.xml</code> package:
+<ul>
 <li><code>XML.marshal(…)</code></li>
 <li><code>XML.unmarshal(…)</code></li>
 </ul>
 </li>
-<li>Class in other package (less convenient but give more control):<ul>
+<li>Class in other package (less convenient but give more control):
+<ul>
 <li><code>org.apache.sis.xml.MarshallerPool</code></li>
 </ul>
 </li>
 </ul>
-<h1 id="performance">Performance consideration<a class="headerlink" href="#performance" title="Permanent link">&para;</a></h1>
+<h1 id="performance">Performance consideration   </h1>
 <p>If there is a large amount of files to process, invoking the above command many time may be inefficient
 since it would restart a new JVM on every invocation.
 If the operation requires the EPSG dataset, booting the Derby database also has a significant cost.
 For such cases, it is more efficient to loop inside a small Java program using the <a href="apidocs/index.html">SIS API</a>.</p>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
-    </div>
-  </footer>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+        </article>
+      </section>
+    </div>
+  </div>
+</div>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
+
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/contributor.html b/contributor.html
index 9be1f70..40a5478 100644
--- a/contributor.html
+++ b/contributor.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>New contributor</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
-
-    
-
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
-
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<head>
+  
+
+  <title>Apache SIS - New contributor</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
+
+<body>
+
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,58 +37,97 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">New contributor</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>Improving and extending SIS requires extensive knowledge of geographic information science,
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">New contributor</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>Improving and extending SIS requires extensive knowledge of geographic information science,
 object oriented programming, the Java language, and of the library itself. Contributors should
 expect that they will need to learn a great deal before being able to become productive.
-However, the effort required to become productive should improve the contributor's understanding
+However, the effort required to become productive should improve the contributor&rsquo;s understanding
 and knowledge of geographic information systems, of geodetic and geographic science, and of
 effective computer programming.</p>
 <p>This document is expected to evolve as the SIS project develops its own mode of operation.</p>
-<div class="toc">
-<ul>
-<li><a href="#knowledge">Background Knowledge</a><ul>
-<li><a href="#science">Geographic Information Systems and Science</a></li>
-<li><a href="#ogc">The ISO/OGC Geospatial Model</a></li>
-<li><a href="#java">Object-Oriented Programming in Java</a></li>
-<li><a href="#math">Mathematical Background</a></li>
-<li><a href="#geoapi">The GeoAPI Interfaces</a></li>
-<li><a href="#modules">The SIS library modules</a></li>
-</ul>
-</li>
-</ul>
-</div>
-<h1 id="knowledge">Background Knowledge<a class="headerlink" href="#knowledge" title="Permanent link">&para;</a></h1>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#knowledge">Background Knowledge   </a>
+      <ul>
+        <li><a href="#science">Geographic Information Systems and Science   </a></li>
+        <li><a href="#ogc">The ISO/OGC Geospatial Model   </a></li>
+        <li><a href="#java">Object-Oriented Programming in Java   </a></li>
+        <li><a href="#math">Mathematical Background   </a></li>
+        <li><a href="#geoapi">The GeoAPI Interfaces   </a></li>
+        <li><a href="#modules">The SIS library modules   </a></li>
+      </ul>
+    </li>
+  </ul>
+</nav>
+<h1 id="knowledge">Background Knowledge   </h1>
 <p>All contributors arrive to the project with different knowledge bases, some with scientific
 backgrounds, some with a background in computer science, and others with geographic backgrounds
 or even no training in geographic information science at all. By sharing the richness of our
 individual backgrounds we have acquired a list of subjects which we consider critical to fully
 understanding the SIS project. New contributors are highly encouraged to explore these
 areas if they have no or little knowledge of them.</p>
-<h2 id="science">Geographic Information Systems and Science<a class="headerlink" href="#science" title="Permanent link">&para;</a></h2>
+<h2 id="science">Geographic Information Systems and Science   </h2>
 <p>While a background in the field is not required, it nonetheless proves exceedingly useful along the way.
 GIS has developed its own language and has particular concerns which return frequently.
 Issues of spatial representation, data size, spatial scale, information workflows and other topics
@@ -134,17 +136,49 @@ arise frequently and are worth understanding.</p>
 by Paul A. Longley, Michael F. Goodchild, David J. Maguire and David W. Rhind published in its
 second edition by John Wiley and Sons Ltd. in 2004.
 Apache SIS also provides an introduction in the <a href="book/en/developer-guide.html">Developer guide</a>.</p>
-<h2 id="ogc">The <abbr title="International Organization for Standardization">ISO</abbr>/<abbr title="Open Geospatial Consortium">OGC</abbr> Geospatial Model<a class="headerlink" href="#ogc" title="Permanent link">&para;</a></h2>
+<h2 id="ogc">The ISO/OGC Geospatial Model   </h2>
 <p>SIS builds on the standards developed through a collaboration between the International
-Organization for Standardization (<abbr title="International Organization for Standardization">ISO</abbr>) and the Open Geospatial Consortium (<abbr title="Open Geospatial Consortium">OGC</abbr>).
+Organization for Standardization (
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+) and the Open Geospatial Consortium (
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+).
 Contributors to SIS should have at least a basic understanding of the model developed in the
-<abbr title="International Organization for Standardization">ISO</abbr> 19000 series of specifications, starting with the Abstract model and working through the
-<em>Feature</em> model. While the <abbr title="International Organization for Standardization">ISO</abbr> specifications are sold, the <abbr title="Open Geospatial Consortium">OGC</abbr> releases its own, essentially
-identical versions of standards which have evolved from the collaboration. The <abbr title="Open Geospatial Consortium">OGC</abbr> specifications
-are available for the <a href="http://www.opengeospatial.org/standards"><abbr title="Open Geospatial Consortium">OGC</abbr> standards and specification</a> page.</p>
-<p>As time progresses, we hope to develop documentation material to introduce the <abbr title="International Organization for Standardization">ISO</abbr> 19000 specification series.
+
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+ 19000 series of specifications, starting with the Abstract model and working through the
+<em>Feature</em> model. While the 
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+ specifications are sold, the 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ releases its own, essentially
+identical versions of standards which have evolved from the collaboration. The 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ specifications
+are available for the <a href="https://www.ogc.org/standards">
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ standards and specification</a> page.</p>
+<p>As time progresses, we hope to develop documentation material to introduce the 
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+ 19000 specification series.
 Most of the documentation provided by SIS can be found in the <a href="book/en/developer-guide.html">Developer guide</a>.</p>
-<h2 id="java">Object-Oriented Programming in Java<a class="headerlink" href="#java" title="Permanent link">&para;</a></h2>
+<h2 id="java">Object-Oriented Programming in Java   </h2>
 <p>SIS is a library designed to be used by other programmers. To play this role effectively,
 SIS must consider the various ways that users can reuse Java code: not only through object
 instantiation and method calls but also through inheritance. SIS pays special attention to
@@ -156,7 +190,7 @@ elements in the Java language and discusses subtleties of the language and its u
 Most importantly, the book reveals the full scope a programmer must consider when developing a code library.</p>
 <p>The <a href="code-patterns.html">Recommended code patterns</a> page also discusses some elements
 of special importance to Apache SIS.</p>
-<h2 id="math">Mathematical Background<a class="headerlink" href="#math" title="Permanent link">&para;</a></h2>
+<h2 id="math">Mathematical Background   </h2>
 <p>SIS frequently deals with complex calculations using relatively simple mathematics of
 trigonometry and matrix algebra. The coordinate operations of the Referencing modules involve
 trigonometric transformations on a flattened ellipsoid of rotation, the image transformations in
@@ -170,40 +204,54 @@ shear, though this latter component is used infrequently in the library. Mathema
 affine transformations are usually applied as a matrix operation applied to a coordinate vector.
 There are numerous introductions to affine transformations available on the World Wide Web since
 the concept is central to all graphics programming.</p>
-<h2 id="geoapi">The GeoAPI Interfaces<a class="headerlink" href="#geoapi" title="Permanent link">&para;</a></h2>
+<h2 id="geoapi">The GeoAPI Interfaces   </h2>
 <p>SIS is build partially as an implementation of the GeoAPI interfaces. GeoAPI defines a set
-of objects offering particular methods thereby providing an interpretation of the <abbr title="International Organization for Standardization">ISO</abbr>/<abbr title="Open Geospatial Consortium">OGC</abbr>
+of objects offering particular methods thereby providing an interpretation of the 
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+/
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+
 standards in the Java language. GeoAPI therefore defines the core of the model implemented
 by Apache SIS.</p>
-<p>GeoAPI can most easily be learned by exploring the <a href="http://www.geoapi.org/3.0/javadoc/index.html">GeoAPI Javadoc</a>.</p>
-<h2 id="modules">The SIS library modules<a class="headerlink" href="#modules" title="Permanent link">&para;</a></h2>
+<p>GeoAPI can most easily be learned by exploring the <a href="https://www.geoapi.org/3.0/javadoc/index.html">GeoAPI Javadoc</a>.</p>
+<h2 id="modules">The SIS library modules   </h2>
 <p>Contributors should gain a basic understanding of the core library including the separation into modules,
 the functionality available in the base module, and the functioning of the modules of interest.</p>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
+
+        </article>
+      </section>
     </div>
-  </footer>
-
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
-
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+  </div>
+</div>
+
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
+
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/css/syntax.css b/css/syntax.css
new file mode 100644
index 0000000..e3b54c8
--- /dev/null
+++ b/css/syntax.css
@@ -0,0 +1,70 @@
+/* Background */ .chroma { color: #272822; background-color: #fafafa }
+/* Error */ .chroma .err { color: #960050; background-color: #1e0010 }
+/* LineTableTD */ .chroma .lntd { vertical-align: top; padding: 0; margin: 0; border: 0; }
+/* LineTable */ .chroma .lntable { border-spacing: 0; padding: 0; margin: 0; border: 0; width: auto; overflow: auto; display: block; }
+/* LineHighlight */ .chroma .hl { display: block; width: 100%;background-color: #ffffcc }
+/* LineNumbersTable */ .chroma .lnt { margin-right: 0.4em; padding: 0 0.4em 0 0.4em;color: #7f7f7f }
+/* LineNumbers */ .chroma .ln { margin-right: 0.4em; padding: 0 0.4em 0 0.4em;color: #7f7f7f }
+/* Keyword */ .chroma .k { color: #00a8c8 }
+/* KeywordConstant */ .chroma .kc { color: #00a8c8 }
+/* KeywordDeclaration */ .chroma .kd { color: #00a8c8 }
+/* KeywordNamespace */ .chroma .kn { color: #f92672 }
+/* KeywordPseudo */ .chroma .kp { color: #00a8c8 }
+/* KeywordReserved */ .chroma .kr { color: #00a8c8 }
+/* KeywordType */ .chroma .kt { color: #00a8c8 }
+/* Name */ .chroma .n { color: #111111 }
+/* NameAttribute */ .chroma .na { color: #75af00 }
+/* NameBuiltin */ .chroma .nb { color: #111111 }
+/* NameBuiltinPseudo */ .chroma .bp { color: #111111 }
+/* NameClass */ .chroma .nc { color: #75af00 }
+/* NameConstant */ .chroma .no { color: #00a8c8 }
+/* NameDecorator */ .chroma .nd { color: #75af00 }
+/* NameEntity */ .chroma .ni { color: #111111 }
+/* NameException */ .chroma .ne { color: #75af00 }
+/* NameFunction */ .chroma .nf { color: #75af00 }
+/* NameFunctionMagic */ .chroma .fm { color: #111111 }
+/* NameLabel */ .chroma .nl { color: #111111 }
+/* NameNamespace */ .chroma .nn { color: #111111 }
+/* NameOther */ .chroma .nx { color: #75af00 }
+/* NameProperty */ .chroma .py { color: #111111 }
+/* NameTag */ .chroma .nt { color: #f92672 }
+/* NameVariable */ .chroma .nv { color: #111111 }
+/* NameVariableClass */ .chroma .vc { color: #111111 }
+/* NameVariableGlobal */ .chroma .vg { color: #111111 }
+/* NameVariableInstance */ .chroma .vi { color: #111111 }
+/* NameVariableMagic */ .chroma .vm { color: #111111 }
+/* Literal */ .chroma .l { color: #ae81ff }
+/* LiteralDate */ .chroma .ld { color: #d88200 }
+/* LiteralString */ .chroma .s { color: #d88200 }
+/* LiteralStringAffix */ .chroma .sa { color: #d88200 }
+/* LiteralStringBacktick */ .chroma .sb { color: #d88200 }
+/* LiteralStringChar */ .chroma .sc { color: #d88200 }
+/* LiteralStringDelimiter */ .chroma .dl { color: #d88200 }
+/* LiteralStringDoc */ .chroma .sd { color: #d88200 }
+/* LiteralStringDouble */ .chroma .s2 { color: #d88200 }
+/* LiteralStringEscape */ .chroma .se { color: #8045ff }
+/* LiteralStringHeredoc */ .chroma .sh { color: #d88200 }
+/* LiteralStringInterpol */ .chroma .si { color: #d88200 }
+/* LiteralStringOther */ .chroma .sx { color: #d88200 }
+/* LiteralStringRegex */ .chroma .sr { color: #d88200 }
+/* LiteralStringSingle */ .chroma .s1 { color: #d88200 }
+/* LiteralStringSymbol */ .chroma .ss { color: #d88200 }
+/* LiteralNumber */ .chroma .m { color: #ae81ff }
+/* LiteralNumberBin */ .chroma .mb { color: #ae81ff }
+/* LiteralNumberFloat */ .chroma .mf { color: #ae81ff }
+/* LiteralNumberHex */ .chroma .mh { color: #ae81ff }
+/* LiteralNumberInteger */ .chroma .mi { color: #ae81ff }
+/* LiteralNumberIntegerLong */ .chroma .il { color: #ae81ff }
+/* LiteralNumberOct */ .chroma .mo { color: #ae81ff }
+/* Operator */ .chroma .o { color: #f92672 }
+/* OperatorWord */ .chroma .ow { color: #f92672 }
+/* Punctuation */ .chroma .p { color: #111111 }
+/* Comment */ .chroma .c { color: #75715e }
+/* CommentHashbang */ .chroma .ch { color: #75715e }
+/* CommentMultiline */ .chroma .cm { color: #75715e }
+/* CommentSingle */ .chroma .c1 { color: #75715e }
+/* CommentSpecial */ .chroma .cs { color: #75715e }
+/* CommentPreproc */ .chroma .cp { color: #75715e }
+/* CommentPreprocFile */ .chroma .cpf { color: #75715e }
+/* GenericEmph */ .chroma .ge { font-style: italic }
+/* GenericStrong */ .chroma .gs { font-weight: bold }
diff --git a/downloads.html b/downloads.html
index 4eeeb88..6a0ed11 100644
--- a/downloads.html
+++ b/downloads.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Apache SIS downloads</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Apache SIS downloads</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,47 +37,87 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Apache SIS downloads</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>Apache SIS 1.0 is now available.
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Apache SIS downloads</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>Apache SIS 1.0 is now available.
 See the <a href="release-notes/1.0.html">release notes</a> for a list of changes since the previous version.</p>
 <p>Apache SIS releases are available under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
 See the <code>NOTICE</code> file contained in each release artifact for applicable copyright attribution notices.</p>
-<div class="toc">
-<ul>
-<li><a href="#bundles">Download ZIP files</a><ul>
-<li><a href="#release-gpg">Verify signatures</a></li>
-</ul>
-</li>
-<li><a href="#maven">Download as a Maven dependency</a><ul>
-<li><a href="#non-free">Include non-free resources</a></li>
-</ul>
-</li>
-</ul>
-</div>
-<h1 id="bundles">Download ZIP files<a class="headerlink" href="#bundles" title="Permanent link">&para;</a></h1>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#bundles">Download ZIP files   </a>
+      <ul>
+        <li><a href="#release-gpg">Verify signatures   </a></li>
+      </ul>
+    </li>
+    <li><a href="#maven">Download as a Maven dependency   </a>
+      <ul>
+        <li><a href="#non-free">Include non-free resources   </a></li>
+      </ul>
+    </li>
+  </ul>
+</nav>
+<h1 id="bundles">Download ZIP files   </h1>
 <p>Apache SIS is distributed in the form of Java source code in a multi-modules Apache Maven project.
 For convenience, an aggregated Javadoc and a pre-compiled JAR file are available as separated downloads.
 The precompiled JAR file contains most modules and dependencies in a single archive for easier inclusion
@@ -124,36 +127,27 @@ in a classpath.</p>
 <li><a href="http://www.apache.org/dyn/closer.cgi/sis/1.0/apache-sis-1.0-doc.zip">Apache SIS 1.0 javadoc</a> [<a href="https://www.apache.org/dist/sis/1.0/apache-sis-1.0-doc.zip.asc">PGP</a>] [<a href="https://www.apache.org/dist/sis/1.0/apache-sis-1.0-doc.zip.md5">MD5</a>] [<a href="https://www.apache.org/dist/sis/1.0/apache-sis-1.0-doc.zip.sha">SHA</a>]</li>
 <li><a href="http://www.apache.org/dyn/closer.cgi/sis/1.0/apache-sis-1.0-bin.zip">Apache SIS 1.0 binary</a>  [<a href="https://www.apache.org/dist/sis/1.0/apache-sis-1.0-bin.zip.asc">PGP</a>] [<a href="https://www.apache.org/dist/sis/1.0/apache-sis-1.0-bin.zip.md5">MD5</a>] [<a href="https://www.apache.org/dist/sis/1.0/apache-sis-1.0-bin.zip.sha">SHA</a>]</li>
 </ul>
-<h2 id="release-gpg">Verify signatures<a class="headerlink" href="#release-gpg" title="Permanent link">&para;</a></h2>
+<h2 id="release-gpg">Verify signatures   </h2>
 <p>All downloads can be verified using the Apache SIS code signing <a href="https://www.apache.org/dist/sis/KEYS">KEYS</a>.
 The PGP (<em>Pretty Good Privacy</em>) signatures can be verified using any OpenPGP implementation, for example GPG (<em>GNU Privacy Guard</em>).
 First download the <a href="https://www.apache.org/dist/sis/KEYS">KEYS</a> file and the <code>.asc</code> signature files for the relevant release packages.
 Make sure you get these files from the main distribution directory, rather than from a mirror.
 Then verify the signatures using the following:</p>
 <p>Using GNU Privacy Guard:</p>
-<div class="codehilite"><pre>gpg --import KEYS
-gpg --verify apache-sis-X.Y.Z.zip.asc
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">gpg --import KEYS
+gpg --verify apache-sis-X.Y.Z.zip.asc</code></pre></div>
 <p>Using PGP version 6:</p>
-<div class="codehilite"><pre>pgp -ka KEYS
-pgp apache-sis-X.Y.Z.zip.asc
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">pgp -ka KEYS
+pgp apache-sis-X.Y.Z.zip.asc</code></pre></div>
 <p>Using PGP version 5:</p>
-<div class="codehilite"><pre>pgpk -a KEYS
-pgpv apache-sis-X.Y.Z.zip.asc
-</pre></div>
-
-
-<h1 id="maven">Download as a Maven dependency<a class="headerlink" href="#maven" title="Permanent link">&para;</a></h1>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">pgpk -a KEYS
+pgpv apache-sis-X.Y.Z.zip.asc</code></pre></div>
+<h1 id="maven">Download as a Maven dependency   </h1>
 <p>An easy approach to integrate Apache SIS into a Java project uses the <a href="http://maven.apache.org/">Apache Maven</a>
 dependency management tool to automatically obtain the required Java Archives (JAR) files from the network.
 Below are examples of declarations in a <code>pom.xml</code> file for building a project with a SIS core module.
 If running on Java 11 or higher, at least one of the two next dependencies is also required:</p>
-<div class="codehilite"><pre><span class="nt">&lt;properties&gt;</span>
+<div class="highlight"><pre class="chroma"><code class="language-xml" data-lang="xml"><span class="nt">&lt;properties&gt;</span>
   <span class="nt">&lt;sis.version&gt;</span>1.0<span class="nt">&lt;/sis.version&gt;</span>
 <span class="nt">&lt;/properties&gt;</span>
 
@@ -165,8 +159,8 @@ If running on Java 11 or higher, at least one of the two next dependencies is al
   <span class="nt">&lt;/dependency&gt;</span>
 <span class="nt">&lt;/dependencies&gt;</span>
 
-<span class="c">&lt;!-- The following dependency can be omitted on Java 8 (unconditionally), or</span>
-<span class="c">     on Java 9 and 10 if the &quot;--add-modules java.xml.bind&quot; option is used. --&gt;</span>
+<span class="c">&lt;!-- The following dependency can be omitted on Java 8 (unconditionally), or
+</span><span class="c">     on Java 9 and 10 if the &#34;--add-modules java.xml.bind&#34; option is used. --&gt;</span>
 <span class="nt">&lt;dependency&gt;</span>
   <span class="nt">&lt;groupId&gt;</span>org.glassfish.jaxb<span class="nt">&lt;/groupId&gt;</span>
   <span class="nt">&lt;artifactId&gt;</span>jaxb-runtime<span class="nt">&lt;/artifactId&gt;</span>
@@ -174,66 +168,66 @@ If running on Java 11 or higher, at least one of the two next dependencies is al
   <span class="nt">&lt;scope&gt;</span>runtime<span class="nt">&lt;/scope&gt;</span>
 <span class="nt">&lt;/dependency&gt;</span>
 
-<span class="c">&lt;!-- Above JAXB dependency can be replaced by the following dependency</span>
-<span class="c">     if no XML (un)marshalling is wanted. This dependency is lighter. --&gt;</span>
+<span class="c">&lt;!-- Above JAXB dependency can be replaced by the following dependency
+</span><span class="c">     if no XML (un)marshalling is wanted. This dependency is lighter. --&gt;</span>
 <span class="nt">&lt;dependency&gt;</span>
   <span class="nt">&lt;groupId&gt;</span>jakarta.xml.bind<span class="nt">&lt;/groupId&gt;</span>
   <span class="nt">&lt;artifactId&gt;</span>jakarta.xml.bind-api<span class="nt">&lt;/artifactId&gt;</span>
   <span class="nt">&lt;version&gt;</span>2.3.2<span class="nt">&lt;/version&gt;</span>
   <span class="nt">&lt;scope&gt;</span>runtime<span class="nt">&lt;/scope&gt;</span>
-<span class="nt">&lt;/dependency&gt;</span>
-</pre></div>
-
-
-<h2 id="non-free">Include non-free resources<a class="headerlink" href="#non-free" title="Permanent link">&para;</a></h2>
-<p>The <a href="http://www.epsg.org/">EPSG geodetic dataset</a> is optional but strongly recommended.
+<span class="nt">&lt;/dependency&gt;</span></code></pre></div>
+<h2 id="non-free">Include non-free resources   </h2>
+<p>The <a href="https://epsg.org/">EPSG geodetic dataset</a> is optional but strongly recommended.
 The EPSG dataset is a de-facto standard providing
 <a href="tables/CoordinateReferenceSystems.html">thousands of Coordinate Reference System (CRS) definitions</a>
 together with information about how to perform coordinate operations, their accuracies and their domains of validity.
 However usage of EPSG dataset requires acceptation of <a href="https://epsg.org/terms-of-use.html">EPSG terms of use</a>.
 If you accept those terms of use, then the following dependency can be added:</p>
-<div class="codehilite"><pre><span class="nt">&lt;dependencies&gt;</span>
+<div class="highlight"><pre class="chroma"><code class="language-xml" data-lang="xml"><span class="nt">&lt;dependencies&gt;</span>
   <span class="nt">&lt;dependency&gt;</span>
     <span class="nt">&lt;groupId&gt;</span>org.apache.sis.non-free<span class="nt">&lt;/groupId&gt;</span>
     <span class="nt">&lt;artifactId&gt;</span>sis-embedded-data<span class="nt">&lt;/artifactId&gt;</span>
     <span class="nt">&lt;version&gt;</span>${sis.version}<span class="nt">&lt;/version&gt;</span>
     <span class="nt">&lt;scope&gt;</span>runtime<span class="nt">&lt;/scope&gt;</span>
   <span class="nt">&lt;/dependency&gt;</span>
-<span class="nt">&lt;/dependencies&gt;</span>
-</pre></div>
-
-
+<span class="nt">&lt;/dependencies&gt;</span></code></pre></div>
 <p>Above dependency uses a read-only embedded Derby database.
 Note that the need to uncompress the <code>sis-embedded-data.jar</code> file
 slows down <code>CRS​.forCode(…)</code> and <code>CRS​.findCoordinateOperation(…)</code> method executions.
 For better flexibility and performance, it is also possible to use an uncompressed
 and writable Derby database, or to install the EPSG dataset on HSQL or PostgreSQL.
 See <a href="epsg.html">How to use EPSG geodetic dataset</a> page for more information.</p>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
-    </div>
-  </footer>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+        </article>
+      </section>
+    </div>
+  </div>
+</div>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
+
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/epsg.html b/epsg.html
index 7b7573b..15a53ff 100644
--- a/epsg.html
+++ b/epsg.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>How to use EPSG geodetic dataset</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - How to use EPSG geodetic dataset</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,34 +37,72 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">How to use EPSG geodetic dataset</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>The <a href="http://www.epsg.org/">EPSG geodetic dataset</a> is a de-facto standard providing
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">How to use EPSG geodetic dataset</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>The <a href="https://epsg.org/">EPSG geodetic dataset</a> is a de-facto standard providing
 <a href="tables/CoordinateReferenceSystems.html">thousands of Coordinate Reference System (CRS) definitions</a>
 together with information about how to perform coordinate operations, their accuracies and their domains of validity.
-The EPSG dataset is owned and maintained by the <a href="http://www.iogp.org/">International Association of Oil &amp; Gas producers</a>.
+The EPSG dataset is owned and maintained by the <a href="https://www.iogp.org/">International Association of Oil &amp; Gas producers</a>.
 Usage of EPSG dataset with Apache SIS is optional but strongly recommended:
 without that geodetic dataset, only a small subset of CRS definitions will be available
 (basically the constants enumerated in the <a href="apidocs/org/apache/sis/referencing/CommonCRS.html"><code>CommonCRS</code></a> Java class)
@@ -111,41 +112,41 @@ and their domains of validity may be unspecified if Apache SIS can not query EPS
 <p>The EPSG geodetic dataset is not distributed with Apache SIS because the <a href="https://epsg.org/terms-of-use.html">EPSG terms of use</a>
 are incompatible with Apache license. The following items are quoted from those terms of use:</p>
 <ul>
-<li>The <a href="http://www.epsg.org/">EPSG</a> Facilities are published by <a href="http://www.iogp.org/">IOGP</a> at no charge. Distribution for profit is forbidden.</li>
+<li>The <a href="https://epsg.org/">EPSG</a> Facilities are published by <a href="https://www.iogp.org/">IOGP</a> at no charge. Distribution for profit is forbidden.</li>
 <li>The data may be included in any commercial package provided that any commerciality is based on value added
-    by the provider and not on a value ascribed to the EPSG Dataset which is made available at no charge.</li>
+by the provider and not on a value ascribed to the EPSG Dataset which is made available at no charge.</li>
 <li>Ownership of the EPSG Dataset by IOGP must be acknowledged in any publication or transmission
-    (by whatever means) thereof (including permitted modifications).</li>
+(by whatever means) thereof (including permitted modifications).</li>
 <li>Modification of parameter values is permitted as described in the table 1 to allow change to the content
-    of the information provided that numeric equivalence is achieved.</li>
+of the information provided that numeric equivalence is achieved.</li>
 <li>No data that has been modified other than as permitted in these Terms of Use shall be attributed to the EPSG Dataset.</li>
 </ul>
 <p>In order to use the EPSG geodetic dataset with Apache SIS, apply <em>one</em> of the following choices:</p>
-<div class="toc">
-<ul>
-<li><a href="#command-line">Install a local copy with command-line tool</a><ul>
-<li><a href="#use-local">Use the local copy in other applications</a></li>
-</ul>
-</li>
-<li><a href="#maven">Add a Maven dependency</a><ul>
-<li><a href="#maven-epsg">As database installer</a></li>
-<li><a href="#maven-embedded">As embedded database</a></li>
-</ul>
-</li>
-<li><a href="#jndi">Use Java Naming and Directory Interface</a><ul>
-<li><a href="#jndi-java">Registration by Java code</a></li>
-<li><a href="#jndi-webapp">Registration in web application containers</a></li>
-</ul>
-</li>
-</ul>
-</div>
-<h1 id="command-line">Install a local copy with command-line tool<a class="headerlink" href="#command-line" title="Permanent link">&para;</a></h1>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#command-line">Install a local copy with command-line tool   </a>
+      <ul>
+        <li><a href="#use-local">Use the local copy in other applications   </a></li>
+      </ul>
+    </li>
+    <li><a href="#maven">Add a Maven dependency   </a>
+      <ul>
+        <li><a href="#maven-epsg">As database installer    </a></li>
+        <li><a href="#maven-embedded">As embedded database    </a></li>
+      </ul>
+    </li>
+    <li><a href="#jndi">Use Java Naming and Directory Interface   </a>
+      <ul>
+        <li><a href="#jndi-java">Registration by Java code   </a></li>
+        <li><a href="#jndi-webapp">Registration in web application containers   </a></li>
+      </ul>
+    </li>
+  </ul>
+</nav>
+<h1 id="command-line">Install a local copy with command-line tool   </h1>
 <p>If the <a href="command-line.html">command-line tool</a> has been downloaded and installed, just query any CRS.
 For example:</p>
-<div class="codehilite"><pre>sis crs EPSG:6676
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">sis crs EPSG:6676</code></pre></div>
 <p>The first time that the command-line tool needs to query EPSG, it will prompt the user for authorization
 to download EPSG geodetic dataset from Maven Central. If the user accepts EPSG terms of use, then a local
 copy of the EPSG geodetic dataset will be created and stored in the <code>apache-sis-1.0/data</code> sub-directory.</p>
@@ -153,12 +154,9 @@ copy of the EPSG geodetic dataset will be created and stored in the <code>apache
 try adding a <code>derby-&lt;version&gt;.jar</code> file (download lib-distribution from <a href="http://db.apache.org/derby/derby_downloads.html">Derby project</a>) in the <code>apache-sis-1.0/lib</code> sub-directory.
 This is normally not needed with Oracle JDK8 because Apache SIS tries to use the JavaDB embedded
 in those distributions, but may be necessary with other distributions or in security-constrained environments:</p>
-<div class="codehilite"><pre><span class="nb">cd </span>apache-sis-1.0/lib
-wget http://repo1.maven.org/maven2/org/apache/derby/derby/10.14.2.0/derby-10.14.2.0.jar
-</pre></div>
-
-
-<h2 id="use-local">Use the local copy in other applications<a class="headerlink" href="#use-local" title="Permanent link">&para;</a></h2>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> apache-sis-1.0/lib
+wget http://repo1.maven.org/maven2/org/apache/derby/derby/10.14.2.0/derby-10.14.2.0.jar</code></pre></div>
+<h2 id="use-local">Use the local copy in other applications   </h2>
 <p>For using the installed EPSG geodetic dataset in your own application, apply <em>one</em> of the following choices:</p>
 <ul>
 <li>Set the <code>SIS_DATA</code> environment variable to the path of <code>apache-sis-1.0/data</code> directory <em>(preferred choice)</em>.</li>
@@ -167,37 +165,31 @@ wget http://repo1.maven.org/maven2/org/apache/derby/derby/10.14.2.0/derby-10.14.
 <p>Alternatively <code>SIS_DATA</code> or <code>derby.system.home</code> can be set to the path of any other directory which contain the same files.
 Examples are shown below for Unix systems, assuming that the current directory is the directory where <code>apache-sis-1.0-bin.zip</code>
 has been unzipped:</p>
-<div class="codehilite"><pre><span class="nb">export </span><span class="nv">SIS_DATA</span><span class="o">=</span>apache-sis-1.0/data
-java -classpath apache-sis-1.0/lib/sis.jar:myApp.jar myMainClass
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">export</span> <span class="nv">SIS_DATA</span><span class="o">=</span>apache-sis-1.0/data
+java -classpath apache-sis-1.0/lib/sis.jar:myApp.jar myMainClass</code></pre></div>
 <p>If the <code>SIS_DATA</code> environment variable can not be set, Java property can be used as a fallback:</p>
-<div class="codehilite"><pre><span class="n">java</span> <span class="o">-</span><span class="n">Dderby</span><span class="p">.</span><span class="n">system</span><span class="p">.</span><span class="n">home</span><span class="p">=</span><span class="n">apache</span><span class="o">-</span><span class="n">sis</span><span class="o">-</span>1<span class="p">.</span>0<span class="o">/</span><span class="n">data</span><span class="o">/</span><span class="n">Databases</span> <span class="o">- [...]
-</pre></div>
-
-
-<h1 id="maven">Add a Maven dependency<a class="headerlink" href="#maven" title="Permanent link">&para;</a></h1>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">java</span> <span class="o">-</span><span class="n">Dderby</span><span class="o">.</span><span class="na">system</span><span class="o">.</span><span class="na">home</span><span class="o">=</span><span class="n">apache</span><span class="o">-</span><span class="n">sis</span><span class="o">-</span><span class="n">1</span><span class="o">.</span><span class="na">0</span><span class="o">/ [...]
+<h1 id="maven">Add a Maven dependency   </h1>
 <p>Maven projects can get the EPSG geodetic dataset automatically, <em>without any prompt for terms of use agreement</em>,
 if they add a <code>sis-epsg</code> or <code>sis-embedded-data</code> dependency (from <code>org.apache.sis.non-free</code> group) in their project.
 Those two approaches have advantages and inconvenient described in following sub-sections.
 In both cases, we assume that developers who add those dependencies explicitely in their project agree with
 <a href="https://epsg.org/terms-of-use.html">EPSG terms of use</a>.</p>
-<h2 id="maven-epsg">As database installer<a class="headerlink" href="#maven-epsg" title="Permanent link">&para;</a></h2>
+<h2 id="maven-epsg">As database installer    </h2>
 <p>With <code>sis-epsg</code> artifact on the classpath, Apache SIS will create a local copy of EPSG database when first needed.
 The target database must be specified by users with <em>one</em> of the following choices:</p>
 <ul>
 <li>Set the <code>SIS_DATA</code> environment variable to the path of an initially empty directory <em>(preferred choice)</em>.
-    The specified directory must exist, but sub-directories will be created as needed.</li>
+The specified directory must exist, but sub-directories will be created as needed.</li>
 <li>Set the <code>derby.system.home</code> Java property to the path of an initially empty directory,
-    or a directory that contain other Derby databases. The specified directory must exist.</li>
+or a directory that contain other Derby databases. The specified directory must exist.</li>
 <li>Register a <code>DataSource</code> under the <code>java:comp/env/jdbc/SpatialMetadata</code> name in a JNDI directory
-    (see <a href="#jndi">next section</a>). The database must exist but can be initially empty.</li>
+(see <a href="#jndi">next section</a>). The database must exist but can be initially empty.</li>
 <li>Set a <code>DataSource</code> <a href="./apidocs/org/apache/sis/setup/Configuration.html">from Java code</a>.</li>
 </ul>
 <p>The Maven dependency is as below (the Derby dependency can be replaced by another database driver
 if that database is specified by JNDI):</p>
-<div class="codehilite"><pre><span class="nt">&lt;dependencies&gt;</span>
+<div class="highlight"><pre class="chroma"><code class="language-xml" data-lang="xml"><span class="nt">&lt;dependencies&gt;</span>
   <span class="nt">&lt;dependency&gt;</span>
     <span class="nt">&lt;groupId&gt;</span>org.apache.sis.non-free<span class="nt">&lt;/groupId&gt;</span>
     <span class="nt">&lt;artifactId&gt;</span>sis-epsg<span class="nt">&lt;/artifactId&gt;</span>
@@ -205,20 +197,17 @@ if that database is specified by JNDI):</p>
     <span class="nt">&lt;scope&gt;</span>runtime<span class="nt">&lt;/scope&gt;</span>
   <span class="nt">&lt;/dependency&gt;</span>
 
-  <span class="c">&lt;!-- Following dependency can be omitted on Oracle JDK8</span>
-<span class="c">       since that Java distributions contain Derby (a.k.a JavaDB). --&gt;</span>
+  <span class="c">&lt;!-- Following dependency can be omitted on Oracle JDK8
+</span><span class="c">       since that Java distributions contain Derby (a.k.a JavaDB). --&gt;</span>
   <span class="nt">&lt;dependency&gt;</span>
     <span class="nt">&lt;groupId&gt;</span>org.apache.derby<span class="nt">&lt;/groupId&gt;</span>
     <span class="nt">&lt;artifactId&gt;</span>derby<span class="nt">&lt;/artifactId&gt;</span>
     <span class="nt">&lt;version&gt;</span>10.14.2.0<span class="nt">&lt;/version&gt;</span>
     <span class="nt">&lt;scope&gt;</span>runtime<span class="nt">&lt;/scope&gt;</span>
   <span class="nt">&lt;/dependency&gt;</span>
-<span class="nt">&lt;/dependencies&gt;</span>
-</pre></div>
-
-
+<span class="nt">&lt;/dependencies&gt;</span></code></pre></div>
 <p>See the <a href="downloads.html#epsg">download</a> page for more information about Maven dependency declaration.</p>
-<h2 id="maven-embedded">As embedded database<a class="headerlink" href="#maven-embedded" title="Permanent link">&para;</a></h2>
+<h2 id="maven-embedded">As embedded database    </h2>
 <p>With <code>sis-embedded-data</code> artifact on the classpath, there is no need to setup environment variable, Java property or JNDI.
 However this simplicity come with the following inconvenient:</p>
 <ul>
@@ -231,17 +220,14 @@ However this simplicity come with the following inconvenient:</p>
 <p>This dependency can be declared as below
 (see the <a href="downloads.html#epsg">download</a> page for more information about Maven dependency declaration).
 Note that <code>sis-epsg</code> and <code>sis-embedded-data</code> should not be specified in the same project; only one is needed:</p>
-<div class="codehilite"><pre><span class="nt">&lt;dependencies&gt;</span>
+<div class="highlight"><pre class="chroma"><code class="language-xml" data-lang="xml"><span class="nt">&lt;dependencies&gt;</span>
   <span class="nt">&lt;dependency&gt;</span>
     <span class="nt">&lt;groupId&gt;</span>org.apache.sis.non-free<span class="nt">&lt;/groupId&gt;</span>
     <span class="nt">&lt;artifactId&gt;</span>sis-embedded-data<span class="nt">&lt;/artifactId&gt;</span>
     <span class="nt">&lt;version&gt;</span>1.0<span class="nt">&lt;/version&gt;</span>
     <span class="nt">&lt;scope&gt;</span>runtime<span class="nt">&lt;/scope&gt;</span>
   <span class="nt">&lt;/dependency&gt;</span>
-<span class="nt">&lt;/dependencies&gt;</span>
-</pre></div>
-
-
+<span class="nt">&lt;/dependencies&gt;</span></code></pre></div>
 <p>The performance issue can be avoided if the JAR file is uncompressed.
 But uncompressed <code>sis-embedded-data.jar</code> file is more than 5 times larger than the compressed file.
 Given that <code>CRS​.forCode(…)</code> and <code>CRS​.findCoordinateOperation(…)</code> should not be invoked too often,
@@ -249,108 +235,99 @@ and that performance degradation does not apply to the <code>CoordinateOperation
 the JAR file is distributed on the Maven repository in its compressed form.
 If desired, better performance can be achieved by using one of the other configurations described in this page,
 or by uncompressing the <code>sis-embedded-data.jar</code> file locally.</p>
-<h1 id="jndi">Use Java Naming and Directory Interface<a class="headerlink" href="#jndi" title="Permanent link">&para;</a></h1>
+<h1 id="jndi">Use Java Naming and Directory Interface   </h1>
 <p>While Apache SIS uses Apache Derby by default, it is also possible to use another database software like HSQL or PostgreSQL.
 For using an arbitrary database, register a <code>javax.sql.DataSource</code> instance through the Java Naming and Directory Interface (JNDI).
 That registration can be done programmatically (by Java code) or by configuring XML files in some environments.
 The database must exist but can be empty, in which case it will be populated with an EPSG schema when first needed
 if the <code style="white-space:normal">org.apache.sis.non-free:​sis-epsg:​1.0</code> dependency is on the classpath
 (see <a href="#maven-epsg">above section</a>).</p>
-<h2 id="jndi-java">Registration by Java code<a class="headerlink" href="#jndi-java" title="Permanent link">&para;</a></h2>
+<h2 id="jndi-java">Registration by Java code   </h2>
 <p>Registration can be done by the following Java code, provided that a JNDI implementation is available on the classpath:</p>
-<div class="codehilite"><pre><span class="c1">// Example using PostgreSQL data source (org.postgresql.ds.PGSimpleDataSource)</span>
-<span class="n">PGSimpleDataSource</span> <span class="n">ds</span> <span class="o">=</span> <span class="k">new</span> <span class="n">PGSimpleDataSource</span><span class="o">();</span>
-<span class="n">ds</span><span class="o">.</span><span class="na">setServerName</span><span class="o">(</span><span class="s">&quot;localhost&quot;</span><span class="o">);</span>
-<span class="n">ds</span><span class="o">.</span><span class="na">setDatabaseName</span><span class="o">(</span><span class="s">&quot;SpatialMetadata&quot;</span><span class="o">);</span>
-
-<span class="c1">// Registration assuming that a JNDI implementation is available</span>
-<span class="n">Context</span> <span class="n">env</span> <span class="o">=</span> <span class="o">(</span><span class="n">Context</span><span class="o">)</span> <span class="n">InitialContext</span><span class="o">.</span><span class="na">doLookup</span><span class="o">(</span><span class="s">&quot;java:comp/env&quot;</span><span class="o">);</span>
-<span class="n">env</span><span class="o">.</span><span class="na">bind</span><span class="o">(</span><span class="s">&quot;jdbc/SpatialMetadata&quot;</span><span class="o">,</span> <span class="n">ds</span><span class="o">);</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="c1">// Example using PostgreSQL data source (org.postgresql.ds.PGSimpleDataSource)
+</span><span class="c1"></span><span class="n">PGSimpleDataSource</span> <span class="n">ds</span> <span class="o">=</span> <span class="k">new</span> <span class="n">PGSimpleDataSource</span><span class="o">();</span>
+<span class="n">ds</span><span class="o">.</span><span class="na">setServerName</span><span class="o">(</span><span class="s">&#34;localhost&#34;</span><span class="o">);</span>
+<span class="n">ds</span><span class="o">.</span><span class="na">setDatabaseName</span><span class="o">(</span><span class="s">&#34;SpatialMetadata&#34;</span><span class="o">);</span>
+
+<span class="c1">// Registration assuming that a JNDI implementation is available
+</span><span class="c1"></span><span class="n">Context</span> <span class="n">env</span> <span class="o">=</span> <span class="o">(</span><span class="n">Context</span><span class="o">)</span> <span class="n">InitialContext</span><span class="o">.</span><span class="na">doLookup</span><span class="o">(</span><span class="s">&#34;java:comp/env&#34;</span><span class="o">);</span>
+<span class="n">env</span><span class="o">.</span><span class="na">bind</span><span class="o">(</span><span class="s">&#34;jdbc/SpatialMetadata&#34;</span><span class="o">,</span> <span class="n">ds</span><span class="o">);</span></code></pre></div>
 <p>If there is no JNDI environment, the <code>org.apache.sis.setup.Configuration</code> class can be used as a fallback:</p>
-<div class="codehilite"><pre><span class="c1">// Fallback if no JNDI environment is available.</span>
-<span class="n">Configuration</span><span class="o">.</span><span class="na">current</span><span class="o">().</span><span class="na">setDatabase</span><span class="o">(()</span> <span class="o">-&gt;</span> <span class="n">ds</span><span class="o">);</span>
-</pre></div>
-
-
-<h2 id="jndi-webapp">Registration in web application containers<a class="headerlink" href="#jndi-webapp" title="Permanent link">&para;</a></h2>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="c1">// Fallback if no JNDI environment is available.
+</span><span class="c1"></span><span class="n">Configuration</span><span class="o">.</span><span class="na">current</span><span class="o">().</span><span class="na">setDatabase</span><span class="o">(()</span> <span class="o">-&gt;</span> <span class="n">ds</span><span class="o">);</span></code></pre></div>
+<h2 id="jndi-webapp">Registration in web application containers   </h2>
 <p>JNDI implementations are provided by web application containers like Apache Tomcat.
 When Apache SIS is used in a JavaEE container, the data source can be configured as below:</p>
 <ol>
 <li>
 <p>Make the JDBC driver available to the web container and its applications.
-   On Tomcat, this is accomplished by installing the driver's JAR files into the <code>$CATALINA_HOME/lib</code> directory.</p>
+On Tomcat, this is accomplished by installing the driver&rsquo;s JAR files into the <code>$CATALINA_HOME/lib</code> directory.</p>
 </li>
 <li>
 <p>If using Derby, copy <code>derby.war</code> into the <code>$CATALINA_HOME/webapps</code> directory and specify the directory where
-   the Derby databases are located (skip this step if another database is used):</p>
-<div class="codehilite"><pre><span class="nb">export </span><span class="nv">JAVA_OPTS</span><span class="o">=</span>-Dderby.system.home<span class="o">=</span><span class="nv">$SIS_DATA</span>/Databases
-</pre></div>
-
-
+the Derby databases are located (skip this step if another database is used):</p>
 </li>
-<li>
-<p>Declare the JNDI name in application <code>WEB-INF/web.xml</code> file:</p>
-<div class="codehilite"><pre><span class="nt">&lt;resource-ref&gt;</span>
+</ol>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">export</span> <span class="nv">JAVA_OPTS</span><span class="o">=</span>-Dderby.system.home<span class="o">=</span><span class="nv">$SIS_DATA</span>/Databases</code></pre></div>
+<ol start="3">
+<li>Declare the JNDI name in application <code>WEB-INF/web.xml</code> file:</li>
+</ol>
+<div class="highlight"><pre class="chroma"><code class="language-xml" data-lang="xml"><span class="nt">&lt;resource-ref&gt;</span>
   <span class="nt">&lt;description&gt;</span>EPSG dataset and other metadata used by Apache SIS.<span class="nt">&lt;/description&gt;</span>
   <span class="nt">&lt;res-ref-name&gt;</span>jdbc/SpatialMetadata<span class="nt">&lt;/res-ref-name&gt;</span>
   <span class="nt">&lt;res-type&gt;</span>javax.sql.DataSource<span class="nt">&lt;/res-type&gt;</span>
   <span class="nt">&lt;res-auth&gt;</span>Container<span class="nt">&lt;/res-auth&gt;</span>
-<span class="nt">&lt;/resource-ref&gt;</span>
-</pre></div>
-
-
-</li>
-<li>
-<p>Configure the data source in <code>$CATALINA_HOME/conf/context.xml</code> or in application <code>META-INF/context.xml</code> file
-   (change attribute values as needed for the chosen JDBC driver):</p>
-<div class="codehilite"><pre><span class="nt">&lt;Context</span> <span class="na">crossContext=</span><span class="s">&quot;true&quot;</span><span class="nt">&gt;</span>
+<span class="nt">&lt;/resource-ref&gt;</span></code></pre></div>
+<ol start="4">
+<li>Configure the data source in <code>$CATALINA_HOME/conf/context.xml</code> or in application <code>META-INF/context.xml</code> file
+(change attribute values as needed for the chosen JDBC driver):</li>
+</ol>
+<div class="highlight"><pre class="chroma"><code class="language-xml" data-lang="xml"><span class="nt">&lt;Context</span> <span class="na">crossContext=</span><span class="s">&#34;true&#34;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;WatchedResource&gt;</span>WEB-INF/web.xml<span class="nt">&lt;/WatchedResource&gt;</span>
-  <span class="nt">&lt;Resource</span> <span class="na">name            =</span> <span class="s">&quot;jdbc/SpatialMetadata&quot;</span>
-            <span class="na">auth            =</span> <span class="s">&quot;Container&quot;</span>
-            <span class="na">type            =</span> <span class="s">&quot;javax.sql.DataSource&quot;</span>
-            <span class="na">username        =</span> <span class="s">&quot;sa&quot;</span>
-            <span class="na">password        =</span> <span class="s">&quot;sa&quot;</span>
-            <span class="na">driverClassName =</span> <span class="s">&quot;org.apache.derby.jdbc.EmbeddedDriver&quot;</span>
-            <span class="na">url             =</span> <span class="s">&quot;jdbc:derby:SpatialMetadata&quot;</span><span class="nt">/&gt;</span>
-<span class="nt">&lt;/Context&gt;</span>
-</pre></div>
-
-
-</li>
-<li>
-<p>If using Derby, verify on the <code>localhost:8080/derby/derbynet</code> page (skip this step if another database is used).</p>
-</li>
+  <span class="nt">&lt;Resource</span> <span class="na">name            =</span> <span class="s">&#34;jdbc/SpatialMetadata&#34;</span>
+            <span class="na">auth            =</span> <span class="s">&#34;Container&#34;</span>
+            <span class="na">type            =</span> <span class="s">&#34;javax.sql.DataSource&#34;</span>
+            <span class="na">username        =</span> <span class="s">&#34;sa&#34;</span>
+            <span class="na">password        =</span> <span class="s">&#34;sa&#34;</span>
+            <span class="na">driverClassName =</span> <span class="s">&#34;org.apache.derby.jdbc.EmbeddedDriver&#34;</span>
+            <span class="na">url             =</span> <span class="s">&#34;jdbc:derby:SpatialMetadata&#34;</span><span class="nt">/&gt;</span>
+<span class="nt">&lt;/Context&gt;</span></code></pre></div>
+<ol start="5">
+<li>If using Derby, verify on the <code>localhost:8080/derby/derbynet</code> page (skip this step if another database is used).</li>
 </ol>
 <p>More advanced configurations are possible. For example Tomcat can invoke a custom Java method instead than
 fetching the data source from the <code>context.xml</code> file.</p>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
-    </div>
-  </footer>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+        </article>
+      </section>
+    </div>
+  </div>
+</div>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
+
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/faq.html b/faq.html
index bde9cca..8b50568 100644
--- a/faq.html
+++ b/faq.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Frequently asked questions</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
-
-    
-
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
-
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<head>
+  
+
+  <title>Apache SIS - Frequently asked questions</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
+
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,81 +37,125 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Frequently asked questions</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>This page lists some Frequently Asked Questions (FAQ) when using Apache SIS.
-This FAQ is also <a href="faq_fr.html">available in French</a>.</p>
-<div class="toc">
-<ul>
-<li><a href="#referencing">Referencing</a><ul>
-<li><a href="#referencing-intro">Getting started</a><ul>
-<li><a href="#transform-point">How do I transform a coordinate?</a></li>
-<li><a href="#operation-methods">Which map projections are supported?</a></li>
-<li><a href="#axisOrder">What is the axis order issue and how is it addressed?</a></li>
-</ul>
-</li>
-<li><a href="#crs">Coordinate Reference Systems</a><ul>
-<li><a href="#UTM">How do I instantiate a Universal Transverse Mercator (UTM) projection?</a></li>
-<li><a href="#google">How do I instantiate a Google projection?</a></li>
-<li><a href="#projectionKind">How can I identify the projection kind of a CRS?</a></li>
-<li><a href="#lookupEPSG">How do I get the EPSG code of an existing CRS?</a></li>
-<li><a href="#lookupURN">How do I get the "urn:ogc:def:crs:…" URN of an existing CRS?</a></li>
-<li><a href="#lookupReliability">Can I rely on IdentifiedObjects.lookupEPSG(…) to work correctly as the inverse of CRS.forCode(…)?</a></li>
-<li><a href="#equalsIgnoreMetadata">How can I determine if two CRS are "functionally" equal?</a></li>
-<li><a href="#crsHashCode">Are CRS objects safe for use as keys in HashMap?</a></li>
-</ul>
-</li>
-<li><a href="#transforms">Coordinate transformations</a><ul>
-<li><a href="#axisOrderInTransforms">My transformed coordinates are totally wrong!</a></li>
-<li><a href="#projectionName">I have correct axis order but my transformed coordinates are still wrong.</a></li>
-<li><a href="#parameterUnits">I just used the WKT of a well-known authority and my transformed coordinates are still wrong!</a></li>
-<li><a href="#BursaWolf">I verified all the above and still have an error of about one kilometer.</a></li>
-<li><a href="#slightDifferences">I get slightly different results depending on the environment I’m running in.</a></li>
-<li><a href="#toWGS84">Can I always expect a transform from an arbitrary CRS to WGS84 to succeed?</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li><a href="#metadata">Metadata</a><ul>
-<li><a href="#metadata-implementation">Custom implementations</a><ul>
-<li><a href="#metadata-proxy">My metadata are stored in a database-like framework. Implementing every GeoAPI interfaces for them is impractical.</a></li>
-<li><a href="#metadata-unknownClass">I can not marshall my custom implementation.</a></li>
-</ul>
-</li>
-</ul>
-</li>
-</ul>
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
 </div>
-<h1 id="referencing">Referencing<a class="headerlink" href="#referencing" title="Permanent link">&para;</a></h1>
-<h2 id="referencing-intro">Getting started<a class="headerlink" href="#referencing-intro" title="Permanent link">&para;</a></h2>
-<h3 id="transform-point">How do I transform a coordinate?<a class="headerlink" href="#transform-point" title="Permanent link">&para;</a></h3>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Frequently asked questions</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>This page lists some Frequently Asked Questions (FAQ) when using Apache SIS.
+This FAQ is also <a href="faq_fr.html">available in French</a>.</p>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#referencing">Referencing   </a>
+      <ul>
+        <li><a href="#referencing-intro">Getting started   </a>
+          <ul>
+            <li><a href="#transform-point">How do I transform a coordinate?   </a></li>
+            <li><a href="#operation-methods">Which map projections are supported?   </a></li>
+            <li><a href="#axisOrder">What is the axis order issue and how is it addressed?   </a></li>
+          </ul>
+        </li>
+        <li><a href="#crs">Coordinate Reference Systems   </a>
+          <ul>
+            <li><a href="#UTM">How do I instantiate a Universal Transverse Mercator (UTM) projection?   </a></li>
+            <li><a href="#google">How do I instantiate a Google projection?   </a></li>
+            <li><a href="#projectionKind">How can I identify the projection kind of a CRS?   </a></li>
+            <li><a href="#lookupEPSG">How do I get the EPSG code of an existing CRS?   </a></li>
+            <li><a href="#lookupURN">How do I get the &ldquo;urn:ogc:def:crs:&hellip;&rdquo; URN of an existing CRS?   </a></li>
+            <li><a href="#lookupReliability">Can I rely on IdentifiedObjects.lookupEPSG(&hellip;) to work correctly as the inverse of CRS.forCode(&hellip;)?  </a></li>
+            <li><a href="#equalsIgnoreMetadata">How can I determine if two CRS are &ldquo;functionally&rdquo; equal?   </a></li>
+            <li><a href="#crsHashCode">Are CRS objects safe for use as keys in HashMap?   </a></li>
+          </ul>
+        </li>
+        <li><a href="#transforms">Coordinate transformations   </a>
+          <ul>
+            <li><a href="#axisOrderInTransforms">My transformed coordinates are totally wrong!   </a></li>
+            <li><a href="#projectionName">I have correct axis order but my transformed coordinates are still wrong.  </a></li>
+            <li><a href="#parameterUnits">I just used the WKT of a well-known authority and my transformed coordinates are still wrong!   </a></li>
+            <li><a href="#BursaWolf">I verified all the above and still have an error of about one kilometer.   </a></li>
+            <li><a href="#slightDifferences">I get slightly different results depending on the environment I’m running in.   </a></li>
+            <li><a href="#toWGS84">Can I always expect a transform from an arbitrary CRS to WGS84 to succeed?   </a></li>
+          </ul>
+        </li>
+      </ul>
+    </li>
+    <li><a href="#metadata">Metadata   </a>
+      <ul>
+        <li><a href="#metadata-implementation">Custom implementations   </a>
+          <ul>
+            <li><a href="#metadata-proxy">My metadata are stored in a database-like framework. Implementing every GeoAPI interfaces for them is impractical.   </a></li>
+            <li><a href="#metadata-unknownClass">I can not marshall my custom implementation.   </a></li>
+          </ul>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</nav>
+<h1 id="referencing">Referencing   </h1>
+<h2 id="referencing-intro">Getting started   </h2>
+<h3 id="transform-point">How do I transform a coordinate?   </h3>
 <p>The following Java code projects a geographic coordinate from the <em>World Geodetic System 1984</em> (WGS84) to <em>WGS 84 / UTM zone 33N</em>.
 In order to make the example a little bit simpler, this code uses predefined constants given by the <code>CommonCRS</code> convenience class.
 But more advanced applications will typically use EPSG codes instead.
 Note that all geographic coordinates below express latitude <em>before</em> longitude.</p>
-<div class="codehilite"><pre><span class="kn">import</span> <span class="nn">org.opengis.geometry.DirectPosition</span><span class="o">;</span>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="kn">import</span> <span class="nn">org.opengis.geometry.DirectPosition</span><span class="o">;</span>
 <span class="kn">import</span> <span class="nn">org.opengis.referencing.crs.CoordinateReferenceSystem</span><span class="o">;</span>
 <span class="kn">import</span> <span class="nn">org.opengis.referencing.operation.CoordinateOperation</span><span class="o">;</span>
 <span class="kn">import</span> <span class="nn">org.opengis.referencing.operation.TransformException</span><span class="o">;</span>
@@ -160,72 +167,126 @@ Note that all geographic coordinates below express latitude <em>before</em> long
 <span class="kd">public</span> <span class="kd">class</span> <span class="nc">MyApp</span> <span class="o">{</span>
     <span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">main</span><span class="o">(</span><span class="n">String</span><span class="o">[]</span> <span class="n">args</span><span class="o">)</span> <span class="kd">throws</span> <span class="n">FactoryException</span><span class="o">,</span> <span class="n">TransformException</span> <span class="o">{</span>
         <span class="n">CoordinateReferenceSystem</span> <span class="n">sourceCRS</span> <span class="o">=</span> <span class="n">CommonCRS</span><span class="o">.</span><span class="na">WGS84</span><span class="o">.</span><span class="na">geographic</span><span class="o">();</span>
-        <span class="n">CoordinateReferenceSystem</span> <span class="n">targetCRS</span> <span class="o">=</span> <span class="n">CommonCRS</span><span class="o">.</span><span class="na">WGS84</span><span class="o">.</span><span class="na">universal</span><span class="o">(</span><span class="mi">40</span><span class="o">,</span> <span class="mi">14</span><span class="o">);</span>  <span class="c1">// Get whatever zone is valid for 14°E.</span>
-        <span class="n">CoordinateOperation</span> <span class="n">operation</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">findOperation</span><span class="o">(</span><span class="n">sourceCRS</span><span class="o">,</span> <span class="n">targetCRS</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span>
-
-        <span class="c1">// The above lines are costly and should be performed only once before to project many points.</span>
-        <span class="c1">// In this example, the operation that we got is valid for coordinates in geographic area from</span>
-        <span class="c1">// 12°E to 18°E (UTM zone 33) and 0°N to 84°N.</span>
-
-        <span class="n">DirectPosition</span> <span class="n">ptSrc</span> <span class="o">=</span> <span class="k">new</span> <span class="n">DirectPosition2D</span><span class="o">(</span><span class="mi">40</span><span class="o">,</span> <span class="mi">14</span><span class="o">);</span>           <span class="c1">// 40°N 14°E</span>
-        <span class="n">DirectPosition</span> <span class="n">ptDst</span> <span class="o">=</span> <span class="n">operation</span><span class="o">.</span><span class="na">getMathTransform</span><span class="o">().</span><span class="na">transform</span><span class="o">(</span><span class="n">ptSrc</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span>
-
-        <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&quot;Source: &quot;</span> <span class="o">+</span> <span class="n">ptSrc</span><span class="o">);</span>
-        <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&quot;Target: &quot;</span> <span class="o">+</span> <span class="n">ptDst</span><span class="o">);</span>
+        <span class="n">CoordinateReferenceSystem</span> <span class="n">targetCRS</span> <span class="o">=</span> <span class="n">CommonCRS</span><span class="o">.</span><span class="na">WGS84</span><span class="o">.</span><span class="na">universal</span><span class="o">(</span><span class="n">40</span><span class="o">,</span> <span class="n">14</span><span class="o">);</span>  <span class="c1">// Get whatever zone is valid for 14°E.
+</span><span class="c1"></span>        <span class="n">CoordinateOperation</span> <span class="n">operation</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">findOperation</span><span class="o">(</span><span class="n">sourceCRS</span><span class="o">,</span> <span class="n">targetCRS</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span>
+
+        <span class="c1">// The above lines are costly and should be performed only once before to project many points.
+</span><span class="c1"></span>        <span class="c1">// In this example, the operation that we got is valid for coordinates in geographic area from
+</span><span class="c1"></span>        <span class="c1">// 12°E to 18°E (UTM zone 33) and 0°N to 84°N.
+</span><span class="c1"></span>
+        <span class="n">DirectPosition</span> <span class="n">ptSrc</span> <span class="o">=</span> <span class="k">new</span> <span class="n">DirectPosition2D</span><span class="o">(</span><span class="n">40</span><span class="o">,</span> <span class="n">14</span><span class="o">);</span>           <span class="c1">// 40°N 14°E
+</span><span class="c1"></span>        <span class="n">DirectPosition</span> <span class="n">ptDst</span> <span class="o">=</span> <span class="n">operation</span><span class="o">.</span><span class="na">getMathTransform</span><span class="o">().</span><span class="na">transform</span><span class="o">(</span><span class="n">ptSrc</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span>
+
+        <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&#34;Source: &#34;</span> <span class="o">+</span> <span class="n">ptSrc</span><span class="o">);</span>
+        <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&#34;Target: &#34;</span> <span class="o">+</span> <span class="n">ptDst</span><span class="o">);</span>
     <span class="o">}</span>
-<span class="o">}</span>
-</pre></div>
-
-
-<h3 id="operation-methods">Which map projections are supported?<a class="headerlink" href="#operation-methods" title="Permanent link">&para;</a></h3>
+<span class="o">}</span></code></pre></div>
+<h3 id="operation-methods">Which map projections are supported?   </h3>
 <p>The operation <em>methods</em> (including, but not limited to, map projections) supported by Apache SIS
 are listed in the <a href="tables/CoordinateOperationMethods.html">Coordinate Operation Methods</a> page.
 The amount of map projection methods is relatively small,
-but the amount of <em>projected <abbr title="Coordinate Reference System">CRS</abbr></em> that we can build from them can be very large.
+but the amount of <em>projected 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+</em> that we can build from them can be very large.
 For example with only three family of methods (<em>Cylindrical Mercator</em>, <em>Transverse Mercator</em> and <em>Lambert Conic Conformal</em>)
-used with different parameter values, we can cover thousands of projected <abbr title="Coordinate Reference System">CRS</abbr> listed in the EPSG geodetic dataset.</p>
+used with different parameter values, we can cover thousands of projected 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ listed in the EPSG geodetic dataset.</p>
 <p>In order to use a map projection method, we need to know the value to assign to the projection parameters.
-For convenience, thousands of projected <abbr title="Coordinate Reference System">CRS</abbr> with pre-defined parameter values are are assigned a unique identifier.
+For convenience, thousands of projected 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ with pre-defined parameter values are are assigned a unique identifier.
 A well-known source of such definitions is the EPSG geodetic dataset, but other authorities also exist.
-The predefined <abbr title="Coordinate Reference System">CRS</abbr> known to Apache SIS are listed in the
+The predefined 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ known to Apache SIS are listed in the
 <a href="tables/CoordinateReferenceSystems.html">Coordinate Reference Systems</a> page.</p>
-<h3 id="axisOrder">What is the axis order issue and how is it addressed?<a class="headerlink" href="#axisOrder" title="Permanent link">&para;</a></h3>
-<p>The axis order is specified by the authority (typically a national agency) defining the Coordinate Reference System (<abbr title="Coordinate Reference System">CRS</abbr>).
-The order depends on the <abbr title="Coordinate Reference System">CRS</abbr> type and the country defining the <abbr title="Coordinate Reference System">CRS</abbr>.
-In the case of geographic <abbr title="Coordinate Reference System">CRS</abbr>, the (<em>latitude</em>, <em>longitude</em>) axis order is widely used by geographers and pilots for centuries.
-However software developers tend to consistently use the (<em>x</em>, <em>y</em>) order for every kind of <abbr title="Coordinate Reference System">CRS</abbr>.
-Those different practices resulted in contradictory definitions of axis order for almost every <abbr title="Coordinate Reference System">CRS</abbr> of kind <code>GeographicCRS</code>,
+<h3 id="axisOrder">What is the axis order issue and how is it addressed?   </h3>
+<p>The axis order is specified by the authority (typically a national agency) defining the Coordinate Reference System (
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+).
+The order depends on the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ type and the country defining the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+.
+In the case of geographic 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+, the (<em>latitude</em>, <em>longitude</em>) axis order is widely used by geographers and pilots for centuries.
+However software developers tend to consistently use the (<em>x</em>, <em>y</em>) order for every kind of 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+.
+Those different practices resulted in contradictory definitions of axis order for almost every 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ of kind <code>GeographicCRS</code>,
 for some <code>ProjectedCRS</code> in the South hemisphere (South Africa, Australia, <em>etc.</em>) and for some polar projections among others.</p>
-<p>For any <abbr title="Coordinate Reference System">CRS</abbr> identified by an EPSG code, the official axis order can be checked on the
-official EPSG registry at <a href="http://www.epsg-registry.org">http://www.epsg-registry.org</a>
-(not to be confused with other sites having "epsg" in their name,
+<p>For any 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ identified by an EPSG code, the official axis order can be checked on the
+official EPSG registry at <a href="https://epsg.org/">https://epsg.org/</a>
+(not to be confused with other sites having &ldquo;epsg&rdquo; in their name,
 but actually unrelated to the organization in charge of EPSG definitions):
-click on the <em>"Retrieve by code"</em> link and enter the numerical code.
-Then click on the <em>"View"</em> link on the right side,
-and click on the <em>"+"</em> symbol of the left side of <em>"Axes"</em>.</p>
-<p>Recent <abbr title="Open Geospatial Consortium">OGC</abbr> standards mandate the use of axis order as defined by the authority.
-Oldest <abbr title="Open Geospatial Consortium">OGC</abbr> standards used the (<em>x</em>, <em>y</em>) axis order instead, ignoring any authority specification.
-Among the legacy <abbr title="Open Geospatial Consortium">OGC</abbr> standards that used the non-conform axis order,
+click on the <em>&ldquo;Retrieve by code&rdquo;</em> link and enter the numerical code.
+Then click on the <em>&ldquo;View&rdquo;</em> link on the right side,
+and click on the <em>&quot;+&quot;</em> symbol of the left side of <em>&ldquo;Axes&rdquo;</em>.</p>
+<p>Recent 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ standards mandate the use of axis order as defined by the authority.
+Oldest 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ standards used the (<em>x</em>, <em>y</em>) axis order instead, ignoring any authority specification.
+Among the legacy 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ standards that used the non-conform axis order,
 an influent one is version 1 of the <em>Well Known Text</em> (WKT) format specification.
-According that widely-used format, WKT definitions without explicit <code>AXIS[…]</code> elements
+According that widely-used format, WKT definitions without explicit <code>AXIS[...]</code> elements
 shall default to (<em>longitude</em>, <em>latitude</em>) or (<em>x</em>, <em>y</em>) axis order.
-In version 2 of the WKT format, <code>AXIS[…]</code> elements are no longer optional
-and should contain an explicit <code>ORDER[…]</code> sub-element for making the intended order yet more obvious.</p>
+In version 2 of the WKT format, <code>AXIS[...]</code> elements are no longer optional
+and should contain an explicit <code>ORDER[...]</code> sub-element for making the intended order yet more obvious.</p>
 <p>Many software products still use the old (<em>x</em>, <em>y</em>) axis order, sometime because it is easier to implement.
 But Apache SIS rather defaults to axis order <em>as defined by the authority</em> (except when parsing a WKT 1 definition),
-but allows changing axis order to the (<em>x</em>, <em>y</em>) order after <abbr title="Coordinate Reference System">CRS</abbr> creation.
-This change can be done with the following code:</p>
-<div class="codehilite"><pre><span class="n">CoordinateReferenceSystem</span> <span class="n">crs</span> <span class="o">=</span> <span class="err">…</span><span class="o">;</span>             <span class="c1">// CRS obtained by any means.</span>
-<span class="n">crs</span> <span class="o">=</span> <span class="n">AbstractCRS</span><span class="o">.</span><span class="na">castOrCopy</span><span class="o">(</span><span class="n">crs</span><span class="o">).</span><span class="na">forConvention</span><span class="o">(</span><span class="n">AxesConvention</span><span class="o">.</span><span class="na">RIGHT_HANDED</span><span class="o">)</span>
-</pre></div>
+but allows changing axis order to the (<em>x</em>, <em>y</em>) order after 
 
 
-<h2 id="crs">Coordinate Reference Systems<a class="headerlink" href="#crs" title="Permanent link">&para;</a></h2>
-<h3 id="UTM">How do I instantiate a Universal Transverse Mercator (UTM) projection?<a class="headerlink" href="#UTM" title="Permanent link">&para;</a></h3>
-<p>If the UTM zone is unknown, an easy way is to invoke the <code>universal(…)</code> method on one of the <code>CommonCRS</code> pre-defined constants.
+<abbr title="Coordinate Reference System">CRS</abbr>
+ creation.
+This change can be done with the following code:</p>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">CoordinateReferenceSystem</span> <span class="n">crs</span> <span class="o">=</span> <span class="o">...;</span> <span class="c1">// CRS obtained by any means.
+</span><span class="c1"></span><span class="n">crs</span> <span class="o">=</span> <span class="n">AbstractCRS</span><span class="o">.</span><span class="na">castOrCopy</span><span class="o">(</span><span class="n">crs</span><span class="o">).</span><span class="na">forConvention</span><span class="o">(</span><span class="n">AxesConvention</span><span class="o">.</span><span class="na">RIGHT_HANDED</span><span class="o">)</span></code></pre></div>
+<h2 id="crs">Coordinate Reference Systems   </h2>
+<h3 id="UTM">How do I instantiate a Universal Transverse Mercator (UTM) projection?   </h3>
+<p>If the UTM zone is unknown, an easy way is to invoke the <code>universal(...)</code> method on one of the <code>CommonCRS</code> pre-defined constants.
 That method receives in argument a geographic coordinate in (<em>latitude</em>, <em>longitude</em>) order and computes the UTM zone from it.
 See the <a href="#transform-point">above Java code example</a>.</p>
-<p>If the UTM zone is know, one way is to use the "EPSG" or "AUTO" authority factory.
+<p>If the UTM zone is know, one way is to use the &ldquo;EPSG&rdquo; or &ldquo;AUTO&rdquo; authority factory.
 The EPSG code of some UTM projections can be determined as below, where <em>zone</em> is a number from 1 to 60 inclusive (unless otherwise specified):</p>
 <ul>
 <li>WGS 84 (northern hemisphere): 32600 + <em>zone</em></li>
@@ -237,234 +298,376 @@ The EPSG code of some UTM projections can be determined as below, where <em>zone
 </ul>
 <p>Note that the above list is incomplete. See the EPSG database for additional UTM definitions
 (WGS 72BE, SIRGAS 2000, SIRGAS 1995, SAD 69, ETRS 89, <em>etc.</em>, most of them defined only for a few zones).
-Once the EPSG code of the UTM projection has been determined, the <abbr title="Coordinate Reference System">CRS</abbr> can be obtained as in the example below:</p>
-<div class="codehilite"><pre><span class="kt">int</span> <span class="n">code</span> <span class="o">=</span> <span class="mi">32600</span> <span class="o">+</span> <span class="n">zone</span><span class="o">;</span>    <span class="c1">// For WGS84 northern hemisphere</span>
-<span class="n">CoordinateReferenceSystem</span> <span class="n">crs</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">forCode</span><span class="o">(</span><span class="s">&quot;EPSG:&quot;</span> <span class="o">+</span> <span class="n">code</span><span class="o">);</span>
-</pre></div>
+Once the EPSG code of the UTM projection has been determined, the 
 
 
-<h3 id="google">How do I instantiate a Google projection?<a class="headerlink" href="#google" title="Permanent link">&para;</a></h3>
+<abbr title="Coordinate Reference System">CRS</abbr>
+ can be obtained as in the example below:</p>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="kt">int</span> <span class="n">code</span> <span class="o">=</span> <span class="n">32600</span> <span class="o">+</span> <span class="n">zone</span><span class="o">;</span>    <span class="c1">// For WGS84 northern hemisphere
+</span><span class="c1"></span><span class="n">CoordinateReferenceSystem</span> <span class="n">crs</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">forCode</span><span class="o">(</span><span class="s">&#34;EPSG:&#34;</span> <span class="o">+</span> <span class="n">code</span><span class="o">);</span></code></pre></div>
+<h3 id="google">How do I instantiate a Google projection?   </h3>
 <p>The Google projection is a Mercator projection that pretends to be defined on the WGS84 datum,
 but actually ignores the ellipsoidal nature of that datum and uses the simpler spherical formulas instead.
-Since version 6.15 of EPSG geodetic dataset, the preferred way to get that projection is to invoke <code>CRS.forCode("EPSG:3857")</code>.
+Since version 6.15 of EPSG geodetic dataset, the preferred way to get that projection is to invoke <code>CRS.forCode(&quot;EPSG:3857&quot;)</code>.
 Note that the use of that projection is <strong>not</strong> recommended, unless needed for compatibility with other data.</p>
-<p>The EPSG:3857 definition uses a map projection method named <em>"Popular Visualisation Pseudo Mercator"</em>.
+<p>The EPSG:3857 definition uses a map projection method named <em>&ldquo;Popular Visualisation Pseudo Mercator&rdquo;</em>.
 The EPSG geodetic dataset provides also some other map projections that use spherical formulas.
-Those methods have "(Spherical)" in their name, for example <em>"Mercator (Spherical)"</em>
-(which differs from <em>"Popular Visualisation Pseudo Mercator"</em> by the use of a more appropriate sphere radius).
+Those methods have &ldquo;(Spherical)&rdquo; in their name, for example <em>&ldquo;Mercator (Spherical)&quot;</em>
+(which differs from <em>&ldquo;Popular Visualisation Pseudo Mercator&rdquo;</em> by the use of a more appropriate sphere radius).
 Those projection methods can be used in Well Known Text (WKT) definitions.</p>
-<p>If there is a need to use spherical formulas with a projection that does not have a "(Spherical)" counterpart,
-this can be done with explicit declarations of <code>"semi_major"</code> and <code>"semi_minor"</code> parameter values in the WKT definition.
+<p>If there is a need to use spherical formulas with a projection that does not have a &ldquo;(Spherical)&rdquo; counterpart,
+this can be done with explicit declarations of <code>&quot;semi_major&quot;</code> and <code>&quot;semi_minor&quot;</code> parameter values in the WKT definition.
 Those parameter values are usually inferred from the datum, but Apache SIS allows explicit declarations to override the inferred values.</p>
-<h3 id="projectionKind">How can I identify the projection kind of a <abbr title="Coordinate Reference System">CRS</abbr>?<a class="headerlink" href="#projectionKind" title="Permanent link">&para;</a></h3>
-<p>The "kind of projection" (Mercator, Lambert Conformal, <em>etc.</em>) is called <em>Operation Method</em> in <abbr title="International Organization for Standardization">ISO</abbr> 19111 terminology.
-One approach is to check the value of <code>OperationMethod.getName()</code> and compare them against the <abbr title="Open Geospatial Consortium">OGC</abbr> or EPSG names
+<h3 id="projectionKind">How can I identify the projection kind of a CRS?   </h3>
+<p>The &ldquo;kind of projection&rdquo; (Mercator, Lambert Conformal, <em>etc.</em>) is called <em>Operation Method</em> in 
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+ 19111 terminology.
+One approach is to check the value of <code>OperationMethod.getName()</code> and compare them against the 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ or EPSG names
 listed in the <a href="tables/CoordinateOperationMethods.html">Coordinate Operation Methods</a> page.</p>
-<h3 id="lookupEPSG">How do I get the EPSG code of an existing <abbr title="Coordinate Reference System">CRS</abbr>?<a class="headerlink" href="#lookupEPSG" title="Permanent link">&para;</a></h3>
-<p>The <em>identifier</em> of a Coordinate Reference System (<abbr title="Coordinate Reference System">CRS</abbr>) object can be obtained by the <code>getIdentifiers()</code> method,
+<h3 id="lookupEPSG">How do I get the EPSG code of an existing CRS?   </h3>
+<p>The <em>identifier</em> of a Coordinate Reference System (CRS) object can be obtained by the <code>getIdentifiers()</code> method,
 which usually return a collection of zero or one element.
-If the <abbr title="Coordinate Reference System">CRS</abbr> has been created from a Well Known Text (WKT) parsing
-and the WKT ends with an <code>AUTHORITY["EPSG", "xxxx"]</code> (WKT version 1) or <code>ID["EPSG", xxxx]</code> (WKT version 2) element,
+If the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ has been created from a Well Known Text (WKT) parsing
+and the WKT ends with an <code>AUTHORITY[&quot;EPSG&quot;, &quot;xxxx&quot;]</code> (WKT version 1) or <code>ID[&quot;EPSG&quot;, xxxx]</code> (WKT version 2) element,
 then the identifier (an EPSG numerical code in this example) is the <em>xxxx</em> value in that element.
-If the <abbr title="Coordinate Reference System">CRS</abbr> has been created from the EPSG geodetic dataset (for example by a call to <code>CRS.forCode("EPSG:xxxx")</code>),
+If the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ has been created from the EPSG geodetic dataset (for example by a call to <code>CRS.forCode(&quot;EPSG:xxxx&quot;)</code>),
 then the identifier is the <em>xxxx</em> code given to that method.
-If the <abbr title="Coordinate Reference System">CRS</abbr> has been created in another way, then the collection returned by the <code>getIdentifiers()</code> method
-may or may not be empty depending if the program that created the <abbr title="Coordinate Reference System">CRS</abbr> took the responsibility of providing identifiers.</p>
+If the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ has been created in another way, then the collection returned by the <code>getIdentifiers()</code> method
+may or may not be empty depending if the program that created the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ took the responsibility of providing identifiers.</p>
 <p>If the collection of identifiers is empty, the most effective fix is to make sure that the WKT
-contains an <code>AUTHORITY</code> or <code>ID</code> element (assuming that the <abbr title="Coordinate Reference System">CRS</abbr> was parsed from a WKT).
+contains an <code>AUTHORITY</code> or <code>ID</code> element (assuming that the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ was parsed from a WKT).
 If this is not possible, then the <code>org.​apache.​sis.​referencing.​IdentifiedObjects</code> class contains some convenience methods which may help.
-In the following example, the call to <code>lookupEPSG(…)</code> will scan the EPSG database for a <abbr title="Coordinate Reference System">CRS</abbr> equals
+In the following example, the call to <code>lookupEPSG(...)</code> will scan the EPSG database for a 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ equals
 (ignoring metadata) to the given one. <em>Note that this scan is sensitive to axis order.</em>
-Most geographic <abbr title="Coordinate Reference System">CRS</abbr> in the EPSG database are declared with (<em>latitude</em>, <em>longitude</em>) axis order.
-Consequently if the given <abbr title="Coordinate Reference System">CRS</abbr> has (<em>longitude</em>, <em>latitude</em>) axis order, then the scan is likely to find no match.</p>
-<div class="codehilite"><pre><span class="n">CoordinateReferenceSystem</span> <span class="n">myCRS</span> <span class="o">=</span> <span class="err">…</span><span class="o">;</span>
+Most geographic 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ in the EPSG database are declared with (<em>latitude</em>, <em>longitude</em>) axis order.
+Consequently if the given 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ has (<em>longitude</em>, <em>latitude</em>) axis order, then the scan is likely to find no match.</p>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">CoordinateReferenceSystem</span> <span class="n">myCRS</span> <span class="o">=</span> <span class="o">...;</span>
 <span class="n">Integer</span> <span class="n">identifier</span> <span class="o">=</span> <span class="n">IdentifiedObjects</span><span class="o">.</span><span class="na">lookupEPSG</span><span class="o">(</span><span class="n">myCRS</span><span class="o">);</span>
 <span class="k">if</span> <span class="o">(</span><span class="n">identifier</span> <span class="o">!=</span> <span class="kc">null</span><span class="o">)</span> <span class="o">{</span>
-    <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&quot;The EPSG code has been found: &quot;</span> <span class="o">+</span> <span class="n">identifier</span><span class="o">);</span>
-<span class="o">}</span>
-</pre></div>
+    <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&#34;The EPSG code has been found: &#34;</span> <span class="o">+</span> <span class="n">identifier</span><span class="o">);</span>
+<span class="o">}</span></code></pre></div>
+<h3 id="lookupURN">How do I get the &ldquo;urn:ogc:def:crs:&hellip;&rdquo; URN of an existing CRS?   </h3>
+<p>
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ defines URN for 
 
 
-<h3 id="lookupURN">How do I get the "urn:ogc:def:crs:…" URN of an existing <abbr title="Coordinate Reference System">CRS</abbr>?<a class="headerlink" href="#lookupURN" title="Permanent link">&para;</a></h3>
-<p><abbr title="Open Geospatial Consortium">OGC</abbr> defines URN for <abbr title="Coordinate Reference System">CRS</abbr> identifiers, for example <code>"urn:​ogc:​def:​crs:​epsg:​7.1:​4326"</code>
-where <code>"7.1"</code> is the version of the EPSG database used.
+<abbr title="Coordinate Reference System">CRS</abbr>
+ identifiers, for example <code>&quot;urn:​ogc:​def:​crs:​epsg:​7.1:​4326&quot;</code>
+where <code>&quot;7.1&quot;</code> is the version of the EPSG database used.
 URN may or may not be present in the set of identifiers returned by <code>crs.getIdentifiers()</code>.
-In many cases (especially if the <abbr title="Coordinate Reference System">CRS</abbr> was parsed from a Well Known Text), only simple identifiers like <code>"EPSG:​4326"</code> are provided.
+In many cases (especially if the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ was parsed from a Well Known Text), only simple identifiers like <code>&quot;EPSG:​4326&quot;</code> are provided.
 An easy way to build the full URN is to use the code below.
-That example may scan the EPSG database for finding the information if it was not explicitely provided in the given <abbr title="Coordinate Reference System">CRS</abbr>.</p>
-<div class="codehilite"><pre><span class="n">CoordinateReferenceSystem</span> <span class="n">myCRS</span> <span class="o">=</span> <span class="err">…</span><span class="o">;</span>
-<span class="n">String</span> <span class="n">urn</span> <span class="o">=</span> <span class="n">IdentifiedObjects</span><span class="o">.</span><span class="na">lookupURN</span><span class="o">(</span><span class="n">myCRS</span><span class="o">);</span>
-</pre></div>
-
-
-<h3 id="lookupReliability">Can I rely on IdentifiedObjects.lookupEPSG(…) to work correctly as the inverse of <abbr title="Coordinate Reference System">CRS</abbr>.forCode(…)?<a class="headerlink" href="#lookupReliability" title="Permanent link">&para;</a></h3>
-<p>For <abbr title="Coordinate Reference System">CRS</abbr> created from the EPSG geodetic dataset, usually yes.
-Note however that <code>IdentifiedObjects.getIdentifier(…)</code> is cheaper and insensitive to the details of <abbr title="Coordinate Reference System">CRS</abbr> definition,
-since it never query the database. But it works only if the <abbr title="Coordinate Reference System">CRS</abbr> declares explicitly its code,
-which is the case for <abbr title="Coordinate Reference System">CRS</abbr> created from the EPSG database or parsed from a Well Known Text (WKT) having an <code>AUTHORITY</code> or <code>ID</code> element.
-The <code>lookupEPSG(…)</code> method on the other hand is robust to erroneous code declaration,
-since it always compares the <abbr title="Coordinate Reference System">CRS</abbr> with the database content.
+That example may scan the EPSG database for finding the information if it was not explicitely provided in the given 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+.</p>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">CoordinateReferenceSystem</span> <span class="n">myCRS</span> <span class="o">=</span> <span class="o">...;</span>
+<span class="n">String</span> <span class="n">urn</span> <span class="o">=</span> <span class="n">IdentifiedObjects</span><span class="o">.</span><span class="na">lookupURN</span><span class="o">(</span><span class="n">myCRS</span><span class="o">);</span></code></pre></div>
+<h3 id="lookupReliability">Can I rely on IdentifiedObjects.lookupEPSG(&hellip;) to work correctly as the inverse of CRS.forCode(&hellip;)?  </h3>
+<p>For 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ created from the EPSG geodetic dataset, usually yes.
+Note however that <code>IdentifiedObjects.getIdentifier(...)</code> is cheaper and insensitive to the details of 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ definition,
+since it never query the database. But it works only if the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ declares explicitly its code,
+which is the case for 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ created from the EPSG database or parsed from a Well Known Text (WKT) having an <code>AUTHORITY</code> or <code>ID</code> element.
+The <code>lookupEPSG(...)</code> method on the other hand is robust to erroneous code declaration,
+since it always compares the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ with the database content.
 But it may fail if there is slight mismatch (for example rounding errors in projection parameters)
-between the supplied <abbr title="Coordinate Reference System">CRS</abbr> and the <abbr title="Coordinate Reference System">CRS</abbr> found in the database.</p>
-<h3 id="equalsIgnoreMetadata">How can I determine if two <abbr title="Coordinate Reference System">CRS</abbr> are "functionally" equal?<a class="headerlink" href="#equalsIgnoreMetadata" title="Permanent link">&para;</a></h3>
+between the supplied 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ and the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ found in the database.</p>
+<h3 id="equalsIgnoreMetadata">How can I determine if two CRS are &ldquo;functionally&rdquo; equal?   </h3>
 <p>Two Coordinate Reference Systems may not be considered equal if they are associated to different metadata
-(name, identifiers, scope, domain of validity, remarks), even though they represent the same logical <abbr title="Coordinate Reference System">CRS</abbr>.
-In order to test if two <abbr title="Coordinate Reference System">CRS</abbr> are functionally equivalent, use <code>Utilities​.equalsIgnoreMetadata(myFirstCRS, mySecondCRS)</code>.</p>
-<h3 id="crsHashCode">Are <abbr title="Coordinate Reference System">CRS</abbr> objects safe for use as keys in HashMap?<a class="headerlink" href="#crsHashCode" title="Permanent link">&para;</a></h3>
+(name, identifiers, scope, domain of validity, remarks), even though they represent the same logical 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+.
+In order to test if two 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ are functionally equivalent, use <code>Utilities​.equalsIgnoreMetadata(myFirstCRS, mySecondCRS)</code>.</p>
+<h3 id="crsHashCode">Are CRS objects safe for use as keys in HashMap?   </h3>
 <p>Yes, every classes defined in the <code>org.apache.sis.referencing.crs</code>, <code>cs</code> and <code>datum</code> packages
 define properly their <code>equals(Object)</code> and <code>hashCode()</code> methods.
-The Apache SIS library itself uses <abbr title="Coordinate Reference System">CRS</abbr> objects in <code>HashMap</code>-like containers for caching purpose.</p>
-<h2 id="transforms">Coordinate transformations<a class="headerlink" href="#transforms" title="Permanent link">&para;</a></h2>
-<h3 id="axisOrderInTransforms">My transformed coordinates are totally wrong!<a class="headerlink" href="#axisOrderInTransforms" title="Permanent link">&para;</a></h3>
+The Apache SIS library itself uses 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ objects in <code>HashMap</code>-like containers for caching purpose.</p>
+<h2 id="transforms">Coordinate transformations   </h2>
+<h3 id="axisOrderInTransforms">My transformed coordinates are totally wrong!   </h3>
 <p>This is most frequently caused by ordinate values given in the wrong order.
 Developers tend to assume a (<em>x</em>, <em>y</em>) or (<em>longitude</em>, <em>latitude</em>) axis order.
 But geographers and pilots are using (<em>latitude</em>, <em>longitude</em>) axis order for centuries,
 and the EPSG geodetic dataset defines geographic Coordinate Reference Systems that way.
 If a coordinate transformation seems to produce totally wrong values,
 the first thing to do should be to print the source and target Coordinate Reference Systems:</p>
-<div class="codehilite"><pre><span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="n">sourceCRS</span><span class="o">);</span>
-<span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="n">targetCRS</span><span class="o">);</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="n">sourceCRS</span><span class="o">);</span>
+<span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="n">targetCRS</span><span class="o">);</span></code></pre></div>
 <p>Attention should be paid to the order of <code>AXIS</code> elements.
 In the example below, the Coordinate Reference System clearly uses (<em>latitude</em>, <em>longitude</em>) axis order:</p>
-<div class="codehilite"><pre>GeodeticCRS[&quot;WGS 84&quot;,
-  Datum[&quot;World Geodetic System 1984&quot;,
-    Ellipsoid[&quot;WGS 84&quot;, 6378137.0, 298.257223563]],
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">GeodeticCRS[&#34;WGS 84&#34;,
+  Datum[&#34;World Geodetic System 1984&#34;,
+    Ellipsoid[&#34;WGS 84&#34;, 6378137.0, 298.257223563]],
   CS[ellipsoidal, 2],
-    Axis[&quot;Geodetic latitude (Lat)&quot;, north],
-    Axis[&quot;Geodetic longitude (Lon)&quot;, east],
-    Unit[&quot;degree&quot;, 0.017453292519943295]]
-</pre></div>
-
-
+    Axis[&#34;Geodetic latitude (Lat)&#34;, north],
+    Axis[&#34;Geodetic longitude (Lon)&#34;, east],
+    Unit[&#34;degree&#34;, 0.017453292519943295]]</code></pre></div>
 <p>If (<em>longitude</em>, <em>latitude</em>) axis order is really wanted, Apache SIS can be forced to that order <a href="#axisOrder">as described above</a>.</p>
-<h3 id="projectionName">I have correct axis order but my transformed coordinates are still wrong.<a class="headerlink" href="#projectionName" title="Permanent link">&para;</a></h3>
+<h3 id="projectionName">I have correct axis order but my transformed coordinates are still wrong.  </h3>
 <p>Make sure that the right projection is used. Some projection names are confusing.
-For example <em>"Oblique Mercator"</em> and <em>"Hotine Oblique Mercator"</em> (in EPSG naming) are two different projections.
-But <em>"Oblique Mercator"</em> (not Hotine) in EPSG naming is also called <em>"Hotine Oblique Mercator Azimuth Center"</em> by ESRI,
-while <em>"Hotine Oblique Mercator"</em> (EPSG naming) is called <em>"Hotine Oblique Mercator Azimuth Natural Origin"</em> by ESRI.</p>
-<p>The <em>"Oblique Stereographic"</em> projection (EPSG name) is called <em>"Double Stereographic"</em> by ESRI.
-ESRI also defines a <em>"Stereographic"</em> projection, which is actually an oblique projection like the former but using different formulas.</p>
-<h3 id="parameterUnits">I just used the WKT of a well-known authority and my transformed coordinates are still wrong!<a class="headerlink" href="#parameterUnits" title="Permanent link">&para;</a></h3>
+For example <em>&ldquo;Oblique Mercator&rdquo;</em> and <em>&ldquo;Hotine Oblique Mercator&rdquo;</em> (in EPSG naming) are two different projections.
+But <em>&ldquo;Oblique Mercator&rdquo;</em> (not Hotine) in EPSG naming is also called <em>&ldquo;Hotine Oblique Mercator Azimuth Center&rdquo;</em> by ESRI,
+while <em>&ldquo;Hotine Oblique Mercator&rdquo;</em> (EPSG naming) is called <em>&ldquo;Hotine Oblique Mercator Azimuth Natural Origin&rdquo;</em> by ESRI.</p>
+<p>The <em>&ldquo;Oblique Stereographic&rdquo;</em> projection (EPSG name) is called <em>&ldquo;Double Stereographic&rdquo;</em> by ESRI.
+ESRI also defines a <em>&ldquo;Stereographic&rdquo;</em> projection, which is actually an oblique projection like the former but using different formulas.</p>
+<h3 id="parameterUnits">I just used the WKT of a well-known authority and my transformed coordinates are still wrong!   </h3>
 <p>The Well Known Text (WKT) specification has been interpreted in different ways by different implementors.
 One subtle issue is the angular units of prime meridian and projection parameter values.
-The WKT 1 specification clary states: <em>"If the <code>PRIMEM</code> clause occurs inside a <code>GEOGCS</code>,
-then the longitude units will match those of the geographic coordinate system"</em> (source: <abbr title="Open Geospatial Consortium">OGC</abbr> 01-009).
-However ESRI and GDAL among others unconditionally use decimal degrees, ignoring this part of the WKT specification.
-This problem can be identified by WKT inspection as in the following extract:</p>
-<div class="codehilite"><pre>PROJCS[&quot;Lambert II étendu&quot;,
-  GEOGCS[&quot;Nouvelle Triangulation Française&quot;, …,
-    PRIMEM[&quot;Paris&quot;, 2.337229167],
-    UNIT[&quot;grad&quot;, 0.01570796326794897]]
-  PROJECTION[&quot;Lambert_Conformal_Conic_1SP&quot;],
-  PARAMETER[&quot;latitude_of_origin&quot;, 46.8], …]
-</pre></div>
+The WKT 1 specification clary states: <em>&ldquo;If the <code>PRIMEM</code> clause occurs inside a <code>GEOGCS</code>,
+then the longitude units will match those of the geographic coordinate system&rdquo;</em> (source: 
 
 
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ 01-009).
+However ESRI and GDAL among others unconditionally use decimal degrees, ignoring this part of the WKT specification.
+This problem can be identified by WKT inspection as in the following extract:</p>
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">PROJCS[&#34;Lambert II étendu&#34;,
+  GEOGCS[&#34;Nouvelle Triangulation Française&#34;, ...,
+    PRIMEM[&#34;Paris&#34;, 2.337229167],
+    UNIT[&#34;grad&#34;, 0.01570796326794897]]
+  PROJECTION[&#34;Lambert_Conformal_Conic_1SP&#34;],
+  PARAMETER[&#34;latitude_of_origin&#34;, 46.8], ...]</code></pre></div>
 <p>The Paris prime meridian is located at approximatively 2.597 gradians from Greenwich, which is 2.337 degrees.
-From this fact, we can see that the above WKT uses decimal degrees despite its <code>UNIT["grad"]</code> declaration.
+From this fact, we can see that the above WKT uses decimal degrees despite its <code>UNIT[&quot;grad&quot;]</code> declaration.
 This mismatch applies also to the parameter value, which declare 46.8° in the above example while the official value is 52 gradians.
 By default, Apache SIS interprets those angular values as gradians when parsing such WKT, resulting in a large error.
 In order to get the intended result, there is a choice:</p>
 <ul>
 <li>
-<p>Replace <code>UNIT["grad", 0.01570796326794897]</code> by <code>UNIT["degree", 0.017453292519943295]</code>,
-    which ensure that Apache SIS, GDAL and ESRI understand that WKT in the same way.</p>
+<p>Replace <code>UNIT[&quot;grad&quot;, 0.01570796326794897]</code> by <code>UNIT[&quot;degree&quot;, 0.017453292519943295]</code>,
+which ensure that Apache SIS, GDAL and ESRI understand that WKT in the same way.</p>
 </li>
 <li>
 <p>Or ask explicitely Apache SIS to parse the WKT using the ESRI or GDAL conventions, by specifying the
-    <code>Convention.​WKT1_COMMON_UNITS</code> enumeration value to <code>WKTFormat</code> in the <code>org.​apache.​sis.​io.​wkt</code> package.</p>
+<code>Convention.​WKT1_COMMON_UNITS</code> enumeration value to <code>WKTFormat</code> in the <code>org.​apache.​sis.​io.​wkt</code> package.</p>
 </li>
 </ul>
-<p>Note that the GeoPackage standard explicitely requires <abbr title="Open Geospatial Consortium">OGC</abbr> 01-009 compliant WKT
-and the new WKT 2 standard also follows the <abbr title="Open Geospatial Consortium">OGC</abbr> 01-009 interpretation.
+<p>Note that the GeoPackage standard explicitely requires 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ 01-009 compliant WKT
+and the new WKT 2 standard also follows the 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ 01-009 interpretation.
 The default Apache SIS behavior is consistent with those two standards.</p>
-<h3 id="BursaWolf">I verified all the above and still have an error of about one kilometer.<a class="headerlink" href="#BursaWolf" title="Permanent link">&para;</a></h3>
-<p>Coordinate Reference Systems (<abbr title="Coordinate Reference System">CRS</abbr>) approximate the Earth’s shape by an ellipsoid.
+<h3 id="BursaWolf">I verified all the above and still have an error of about one kilometer.   </h3>
+<p>Coordinate Reference Systems (CRS) approximate the Earth’s shape by an ellipsoid.
 Different ellipsoids (actually different <em>datum</em>) are used in different countries of the world and at different time in history.
-When transforming coordinates between two <abbr title="Coordinate Reference System">CRS</abbr> using the same datum, no Bursa-Wolf parameters are needed.
+When transforming coordinates between two 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ using the same datum, no Bursa-Wolf parameters are needed.
 But when the transformation involves a change of datum, the referencing module needs some information about how to perform that datum shift.</p>
 <p>There is many way to specify how to perform a datum shift, and most of them are only approximation.
 The Bursa-Wolf method is one of them, not the only one. However it is one of the most frequently used methods.
 The Bursa-Wolf parameters can be specified inside a <code>TOWGS84</code> element with version 1 of Well Known Text (WKT) format,
 or in a <code>BOUNDCRS</code> element with version 2 of WKT format.
-If the <abbr title="Coordinate Reference System">CRS</abbr> are parsed from a WKT string, make sure that the string contains the appropriate element.</p>
-<h3 id="slightDifferences">I get slightly different results depending on the environment I’m running in.<a class="headerlink" href="#slightDifferences" title="Permanent link">&para;</a></h3>
+If the CRS are parsed from a WKT string, make sure that the string contains the appropriate element.</p>
+<h3 id="slightDifferences">I get slightly different results depending on the environment I’m running in.   </h3>
 <p>The results of coordinate transformations when running in a web application container (JBoss, <em>etc.</em>)
 may be a few meters off compared to coordinates transformations in an IDE (NetBeans, Eclipse, <em>etc.</em>).
-The results depend on whether an EPSG factory is available on the classpath, <strong>regardless how the <abbr title="Coordinate Reference System">CRS</abbr> were created</strong>,
-because the EPSG factory specifies explicitly the coordinate operation to apply for some pairs of <abbr title="Coordinate Reference System">CRS</abbr>.
+The results depend on whether an EPSG factory is available on the classpath, <strong>regardless how the 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ were created</strong>,
+because the EPSG factory specifies explicitly the coordinate operation to apply for some pairs of 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+.
 In such case, the coordinate operation specified by EPSG has precedence over the Burwa-Wolf parameters
 (the <code>TOWGS84</code> element in version 1 of Well Known Text format).</p>
 <p>A connection to the EPSG database may have been established for one environment
-(typically the JEE one) and not the other (typically the IDE one) because only the former has <abbr title="Java DataBase Connectivity">JDBC</abbr> driver.
+(typically the JEE one) and not the other (typically the IDE one) because only the former has 
+
+
+<abbr title="Java DataBase Connectivity">JDBC</abbr>
+ driver.
 The recommended way to uniformize the results is to add in the second environment (IDE)
-the same <abbr title="Java DataBase Connectivity">JDBC</abbr> driver than the one available in the first environment (JEE).
+the same 
+
+
+<abbr title="Java DataBase Connectivity">JDBC</abbr>
+ driver than the one available in the first environment (JEE).
 It should be one of the following: JavaDB (a.k.a. Derby), HSQL or PostgreSQL.
 Make sure that the <a href="epsg.html">connection parameters to the EPSG database</a> are also the same.</p>
-<h3 id="toWGS84">Can I always expect a transform from an arbitrary <abbr title="Coordinate Reference System">CRS</abbr> to WGS84 to succeed?<a class="headerlink" href="#toWGS84" title="Permanent link">&para;</a></h3>
-<p>For 2D horizontal <abbr title="Coordinate Reference System">CRS</abbr> created from the EPSG database, calls to <code>CRS.findOperation(…)</code> should generally succeed.
-For 3D <abbr title="Coordinate Reference System">CRS</abbr> having any kind of height different than ellipsoidal height, or for a 2D <abbr title="Coordinate Reference System">CRS</abbr> of type <code>EngineeringCRS</code>, it may fail.
-Note however that even if the call to <code>CRS.findOperation(…)</code> succeed, the call to <code>MathTransform.transform(…)</code> may fail
+<h3 id="toWGS84">Can I always expect a transform from an arbitrary CRS to WGS84 to succeed?   </h3>
+<p>For 2D horizontal 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ created from the EPSG database, calls to <code>CRS.findOperation(...)</code> should generally succeed.
+For 3D 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ having any kind of height different than ellipsoidal height, or for a 2D 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ of type <code>EngineeringCRS</code>, it may fail.
+Note however that even if the call to <code>CRS.findOperation(...)</code> succeed, the call to <code>MathTransform.transform(...)</code> may fail
 or produce <code>NaN</code> or infinity values if the coordinate to transform is far from the domain of validity.</p>
-<h1 id="metadata">Metadata<a class="headerlink" href="#metadata" title="Permanent link">&para;</a></h1>
-<h2 id="metadata-implementation">Custom implementations<a class="headerlink" href="#metadata-implementation" title="Permanent link">&para;</a></h2>
-<h3 id="metadata-proxy">My metadata are stored in a database-like framework. Implementing every GeoAPI interfaces for them is impractical.<a class="headerlink" href="#metadata-proxy" title="Permanent link">&para;</a></h3>
+<h1 id="metadata">Metadata   </h1>
+<h2 id="metadata-implementation">Custom implementations   </h2>
+<h3 id="metadata-proxy">My metadata are stored in a database-like framework. Implementing every GeoAPI interfaces for them is impractical.   </h3>
 <p>Developers do not need to implement directly the metadata interfaces.
 If the underlying storage framework can access metadata from their class and attribute names (either Java names
-or <abbr title="International Organization for Standardization">ISO</abbr>/<abbr title="Open Geospatial Consortium">OGC</abbr> names), then it is possible to implement a single engine accessing any kind of metadata and let the
+or 
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+/
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ names), then it is possible to implement a single engine accessing any kind of metadata and let the
 Java Virtual Machine implements the GeoAPI interfaces on-the-fly, using the <code>java.lang.reflect.Proxy</code> class.
-See the <code>Proxy</code> Javadoc for details, keeping in mind that the <abbr title="International Organization for Standardization">ISO</abbr>/<abbr title="Open Geospatial Consortium">OGC</abbr> name of a <code>java.lang.Class</code> or
+See the <code>Proxy</code> Javadoc for details, keeping in mind that the 
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+/
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ name of a <code>java.lang.Class</code> or
 <code>java.lang.reflect.Method</code> object can be obtained as below:</p>
-<div class="codehilite"><pre><span class="n">UML</span> <span class="n">uml</span> <span class="o">=</span> <span class="n">method</span><span class="o">.</span><span class="na">getAnnotation</span><span class="o">(</span><span class="n">UML</span><span class="o">.</span><span class="na">class</span><span class="o">);</span>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">UML</span> <span class="n">uml</span> <span class="o">=</span> <span class="n">method</span><span class="o">.</span><span class="na">getAnnotation</span><span class="o">(</span><span class="n">UML</span><span class="o">.</span><span class="na">class</span><span class="o">);</span>
 <span class="k">if</span> <span class="o">(</span><span class="n">uml</span> <span class="o">!=</span> <span class="kc">null</span><span class="o">)</span> <span class="o">{</span>
     <span class="n">String</span> <span class="n">name</span> <span class="o">=</span> <span class="n">uml</span><span class="o">.</span><span class="na">identifier</span><span class="o">();</span>
-    <span class="c1">// Fetch the metadata here.</span>
-<span class="o">}</span>
-</pre></div>
-
-
+    <span class="c1">// Fetch the metadata here.
+</span><span class="c1"></span><span class="o">}</span></code></pre></div>
 <p>This is indeed the approach taken by the <code>org.apache.sis.metadata.sql</code> package for providing an implementation
 of all GeoAPI metadata interfaces reading their values directly from a SQL database.</p>
-<h3 id="metadata-unknownClass">I can not marshall my custom implementation.<a class="headerlink" href="#metadata-unknownClass" title="Permanent link">&para;</a></h3>
+<h3 id="metadata-unknownClass">I can not marshall my custom implementation.   </h3>
 <p>The classes given to the JAXB marshaller shall contain JAXB annotations,
 otherwise the following exception is thrown:</p>
-<div class="codehilite"><pre>javax.xml.bind.JAXBException: class MyCustomClass nor any of its super class is known to this context.
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">javax.xml.bind.JAXBException: class MyCustomClass nor any of its super class is known to this context.</code></pre></div>
 <p>The easiest workaround is to wrap the custom implementation into one of the implementations
 provided in the <code>org.apache.metadata.iso</code> package.
 All those SIS implementation classes provide shallow copy constructor for making that easy.
 Note that you need to wrap only the root class, not the attributes.
 The attribute values will be wrapped automatically as needed by JAXB adapters.</p>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
+
+        </article>
+      </section>
     </div>
-  </footer>
-
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
-
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+  </div>
+</div>
+
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
+
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/faq_fr.html b/faq_fr.html
index d7f741a..783095a 100644
--- a/faq_fr.html
+++ b/faq_fr.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Questions fréquentes (FAQ)</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
-
-    
-
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
-
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<head>
+  
+
+  <title>Apache SIS - Questions fréquentes (FAQ)</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
+
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,81 +37,125 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Questions fréquentes (FAQ)</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>Cette page liste quelques questions fréquemment posées à propos de Apache SIS.
-Son contenu est traduit de la <a href="faq.html">page de FAQ en anglais</a>.</p>
-<div class="toc">
-<ul>
-<li><a href="#referencing">Géoréférencement</a><ul>
-<li><a href="#referencing-intro">Pour bien commencer</a><ul>
-<li><a href="#transform-point">Comment transformer une coordonnée ?</a></li>
-<li><a href="#operation-methods">Quelles projections sont supportées ?</a></li>
-<li><a href="#axisOrder">Qu’est ce que le problème d’ordre des axes et comment est il abordé ?</a></li>
-</ul>
-</li>
-<li><a href="#crs">Systèmes de Référence des Coordonnées</a><ul>
-<li><a href="#UTM">Comment créer une projection de type Transverse Universelle de Mercator (UTM) ?</a></li>
-<li><a href="#google">Comment instancier une projection Google ?</a></li>
-<li><a href="#projectionKind">Comment puis-je identifier le type de projection d’un CRS ?</a></li>
-<li><a href="#lookupEPSG">Comment obtenir le code EPSG d’un CRS existant ?</a></li>
-<li><a href="#lookupURN">Comment obtenir l’URN « urn:ogc:def:crs:… » d’un CRS existant ?</a></li>
-<li><a href="#lookupReliability">Puis-je m’appuyer sur IdentifiedObjects.lookupEPSG(…) comme inverse de CRS.forCode(…) ?</a></li>
-<li><a href="#equalsIgnoreMetadata">Comment déterminer si deux CRS sont « fonctionnellement » égaux ?</a></li>
-<li><a href="#crsHashCode">Est-ce que les CRS sont utilisables comme clé dans un HashMap ?</a></li>
-</ul>
-</li>
-<li><a href="#transforms">Transformation de coordonnées</a><ul>
-<li><a href="#axisOrderInTransforms">Mes coordonnées transformées sont totalement fausses !</a></li>
-<li><a href="#projectionName">Les ordres des axes sont corrects mais les coordonnées transformées sont encore fausses.</a></li>
-<li><a href="#parameterUnits">J’ai juste utilisé le WKT d’une autorité connue et mes coordonnées transformées sont toujours fausses !</a></li>
-<li><a href="#BursaWolf">J’ai vérifié tous ce qui est ci-dessus et j’ai toujours une erreur d’environ un kilomètre.</a></li>
-<li><a href="#slightDifferences">J’obtiens des résultats légèrement différents d’un environnement d’exécution à l’autre.</a></li>
-<li><a href="#toWGS84">Puis-je présumer qu’il est toujours possible de transformer un CRS arbitraire vers WGS84 ?</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li><a href="#metadata">Métadonnées</a><ul>
-<li><a href="#metadata-implementation">Implementations sur mesures</a><ul>
-<li><a href="#metadata-proxy">Mes metadonnées sont stockées dans une forme de base de données. Implémenter toute les interfaces de GeoAPI est infaisable.</a></li>
-<li><a href="#metadata-unknownClass">Je n’arrive pas à écrire mon implémentation de metadonnée</a></li>
-</ul>
-</li>
-</ul>
-</li>
-</ul>
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
 </div>
-<h1 id="referencing">Géoréférencement<a class="headerlink" href="#referencing" title="Permanent link">&para;</a></h1>
-<h2 id="referencing-intro">Pour bien commencer<a class="headerlink" href="#referencing-intro" title="Permanent link">&para;</a></h2>
-<h3 id="transform-point">Comment transformer une coordonnée ?<a class="headerlink" href="#transform-point" title="Permanent link">&para;</a></h3>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Questions fréquentes (FAQ)</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>Cette page liste quelques questions fréquemment posées à propos de Apache SIS.
+Son contenu est traduit de la <a href="faq.html">page de FAQ en anglais</a>.</p>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#referencing">Géoréférencement   </a>
+      <ul>
+        <li><a href="#referencing-intro">Pour bien commencer   </a>
+          <ul>
+            <li><a href="#transform-point">Comment transformer une coordonnée ?   </a></li>
+            <li><a href="#operation-methods">Quelles projections sont supportées ?   </a></li>
+            <li><a href="#axisOrder">Qu’est ce que le problème d’ordre des axes et comment est il abordé ?   </a></li>
+          </ul>
+        </li>
+        <li><a href="#crs">Systèmes de Référence des Coordonnées   </a>
+          <ul>
+            <li><a href="#UTM">Comment créer une projection de type Transverse Universelle de Mercator (UTM) ?   </a></li>
+            <li><a href="#google">Comment instancier une projection Google ?   </a></li>
+            <li><a href="#projectionKind">Comment puis-je identifier le type de projection d’un CRS ?   </a></li>
+            <li><a href="#lookupEPSG">Comment obtenir le code EPSG d’un CRS existant ?   </a></li>
+            <li><a href="#lookupURN">Comment obtenir l’URN « urn:ogc:def:crs:&hellip; » d’un CRS existant ?   </a></li>
+            <li><a href="#lookupReliability">Puis-je m’appuyer sur IdentifiedObjects.lookupEPSG(&hellip;) comme inverse de CRS.forCode(&hellip;) ?  </a></li>
+            <li><a href="#equalsIgnoreMetadata">Comment déterminer si deux CRS sont « fonctionnellement » égaux ? </a></li>
+            <li><a href="#crsHashCode">Est-ce que les CRS sont utilisables comme clé dans un HashMap ?   </a></li>
+          </ul>
+        </li>
+        <li><a href="#transforms">Transformation de coordonnées  </a>
+          <ul>
+            <li><a href="#axisOrderInTransforms">Mes coordonnées transformées sont totalement fausses !   </a></li>
+            <li><a href="#projectionName">Les ordres des axes sont corrects mais les coordonnées transformées sont encore fausses. </a></li>
+            <li><a href="#parameterUnits">J’ai juste utilisé le WKT d’une autorité connue et mes coordonnées transformées sont toujours fausses !   </a></li>
+            <li><a href="#BursaWolf">J’ai vérifié tous ce qui est ci-dessus et j’ai toujours une erreur d’environ un kilomètre.</a></li>
+            <li><a href="#slightDifferences">J’obtiens des résultats légèrement différents d’un environnement d’exécution à l’autre.  </a></li>
+            <li><a href="#toWGS84">Puis-je présumer qu’il est toujours possible de transformer un CRS arbitraire vers WGS84 ?   </a></li>
+          </ul>
+        </li>
+      </ul>
+    </li>
+    <li><a href="#metadata">Métadonnées   </a>
+      <ul>
+        <li><a href="#metadata-implementation">Implementations sur mesures  </a>
+          <ul>
+            <li><a href="#metadata-proxy">Mes metadonnées sont stockées dans une forme de base de données. Implémenter toute les interfaces de GeoAPI est infaisable.   </a></li>
+            <li><a href="#metadata-unknownClass">Je n’arrive pas à écrire mon implémentation de metadonnée </a></li>
+          </ul>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</nav>
+<h1 id="referencing">Géoréférencement   </h1>
+<h2 id="referencing-intro">Pour bien commencer   </h2>
+<h3 id="transform-point">Comment transformer une coordonnée ?   </h3>
 <p>Le code java suivant projète une coordonnée de <em>World Geodetic System 1984</em> (WGS84) vers <em>WGS 84 / UTM zone 33N</em>.
 Afin de rendre cet exemple un peu plus simple, le code utilise des constantes prédéfinies dans la classe <code>CommonCRS</code>.
 Mais les applications plus avancées utilisent habituellement des codes EPSG à la place.
 Notez que les coordonnées ci-dessous sont en latitude puis longitude.</p>
-<div class="codehilite"><pre><span class="kn">import</span> <span class="nn">org.opengis.geometry.DirectPosition</span><span class="o">;</span>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="kn">import</span> <span class="nn">org.opengis.geometry.DirectPosition</span><span class="o">;</span>
 <span class="kn">import</span> <span class="nn">org.opengis.referencing.crs.CoordinateReferenceSystem</span><span class="o">;</span>
 <span class="kn">import</span> <span class="nn">org.opengis.referencing.operation.CoordinateOperation</span><span class="o">;</span>
 <span class="kn">import</span> <span class="nn">org.opengis.referencing.operation.TransformException</span><span class="o">;</span>
@@ -160,24 +167,21 @@ Notez que les coordonnées ci-dessous sont en latitude puis longitude.</p>
 <span class="kd">public</span> <span class="kd">class</span> <span class="nc">MyApp</span> <span class="o">{</span>
     <span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">main</span><span class="o">(</span><span class="n">String</span><span class="o">[]</span> <span class="n">args</span><span class="o">)</span> <span class="kd">throws</span> <span class="n">FactoryException</span><span class="o">,</span> <span class="n">TransformException</span> <span class="o">{</span>
         <span class="n">CoordinateReferenceSystem</span> <span class="n">sourceCRS</span> <span class="o">=</span> <span class="n">CommonCRS</span><span class="o">.</span><span class="na">WGS84</span><span class="o">.</span><span class="na">geographic</span><span class="o">();</span>
-        <span class="n">CoordinateReferenceSystem</span> <span class="n">targetCRS</span> <span class="o">=</span> <span class="n">CommonCRS</span><span class="o">.</span><span class="na">WGS84</span><span class="o">.</span><span class="na">universal</span><span class="o">(</span><span class="mi">40</span><span class="o">,</span> <span class="mi">14</span><span class="o">);</span>      <span class="c1">// Obtient la zone valide pour 14°E.</span>
-        <span class="n">CoordinateOperation</span> <span class="n">operation</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">findOperation</span><span class="o">(</span><span class="n">sourceCRS</span><span class="o">,</span> <span class="n">targetCRS</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span>
-
-        <span class="c1">// Les lignes ci-dessus sont coûteuses et ne devraient être appelées qu’une fois pour un ensemble de points.</span>
-        <span class="c1">// Dans cet exemple, l’opération que l’on obtient est valide pour la zone géographique allant</span>
-        <span class="c1">// de 12°E à 18°E (UTM zone 33) et de 0°N à 84°N.</span>
-
-        <span class="n">DirectPosition</span> <span class="n">ptSrc</span> <span class="o">=</span> <span class="k">new</span> <span class="n">DirectPosition2D</span><span class="o">(</span><span class="mi">40</span><span class="o">,</span> <span class="mi">14</span><span class="o">);</span>           <span class="c1">// 40°N 14°E</span>
-        <span class="n">DirectPosition</span> <span class="n">ptDst</span> <span class="o">=</span> <span class="n">operation</span><span class="o">.</span><span class="na">getMathTransform</span><span class="o">().</span><span class="na">transform</span><span class="o">(</span><span class="n">ptSrc</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span>
-
-        <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&quot;Source: &quot;</span> <span class="o">+</span> <span class="n">ptSrc</span><span class="o">);</span>
-        <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&quot;Target: &quot;</span> <span class="o">+</span> <span class="n">ptDst</span><span class="o">);</span>
+        <span class="n">CoordinateReferenceSystem</span> <span class="n">targetCRS</span> <span class="o">=</span> <span class="n">CommonCRS</span><span class="o">.</span><span class="na">WGS84</span><span class="o">.</span><span class="na">universal</span><span class="o">(</span><span class="n">40</span><span class="o">,</span> <span class="n">14</span><span class="o">);</span>      <span class="c1">// Obtient la zone valide pour 14°E.
+</span><span class="c1"></span>        <span class="n">CoordinateOperation</span> <span class="n">operation</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">findOperation</span><span class="o">(</span><span class="n">sourceCRS</span><span class="o">,</span> <span class="n">targetCRS</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span>
+
+        <span class="c1">// Les lignes ci-dessus sont coûteuses et ne devraient être appelées qu’une fois pour un ensemble de points.
+</span><span class="c1"></span>        <span class="c1">// Dans cet exemple, l’opération que l’on obtient est valide pour la zone géographique allant
+</span><span class="c1"></span>        <span class="c1">// de 12°E à 18°E (UTM zone 33) et de 0°N à 84°N.
+</span><span class="c1"></span>
+        <span class="n">DirectPosition</span> <span class="n">ptSrc</span> <span class="o">=</span> <span class="k">new</span> <span class="n">DirectPosition2D</span><span class="o">(</span><span class="n">40</span><span class="o">,</span> <span class="n">14</span><span class="o">);</span>           <span class="c1">// 40°N 14°E
+</span><span class="c1"></span>        <span class="n">DirectPosition</span> <span class="n">ptDst</span> <span class="o">=</span> <span class="n">operation</span><span class="o">.</span><span class="na">getMathTransform</span><span class="o">().</span><span class="na">transform</span><span class="o">(</span><span class="n">ptSrc</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span>
+
+        <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&#34;Source: &#34;</span> <span class="o">+</span> <span class="n">ptSrc</span><span class="o">);</span>
+        <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&#34;Target: &#34;</span> <span class="o">+</span> <span class="n">ptDst</span><span class="o">);</span>
     <span class="o">}</span>
-<span class="o">}</span>
-</pre></div>
-
-
-<h3 id="operation-methods">Quelles projections sont supportées ?<a class="headerlink" href="#operation-methods" title="Permanent link">&para;</a></h3>
+<span class="o">}</span></code></pre></div>
+<h3 id="operation-methods">Quelles projections sont supportées ?   </h3>
 <p>Les formules supportées par Apache SIS (incluant les projections cartographiques, mais pas uniquement)
 sont listées sur la page <a href="tables/CoordinateOperationMethods.html">Coordinate Operation Methods</a>.
 La quantité de formules de projection est relativement faible,
@@ -189,40 +193,77 @@ Par soucis de facilité d’utilisation, des milliers de projections avec des pa
 Une source bien connue de ces définitions est la base de données EPSG, mais il existe d’autres autorités.
 Les systèmes de coordonnées prédéfinis dans Apache SIS sont listés à la page
 <a href="tables/CoordinateReferenceSystems.html">Coordinate Reference Systems</a>.</p>
-<h3 id="axisOrder">Qu’est ce que le problème d’ordre des axes et comment est il abordé ?<a class="headerlink" href="#axisOrder" title="Permanent link">&para;</a></h3>
-<p>L’ordre des axes est spécifié par l’autorité (typiquement un organisme public) qui défini les Systèmes de Référence des Coordonnées (<abbr title="Coordinate Reference System">CRS</abbr>).
-L’ordre dépend du type de <abbr title="Coordinate Reference System">CRS</abbr> et du pays qui définit le <abbr title="Coordinate Reference System">CRS</abbr>.
-Dans le cas d’un <abbr title="Coordinate Reference System">CRS</abbr> géographique, l’ordre des axes (<em>latitude</em>, <em>longitude</em>) est largement répandu chez les géographes et les pilotes depuis des siècles.
-Toutefois certains développeurs de logiciels ont tendance à toujours utiliser l’ordre (<em>x</em>, <em>y</em>) pour tous les <abbr title="Coordinate Reference System">CRS</abbr>.
-Ces pratiques différentes ont conduit à des définitions contradictoires d’ordre des axes pour presque tous les <abbr title="Coordinate Reference System">CRS</abbr> de type <code>GeographicCRS</code>,
+<h3 id="axisOrder">Qu’est ce que le problème d’ordre des axes et comment est il abordé ?   </h3>
+<p>L’ordre des axes est spécifié par l’autorité (typiquement un organisme public) qui défini les Systèmes de Référence des Coordonnées (CRS).
+L’ordre dépend du type de 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ et du pays qui définit le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+.
+Dans le cas d’un 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ géographique, l’ordre des axes (<em>latitude</em>, <em>longitude</em>) est largement répandu chez les géographes et les pilotes depuis des siècles.
+Toutefois certains développeurs de logiciels ont tendance à toujours utiliser l’ordre (<em>x</em>, <em>y</em>) pour tous les 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+.
+Ces pratiques différentes ont conduit à des définitions contradictoires d’ordre des axes pour presque tous les 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ de type <code>GeographicCRS</code>,
 pour certains <code>ProjectedCRS</code> de l’hémisphère sud (Afrique de sud, Australie, <em>etc.</em>) et pour certaines projections polaires entre autre.</p>
-<p>Pour chaque <abbr title="Coordinate Reference System">CRS</abbr> identifié par un code EPSG, l’ordre officiel des axes peut être vérifié avec
-le registre EPSG à l’adresse <a href="http://www.epsg-registry.org">http://www.epsg-registry.org</a>
+<p>Pour chaque 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ identifié par un code EPSG, l’ordre officiel des axes peut être vérifié avec
+le registre EPSG à l’adresse <a href="https://epsg.org/">https://epsg.org/</a>
 (à ne pas confondre avec d’autres sites ayant « epsg » dans leur nom
 mais qui sont sans aucune relation avec l’organisme en charge des définitions EPSG) :
 Cliquez sur le lien <em>« Retrieve by code »</em> et entrez le code numérique.
 Cliquez ensuite sur le lien <em>« View »</em> de la partie droite
 et cliquez sur le symbole <em>« + »</em> à gauche de <em>« Axes »</em>.</p>
-<p>Les standards <abbr title="Open Geospatial Consortium">OGC</abbr> récents stipulent que l’ordre des axes est celui défini par l’autorité.
-Les standards <abbr title="Open Geospatial Consortium">OGC</abbr> plus anciens utilisaient l’ordre des axes (<em>x</em>, <em>y</em>), ignorant la définition de l’autorité.
-Parmi les standards <abbr title="Open Geospatial Consortium">OGC</abbr> obsolètes qui utilisent un ordre des axes non-conforme,
+<p>Les standards 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ récents stipulent que l’ordre des axes est celui défini par l’autorité.
+Les standards 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ plus anciens utilisaient l’ordre des axes (<em>x</em>, <em>y</em>), ignorant la définition de l’autorité.
+Parmi les standards 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ obsolètes qui utilisent un ordre des axes non-conforme,
 l’un des plus influent est la version 1 de la spécification <em>Well Known Text</em> (WKT).
-Selon ce format très utilisé, les définitions WKT sans éléments <code>AXIS[…]</code>
+Selon ce format très utilisé, les définitions WKT sans éléments <code>AXIS[...]</code>
 doivent par défaut être dans l’ordre (<em>longitude</em>, <em>latitude</em>) ou (<em>x</em>, <em>y</em>).
-Dans la version 2 du format WKT, les éléments <code>AXIS[…]</code> ne sont plus optionnels
-et doivent contenir explicitement le sous-élément <code>ORDER[…]</code> pour appuyer l’ordre des axes à appliquer.</p>
+Dans la version 2 du format WKT, les éléments <code>AXIS[...]</code> ne sont plus optionnels
+et doivent contenir explicitement le sous-élément <code>ORDER[...]</code> pour appuyer l’ordre des axes à appliquer.</p>
 <p>Beaucoup de logiciels utilisent toujours l’ancien ordre des axes (<em>x</em>, <em>y</em>), parfois parce qu’il est plus simple à implémenter.
 Mais Apache SIS suit l’ordre des axes <em>tel que défini par l’autorité</em> (à l’exception de la lecture de fichier WKT 1).
-Il permet toutefois de changer l’ordre des axes après la création d’un <abbr title="Coordinate Reference System">CRS</abbr>.
-Ce changement se fait avec le code suivant :</p>
-<div class="codehilite"><pre><span class="n">CoordinateReferenceSystem</span> <span class="n">crs</span> <span class="o">=</span> <span class="err">…</span><span class="o">;</span>             <span class="c1">// CRS obtenu de n’importe quelle façon.</span>
-<span class="n">crs</span> <span class="o">=</span> <span class="n">AbstractCRS</span><span class="o">.</span><span class="na">castOrCopy</span><span class="o">(</span><span class="n">crs</span><span class="o">).</span><span class="na">forConvention</span><span class="o">(</span><span class="n">AxesConvention</span><span class="o">.</span><span class="na">RIGHT_HANDED</span><span class="o">)</span>
-</pre></div>
+Il permet toutefois de changer l’ordre des axes après la création d’un 
 
 
-<h2 id="crs">Systèmes de Référence des Coordonnées<a class="headerlink" href="#crs" title="Permanent link">&para;</a></h2>
-<h3 id="UTM">Comment créer une projection de type Transverse Universelle de Mercator (UTM) ?<a class="headerlink" href="#UTM" title="Permanent link">&para;</a></h3>
-<p>Si la zone UTM n’est pas connue, une façon simple est d’utiliser la méthode <code>universal(…)</code> sur l’une des constantes de <code>CommonCRS</code>.
+<abbr title="Coordinate Reference System">CRS</abbr>
+.
+Ce changement se fait avec le code suivant :</p>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">CoordinateReferenceSystem</span> <span class="n">crs</span> <span class="o">=</span> <span class="o">...;</span>             <span class="c1">// CRS obtenu de n’importe quelle façon.
+</span><span class="c1"></span><span class="n">crs</span> <span class="o">=</span> <span class="n">AbstractCRS</span><span class="o">.</span><span class="na">castOrCopy</span><span class="o">(</span><span class="n">crs</span><span class="o">).</span><span class="na">forConvention</span><span class="o">(</span><span class="n">AxesConvention</span><span class="o">.</span><span class="na">RIGHT_HANDED</span><span class="o">)</span></code></pre></div>
+<h2 id="crs">Systèmes de Référence des Coordonnées   </h2>
+<h3 id="UTM">Comment créer une projection de type Transverse Universelle de Mercator (UTM) ?   </h3>
+<p>Si la zone UTM n’est pas connue, une façon simple est d’utiliser la méthode <code>universal(...)</code> sur l’une des constantes de <code>CommonCRS</code>.
 Cette méthode prend en argument une coordonnées géographique en (<em>latitude</em>, <em>longitude</em>) et en calcule la zone UTM correspondante.
 Voir <a href="#transform-point">le code java ci-dessus</a>.</p>
 <p>Si la zone UTM est connue, une solution est d’utiliser la fabrique des autorités « EPSG » ou « AUTO ».
@@ -238,16 +279,17 @@ où <em>zone</em> est un nombre de 1 à 60 inclusif (sauf spécifié autrement)
 </ul>
 <p>Notez que la liste ci-dessus est incomplète. Voir la base EPSG pour d’avantages de définitions UTM
 (WGS 72BE, SIRGAS 2000, SIRGAS 1995, SAD 69, ETRS 89, <em>etc.</em>, la plupart définissent quelques zones).
-Une fois que le code EPSG de la projection UTM est déterminé, le <abbr title="Coordinate Reference System">CRS</abbr> peut être obtenu comme dans l’exemple ci-dessous:</p>
-<div class="codehilite"><pre><span class="kt">int</span> <span class="n">code</span> <span class="o">=</span> <span class="mi">32600</span> <span class="o">+</span> <span class="n">zone</span><span class="o">;</span>    <span class="c1">// Pour l’hémisphère nord WGS84</span>
-<span class="n">CoordinateReferenceSystem</span> <span class="n">crs</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">forCode</span><span class="o">(</span><span class="s">&quot;EPSG:&quot;</span> <span class="o">+</span> <span class="n">code</span><span class="o">);</span>
-</pre></div>
+Une fois que le code EPSG de la projection UTM est déterminé, le 
 
 
-<h3 id="google">Comment instancier une projection Google ?<a class="headerlink" href="#google" title="Permanent link">&para;</a></h3>
+<abbr title="Coordinate Reference System">CRS</abbr>
+ peut être obtenu comme dans l’exemple ci-dessous:</p>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="kt">int</span> <span class="n">code</span> <span class="o">=</span> <span class="n">32600</span> <span class="o">+</span> <span class="n">zone</span><span class="o">;</span>    <span class="c1">// Pour l’hémisphère nord WGS84
+</span><span class="c1"></span><span class="n">CoordinateReferenceSystem</span> <span class="n">crs</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">forCode</span><span class="o">(</span><span class="s">&#34;EPSG:&#34;</span> <span class="o">+</span> <span class="n">code</span><span class="o">);</span></code></pre></div>
+<h3 id="google">Comment instancier une projection Google ?   </h3>
 <p>La projection Google est une projection de Mercator qui prétend utiliser un référentiel WGS84
 mais qui ignore la nature ellipsoïdale de ce référentiel et utilise un forme sphérique des formules à la place.
-Depuis la version 6.15 de la base EPSG, la façon privilégiée d’obtenir cette projection est d’utiliser la méthode <code>CRS.forCode("EPSG:3857")</code>.
+Depuis la version 6.15 de la base EPSG, la façon privilégiée d’obtenir cette projection est d’utiliser la méthode <code>CRS.forCode(&quot;EPSG:3857&quot;)</code>.
 Il faut noter que l’usage de cette projection <strong>n’est pas</strong> recommandé, sauf pour des raisons de compatibilité.</p>
 <p>La définition de EPSG:3857 utilise une formule de projection nommée <em>« Popular Visualisation Pseudo Mercator »</em>.
 La base EPSG propose aussi d’autres projections qui utilisent des formules sphériques.
@@ -255,216 +297,369 @@ Ces méthodes ont le mot « (Spherical) » dans leur nom, par exemple <em>« 
 (qui diffère de <em>« Popular Visualisation Pseudo Mercator »</em> par l’utilisation d’une sphère de rayon plus approprié).
 Ces formules de projections peuvent être utilisées dans les définitions <em>Well Known Text</em> (WKT).</p>
 <p>Il est possible d’utiliser une formule sphérique avec une projection qui n’a pas de contrepartie sphérique
-en déclarant explicitement les paramètres <code>"semi_major"</code> et <code>"semi_minor"</code> dans la définition WKT.
+en déclarant explicitement les paramètres <code>&quot;semi_major&quot;</code> et <code>&quot;semi_minor&quot;</code> dans la définition WKT.
 Ces paramètres sont généralement déduit du référentiel, mais Apache SIS autorise les déclarations à surcharger ces valeurs.</p>
-<h3 id="projectionKind">Comment puis-je identifier le type de projection d’un <abbr title="Coordinate Reference System">CRS</abbr> ?<a class="headerlink" href="#projectionKind" title="Permanent link">&para;</a></h3>
-<p>Le terme « type de projection » (Mercator, Lambert Conformal, <em>etc.</em>) est appelé <em>Operation Method</em> dans la terminologie <abbr title="International Organization for Standardization">ISO</abbr> 19111.
-Une approche possible est de vérifier la valeur de <code>OperationMethod.getName()</code> et de comparer avec les noms <abbr title="Open Geospatial Consortium">OGC</abbr> et EPSG
+<h3 id="projectionKind">Comment puis-je identifier le type de projection d’un CRS ?   </h3>
+<p>Le terme « type de projection » (Mercator, Lambert Conformal, <em>etc.</em>) est appelé <em>Operation Method</em> dans la terminologie 
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+ 19111.
+Une approche possible est de vérifier la valeur de <code>OperationMethod.getName()</code> et de comparer avec les noms 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ et EPSG
 listés à la page <a href="tables/CoordinateOperationMethods.html">Coordinate Operation Methods</a>.</p>
-<h3 id="lookupEPSG">Comment obtenir le code EPSG d’un <abbr title="Coordinate Reference System">CRS</abbr> existant ?<a class="headerlink" href="#lookupEPSG" title="Permanent link">&para;</a></h3>
-<p>La propriété <em>identifiant</em> d’un <abbr title="Coordinate Reference System">CRS</abbr> peut être obtenue par la méthode <code>getIdentifiers()</code>
+<h3 id="lookupEPSG">Comment obtenir le code EPSG d’un CRS existant ?   </h3>
+<p>La propriété <em>identifiant</em> d’un 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ peut être obtenue par la méthode <code>getIdentifiers()</code>
 qui retourne une collection de zéro ou un élément.
-Si le <abbr title="Coordinate Reference System">CRS</abbr> a été créé à partir d’un <em>Well Known Text</em> (WKT)
-et que le WKT se termine avec un élément <code>AUTHORITY["EPSG", "xxxx"]</code> (WKT version 1) ou <code>ID["EPSG", xxxx]</code> (WKT version 2,
+Si le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ a été créé à partir d’un <em>Well Known Text</em> (WKT)
+et que le WKT se termine avec un élément <code>AUTHORITY[&quot;EPSG&quot;, &quot;xxxx&quot;]</code> (WKT version 1) ou <code>ID[&quot;EPSG&quot;, xxxx]</code> (WKT version 2,
 alors l’identifiant (un code numérique EPSG dans cet exemple) sera le <em>xxxx</em> de cet élément.
-Si le <abbr title="Coordinate Reference System">CRS</abbr> a été créé à partir de la base EPSG (par exemple avec l’appelle à <code>CRS.forCode("EPSG:xxxx")</code>),
+Si le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ a été créé à partir de la base EPSG (par exemple avec l’appelle à <code>CRS.forCode(&quot;EPSG:xxxx&quot;)</code>),
 alors l’identifiant est le code <em>xxxx</em> donné à la méthode.
-Si le <abbr title="Coordinate Reference System">CRS</abbr> a été créé d’une autre façon, alors la collection retournée par la méthode <code>getIdentifiers()</code>
-pourra être vide dans le cas où le programme qui a créé le <abbr title="Coordinate Reference System">CRS</abbr> a aussi pris la responsabilité de fournir les identifiants.</p>
+Si le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ a été créé d’une autre façon, alors la collection retournée par la méthode <code>getIdentifiers()</code>
+pourra être vide dans le cas où le programme qui a créé le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ a aussi pris la responsabilité de fournir les identifiants.</p>
 <p>Si la collection d’identifiants est vide, la méthode la plus efficace de le corriger est de s’assurer que le WKT
-contient un élément <code>AUTHORITY</code> ou <code>ID</code> (en supposant que le <abbr title="Coordinate Reference System">CRS</abbr> vient d’un WKT).
+contient un élément <code>AUTHORITY</code> ou <code>ID</code> (en supposant que le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ vient d’un WKT).
 Si ce n’est pas possible, alors la classe <code>org.​apache.​sis.​referencing.​IdentifiedObjects</code> contient des méthodes utilitaires qui peuvent aider
-Dans l’exemple suivant, l’appel à <code>lookupEPSG(…)</code> va parcourir la base EPSG pour un <abbr title="Coordinate Reference System">CRS</abbr> équivalent (en ignorant les métadonnées).
+Dans l’exemple suivant, l’appel à <code>lookupEPSG(...)</code> va parcourir la base EPSG pour un 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ équivalent (en ignorant les métadonnées).
 <em>Attention, cette recherche est sensible à l’ordre des axes.</em>
-La plupart des <abbr title="Coordinate Reference System">CRS</abbr> géographiques de la base EPSG sont déclarés avec l’ordre des axes (<em>latitude</em>, <em>longitude</em>).
-En conséquence, si le <abbr title="Coordinate Reference System">CRS</abbr> possède un ordre des axes (<em>longitude</em>, <em>latitude</em>), la recherche a toutes les chances de ne pas trouver de résultats.</p>
-<div class="codehilite"><pre><span class="n">CoordinateReferenceSystem</span> <span class="n">myCRS</span> <span class="o">=</span> <span class="err">…</span><span class="o">;</span>
+La plupart des 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ géographiques de la base EPSG sont déclarés avec l’ordre des axes (<em>latitude</em>, <em>longitude</em>).
+En conséquence, si le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ possède un ordre des axes (<em>longitude</em>, <em>latitude</em>), la recherche a toutes les chances de ne pas trouver de résultats.</p>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">CoordinateReferenceSystem</span> <span class="n">myCRS</span> <span class="o">=</span> <span class="o">...;</span>
 <span class="n">Integer</span> <span class="n">identifier</span> <span class="o">=</span> <span class="n">IdentifiedObjects</span><span class="o">.</span><span class="na">lookupEPSG</span><span class="o">(</span><span class="n">myCRS</span><span class="o">);</span>
 <span class="k">if</span> <span class="o">(</span><span class="n">identifier</span> <span class="o">!=</span> <span class="kc">null</span><span class="o">)</span> <span class="o">{</span>
-    <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&quot;Le code EPSG a été trouvé : &quot;</span> <span class="o">+</span> <span class="n">identifier</span><span class="o">);</span>
-<span class="o">}</span>
-</pre></div>
+    <span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="s">&#34;Le code EPSG a été trouvé : &#34;</span> <span class="o">+</span> <span class="n">identifier</span><span class="o">);</span>
+<span class="o">}</span></code></pre></div>
+<h3 id="lookupURN">Comment obtenir l’URN « urn:ogc:def:crs:&hellip; » d’un CRS existant ?   </h3>
+<p>L’
+
 
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ définit les URN pour les identifiants de 
 
-<h3 id="lookupURN">Comment obtenir l’URN « urn:ogc:def:crs:… » d’un <abbr title="Coordinate Reference System">CRS</abbr> existant ?<a class="headerlink" href="#lookupURN" title="Permanent link">&para;</a></h3>
-<p>L’<abbr title="Open Geospatial Consortium">OGC</abbr> définit les URN pour les identifiants de <abbr title="Coordinate Reference System">CRS</abbr>, par exemple <code>"urn:​ogc:​def:​crs:​epsg:​7.1:​4326"</code>
-avec <code>"7.1"</code> comme version de la base EPSG utilisée.
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+, par exemple <code>&quot;urn:​ogc:​def:​crs:​epsg:​7.1:​4326&quot;</code>
+avec <code>&quot;7.1&quot;</code> comme version de la base EPSG utilisée.
 Les URN peuvent ou non être présentes dans la collection d’identifiants retournée par <code>crs.getIdentifiers()</code>.
-Dans beaucoup de cas (principalement quand le <abbr title="Coordinate Reference System">CRS</abbr> provient d’un <em>Well Known Text</em>), seul des identifiants simples comme <code>"EPSG:​4326"</code> sont présents.
+Dans beaucoup de cas (principalement quand le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ provient d’un <em>Well Known Text</em>), seul des identifiants simples comme <code>&quot;EPSG:​4326&quot;</code> sont présents.
 Une façon simple de construire une URN complète est d’utiliser le code ci-dessous.
 Cet exemple peut avoir à parcourir la base EPSG afin de trouver les informations qui n’apparaissent pas explicitement dans <code>myCRS</code>.</p>
-<div class="codehilite"><pre><span class="n">CoordinateReferenceSystem</span> <span class="n">myCRS</span> <span class="o">=</span> <span class="err">…</span><span class="o">;</span>
-<span class="n">String</span> <span class="n">urn</span> <span class="o">=</span> <span class="n">IdentifiedObjects</span><span class="o">.</span><span class="na">lookupURN</span><span class="o">(</span><span class="n">myCRS</span><span class="o">);</span>
-</pre></div>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">CoordinateReferenceSystem</span> <span class="n">myCRS</span> <span class="o">=</span> <span class="o">...;</span>
+<span class="n">String</span> <span class="n">urn</span> <span class="o">=</span> <span class="n">IdentifiedObjects</span><span class="o">.</span><span class="na">lookupURN</span><span class="o">(</span><span class="n">myCRS</span><span class="o">);</span></code></pre></div>
+<h3 id="lookupReliability">Puis-je m’appuyer sur IdentifiedObjects.lookupEPSG(&hellip;) comme inverse de CRS.forCode(&hellip;) ?  </h3>
+<p>Pour les 
+
 
+<abbr title="Coordinate Reference System">CRS</abbr>
+ créés avec la base EPSG, en général oui.
+À noter toutefois que <code>IdentifiedObjects.getIdentifier(...)</code> est moins riche et insensible aux détails de la définition du 
 
-<h3 id="lookupReliability">Puis-je m’appuyer sur IdentifiedObjects.lookupEPSG(…) comme inverse de <abbr title="Coordinate Reference System">CRS</abbr>.forCode(…) ?<a class="headerlink" href="#lookupReliability" title="Permanent link">&para;</a></h3>
-<p>Pour les <abbr title="Coordinate Reference System">CRS</abbr> créés avec la base EPSG, en général oui.
-À noter toutefois que <code>IdentifiedObjects.getIdentifier(…)</code> est moins riche et insensible aux détails de la définition du <abbr title="Coordinate Reference System">CRS</abbr>
-car il n’interroge pas la base de données EPSG. Il marche uniquement si le <abbr title="Coordinate Reference System">CRS</abbr> déclare explicitement son code
-ce qui est le cas des <abbr title="Coordinate Reference System">CRS</abbr> créés à partir de la base EPSG ou lus à partir d’un <em>Well Known Text</em> (WKT) avec un élément <code>AUTHORITY</code> ou <code>ID</code>.
-La méthode <code>lookupEPSG(…)</code> à l’inverse est plus robuste contre les erreurs de déclaration de code car elle compare toujours le <abbr title="Coordinate Reference System">CRS</abbr> avec celui de la base.
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+
+car il n’interroge pas la base de données EPSG. Il marche uniquement si le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ déclare explicitement son code
+ce qui est le cas des 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ créés à partir de la base EPSG ou lus à partir d’un <em>Well Known Text</em> (WKT) avec un élément <code>AUTHORITY</code> ou <code>ID</code>.
+La méthode <code>lookupEPSG(...)</code> à l’inverse est plus robuste contre les erreurs de déclaration de code car elle compare toujours le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ avec celui de la base.
 Elle peut échouer s’il y a une légère différence (par exemple d’arrondie dans les paramètres)
-entre le <abbr title="Coordinate Reference System">CRS</abbr> fourni et le <abbr title="Coordinate Reference System">CRS</abbr> trouvé dans la base de données.</p>
-<h3 id="equalsIgnoreMetadata">Comment déterminer si deux <abbr title="Coordinate Reference System">CRS</abbr> sont « fonctionnellement » égaux ?<a class="headerlink" href="#equalsIgnoreMetadata" title="Permanent link">&para;</a></h3>
-<p>Deux <abbr title="Coordinate Reference System">CRS</abbr> peuvent ne pas être considérés égaux s’ils sont associés à des métadonnées différentes
-(nom, identifiant, domaine d’usage, domaine de validité, remarque), même s’ils représentent mathématiquement le même <abbr title="Coordinate Reference System">CRS</abbr>.
-Afin de tester si deux <abbr title="Coordinate Reference System">CRS</abbr> sont fonctionnellement équivalents, utilisez la méthode <code>Utilities​.equalsIgnoreMetadata(myFirstCRS, mySecondCRS)</code>.</p>
-<h3 id="crsHashCode">Est-ce que les <abbr title="Coordinate Reference System">CRS</abbr> sont utilisables comme clé dans un HashMap ?<a class="headerlink" href="#crsHashCode" title="Permanent link">&para;</a></h3>
+entre le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ fourni et le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ trouvé dans la base de données.</p>
+<h3 id="equalsIgnoreMetadata">Comment déterminer si deux CRS sont « fonctionnellement » égaux ? </h3>
+<p>Deux 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ peuvent ne pas être considérés égaux s’ils sont associés à des métadonnées différentes
+(nom, identifiant, domaine d’usage, domaine de validité, remarque), même s’ils représentent mathématiquement le même 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+.
+Afin de tester si deux 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ sont fonctionnellement équivalents, utilisez la méthode <code>Utilities​.equalsIgnoreMetadata(myFirstCRS, mySecondCRS)</code>.</p>
+<h3 id="crsHashCode">Est-ce que les CRS sont utilisables comme clé dans un HashMap ?   </h3>
 <p>Oui, toutes les classes définies dans les paquets <code>org.apache.sis.referencing.crs</code>, <code>cs</code> et <code>datum</code>
 définissent leurs propres méthodes <code>equals(Object)</code> et <code>hashCode()</code>.
-La bibliothèque Apache SIS utilise elle-même les objets <abbr title="Coordinate Reference System">CRS</abbr> dans des <code>Map</code> à des fins de cache.</p>
-<h2 id="transforms">Transformation de coordonnées<a class="headerlink" href="#transforms" title="Permanent link">&para;</a></h2>
-<h3 id="axisOrderInTransforms">Mes coordonnées transformées sont totalement fausses !<a class="headerlink" href="#axisOrderInTransforms" title="Permanent link">&para;</a></h3>
+La bibliothèque Apache SIS utilise elle-même les objets 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ dans des <code>Map</code> à des fins de cache.</p>
+<h2 id="transforms">Transformation de coordonnées  </h2>
+<h3 id="axisOrderInTransforms">Mes coordonnées transformées sont totalement fausses !   </h3>
 <p>Ce cas se produit principalement à cause des ordonnées données dans le mauvais ordre.
 Les développeurs ont tendance à présumer que l’ordre des  axes est (<em>x</em>, <em>y</em>) ou (<em>longitude</em>, <em>latitude</em>)
 mais les géographes et pilotes utilisent l’ordre (<em>latitude</em>, <em>longitude</em>) depuis des siècles
 et la base de données EPSG définit les systèmes de coordonnées de cette façon.
 Si une transformation de coordonnées semble produire des valeurs complètement fausses,
-la première chose à faire est d’afficher les <abbr title="Coordinate Reference System">CRS</abbr> source et cible :</p>
-<div class="codehilite"><pre><span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="n">sourceCRS</span><span class="o">);</span>
-<span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="n">targetCRS</span><span class="o">);</span>
-</pre></div>
+la première chose à faire est d’afficher les 
 
 
+<abbr title="Coordinate Reference System">CRS</abbr>
+ source et cible :</p>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="n">sourceCRS</span><span class="o">);</span>
+<span class="n">System</span><span class="o">.</span><span class="na">out</span><span class="o">.</span><span class="na">println</span><span class="o">(</span><span class="n">targetCRS</span><span class="o">);</span></code></pre></div>
 <p>Une attention particulière doit être portée à l’ordre des éléments <code>AXIS</code>.
-Dans l’exemple ci-dessous, le <abbr title="Coordinate Reference System">CRS</abbr> stipule clairement l’ordre (<em>latitude</em>, <em>longitude</em>) :</p>
-<div class="codehilite"><pre>GeodeticCRS[&quot;WGS 84&quot;,
-  Datum[&quot;World Geodetic System 1984&quot;,
-    Ellipsoid[&quot;WGS 84&quot;, 6378137.0, 298.257223563]],
-  CS[ellipsoidal, 2],
-    Axis[&quot;Geodetic latitude (Lat)&quot;, north],
-    Axis[&quot;Geodetic longitude (Lon)&quot;, east],
-    Unit[&quot;degree&quot;, 0.017453292519943295]]
-</pre></div>
+Dans l’exemple ci-dessous, le 
 
 
+<abbr title="Coordinate Reference System">CRS</abbr>
+ stipule clairement l’ordre (<em>latitude</em>, <em>longitude</em>) :</p>
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">GeodeticCRS[&#34;WGS 84&#34;,
+  Datum[&#34;World Geodetic System 1984&#34;,
+    Ellipsoid[&#34;WGS 84&#34;, 6378137.0, 298.257223563]],
+  CS[ellipsoidal, 2],
+    Axis[&#34;Geodetic latitude (Lat)&#34;, north],
+    Axis[&#34;Geodetic longitude (Lon)&#34;, east],
+    Unit[&#34;degree&#34;, 0.017453292519943295]]</code></pre></div>
 <p>Si l’ordre (<em>longitude</em>, <em>latitude</em>) est voulu, Apache SIS est capable de le forcer comme décrit <a href="#axisOrder">ci-dessus</a>.</p>
-<h3 id="projectionName">Les ordres des axes sont corrects mais les coordonnées transformées sont encore fausses.<a class="headerlink" href="#projectionName" title="Permanent link">&para;</a></h3>
+<h3 id="projectionName">Les ordres des axes sont corrects mais les coordonnées transformées sont encore fausses. </h3>
 <p>Vérifiez que se sont les bonnes projections qui sont utilisées. Certains noms sont déroutants.
 Par exemple <em>« Oblique Mercator »</em> et <em>« Hotine Oblique Mercator »</em> (dans l’autorité EPSG) sont deux projections différentes.
 Mais <em>« Oblique Mercator »</em> (sans le Hotine) de l’autorité EPSG est aussi appelée <em>« Hotine Oblique Mercator Azimuth Center »</em> par ESRI.
 tandis que <em>« Hotine Oblique Mercator »</em> (de l’autorité EPSG) est appelée <em>« Hotine Oblique Mercator Azimuth Natural Origin »</em> par ESRI.</p>
 <p>La projection <em>« Oblique Stereographic »</em> (de l’autorité EPSG) est appelée <em>« Double Stereographic »</em> par ESRI.
 ESRI définit aussi une projection <em>« Stereographic »</em> qui est en réalité une projection oblique comme la précédente mais avec des formules différentes.</p>
-<h3 id="parameterUnits">J’ai juste utilisé le WKT d’une autorité connue et mes coordonnées transformées sont toujours fausses !<a class="headerlink" href="#parameterUnits" title="Permanent link">&para;</a></h3>
+<h3 id="parameterUnits">J’ai juste utilisé le WKT d’une autorité connue et mes coordonnées transformées sont toujours fausses !   </h3>
 <p>La spécification <em>Well Known Text</em> (WKT) a été interprétée de différentes façons en fonction des implémentations logicielles.
 Un problème subtil vient des unités d’angles pour le méridien d’origine et les paramètres de projection.
 La spécification WKT 1 stipule clairement : <em>« Si l’élément <code>PRIMEM</code> apparaît dans <code>GEOGCS</code>,
-alors l’unité des longitudes doit correspondre à celle du système de coordonnées géographiques »</em> (traduction libre de <abbr title="Open Geospatial Consortium">OGC</abbr> 01-009).
-Toutefois ESRI et GDAL entres autres utilisent inconditionnellement des degrés décimaux, ignorant cette partie de la spécification WKT.
-Ce problème peut être identifié en inspectant l’extrait de WKT suivant :</p>
-<div class="codehilite"><pre>PROJCS[&quot;Lambert II étendu&quot;,
-  GEOGCS[&quot;Nouvelle Triangulation Française&quot;, …,
-    PRIMEM[&quot;Paris&quot;, 2.337229167],
-    UNIT[&quot;grad&quot;, 0.01570796326794897]]
-  PROJECTION[&quot;Lambert_Conformal_Conic_1SP&quot;],
-  PARAMETER[&quot;latitude_of_origin&quot;, 46.8], …]
-</pre></div>
+alors l’unité des longitudes doit correspondre à celle du système de coordonnées géographiques »</em> (traduction libre de 
 
 
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ 01-009).
+Toutefois ESRI et GDAL entres autres utilisent inconditionnellement des degrés décimaux, ignorant cette partie de la spécification WKT.
+Ce problème peut être identifié en inspectant l’extrait de WKT suivant :</p>
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">PROJCS[&#34;Lambert II étendu&#34;,
+  GEOGCS[&#34;Nouvelle Triangulation Française&#34;, ...,
+    PRIMEM[&#34;Paris&#34;, 2.337229167],
+    UNIT[&#34;grad&#34;, 0.01570796326794897]]
+  PROJECTION[&#34;Lambert_Conformal_Conic_1SP&#34;],
+  PARAMETER[&#34;latitude_of_origin&#34;, 46.8], ...]</code></pre></div>
 <p>Le méridien d’origine de Paris est situé à approximativement 2,597 gradians de Greenwich, ce qui correspond à 2,337 degrés.
-À partir de ce fait, on peut voir que le WKT ci-dessus utilise des degrés malgré la déclaration de l’unité <code>UNIT["grad"]</code>.
+À partir de ce fait, on peut voir que le WKT ci-dessus utilise des degrés malgré la déclaration de l’unité <code>UNIT[&quot;grad&quot;]</code>.
 Cette erreur s’applique aussi aux valeurs des paramètres, qui déclarent 46,8° dans l’exemple ci-dessus alors que la valeur officielle est de 52 gradians.
 Par défaut, Apache SIS interprète ces valeurs angulaires en gradians quand il lit ce type de WKT, ce qui produit de grandes erreurs.
 Afin d’obtenir le résultat attendu, il est possible de :</p>
 <ul>
 <li>
-<p>Remplacer <code>UNIT["grad", 0.01570796326794897]</code> par <code>UNIT["degree", 0.017453292519943295]</code>,
-    ce qui va assurer que Apache SIS, GDAL et ESRI comprennent ce WKT de la même manière.</p>
+<p>Remplacer <code>UNIT[&quot;grad&quot;, 0.01570796326794897]</code> par <code>UNIT[&quot;degree&quot;, 0.017453292519943295]</code>,
+ce qui va assurer que Apache SIS, GDAL et ESRI comprennent ce WKT de la même manière.</p>
 </li>
 <li>
 <p>Ou demander explicitement à Apache SIS de lire le WKT en utilisant les conventions ESRI ou GDAL,
-    avec l’énumération <code>Convention.​WKT1_COMMON_UNITS</code> pour la valeur de <code>WKTFormat</code> dans le paquet <code>org.​apache.​sis.​io.​wkt</code>.</p>
+avec l’énumération <code>Convention.​WKT1_COMMON_UNITS</code> pour la valeur de <code>WKTFormat</code> dans le paquet <code>org.​apache.​sis.​io.​wkt</code>.</p>
 </li>
 </ul>
-<p>Il est à noter que le standard GeoPackage requiert explicitement la conformité avec <abbr title="Open Geospatial Consortium">OGC</abbr> 01-009
-et que le nouveau standard WKT 2 suit aussi l’interprétation de <abbr title="Open Geospatial Consortium">OGC</abbr> 01-009.
+<p>Il est à noter que le standard GeoPackage requiert explicitement la conformité avec 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ 01-009
+et que le nouveau standard WKT 2 suit aussi l’interprétation de 
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ 01-009.
 Le comportement par défaut de Apache SIS est cohérent avec ces deux standards.</p>
-<h3 id="BursaWolf">J’ai vérifié tous ce qui est ci-dessus et j’ai toujours une erreur d’environ un kilomètre.<a class="headerlink" href="#BursaWolf" title="Permanent link">&para;</a></h3>
-<p>Les systèmes de coordonnées (<abbr title="Coordinate Reference System">CRS</abbr>) font une approximation de la forme de la terre avec une ellipsoïde.
+<h3 id="BursaWolf">J’ai vérifié tous ce qui est ci-dessus et j’ai toujours une erreur d’environ un kilomètre.</h3>
+<p>Les systèmes de coordonnées (CRS) font une approximation de la forme de la terre avec une ellipsoïde.
 Différentes ellipsoïdes (en réalité différents <em>référentiels</em>) sont utilisées dans différents pays du monde et à différents moments de l’histoire.
-Quand on transforme des coordonnées entre deux <abbr title="Coordinate Reference System">CRS</abbr> utilisant le même référentiel, aucun paramètre Bursa-Wolf n’est requis.
+Quand on transforme des coordonnées entre deux 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ utilisant le même référentiel, aucun paramètre Bursa-Wolf n’est requis.
 Mais quand la transformation implique un changement de référentiel, le module de géoréférencement à besoin d’informations sur la manière d’effectuer ce changement.</p>
 <p>Il y a plusieurs façon de spécifier comment appliquer un changement de référentiel, et la plupart sont seulement approximatives.
 La méthode de Bursa-Wolf est l’une d’elle, mais pas la seule. Toutefois elle est une des plus fréquemment utilisées.
 Les paramètres Bursa-Wolf peuvent être spécifiés à l’intérieur de l’élément <code>TOWGS84</code> de la version 1 du format <em>Well Known Text</em> (WKT),
 ou dans l’élément <code>BOUNDCRS</code> avec la version 2 du format WKT.
-Si le <abbr title="Coordinate Reference System">CRS</abbr> est lu à partir d’une chaine WKT, assurez-vous qu’elle contient l’élément approprié.</p>
-<h3 id="slightDifferences">J’obtiens des résultats légèrement différents d’un environnement d’exécution à l’autre.<a class="headerlink" href="#slightDifferences" title="Permanent link">&para;</a></h3>
+Si le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ est lu à partir d’une chaine WKT, assurez-vous qu’elle contient l’élément approprié.</p>
+<h3 id="slightDifferences">J’obtiens des résultats légèrement différents d’un environnement d’exécution à l’autre.  </h3>
 <p>Les résultats de transformations de coordonnées quand on lance l’application dans un conteneur web (type JBoss, <em>etc.</em>)
 peuvent avoir quelques mètres de différence avec la transformation exécutée dans un IDE (NetBeans, Eclipse, <em>etc.</em>).
 Les résultats dépendent de la présence de la fabrique EPSG dans le chemin de classes (classpath),
-<strong>peu importe comment le <abbr title="Coordinate Reference System">CRS</abbr> a été créé</strong>, parce-que la fabrique EPSG spécifie explicitement l’opération à appliquer pour certaines paires de <abbr title="Coordinate Reference System">CRS</abbr>.
+<strong>peu importe comment le 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ a été créé</strong>, parce-que la fabrique EPSG spécifie explicitement l’opération à appliquer pour certaines paires de 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+.
 Dans ces cas, l’opération spécifiée par EPSG a priorité par rapport aux paramètres de Bursa-Wolf
 (l’element <code>TOWGS84</code> de la version 1 du format <em>Well Known Text</em>).</p>
 <p>Une connexion à la base EPSG peut avoir été établie dans un environnement (typiquement celui JEE)
-et pas dans l’autre (typiquement un IDE) car uniquement le premier à un pilote <abbr title="Java DataBase Connectivity">JDBC</abbr>.
+et pas dans l’autre (typiquement un IDE) car uniquement le premier à un pilote 
+
+
+<abbr title="Java DataBase Connectivity">JDBC</abbr>
+.
 La méthode recommandée pour uniformiser les résultats est d’ajouter dans le second environnement (l’IDE)
 le même pilote que celui présent dans le premier environnement (JEE).
 Cela devrait être un des suivant : JavaDB (aussi nommé Derby), HSQL ou PostgreSQL.
 Assurez vous également que les <a href="epsg.html">paramètres de connexion à la base EPSG</a> sont les mêmes.</p>
-<h3 id="toWGS84">Puis-je présumer qu’il est toujours possible de transformer un <abbr title="Coordinate Reference System">CRS</abbr> arbitraire vers WGS84 ?<a class="headerlink" href="#toWGS84" title="Permanent link">&para;</a></h3>
-<p>Pour les <abbr title="Coordinate Reference System">CRS</abbr> 2D horizontaux créés avec la base de données EPSG, l’appel à <code>CRS.findOperation(…)</code> devrait toujours marcher.
-Pour les <abbr title="Coordinate Reference System">CRS</abbr> 3D ayant n’importe quel axe de hauteur autre que la hauteur ellipsoïdale, ou pour les <abbr title="Coordinate Reference System">CRS</abbr> 2D de type <code>EngineeringCRS</code>, la méthode peu échouer.
-Il reste à noter que dans le cas ou la méthode <code>CRS.findOperation(…)</code> ne lève pas d’erreur, l’appel à <code>MathTransform.transform(…)</code> peut
+<h3 id="toWGS84">Puis-je présumer qu’il est toujours possible de transformer un CRS arbitraire vers WGS84 ?   </h3>
+<p>Pour les 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ 2D horizontaux créés avec la base de données EPSG, l’appel à <code>CRS.findOperation(...)</code> devrait toujours marcher.
+Pour les 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ 3D ayant n’importe quel axe de hauteur autre que la hauteur ellipsoïdale, ou pour les 
+
+
+<abbr title="Coordinate Reference System">CRS</abbr>
+ 2D de type <code>EngineeringCRS</code>, la méthode peu échouer.
+Il reste à noter que dans le cas ou la méthode <code>CRS.findOperation(...)</code> ne lève pas d’erreur, l’appel à <code>MathTransform.transform(...)</code> peut
 produire des valeurs <code>NaN</code> or <code>Infinity</code>si la coordonnée transformée est éloignée de la zone de validité.</p>
-<h1 id="metadata">Métadonnées<a class="headerlink" href="#metadata" title="Permanent link">&para;</a></h1>
-<h2 id="metadata-implementation">Implementations sur mesures<a class="headerlink" href="#metadata-implementation" title="Permanent link">&para;</a></h2>
-<h3 id="metadata-proxy">Mes metadonnées sont stockées dans une forme de base de données. Implémenter toute les interfaces de GeoAPI est infaisable.<a class="headerlink" href="#metadata-proxy" title="Permanent link">&para;</a></h3>
+<h1 id="metadata">Métadonnées   </h1>
+<h2 id="metadata-implementation">Implementations sur mesures  </h2>
+<h3 id="metadata-proxy">Mes metadonnées sont stockées dans une forme de base de données. Implémenter toute les interfaces de GeoAPI est infaisable.   </h3>
 <p>Les développeurs n’ont pas besoin d’implémenter directement les interfaces de metadonnées.
 Si le système de stockage sous-jacent peut accéder aux metadonnées à partir de leur classes et nom de propriétés
-(soit le nom java ou le nom <abbr title="International Organization for Standardization">ISO</abbr>/<abbr title="Open Geospatial Consortium">OGC</abbr>), alors il est possible d’implémenter un seul moteur pour tous les types de metadonnées
+(soit le nom java ou le nom 
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+/
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+), alors il est possible d’implémenter un seul moteur pour tous les types de metadonnées
 et de laisser la Machine Virtuelle Java implémenter les interfaces GeoAPI à la volée, en utilisant la classe <code>java.lang.reflect.Proxy</code>.
-Pour plus de détails voir la javadoc de la classe <code>Proxy</code>, en gardant à l’esprit que le nom <abbr title="International Organization for Standardization">ISO</abbr>/<abbr title="Open Geospatial Consortium">OGC</abbr> d’une <code>java.lang.Class</code> ou
+Pour plus de détails voir la javadoc de la classe <code>Proxy</code>, en gardant à l’esprit que le nom 
+
+
+<abbr title="International Organization for Standardization">ISO</abbr>
+/
+
+
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ d’une <code>java.lang.Class</code> ou
 <code>java.lang.reflect.Method</code> peut être obtenu comme suit :</p>
-<div class="codehilite"><pre><span class="n">UML</span> <span class="n">uml</span> <span class="o">=</span> <span class="n">method</span><span class="o">.</span><span class="na">getAnnotation</span><span class="o">(</span><span class="n">UML</span><span class="o">.</span><span class="na">class</span><span class="o">);</span>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">UML</span> <span class="n">uml</span> <span class="o">=</span> <span class="n">method</span><span class="o">.</span><span class="na">getAnnotation</span><span class="o">(</span><span class="n">UML</span><span class="o">.</span><span class="na">class</span><span class="o">);</span>
 <span class="k">if</span> <span class="o">(</span><span class="n">uml</span> <span class="o">!=</span> <span class="kc">null</span><span class="o">)</span> <span class="o">{</span>
     <span class="n">String</span> <span class="n">name</span> <span class="o">=</span> <span class="n">uml</span><span class="o">.</span><span class="na">identifier</span><span class="o">();</span>
-    <span class="c1">// Extraire les métadonnées ici.</span>
-<span class="o">}</span>
-</pre></div>
-
-
+    <span class="c1">// Extraire les métadonnées ici.
+</span><span class="c1"></span><span class="o">}</span></code></pre></div>
 <p>Cette approche est utilisée dans le paquet <code>org.apache.sis.metadata.sql</code> pour fournir une implémentation
 de toutes les interfaces de metadonnées de GeoAPI à partir d’une base de données SQL.</p>
-<h3 id="metadata-unknownClass">Je n’arrive pas à écrire mon implémentation de metadonnée<a class="headerlink" href="#metadata-unknownClass" title="Permanent link">&para;</a></h3>
+<h3 id="metadata-unknownClass">Je n’arrive pas à écrire mon implémentation de metadonnée </h3>
 <p>Les classes données à un marshaller JAXB doivent contenir des annotations JAXB,
 sinon l’exception suivante sera lancée :</p>
-<div class="codehilite"><pre>javax.xml.bind.JAXBException: class MyCustomClass nor any of its super class is known to this context.
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">javax.xml.bind.JAXBException: class MyCustomClass nor any of its super class is known to this context.</code></pre></div>
 <p>La solution de contournement la plus simple est de décorer l’implémentation dans une des implémentations
 fournies dans le paquet <code>org.apache.metadata.iso</code>.
 Toutes les implémentations du SDK fournissent des constructeurs de copies peu profondes pour rendre cela plus simple.
 Il est uniquement nécéssaire de décorer la classes racine, pas les attributs.
 Les valeurs des attributs seront décorées automatiquement au besoin par les adaptateurs JAXB.</p>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
+
+        </article>
+      </section>
     </div>
-  </footer>
-
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
-
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+  </div>
+</div>
+
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
+
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/gdal.html b/gdal.html
index 64123d2..09fceb9 100644
--- a/gdal.html
+++ b/gdal.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Bridge with GDAL</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Bridge with GDAL</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,127 +37,159 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Bridge with GDAL</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>While Apache SIS provides its own map projection engine, some applications may want to also use the Proj.4 library.
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Bridge with GDAL</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>While Apache SIS provides its own map projection engine, some applications may want to also use the Proj.4 library.
 One reason may be to use map projection methods not yet supported by Apache SIS,
 or for getting the exact same numerical results than Proj.4.
 The two libraries can coexist and can be used through the same API,
 provided that prerequisites are meet.</p>
 <p><strong>NOTE: this module has been temporarily retired in Apache SIS 1.0. It needs to be upgraded to Proj version 5 and 6 before new release.</strong></p>
-<div class="toc">
-<ul>
-<li><a href="#prerequisites">Prerequisites</a></li>
-<li><a href="#usage">Usage</a></li>
-<li><a href="#limitations">Limitations</a></li>
-</ul>
-</div>
-<h1 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h1>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#prerequisites">Prerequisites   </a></li>
+    <li><a href="#usage">Usage   </a></li>
+    <li><a href="#limitations">Limitations   </a></li>
+  </ul>
+</nav>
+<h1 id="prerequisites">Prerequisites   </h1>
 <p>Proj.4 needs to be pre-installed; there is no copy embedded in Apache SIS.
 Proj.4 can be installed by package managers on most Linux distributions,
 or with tools like MacPorts on MacOS
 (Windows is not yet supported – see <a href="#limitations">limitations</a>).
 In addition, the <code>sis-gdal</code> module must be present on the classpath.
 Maven projects can use the following dependency in their <code>pom.xml</code> file:</p>
-<div class="codehilite"><pre><span class="nt">&lt;dependencies&gt;</span>
+<div class="highlight"><pre class="chroma"><code class="language-xml" data-lang="xml"><span class="nt">&lt;dependencies&gt;</span>
   <span class="nt">&lt;dependency&gt;</span>
     <span class="nt">&lt;groupId&gt;</span>org.apache.sis.storage<span class="nt">&lt;/groupId&gt;</span>
     <span class="nt">&lt;artifactId&gt;</span>sis-gdal<span class="nt">&lt;/artifactId&gt;</span>
     <span class="nt">&lt;version&gt;</span>0.8<span class="nt">&lt;/version&gt;</span>
   <span class="nt">&lt;/dependency&gt;</span>
-<span class="nt">&lt;/dependencies&gt;</span>
-</pre></div>
-
-
-<h1 id="usage">Usage<a class="headerlink" href="#usage" title="Permanent link">&para;</a></h1>
+<span class="nt">&lt;/dependencies&gt;</span></code></pre></div>
+<h1 id="usage">Usage   </h1>
 <p>For instantiating a coordinate reference system (CRS) backed by Proj.4:</p>
-<div class="codehilite"><pre><span class="n">CoordinateReferenceSystem</span> <span class="n">crs</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">forCode</span><span class="o">(</span><span class="s">&quot;Proj4::+init=epsg:4326&quot;</span><span class="o">);</span>
-</pre></div>
-
-
-<p>Everything after <code>"PROJ4::"</code> is forwarded as-is to the Proj.4 library.
-Note that despite the <code>"epsg"</code> part in above definition string, the CRS created by above method call is <strong>not</strong>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">CoordinateReferenceSystem</span> <span class="n">crs</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">forCode</span><span class="o">(</span><span class="s">&#34;Proj4::+init=epsg:4326&#34;</span><span class="o">);</span></code></pre></div>
+<p>Everything after <code>&quot;PROJ4::&quot;</code> is forwarded as-is to the Proj.4 library.
+Note that despite the <code>&quot;epsg&quot;</code> part in above definition string, the CRS created by above method call is <strong>not</strong>
 conform to EPSG:4326 authoritative definition. The string should rather be understood as a Proj.4-specific code.
 Proj.4 definitions may differ from authoritative definitions in axis order, axis directions or units of measurement.
-To get the authoritative definition, use <code>CRS.forCode("EPSG::4326")</code> instead.</p>
+To get the authoritative definition, use <code>CRS.forCode(&quot;EPSG::4326&quot;)</code> instead.</p>
 <p>For creating a coordinate operation backed by Proj.4, there is nothing special to do;
 we can invoke the same method regardless if the CRS are backed by Proj.4 or Apache SIS.
 The following code will create a transform backed by Proj.4 if <em>both</em> <code>sourceCRS</code> and <code>targetCRS</code>
-were created with <code>CRS.forCode("Proj4::…")</code> calls.
+were created with <code>CRS.forCode(&quot;Proj4::...&quot;)</code> calls.
 Note however that <code>CoordinateOperation</code> backed by Proj.4 does not provide metadata about accuracy or domain of validity.</p>
-<div class="codehilite"><pre><span class="n">CoordinateOperation</span>  <span class="n">op</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">findOperation</span><span class="o">(</span><span class="n">sourceCRS</span><span class="o">,</span> <span class="n">targetCRS</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span>
+<div class="highlight"><pre class="chroma"><code class="language-java" data-lang="java"><span class="n">CoordinateOperation</span>  <span class="n">op</span> <span class="o">=</span> <span class="n">CRS</span><span class="o">.</span><span class="na">findOperation</span><span class="o">(</span><span class="n">sourceCRS</span><span class="o">,</span> <span class="n">targetCRS</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span>
 <span class="n">MathTransform</span>        <span class="n">mt</span> <span class="o">=</span> <span class="n">op</span><span class="o">.</span><span class="na">getMathTransform</span><span class="o">();</span>
 <span class="n">DirectPosition</span> <span class="n">sourcePt</span> <span class="o">=</span> <span class="k">new</span> <span class="n">DirectPosition2D</span><span class="o">(</span><span class="n">x</span><span class="o">,</span> <span class="n">y</span><span class="o">);</span>
-<span class="n">DirectPosition</span> <span class="n">targetPt</span> <span class="o">=</span> <span class="n">mt</span><span class="o">.</span><span class="na">transform</span><span class="o">(</span><span class="n">sourcePt</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span>
-</pre></div>
-
-
+<span class="n">DirectPosition</span> <span class="n">targetPt</span> <span class="o">=</span> <span class="n">mt</span><span class="o">.</span><span class="na">transform</span><span class="o">(</span><span class="n">sourcePt</span><span class="o">,</span> <span class="kc">null</span><span class="o">);</span></code></pre></div>
 <p>To verify if a <code>MathTransform</code> instance is implemented by Proj.4 or by Apache SIS,
 one can look at the <em>Well Known Text</em> (WKT) representation as given by <code>System.out.println(mt)</code>.
 If the transform is backed by Apache SIS, the output may show any of the parameters listed
 in the <a href="tables/CoordinateOperationMethods.html">coordinate operation methods table</a>.
 But if the transform is backed by Proj.4, then the transform will always be described
-by the <code>"pj_transform"</code> method with exactly two parameters: <code>"srcdefn"</code> and <code>"dstdefn"</code>:</p>
-<div class="codehilite"><pre>PARAM_MT[&quot;pj_transform&quot;,
-  PARAMETER[&quot;srcdefn&quot;, &quot;+proj=…&quot;],
-  PARAMETER[&quot;dstdefn&quot;, &quot;+proj=…&quot;]]
-</pre></div>
-
-
+by the <code>&quot;pj_transform&quot;</code> method with exactly two parameters: <code>&quot;srcdefn&quot;</code> and <code>&quot;dstdefn&quot;</code>:</p>
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">PARAM_MT[&#34;pj_transform&#34;,
+  PARAMETER[&#34;srcdefn&#34;, &#34;+proj=...&#34;],
+  PARAMETER[&#34;dstdefn&#34;, &#34;+proj=...&#34;]]</code></pre></div>
 <p>See the <a href="apidocs/org/apache/sis/storage/gdal/package-summary.html">Javadoc</a> for more information.</p>
-<h1 id="limitations">Limitations<a class="headerlink" href="#limitations" title="Permanent link">&para;</a></h1>
+<h1 id="limitations">Limitations   </h1>
 <p>Current Apache SIS version can create CRS backed by Proj.4 only when SIS can map Proj.4 parameters to EPSG parameters.
 For example the Proj.4 <code>+x_0=</code> parameter is often (but not always) mapped to EPSG <em>False easting</em> parameter.
 Future SIS versions may relax the requirement for such mapping.</p>
 <p>Current Apache SIS version supports only Linux and MacOS platforms.
 A future version will add Windows support.</p>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
-    </div>
-  </footer>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+        </article>
+      </section>
+    </div>
+  </div>
+</div>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
+
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/index.html b/index.html
index 970e937..527eb2d 100644
--- a/index.html
+++ b/index.html
@@ -1,72 +1,36 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>The Apache SIS™ library</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+	<meta name="generator" content="Hugo 0.80.0" />
+  
 
-    
+  <title>Apache SIS - The Apache SIS™ library</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,31 +38,69 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">The Apache SIS™ library</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>Apache Spatial Information System (SIS) is a free software, Java language library for developing geospatial applications.
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">The Apache SIS™ library</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>Apache Spatial Information System (SIS) is a free software, Java language library for developing geospatial applications.
 SIS provides data structures for geographic features and associated metadata along with methods to manipulate those data structures.
 The library is an implementation of <a href="http://www.geoapi.org/">GeoAPI 3.0.1</a> interfaces and can be used for desktop or server applications.</p>
 <p>The SIS metadata module forms the base of the library and enables the creation of metadata objects which comply with the model of OGC/ISO international standards.
@@ -108,40 +110,44 @@ The SIS storage modules provide a common approach to the reading and writing of
 applicable to simple imagery as to many dimensional data structures.</p>
 <p>Some Apache SIS features are:</p>
 <ul>
-<li>Geographic metadata (ISO 19115-1:2014)<ul>
+<li>Geographic metadata (ISO 19115-1:2014)
+<ul>
 <li>Read from or written to ISO 19115-3:2016 (current standard) or ISO 19139:2007 (older standard) compliant XML documents.</li>
 <li>Read from netCDF, GeoTIFF, Landsat, GPX and Moving Feature CSV encoding.</li>
 <li>Automatic conversions between the metadata model published in 2003 and the revision published in 2014.</li>
 </ul>
 </li>
-<li>Referencing by coordinates (ISO 19111:2007)<ul>
+<li>Referencing by coordinates (ISO 19111:2007)
+<ul>
 <li>Well Known Text (WKT) version 1 and 2 (ISO 19162:2015).</li>
 <li>Geographic Markup Language (GML) version 3.2 (ISO 19136:2007).</li>
 <li><a href="epsg.html">EPSG geodetic dataset</a> for geodetic definitions and for coordinate operations.
-  See the list of <a href="tables/CoordinateReferenceSystems.html">supported coordinate reference systems</a>.</li>
+See the list of <a href="tables/CoordinateReferenceSystems.html">supported coordinate reference systems</a>.</li>
 <li>Mercator, Transverse Mercator, Lambert Conic Conformal, stereographic and more map projections.
-  See the list of <a href="tables/CoordinateOperationMethods.html">supported operation methods</a>.</li>
+See the list of <a href="tables/CoordinateOperationMethods.html">supported operation methods</a>.</li>
 </ul>
 </li>
-<li>Referencing by identifiers (ISO 19112:2003)<ul>
+<li>Referencing by identifiers (ISO 19112:2003)
+<ul>
 <li>Geohashes (a simple encoding of geographic coordinates into short strings of letters and digits).</li>
 <li>Military Grid Reference System (MGRS), also used for some civilian uses.</li>
 </ul>
 </li>
-<li>Units of measurement<ul>
+<li>Units of measurement
+<ul>
 <li>Implementation of <a href="https://www.jcp.org/aboutJava/communityprocess/final/jsr363/index.html">JSR-363</a>
-  with parsing, formating and unit conversion functionalities.</li>
+with parsing, formating and unit conversion functionalities.</li>
 </ul>
 </li>
 </ul>
-<h2 id="user">Using Apache SIS<a class="headerlink" href="#user" title="Permanent link">&para;</a></h2>
+<h2 id="user">Using Apache SIS   </h2>
 <p>The latest SIS release is 1.0, released September 2019.
 Apache SIS requires Java 10 or higher for building, but can be executed on Java 8 or higher.
 If using Java 8 Runtime Environment, nothing else is needed since Java 8 includes JAXB.
 If using Java 9 or higher, one of the following configurations is needed
 (those extra configurations are temporary until support for Java 8 will be dropped in a future SIS version):</p>
 <ul>
-<li>"<code>--add-modules java.xml.bind,java.xml.ws.annotation</code>" option (available with Java 9 or 10 only) added to the <code>java</code> command</li>
+<li>&ldquo;<code>--add-modules java.xml.bind,java.xml.ws.annotation</code>&rdquo; option (available with Java 9 or 10 only) added to the <code>java</code> command</li>
 <li>or JAXB dependency added from Glassfish or Jakarata projects. See <a href="downloads.html#maven">Maven coordinates</a>.</li>
 </ul>
 <p>The EPSG geodetic dataset is optional for licensing reasons, but recommended.
@@ -156,7 +162,7 @@ However a command-line tool is provided for allowing users to experiment some SI
 <li><a href="command-line.html">Command-line interface</a> for an overview of the command-line tool.</li>
 <li><a href="code-patterns.html">Recommended code patterns</a> for writing more robust applications with Apache SIS.</li>
 </ul>
-<h2 id="developer">Developing Apache SIS<a class="headerlink" href="#developer" title="Permanent link">&para;</a></h2>
+<h2 id="developer">Developing Apache SIS   </h2>
 <p>Following links are for those who wish to contribute to Apache SIS:</p>
 <ul>
 <li><a href="contributor.html">New contributor</a>: background knowledge.</li>
@@ -166,33 +172,39 @@ However a command-line tool is provided for allowing users to experiment some SI
 <li><a href="http://issues.apache.org/jira/browse/SIS">Issue tracking</a>: JIRA.</li>
 <li><a href="release-management.html">Release management</a> (for release managers)</li>
 <li><a href="site-management.html">Web site management</a> (for release managers and site maintainers)</li>
-<li><a href="http://cwiki.apache.org/confluence/display/SIS">SIS Wiki</a> for "drawing board" and roadmap.</li>
+<li><a href="http://cwiki.apache.org/confluence/display/SIS">SIS Wiki</a> for &ldquo;drawing board&rdquo; and roadmap.</li>
 </ul>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
+
+        </article>
+      </section>
     </div>
-  </footer>
+  </div>
+</div>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/index.xml b/index.xml
new file mode 100644
index 0000000..1317bd9
--- /dev/null
+++ b/index.xml
@@ -0,0 +1,172 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <title>The Apache SIS™ library on Apache SIS</title>
+    <link>https://sis.apache.org/</link>
+    <description>Recent content in The Apache SIS™ library on Apache SIS</description>
+    <generator>Hugo -- gohugo.io</generator>
+    <language>en</language><atom:link href="https://sis.apache.org/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Apache SIS downloads</title>
+      <link>https://sis.apache.org/downloads.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/downloads.html</guid>
+      <description>Apache SIS 1.0 is now available. See the release notes for a list of changes since the previous version.
+Apache SIS releases are available under the Apache License, Version 2.0. See the NOTICE file contained in each release artifact for applicable copyright attribution notices.
+ Download ZIP files   Verify signatures    Download as a Maven dependency   Include non-free resources      Download ZIP files  Apache SIS is distributed in the form of Java source code in a multi-modules Apache Maven project.</description>
+    </item>
+    
+    <item>
+      <title>Apache SIS team</title>
+      <link>https://sis.apache.org/team-list.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/team-list.html</guid>
+      <description>Project Management Committee (PMC)  The Project Management Committee (PMC) is the group of people with formal oversight of the project.
+ Adam Estrada Andrew Hart Charitha Madusanka Gregory D. Reddin Johann Sorel Joseph F. White Marc Le Bihan Martin Desruisseaux Nga Thien Chung Olivier Nouguier Patrick O&amp;rsquo;Leary Paul Michael Ramirez Peter Karich Ross Laidlaw Sean William McCleese Suresh Marru Travis Pinney  Committers  Committers are peoples with write access to the source code repository.</description>
+    </item>
+    
+    <item>
+      <title>Bridge with GDAL</title>
+      <link>https://sis.apache.org/gdal.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/gdal.html</guid>
+      <description>While Apache SIS provides its own map projection engine, some applications may want to also use the Proj.4 library. One reason may be to use map projection methods not yet supported by Apache SIS, or for getting the exact same numerical results than Proj.4. The two libraries can coexist and can be used through the same API, provided that prerequisites are meet.
+NOTE: this module has been temporarily retired in Apache SIS 1.</description>
+    </item>
+    
+    <item>
+      <title>Build from source</title>
+      <link>https://sis.apache.org/build.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/build.html</guid>
+      <description>Apache SIS is built by Maven. For installing the JAR files in the local Maven repository, execute the following command from the SIS project root:
+mvn install For signing the artifacts and producing distribution files (apache-sis-bin.zip and apache-sis.oxt), execute the following command. Note that it requires an OpenPGP (Open Pretty Good Privacy) software for cryptography signatures (more information on the release management setup page):
+mvn install --activate-profiles apache-release The remaining of this page provides more advanced tips for SIS developers.</description>
+    </item>
+    
+    <item>
+      <title>Checkout source code</title>
+      <link>https://sis.apache.org/source.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/source.html</guid>
+      <description>Apache SIS source code is maintained using Git version control, completed by optional data maintained using Subversion version control. Optional data include in particular the EPSG geodetic dataset, which is subject to licensing terms different than Apache ones. This page describes two ways to checkout Apache SIS source code:
+ A basic checkout with only the main repository, the most stable branch, and no configuration requirement. A more advanced configuration for active SIS developments, using uncommitted (for now) API and including optional data for more extensive tests.</description>
+    </item>
+    
+    <item>
+      <title>Command-line interface</title>
+      <link>https://sis.apache.org/command-line.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/command-line.html</guid>
+      <description>A command-line interface is provided for extracting information from data files or authority codes, and for performing coordinate operations. That command-line tool is provided for allowing users to experiment some Apache SIS functionalities without writing Java code. For each example, key Java APIs are listed for allowing users to reproduce the functionality in their own application.
+ Installation   Optional dependencies    Usage  Examples   Print Coordinate Reference Systems (CRS) definition  Getting a verified EPSG identifier from a Coordinate Reference System  Performing coordinate conversions or transformations  Extracting ISO 19115 Metadata    Performance consideration    Installation  Select &amp;ldquo;Apache SIS 1.</description>
+    </item>
+    
+    <item>
+      <title>Frequently asked questions</title>
+      <link>https://sis.apache.org/faq.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/faq.html</guid>
+      <description>This page lists some Frequently Asked Questions (FAQ) when using Apache SIS. This FAQ is also available in French.
+ Referencing   Getting started   How do I transform a coordinate?  Which map projections are supported?  What is the axis order issue and how is it addressed?    Coordinate Reference Systems   How do I instantiate a Universal Transverse Mercator (UTM) projection?  How do I instantiate a Google projection?</description>
+    </item>
+    
+    <item>
+      <title>How to use EPSG geodetic dataset</title>
+      <link>https://sis.apache.org/epsg.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/epsg.html</guid>
+      <description>The EPSG geodetic dataset is a de-facto standard providing thousands of Coordinate Reference System (CRS) definitions together with information about how to perform coordinate operations, their accuracies and their domains of validity. The EPSG dataset is owned and maintained by the International Association of Oil &amp;amp; Gas producers. Usage of EPSG dataset with Apache SIS is optional but strongly recommended: without that geodetic dataset, only a small subset of C [...]
+    </item>
+    
+    <item>
+      <title>Mailing lists</title>
+      <link>https://sis.apache.org/mail-lists.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/mail-lists.html</guid>
+      <description>We welcome you to join mailing lists and let us know about your thoughts or ideas about Apache SIS. Everyone can subscribe, but note that all emails sent to those lists are archived and publicly readable on the web. See Public Forum Archive Policy for more information.
+Geospatial Mailing List  This is where peoples can ask questions or discuss about geospatial topics that are not specific to Apache SIS. Those topics can include questions about international standards, participation to upcomming geospatial events or collaboration with communities outside Apache.</description>
+    </item>
+    
+    <item>
+      <title>New contributor</title>
+      <link>https://sis.apache.org/contributor.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/contributor.html</guid>
+      <description>Improving and extending SIS requires extensive knowledge of geographic information science, object oriented programming, the Java language, and of the library itself. Contributors should expect that they will need to learn a great deal before being able to become productive. However, the effort required to become productive should improve the contributor&amp;rsquo;s understanding and knowledge of geographic information systems, of geodetic and geographic science, and o [...]
+This document is expected to evolve as the SIS project develops its own mode of operation.</description>
+    </item>
+    
+    <item>
+      <title>Questions fréquentes (FAQ)</title>
+      <link>https://sis.apache.org/faq_fr.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/faq_fr.html</guid>
+      <description>Cette page liste quelques questions fréquemment posées à propos de Apache SIS. Son contenu est traduit de la page de FAQ en anglais.
+ Géoréférencement   Pour bien commencer   Comment transformer une coordonnée ?  Quelles projections sont supportées ?  Qu’est ce que le problème d’ordre des axes et comment est il abordé ?    Systèmes de Référence des Coordonnées   Comment créer une projection de type Transverse Universelle de Mercator (UTM) ?</description>
+    </item>
+    
+    <item>
+      <title>Recommended code patterns</title>
+      <link>https://sis.apache.org/code-patterns.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/code-patterns.html</guid>
+      <description>This page lists some recommended code pattern for developing or using Apache SIS.
+ Referencing   Never explicitely swap ordinates for axis order    Coverages   Georeference images with affine transforms, not bounding boxes    International   Specify timezone  Replace underscores by spaces before sorting  Loop over character sequences using code points    Logging    Referencing  Recommended code pattern when using the sis-referencing module.</description>
+    </item>
+    
+    <item>
+      <title>Release management</title>
+      <link>https://sis.apache.org/release-management.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/release-management.html</guid>
+      <description>This page describes how to create and deploy the SIS Maven artifacts, binary bundle, javadoc and list of API changes. The Release FAQ page describes the foundation wide policies. Instructions on this page describe the steps specific to SIS (we do not use the mvn release command). The intended audiences are SIS release managers.
+ Configure   Directory layout    Review project status before branching   Update the list of supported CRS  Prepare release notes    Create release branch   Test branch extensively  Prepare non-free resources  Integration test    Deploy Maven artifacts   Verify and close the Nexus release artifacts  Test the Nexus release artifacts    Stage the source, binary and javadoc artifacts   Initialize the distribution directory  Sign and commit  Update online Javadoc  Test the release    Prepare [...]
+    </item>
+    
+    <item>
+      <title>Release management setup</title>
+      <link>https://sis.apache.org/release-management-setup.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/release-management-setup.html</guid>
+      <description>The following instructions need to be done only once by new release managers, or when configuring a new machine for performing the releases. If those steps have already been done, jump directly to the Release Management page.
+ Directory layout  Generate GPG key   Web of trust    Maven Configuration &amp;amp; Nexus Setup    Directory layout  The steps described in the release management page assume the following directory layout.</description>
+    </item>
+    
+    <item>
+      <title>Site management</title>
+      <link>https://sis.apache.org/site-management.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/site-management.html</guid>
+      <description>This page explains how the Apache SIS web site is created and how to update the site. The intended audiences are SIS release managers and SIS web site maintainers.
+General documentation about Apache Content Management System (CMS) can be found in the CMS reference page. The remaining of this page is specific to the SIS project.
+ Directory layout  Content  Style sheets  Updating bootstrap      Directory layout  The source files for the Apache SIS web site can be fetched from Subversion using the following command:</description>
+    </item>
+    
+    <item>
+      <title>Source code</title>
+      <link>https://sis.apache.org/coding-conventions.html</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://sis.apache.org/coding-conventions.html</guid>
+      <description>This page describes some coding conventions applied in Apache SIS development.
+ License header  Naming convention   Internal packages  Substitution for non-existent classes    Code formatting   Import statements  Spaces and line length  Brackets  Member declarations  Exceptions to coding conventions    Documentation formatting   Javadoc annotations  HTML elements   Paragraphs  Javadoc CSS    MathML elements      License header  All Java source files (*.</description>
+    </item>
+    
+  </channel>
+</rss>
diff --git a/mail-lists.html b/mail-lists.html
index 71daec3..4a041a7 100644
--- a/mail-lists.html
+++ b/mail-lists.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Mailing lists</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Mailing lists</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,34 +37,72 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Mailing lists</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>We welcome you to join mailing lists and let us know about your thoughts or ideas about Apache SIS.
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Mailing lists</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>We welcome you to join mailing lists and let us know about your thoughts or ideas about Apache SIS.
 Everyone can subscribe, but note that all emails sent to those lists are archived and publicly readable on the web.
 See <a href="http://www.apache.org/foundation/public-archives.html">Public Forum Archive Policy</a> for more information.</p>
-<h2 id="geospatial">Geospatial Mailing List<a class="headerlink" href="#geospatial" title="Permanent link">&para;</a></h2>
+<h2 id="geospatial">Geospatial Mailing List   </h2>
 <p>This is where peoples can ask questions or discuss about geospatial topics that are not specific to Apache SIS.
 Those topics can include questions about international standards, participation to upcomming geospatial events
 or collaboration with communities outside Apache.</p>
@@ -109,72 +110,82 @@ or collaboration with communities outside Apache.</p>
 <li>Subscribe: <a href="mailto:geospatial-subscribe@apache.org">geospatial-subscribe@apache.org</a></li>
 <li>Post (after subscription): <a href="mailto:geospatial@apache.org">geospatial@apache.org</a></li>
 <li>Unsubscribe: <a href="mailto:geospatial-unsubscribe@apache.org">geospatial-unsubscribe@apache.org</a></li>
-<li>Archives:<ul>
+<li>Archives:
+<ul>
 <li><a href="https://lists.apache.org/list.html?geospatial@apache.org">Pony mail</a></li>
 </ul>
 </li>
 </ul>
-<h2 id="user">Apache SIS User Mailing List<a class="headerlink" href="#user" title="Permanent link">&para;</a></h2>
+<h2 id="user">Apache SIS User Mailing List   </h2>
 <p>This is where users can ask questions about how to use SIS.</p>
 <ul>
 <li>Subscribe: <a href="mailto:user-subscribe@sis.apache.org">user-subscribe@sis.apache.org</a></li>
 <li>Post (after subscription): <a href="mailto:user@sis.apache.org">user@sis.apache.org</a></li>
 <li>Unsubscribe: <a href="mailto:user-unsubscribe@sis.apache.org">user-unsubscribe@sis.apache.org</a></li>
-<li>Archives:<ul>
+<li>Archives:
+<ul>
 <li><a href="https://lists.apache.org/list.html?user@sis.apache.org">Pony mail</a></li>
 <li><a href="http://mail-archives.apache.org/mod_mbox/sis-user/">Apache</a></li>
 </ul>
 </li>
 </ul>
-<h2 id="developer">Apache SIS Developer Mailing List<a class="headerlink" href="#developer" title="Permanent link">&para;</a></h2>
+<h2 id="developer">Apache SIS Developer Mailing List   </h2>
 <p>This is where the community hangs out and SIS development happens.</p>
 <ul>
 <li>Subscribe: <a href="mailto:dev-subscribe@sis.apache.org">dev-subscribe@sis.apache.org</a></li>
 <li>Post (after subscription): <a href="mailto:dev@sis.apache.org">dev@sis.apache.org</a></li>
 <li>Unsubscribe: <a href="mailto:dev-unsubscribe@sis.apache.org">dev-unsubscribe@sis.apache.org</a></li>
-<li>Archives:<ul>
+<li>Archives:
+<ul>
 <li><a href="https://lists.apache.org/list.html?dev@sis.apache.org">Pony mail</a></li>
 <li><a href="http://mail-archives.apache.org/mod_mbox/sis-dev/">Apache</a></li>
 </ul>
 </li>
 </ul>
-<h2 id="commit">Apache SIS Commit Mailing List<a class="headerlink" href="#commit" title="Permanent link">&para;</a></h2>
+<h2 id="commit">Apache SIS Commit Mailing List   </h2>
 <p>This is where the community receives automated notifications of
 any changes to the sis code and documentation.</p>
 <ul>
 <li>Subscribe: <a href="mailto:commits-subscribe@sis.apache.org">commits-subscribe@sis.apache.org</a></li>
 <li>Unsubscribe: <a href="mailto:commits-unsubscribe@sis.apache.org">commmits-unsubscribe@sis.apache.org</a></li>
-<li>Archives:<ul>
+<li>Archives:
+<ul>
 <li><a href="https://lists.apache.org/list.html?commits@sis.apache.org">Pony mail</a></li>
 <li><a href="http://mail-archives.apache.org/mod_mbox/sis-commits/">Apache</a></li>
 </ul>
 </li>
 </ul>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
+
+        </article>
+      </section>
     </div>
-  </footer>
+  </div>
+</div>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/openoffice/en/formula.html b/openoffice/en/formula.html
index f7d1979..85a8a9e 100644
--- a/openoffice/en/formula.html
+++ b/openoffice/en/formula.html
@@ -32,7 +32,7 @@
       Apache <abbr title="Spatial Information System">SIS</abbr> add-in for Open/LibreOffice
       provides new functions in two categories: <i>Text</i> and <i>Add-in</i>.
       Most <i>Add-in</i> functions expect one or two Coordinate Reference Systems (<abbr>CRS</abbr>) identified
-      by a code from the <a href="http://www.epsg.org/"><abbr>EPSG</abbr> geodetic dataset</a> or other authority.
+      by a code from the <a href="https://epsg.org/"><abbr>EPSG</abbr> geodetic dataset</a> or other authority.
       The <abbr>EPSG</abbr> geodetic dataset defines more then 6000 coordinate reference systems in use around the Earth,
       together with methods and parameters for performing coordinate operations from one system to another system.
       Some add-in functions fetch information about a given coordinate reference system,
@@ -42,7 +42,7 @@
       The first code identifies the source reference system and the second code identifies the target reference system.
       The operation is defined by the algorithm transforming coordinates from the source system to the target system.
     </p><p>
-      Authoritative definitions of <abbr>EPSG</abbr> codes can be browsed on-line on <a href="http://epsg-registry.org/"><abbr>EPSG</abbr> registry</a>.
+      Authoritative definitions of <abbr>EPSG</abbr> codes can be browsed on-line on <a href="https://epsg.org/"><abbr>EPSG</abbr> repository</a>.
       This add-in for Open/LibreOffice contains a copy (in binary format) of <abbr>EPSG</abbr> database for convenience,
       but note that its use <a href="https://epsg.org/terms-of-use.html">is subject to conditions</a>.
       Apache <abbr>SIS</abbr> extends this list with a few codes defined outside <abbr>EPSG</abbr>, in particular codes defined by <abbr title="Open Geospatial Consortium">OGC</abbr>.
diff --git a/openoffice/en/install.html b/openoffice/en/install.html
index 85964a6..d805e7a 100644
--- a/openoffice/en/install.html
+++ b/openoffice/en/install.html
@@ -59,7 +59,7 @@
         and save the file in any directory.
         In Open/LibreOffice menus, select <i>Tools</i> → <i>Extensions manager</i>.
         Push the <i>Add…</i> button and select the downloaded <code>apache-sis.oxt</code> file.
-        The installer will ask user to accept Apache 2 license and the <a href="http://www.epsg.org/"><abbr>EPSG</abbr> terms of use</a>.
+        The installer will ask user to accept Apache 2 license and the <a href="https://epsg.org/"><abbr>EPSG</abbr> terms of use</a>.
         After installation, in may be necessary to restart Open/LibreOffice before the changes become effective.
         If a quick-start icon is present in the tasks bar, it should be closed before to restart Open/LibreOffice.
       </p><p>
diff --git a/openoffice/fr/formula.html b/openoffice/fr/formula.html
index 4301b30..dce4c4b 100644
--- a/openoffice/fr/formula.html
+++ b/openoffice/fr/formula.html
@@ -33,7 +33,7 @@
       fournit de nouvelles fonctions réparties dans 2 catégories : <i>Texte</i> et <i>Add-in</i>.
       Le principe de base des fonctions de la catégorie <i>Add-in</i> est le suivant :
       chaque système de référence des coordonnées est identifié par un code numérique de la
-      <a href="http://www.epsg.org/">base de données géodesiques <abbr>EPSG</abbr></a> ou d’une autre autorité.
+      <a href="https://epsg.org/">base de données géodesiques <abbr>EPSG</abbr></a> ou d’une autre autorité.
       La base de donnnées <abbr>EPSG</abbr> recense plus de 6000 systèmes en usage sur la planète,
       ainsi que des paramètres permettant d’effectuer des transformations d’un système vers un autre.
       Certaines fonctions permettent d’obtenir des informations sur un système de référence en particulier,
@@ -44,7 +44,7 @@
       Le premier code définit le système source, et le second code définit le système destination.
       L’opération est définie par l’algorithme permettant de passer des coordonnées du système source vers celles du système destination.
     </p><p>
-      Les définitions officielles des codes <abbr>EPSG</abbr> peuvent être explorées en-ligne avec le <a href="http://epsg-registry.org/">registre <abbr>EPSG</abbr></a>.
+      Les définitions officielles des codes <abbr>EPSG</abbr> peuvent être explorées en-ligne avec le <a href="https://epsg.org/">registre <abbr>EPSG</abbr></a>.
       Cette extension pour Open/LibreOffice est toutefois livrée avec sa propre copie (dans un format binaire) de la base de données <abbr>EPSG</abbr>,
       dont <a href="https://epsg.org/terms-of-use.html">l’utilisation est soumise à des conditions</a>.
       Apache <abbr>SIS</abbr> étend cette liste avec quelques codes définis en dehors d’<abbr>EPSG</abbr>, notamment par l’<abbr title="Open Geospatial Consortium">OGC</abbr>.
diff --git a/openoffice/fr/install.html b/openoffice/fr/install.html
index 0b83ab5..b2bcdf3 100644
--- a/openoffice/fr/install.html
+++ b/openoffice/fr/install.html
@@ -61,7 +61,7 @@
         Dans Open/LibreOffice, sélectionnez le menu <i>Outils</i> → <i>Gestionnaire des extensions</i>.
         Appuyez sur le bouton <i>Ajouter…</i> et sélectionnez le fichier <code>apache-sis.oxt</code> qui a été téléchargé.
         L’installateur vous demandera d’accepter la licence Apache 2 ainsi que les conditions d’utilisation
-        de la <a href="http://www.epsg.org/">base de données géodésiques <abbr>EPSG</abbr></a>.
+        de la <a href="https://epsg.org/">base de données géodésiques <abbr>EPSG</abbr></a>.
         Après installation, il peut être nécessaire de redémarrer Open/LibreOffice pour qu’elle soit prise en compte.
         Si un icône de démarrage rapide apparaît dans la barre des tâches, il doit être fermé lui aussi avant de relancer Open/LibreOffice.
       </p><p>
diff --git a/release-management-setup.html b/release-management-setup.html
index 70d7785..76b2379 100644
--- a/release-management-setup.html
+++ b/release-management-setup.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Release management setup</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Release management setup</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,48 +37,87 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Release management setup</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>The following instructions need to be done only once by new release managers,
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Release management setup</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>The following instructions need to be done only once by new release managers,
 or when configuring a new machine for performing the releases.
 If those steps have already been done, jump directly to the <a href="release-management.html">Release Management</a> page.</p>
-<div class="toc">
-<ul>
-<li><a href="#directory-layout">Directory layout</a></li>
-<li><a href="#generate-key">Generate GPG key</a><ul>
-<li><a href="#trust">Web of trust</a></li>
-</ul>
-</li>
-<li><a href="#maven">Maven Configuration &amp; Nexus Setup</a></li>
-</ul>
-</div>
-<h1 id="directory-layout">Directory layout<a class="headerlink" href="#directory-layout" title="Permanent link">&para;</a></h1>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#directory-layout">Directory layout   </a></li>
+    <li><a href="#generate-key">Generate GPG key   </a>
+      <ul>
+        <li><a href="#trust">Web of trust   </a></li>
+      </ul>
+    </li>
+    <li><a href="#maven">Maven Configuration &amp; Nexus Setup   </a></li>
+  </ul>
+</nav>
+<h1 id="directory-layout">Directory layout   </h1>
 <p>The steps described in the <em>release management</em> page assume the following directory layout.
 Some directories are Git checkout, other are ordinary directories. Any other layout can be used.
 However in the later case, all relative paths in the <em>release management</em> page will need to be adjusted accordingly.</p>
-<div class="codehilite"><pre>&lt;any root directory for SIS&gt;
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">&lt;any root directory for SIS&gt;
 ├─ master
 ├─ non-free
 │  ├─ sis-epsg
@@ -124,21 +126,15 @@ However in the later case, all relative paths in the <em>release management</em>
 │  ├─ distribution
 │  └─ integration-test
 │     └─ maven
-└─ site
-</pre></div>
-
-
+└─ site</code></pre></div>
 <p>Create the above directory structure as below:</p>
-<div class="codehilite"><pre>mkdir releases
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mkdir releases
 git clone    https://gitbox.apache.org/repos/asf/sis.git master
 svn checkout https://svn.apache.org/repos/asf/sis/data/non-free
 svn checkout https://svn.apache.org/repos/asf/sis/site/trunk site
 svn checkout https://svn.apache.org/repos/asf/sis/release-test releases/integration-test
-svn checkout https://dist.apache.org/repos/dist/dev/sis releases/distribution
-</pre></div>
-
-
-<h1 id="generate-key">Generate GPG key<a class="headerlink" href="#generate-key" title="Permanent link">&para;</a></h1>
+svn checkout https://dist.apache.org/repos/dist/dev/sis releases/distribution</code></pre></div>
+<h1 id="generate-key">Generate GPG key   </h1>
 <p>The releases have to be signed by public key cryptography signatures.
 Detailed instructions about why releases have to be signed are provided on the <a href="http://www.apache.org/dev/release-signing.html">Release Signing</a> page.
 The standard used is OpenPGP (<em>Open Pretty Good Privacy</em>), and a popular software implementation of that standard is GPG (<em>GNU Privacy Guard</em>).
@@ -146,101 +142,71 @@ The <a href="http://www.apache.org/dev/openpgp.html">OpenPGP instructions</a> li
 The following steps provide a summary:</p>
 <p>Edit the <code>~/.gnupg/gpg.conf</code> configuration file and add the following configuration options,
 or edit the existing values if any:</p>
-<div class="codehilite"><pre>personal-digest-preferences SHA512
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">personal-digest-preferences SHA512
 cert-digest-algo SHA512
-default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
-</pre></div>
-
-
+default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed</code></pre></div>
 <p>If a private key already exists for emails or other purposes, it may be a good idea to keep that key as the default one.
 Add or modify the following line in the <code>gpg.conf</code> file, replacing <code>&lt;previous_key_id&gt;</code> by the existing key identifier
 (a value like <code>621CC013</code>):</p>
-<div class="codehilite"><pre>default-key &lt;previous_key_id&gt;
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">default-key &lt;previous_key_id&gt;</code></pre></div>
 <p>Generate 4096 bits RSA key pair using the following command-line. GPG will prompts for various informations.
 The list below the command suggests some values, keeping in mind that the new key should be used only for
 signing Apache software packages - not for daily emails.</p>
-<div class="codehilite"><pre>gpg --gen-key
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">gpg --gen-key</code></pre></div>
 <ul>
 <li>Kind of key: RSA and RSA (default). Do not create DSA key.</li>
 <li>Key size: 4096 bits.</li>
 <li>Validity time: 0 (key does not expire).</li>
-<li>Real name: the developer's name.</li>
-<li>Email address: developer's email address at <code>@apache.org</code>.</li>
-<li>Comment: "CODE SIGNING KEY".</li>
+<li>Real name: the developer&rsquo;s name.</li>
+<li>Email address: developer&rsquo;s email address at <code>@apache.org</code>.</li>
+<li>Comment: &ldquo;CODE SIGNING KEY&rdquo;.</li>
 <li>Passphrase: please choose a strong one.</li>
 </ul>
-<p>Verify the key information (replace <em>Real Name</em> by the above-cited developer's name, keeping quotes in the command below).
+<p>Verify the key information (replace <em>Real Name</em> by the above-cited developer&rsquo;s name, keeping quotes in the command below).
 Note the key identifier, which is a value like <code>74383E9D</code>. This key identifier will be needed for the next steps.</p>
-<div class="codehilite"><pre>gpg --list-sigs <span class="s2">&quot;Real Name&quot;</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">gpg --list-sigs <span class="s2">&#34;Real Name&#34;</span></code></pre></div>
 <p>Sends the public key to a keys server (replace <code>&lt;key_id&gt;</code> by the above-cited key identifier).
 The default GPG configuration sends the key to <code>hkp://keys.gnupg.net</code>.
 Note that while there is many key servers, most of them synchronize changes with each other,
 so a key uploaded to one should be disseminated to the rest.</p>
-<div class="codehilite"><pre>gpg --send-key &lt;key_id&gt;
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">gpg --send-key &lt;key_id&gt;</code></pre></div>
 <p>The key publication can be verified by going on the <a href="http://pgp.mit.edu">MIT server</a>,
-then entering the developer's "Real Name" in the <em>Search String</em> field.
+then entering the developer&rsquo;s &ldquo;Real Name&rdquo; in the <em>Search String</em> field.
 It may take a few hours before the published key is propagated.</p>
 <p>Generate a revocation certificate. This is not for immediate use, but generating the certificate now
 is a safety in case the passphrase is lost. Keep the revocation certificate in a safe place,
 preferably on a removable device.</p>
-<div class="codehilite"><pre>gpg --output revocation_certificate.asc --gen-revoke &lt;key_id&gt;
-</pre></div>
-
-
-<h2 id="trust">Web of trust<a class="headerlink" href="#trust" title="Permanent link">&para;</a></h2>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">gpg --output revocation_certificate.asc --gen-revoke &lt;key_id&gt;</code></pre></div>
+<h2 id="trust">Web of trust   </h2>
 <p>Have the key signed by at least three Apache commiters. This can be done by executing the following commands on
-the machine of the other Apache commiter, where <code>&lt;key_to_use&gt;</code> is the identifier of the other commiter's key.
+the machine of the other Apache commiter, where <code>&lt;key_to_use&gt;</code> is the identifier of the other commiter&rsquo;s key.
 Those operation should preferably be done in some event where the commiters can meet face-to-face.
 The other commiter should verify that the <code>gpg --fingerprint</code> command output matches the fingerprint of the key to sign.</p>
-<div class="codehilite"><pre>gpg --recv-keys &lt;key_id&gt;
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">gpg --recv-keys &lt;key_id&gt;
 gpg --fingerprint &lt;key_id&gt;
 gpg --default-key &lt;key_to_use&gt; --sign-key &lt;key_id&gt;
-gpg --send-key &lt;key_id&gt;
-</pre></div>
-
-
+gpg --send-key &lt;key_id&gt;</code></pre></div>
 <p>The above-cited <em>Release Signing</em> page provides more instructions.
 Then, the signed public key shall be appended to the <code>KEYS</code> file on the <a href="https://gitbox.apache.org/repos/asf?p=sis.git">SIS source code repository</a>,
 then copied to the <a href="http://dist.apache.org/repos/dist/release/sis/">SIS distribution directory</a>.</p>
-<h1 id="maven">Maven Configuration &amp; Nexus Setup<a class="headerlink" href="#maven" title="Permanent link">&para;</a></h1>
+<h1 id="maven">Maven Configuration &amp; Nexus Setup   </h1>
 <p>Detailed instructions are at <a href="http://www.apache.org/dev/publishing-maven-artifacts.html">Publishing Maven Artifacts</a>.
 In summary, the developer needs to specify his Apache username and password (<strong>not</strong> the PGP passphrase)
 in his local <code>~/.m2</code> directory, and the GPG key identifier.
 First, if not already done, create a Maven master password:</p>
-<div class="codehilite"><pre>mvn --encrypt-master-password &lt;password&gt;
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mvn --encrypt-master-password &lt;password&gt;</code></pre></div>
 <p>The command will produce an encrypted version of the given password, something like <code>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</code>.
 Store this password in the <code>~/.m2/settings-security.xml</code> file like below:</p>
-<div class="codehilite"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>
+<div class="highlight"><pre class="chroma"><code class="language-xml" data-lang="xml"><span class="cp">&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;</span>
 <span class="nt">&lt;settingsSecurity&gt;</span>
   <span class="nt">&lt;master&gt;</span>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}<span class="nt">&lt;/master&gt;</span>
-<span class="nt">&lt;/settingsSecurity&gt;</span>
-</pre></div>
-
-
+<span class="nt">&lt;/settingsSecurity&gt;</span></code></pre></div>
 <p>Then encrypt the Apache account password (<strong>not</strong> the PGP passphrase) like below:</p>
-<div class="codehilite"><pre>mvn --encrypt-password &lt;passphrase&gt;
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mvn --encrypt-password &lt;passphrase&gt;</code></pre></div>
 <p>The command will produce an encrypted version of the password, something like <code>{COQLCE6DU6GtcS5P=}</code>.
 Cut-and-paste it in a section of the <code>~/.m2/settings.xml</code> file like below,
 together with the PGP key name:</p>
-<div class="codehilite"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>
+<div class="highlight"><pre class="chroma"><code class="language-xml" data-lang="xml"><span class="cp">&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;</span>
 <span class="nt">&lt;settings&gt;</span>
 ...
   <span class="nt">&lt;servers&gt;</span>
@@ -260,46 +226,50 @@ together with the PGP key name:</p>
       <span class="nt">&lt;/properties&gt;</span>
     <span class="nt">&lt;/profile&gt;</span>
   <span class="nt">&lt;/profiles&gt;</span>
-<span class="nt">&lt;/settings&gt;</span>
-</pre></div>
-
-
+<span class="nt">&lt;/settings&gt;</span></code></pre></div>
 <p>Notes:</p>
 <ul>
 <li>Do not store the PGP passphrase in the <code>settings.xml</code> file.
-    We will use the <code>gpg-agent</code> instead, as described in the <a href="release-management.html">release management</a> page.</li>
-<li>In the <code>&lt;profile&gt;</code> section:<ul>
+We will use the <code>gpg-agent</code> instead, as described in the <a href="release-management.html">release management</a> page.</li>
+<li>In the <code>&lt;profile&gt;</code> section:
+<ul>
 <li>The <code>&lt;user.name&gt;</code> property can be omitted if the Apache user name matches the user name on the local operating system.</li>
 <li>The <code>&lt;gpg.keyname&gt;</code> property can be omitted if GPG contains only one private key.</li>
 <li>The whole <code>&lt;profile&gt;</code> section can be omitted if the two above-cited properties are omitted.</li>
 </ul>
 </li>
 </ul>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
-    </div>
-  </footer>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+        </article>
+      </section>
+    </div>
+  </div>
+</div>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
+
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/release-management.html b/release-management.html
index addf82c..5fdfb71 100644
--- a/release-management.html
+++ b/release-management.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Release management</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Release management</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,81 +37,127 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Release management</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>This page describes how to create and deploy the SIS Maven artifacts, binary bundle, javadoc and list of API changes.
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Release management</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>This page describes how to create and deploy the SIS Maven artifacts, binary bundle, javadoc and list of API changes.
 The <a href="http://www.apache.org/dev/release.html">Release FAQ</a> page describes the foundation wide policies.
 Instructions on this page describe the steps specific to SIS (we do not use the <code>mvn release</code> command).
 The intended audiences are SIS release managers.</p>
-<div class="toc">
-<ul>
-<li><a href="#configure">Configure</a><ul>
-<li><a href="#directory-layout">Directory layout</a></li>
-</ul>
-</li>
-<li><a href="#prepare-source">Review project status before branching</a><ul>
-<li><a href="#update-crs-list">Update the list of supported CRS</a></li>
-<li><a href="#release-notes">Prepare release notes</a></li>
-</ul>
-</li>
-<li><a href="#branch">Create release branch</a><ul>
-<li><a href="#test-branch">Test branch extensively</a></li>
-<li><a href="#maven-nonfree">Prepare non-free resources</a></li>
-<li><a href="#integration-tests">Integration test</a></li>
-</ul>
-</li>
-<li><a href="#maven-deploy">Deploy Maven artifacts</a><ul>
-<li><a href="#nexus-close">Verify and close the Nexus release artifacts</a></li>
-<li><a href="#nexus-text">Test the Nexus release artifacts</a></li>
-</ul>
-</li>
-<li><a href="#stage">Stage the source, binary and javadoc artifacts</a><ul>
-<li><a href="#dist">Initialize the distribution directory</a></li>
-<li><a href="#sign">Sign and commit</a></li>
-<li><a href="#apidocs">Update online Javadoc</a></li>
-<li><a href="#test">Test the release</a></li>
-</ul>
-</li>
-<li><a href="#openoffice">Prepare OpenOffice add-in</a></li>
-<li><a href="#prepare-website">Prepare Web site</a></li>
-<li><a href="#vote">Put the release candidate up for a vote</a><ul>
-<li><a href="#veto">Recovering from a vetoed release</a></li>
-</ul>
-</li>
-<li><a href="#finalize">Finalize the release</a><ul>
-<li><a href="#verify">Verify release signatures</a></li>
-<li><a href="#announce">Announce the release</a></li>
-</ul>
-</li>
-<li><a href="#next-release">Update master for the next development cycle</a><ul>
-<li><a href="#nexus-clean">Delete old artifacts on Maven snapshot repository</a></li>
-</ul>
-</li>
-</ul>
-</div>
-<h1 id="configure">Configure<a class="headerlink" href="#configure" title="Permanent link">&para;</a></h1>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#configure">Configure   </a>
+      <ul>
+        <li><a href="#directory-layout">Directory layout   </a></li>
+      </ul>
+    </li>
+    <li><a href="#prepare-source">Review project status before branching   </a>
+      <ul>
+        <li><a href="#update-crs-list">Update the list of supported CRS   </a></li>
+        <li><a href="#release-notes">Prepare release notes   </a></li>
+      </ul>
+    </li>
+    <li><a href="#branch">Create release branch   </a>
+      <ul>
+        <li><a href="#test-branch">Test branch extensively   </a></li>
+        <li><a href="#maven-nonfree">Prepare non-free resources   </a></li>
+        <li><a href="#integration-tests">Integration test   </a></li>
+      </ul>
+    </li>
+    <li><a href="#maven-deploy">Deploy Maven artifacts   </a>
+      <ul>
+        <li><a href="#nexus-close">Verify and close the Nexus release artifacts   </a></li>
+        <li><a href="#nexus-text">Test the Nexus release artifacts   </a></li>
+      </ul>
+    </li>
+    <li><a href="#stage">Stage the source, binary and javadoc artifacts   </a>
+      <ul>
+        <li><a href="#dist">Initialize the distribution directory   </a></li>
+        <li><a href="#sign">Sign and commit   </a></li>
+        <li><a href="#apidocs">Update online Javadoc    </a></li>
+        <li><a href="#test">Test the release   </a></li>
+      </ul>
+    </li>
+    <li><a href="#openoffice">Prepare OpenOffice add-in   </a></li>
+    <li><a href="#prepare-website">Prepare Web site   </a></li>
+    <li><a href="#vote">Put the release candidate up for a vote   </a>
+      <ul>
+        <li><a href="#veto">Recovering from a vetoed release   </a></li>
+      </ul>
+    </li>
+    <li><a href="#finalize">Finalize the release   </a>
+      <ul>
+        <li><a href="#verify">Verify release signatures   </a></li>
+        <li><a href="#announce">Announce the release   </a></li>
+      </ul>
+    </li>
+    <li><a href="#next-release">Update master for the next development cycle   </a>
+      <ul>
+        <li><a href="#nexus-clean">Delete old artifacts on Maven snapshot repository   </a></li>
+      </ul>
+    </li>
+  </ul>
+</nav>
+<h1 id="configure">Configure   </h1>
 <p>Before to perform a release, make sure that the following conditions hold:</p>
 <ul>
 <li>Commands will be executed in a Unix shell.</li>
@@ -158,37 +167,31 @@ The intended audiences are SIS release managers.</p>
 <p>For all instructions in this page, <code>$OLD_VERSION</code> and <code>$NEW_VERSION</code> stand for the version
 number of the previous and the new release respectively, and <code>$RELEASE_CANDIDATE</code> stands for
 the current release attempt. Those versions shall be set on the command line like below (Unix):</p>
-<div class="codehilite"><pre>gpg --list-keys                     <span class="c"># For getting the value to put in &lt;your key ID&gt;</span>
-<span class="nb">unset </span>PATH_TO_FX
-<span class="nb">export </span><span class="nv">OLD_VERSION</span><span class="o">=</span>0.8
-<span class="nb">export </span><span class="nv">NEW_VERSION</span><span class="o">=</span>1.0
-<span class="nb">export </span><span class="nv">RELEASE_CANDIDATE</span><span class="o">=</span>1
-<span class="nb">export </span><span class="nv">SIGNING_KEY</span><span class="o">=</span>&lt;your key ID&gt;    <span class="c"># hexadecimal number with 8 or 40 digits.</span>
-</pre></div>
-
-
-<h2 id="directory-layout">Directory layout<a class="headerlink" href="#directory-layout" title="Permanent link">&para;</a></h2>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">gpg --list-keys                     <span class="c1"># For getting the value to put in &lt;your key ID&gt;</span>
+<span class="nb">unset</span> PATH_TO_FX
+<span class="nb">export</span> <span class="nv">OLD_VERSION</span><span class="o">=</span>0.8
+<span class="nb">export</span> <span class="nv">NEW_VERSION</span><span class="o">=</span>1.0
+<span class="nb">export</span> <span class="nv">RELEASE_CANDIDATE</span><span class="o">=</span><span class="m">1</span>
+<span class="nb">export</span> <span class="nv">SIGNING_KEY</span><span class="o">=</span>&lt;your key ID&gt;    <span class="c1"># hexadecimal number with 8 or 40 digits.</span></code></pre></div>
+<h2 id="directory-layout">Directory layout   </h2>
 <p>The steps described in this page assume the following directory layout (some directories will be created as
 a result of the steps). Any other layout can be used. However if the layout differs, then the relative paths
 in this page shall be adjusted accordingly.</p>
-<div class="codehilite"><pre>&lt;any root directory for SIS&gt;
-├─ $NEW_VERSION-RC
-├─ master
-├─ non-free
-│  └─ sis-epsg
-├─ releases
-│  ├─ distribution
-│  │  └─ $NEW_VERSION
-│  │     └─ RC$RELEASE_CANDIDATE
-│  └─ integration-test
-│     └─ maven
-└─ site
-   └─ content
-      └─ apidocs
-</pre></div>
-
-
-<h1 id="prepare-source">Review project status before branching<a class="headerlink" href="#prepare-source" title="Permanent link">&para;</a></h1>
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">    &lt;any root directory for SIS&gt;
+    ├─ $NEW_VERSION-RC
+    ├─ master
+    ├─ non-free
+    │  └─ sis-epsg
+    ├─ releases
+    │  ├─ distribution
+    │  │  └─ $NEW_VERSION
+    │  │     └─ RC$RELEASE_CANDIDATE
+    │  └─ integration-test
+    │     └─ maven
+    └─ site
+       ├─ main
+       └─ javadoc</code></pre></div>
+<h1 id="prepare-source">Review project status before branching   </h1>
 <p>Replace the <code>$OLD_VERSION</code> number by <code>$NEW_VERSION</code> in the values of following properties on the development branch:</p>
 <ul>
 <li><code>DOWNLOAD_URL</code> in <code>application/sis-console/src/main/java/org/apache/sis/console/ResourcesDownloader.java</code> file.</li>
@@ -197,19 +200,13 @@ in this page shall be adjusted accordingly.</p>
 <li>Review the <code>README</code> files in <code>application/sis-console/src/main/artifact/</code> and subdirectories.</li>
 </ul>
 <p>If not already done, build the C/C++ code of <code>sis-gdal</code> module:</p>
-<div class="codehilite"><pre><span class="nb">cd </span>storage/sis-gdal/src/main/c
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> storage/sis-gdal/src/main/c
 make
-<span class="nb">cd</span> -
-</pre></div>
-
-
+<span class="nb">cd</span> -</code></pre></div>
 <p>Commit and merge with other branches up to master.</p>
-<div class="codehilite"><pre>git add --update
-git commit --message<span class="o">=</span><span class="s2">&quot;Set version number and the EPSG geodetic dataset URL to expected values after release.&quot;</span>
-<span class="c"># merge with master</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">git add --update
+git commit --message<span class="o">=</span><span class="s2">&#34;Set version number and the EPSG geodetic dataset URL to expected values after release.&#34;</span>
+<span class="c1"># merge with master</span></code></pre></div>
 <p>Before to start the release process, we need to test more extensively the master.
 The tests described below often reveal errors that were unnoticed in daily builds.
 It is better to detect and fix them before to create the release branch.
@@ -217,41 +214,35 @@ First, ensure that a PostgreSQL server is running and listening to the default p
 (optional but recommended for more exhaustive testing —
 see <a href="./source.html#postgres">PostgreSQL testing configuration</a> for more details).
 Then execute the following commands and fix as much warnings as practical:</p>
-<div class="codehilite"><pre>systemctl start postgresql.service        <span class="c"># Optional — exact command depends on Linux distribution.</span>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">systemctl start postgresql.service        <span class="c1"># Optional — exact command depends on Linux distribution.</span>
 mvn clean install --define org.apache.sis.test.extensive<span class="o">=</span><span class="nb">true</span>
-mvn javadoc:aggregate
-</pre></div>
-
-
+mvn javadoc:aggregate</code></pre></div>
 <p>If the <code>SIS_DATA</code> environment variable was set during above build, unset it a try again.
 Ideally the build should be tested in both conditions (<code>SIS_DATA</code> set and unset).
 That test may be done in a separated shell (console window) in order to preserve
 the variable value in the shell performing the release.</p>
-<div class="codehilite"><pre><span class="nb">unset </span>SIS_DATA
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">unset</span> SIS_DATA
 <span class="nb">echo</span> <span class="nv">$SIS_DATA</span>
-mvn <span class="nb">test</span>
-</pre></div>
-
-
-<h2 id="update-crs-list">Update the list of supported CRS<a class="headerlink" href="#update-crs-list" title="Permanent link">&para;</a></h2>
+mvn test</code></pre></div>
+<h2 id="update-crs-list">Update the list of supported CRS   </h2>
 <p>The following steps regenerate
 the <a href="./tables/CoordinateOperationMethods.html">CoordinateOperationMethods</a>
 and <a href="./tables/CoordinateReferenceSystems.html">CoordinateReferenceSystems</a> pages.
 Those steps are also useful as additional tests, since failure to generate those pages may reveal problems.</p>
 <ol>
 <li>Open the <code>AuthorityCodes</code> class, search <code>DEPRECATED=0</code> (it appears in a SQL fragment) and replace by <code>(DEPRECATED=0 OR TRUE)</code>.
-     <strong>Do not commit!</strong> This is a temporary hack for including deprecated codes in the CRS list to be generated.
-     Those codes will appear with strike for making clear that they are deprecated.</li>
+<strong>Do not commit!</strong> This is a temporary hack for including deprecated codes in the CRS list to be generated.
+Those codes will appear with strike for making clear that they are deprecated.</li>
 <li>Open the <code>CoordinateOperationMethods</code> Java class and execute its <code>main</code> method, for example in an IDE.</li>
 <li>Open the <code>CoordinateReferenceSystems</code> Java class and execute its <code>main</code> method.</li>
 <li>If successful, HTML files will be generated in the current directory.
-     Open those files in a web browser and verify that information are okay,
-     in particular the SIS and EPSG version numbers in the first paragraph.</li>
+Open those files in a web browser and verify that information are okay,
+in particular the SIS and EPSG version numbers in the first paragraph.</li>
 <li>If okay, move those two HTML files to the <code>../site/content/tables/</code> directory, overwriting previous files.</li>
 <li>Revert the hack in <code>AuthorityCodes</code> class.</li>
-<li>Commit: <code>svn commit --message="Update the list CRS and operation methods supported by Apache SIS $NEW_VERSION."</code></li>
+<li>Commit: <code>svn commit --message=&quot;Update the list CRS and operation methods supported by Apache SIS $NEW_VERSION.&quot;</code></li>
 </ol>
-<h2 id="release-notes">Prepare release notes<a class="headerlink" href="#release-notes" title="Permanent link">&para;</a></h2>
+<h2 id="release-notes">Prepare release notes   </h2>
 <p>We update JIRA soon because doing so is sometime a reminder of uncompleted tasks in source code.
 Update <a href="http://issues.apache.org/jira/browse/SIS">JIRA</a> tasks and prepare release notes as below:</p>
 <ul>
@@ -260,144 +251,115 @@ Update <a href="http://issues.apache.org/jira/browse/SIS">JIRA</a> tasks and pre
 <li>On the <code>site</code> source code repository, create a <code>content/release-notes/$NEW_VERSION.html</code> file with all the features added.</li>
 <li>Use <code>content/release-notes/$OLD_VERSION.html</code> as a template, omitting everything between the <code>&lt;body&gt;</code> and <code>&lt;/body&gt;</code> tags.</li>
 <li>The release notes can be obtained from JIRA, by clicking on the <em>Versions</em> tab → the version number → <em>Release notes</em>
-    and then configuring the release notes to display HTML format and copying it.
-    A suggested approach would be to reorganize the release notes as
-    <em>New Features</em>, then <em>Improvements</em>, then <em>Bug Fixes</em>, then <em>Tests</em> and finally <em>Tasks</em>.
-    The <em>Sub Tasks</em> can be classified according the category of their parent issue.</li>
+and then configuring the release notes to display HTML format and copying it.
+A suggested approach would be to reorganize the release notes as
+<em>New Features</em>, then <em>Improvements</em>, then <em>Bug Fixes</em>, then <em>Tests</em> and finally <em>Tasks</em>.
+The <em>Sub Tasks</em> can be classified according the category of their parent issue.</li>
 </ul>
 <p>Commit to staging area (not published immediately):</p>
-<div class="codehilite"><pre><span class="nb">cd</span> ../site
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> ../site
 cp content/release-notes/<span class="nv">$OLD_VERSION</span>.html content/release-notes/<span class="nv">$NEW_VERSION</span>.html
-<span class="c"># Edit release notes before to continue.</span>
+<span class="c1"># Edit release notes before to continue.</span>
 svn add content/release-notes/<span class="nv">$NEW_VERSION</span>.html
-svn commit --message <span class="s2">&quot;Release notes for Apache SIS $NEW_VERSION.&quot;</span>
-</pre></div>
-
-
-<h1 id="branch">Create release branch<a class="headerlink" href="#branch" title="Permanent link">&para;</a></h1>
+svn commit --message <span class="s2">&#34;Release notes for Apache SIS </span><span class="nv">$NEW_VERSION</span><span class="s2">.&#34;</span></code></pre></div>
+<h1 id="branch">Create release branch   </h1>
 <p>Execute the following commands.
 It is okay to checkout the branch in a separated directory if desired.
 The <code>SIS_RC_DIR</code> environment variable will specify that directory.</p>
-<div class="codehilite"><pre><span class="nb">cd</span> ../master
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> ../master
 git checkout -b <span class="nv">$NEW_VERSION</span>-RC
 <span class="nb">cd</span> <span class="nv">$NEW_VERSION</span>-RC
-<span class="nb">export </span><span class="nv">SIS_RC_DIR</span><span class="o">=</span><span class="sb">`</span><span class="nb">pwd</span><span class="sb">`</span>
-</pre></div>
-
-
+<span class="nb">export</span> <span class="nv">SIS_RC_DIR</span><span class="o">=</span><span class="sb">`</span><span class="nb">pwd</span><span class="sb">`</span></code></pre></div>
 <p>Remove the modules that are not yet ready for a release.
 This may require removing <code>&lt;module&gt;</code> elements in the parent <code>pom.xml</code> file.</p>
-<div class="codehilite"><pre>git rm core/sis-cql
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">git rm core/sis-cql
 git rm core/sis-portrayal
 git rm storage/sis-shapefile
 git rm application/sis-javafx
 git rm application/sis-webapp
 git rm storage/sis-storage/src/main/java/org/apache/sis/storage/WritableGridCoverageResource.java
-git add --update    <span class="c"># for the removal of &lt;module&gt; elements in pom.xml files.</span>
-git commit --message<span class="o">=</span><span class="s2">&quot;Remove the modules to be excluded from $NEW_VERSION release.&quot;</span>
-</pre></div>
-
-
+git add --update    <span class="c1"># for the removal of &lt;module&gt; elements in pom.xml files.</span>
+git commit --message<span class="o">=</span><span class="s2">&#34;Remove the modules to be excluded from </span><span class="nv">$NEW_VERSION</span><span class="s2"> release.&#34;</span></code></pre></div>
 <p>Open the root <code>pom.xml</code> file in an editor and perform the following changes:</p>
 <ul>
 <li>Remove the whole <code>&lt;pluginRepositories&gt;</code> block (including comment),
-    since it should not be needed for releases (and is actually not allowed).</li>
+since it should not be needed for releases (and is actually not allowed).</li>
 <li>Remove the <code>jetty</code> dependency since the module that used it has been removed.</li>
 </ul>
 <p>We need to update the SIS version numbers not only in the <code>pom.xml</code> files, but also in a few Java files.
 The following command performs the replacement using Ant.</p>
-<div class="codehilite"><pre>ant -buildfile core/sis-build-helper/src/main/ant/prepare-release.xml branch -Dsis.version<span class="o">=</span><span class="nv">$NEW_VERSION</span>
-git rm core/sis-build-helper/src/main/ant
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">ant -buildfile core/sis-build-helper/src/main/ant/prepare-release.xml branch -Dsis.version<span class="o">=</span><span class="nv">$NEW_VERSION</span>
+git rm core/sis-build-helper/src/main/ant</code></pre></div>
 <p>Validate with <code>git diff</code>, search <code>SNAPSHOT</code> in the whole source directory in case we missed some, then commit:</p>
-<div class="codehilite"><pre><span class="n">git</span> <span class="n">add</span> <span class="o">--</span><span class="n">update</span>
-<span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span>
-<span class="n">git</span> <span class="n">commit</span> <span class="o">--</span><span class="n">message</span><span class="p">=</span>&quot;<span class="n">Set</span> <span class="n">version</span> <span class="n">number</span> <span class="n">to</span> $<span class="n">NEW_VERSION</span><span class="p">.</span>&quot;
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">git add --update
+mvn clean install
+git commit --message<span class="o">=</span><span class="s2">&#34;Set version number to </span><span class="nv">$NEW_VERSION</span><span class="s2">.&#34;</span></code></pre></div>
 <p>Maybe apply the following hacks on the release branch only (do not apply them on master).
 Check first if those hacks are still needed for the next release (they were needed for 1.0):</p>
 <ul>
 <li>Remove all use of <code>javax.annotation.Generated</code> annotation.
-    This removal should not have any effect on compilation result.</li>
-<li>In the root <code>pom.xml</code> under <code>maven-javadoc-plugin</code> configuration, add the following elements:<ul>
+This removal should not have any effect on compilation result.</li>
+<li>In the root <code>pom.xml</code> under <code>maven-javadoc-plugin</code> configuration, add the following elements:
+<ul>
 <li><code>&lt;link&gt;http://sis.apache.org/apidocs&lt;/link&gt;</code> inside <code>&lt;links&gt;</code> block.</li>
 <li><code>&lt;additionalOption&gt;-Xdoclint:all,-reference&lt;/additionalOption&gt;</code> inside <code>&lt;additionalOptions&gt;</code> block.</li>
 </ul>
 </li>
 <li>Commit on the release branch only.</li>
 </ul>
-<h2 id="test-branch">Test branch extensively<a class="headerlink" href="#test-branch" title="Permanent link">&para;</a></h2>
+<h2 id="test-branch">Test branch extensively   </h2>
 <p>Build the project with the <code>apache-release</code> profile enabled.
 This profile performs the following actions:</p>
 <ul>
 <li>Enable extensive tests (i.e. it will set the <code>org.apache.sis.test.extensive</code> property to <code>true</code>).</li>
 <li>Generate Javadoc. This may fail if the source code contains invalid Javadoc tags or broken HTML.</li>
 <li>Generate additional binary artifacts (<code>*.zip</code> and <code>*.oxt</code> files).
-    This will fail if duplicated class files or resources are found.
-    Consequently building the <code>*.zip</code> file is an additional test worth to do before deployment.</li>
+This will fail if duplicated class files or resources are found.
+Consequently building the <code>*.zip</code> file is an additional test worth to do before deployment.</li>
 <li>Sign the artifacts.</li>
 </ul>
 <p>Each of those additional products may cause a failure that did not happen in normal builds.</p>
-<div class="codehilite"><pre>mvn clean install --activate-profiles apache-release
-find . -name <span class="s2">&quot;sis-*.asc&quot;</span> -exec gpg --verify <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>     <span class="c"># Verify signatures.</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mvn clean install --activate-profiles apache-release
+find . -name <span class="s2">&#34;sis-*.asc&#34;</span> -exec gpg --verify <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>     <span class="c1"># Verify signatures.</span></code></pre></div>
 <p>More the <code>target</code> directory and execute all examples documented in the <a href="./command-line.html">command-line interface page</a>
 with the <code>sis</code> command replaced by the following:</p>
-<div class="codehilite"><pre>java -classpath <span class="s2">&quot;binaries/*&quot;</span> -enableassertions org.apache.sis.console.Command
-</pre></div>
-
-
-<h2 id="maven-nonfree">Prepare non-free resources<a class="headerlink" href="#maven-nonfree" title="Permanent link">&para;</a></h2>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">    java -classpath <span class="s2">&#34;binaries/*&#34;</span> -enableassertions org.apache.sis.console.Command</code></pre></div>
+<h2 id="maven-nonfree">Prepare non-free resources   </h2>
 <p>Go to the directory that contains a checkout of <code>https://svn.apache.org/repos/asf/sis/data/non-free/sis-epsg</code>.
 Those modules will not be part of the distribution (except on Maven), but we nevertheless need to ensure that they work.
 Replace occurrences of <code>&lt;version&gt;$OLD_VERSION&lt;/version&gt;</code> by <code>&lt;version&gt;$NEW_VERSION&lt;/version&gt;</code> in the <code>pom.xml</code> files.</p>
-<div class="codehilite"><pre><span class="nb">cd</span> ../non-free
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> ../non-free
 svn update
 mvn clean install
-mvn javadoc:javadoc                   <span class="c"># Test that javadoc can be generated.</span>
-svn commit --message <span class="s2">&quot;Set version number and dependencies to $NEW_VERSION.&quot;</span>
-</pre></div>
-
-
-<h2 id="integration-tests">Integration test<a class="headerlink" href="#integration-tests" title="Permanent link">&para;</a></h2>
+mvn javadoc:javadoc                   <span class="c1"># Test that javadoc can be generated.</span>
+svn commit --message <span class="s2">&#34;Set version number and dependencies to </span><span class="nv">$NEW_VERSION</span><span class="s2">.&#34;</span></code></pre></div>
+<h2 id="integration-tests">Integration test   </h2>
 <p>Open the root <code>pom.xml</code> file of integration tests.
 Set version numbers to <code>$NEW_VERSION</code> without <code>-SNAPSHOT</code> suffix.
 Verify the configuration and version of Maven plugins.
 Then test and commit (note that execution may be slow).</p>
-<div class="codehilite"><pre><span class="nb">cd</span> ../distribution/integration-test
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> ../distribution/integration-test
 svn update
-<span class="nb">cd </span>maven
+<span class="nb">cd</span> maven
 mvn clean <span class="nb">test</span>
-svn commit --message <span class="s2">&quot;Set version number and dependencies to $NEW_VERSION.&quot;</span>
-</pre></div>
-
-
-<h1 id="maven-deploy">Deploy Maven artifacts<a class="headerlink" href="#maven-deploy" title="Permanent link">&para;</a></h1>
+svn commit --message <span class="s2">&#34;Set version number and dependencies to </span><span class="nv">$NEW_VERSION</span><span class="s2">.&#34;</span></code></pre></div>
+<h1 id="maven-deploy">Deploy Maven artifacts   </h1>
 <p>If above verifications succeeded, performs the following <em>temporary</em> changes
 (to be discarded after the deployment to Maven repository):</p>
 <ul>
 <li>Remove temporarily the <code>sis-openoffice</code> module from <code>application/pom.xml</code>.</li>
 <li>Remove the <code>test-jar</code> goal from <code>maven-jar-plugin</code> in the root <code>pom.xml</code>.</li>
 <li>Remove all SIS dependencies declared with <code>&lt;type&gt;test-jar&lt;/type&gt;</code> in all <code>pom.xml</code> files.
-    This hack will force us to skip test compilations.</li>
+This hack will force us to skip test compilations.</li>
 </ul>
 <p>Then deploy SIS (without test JAR files).
 Deploy also the non-free resources in a staging repository separated from the rest of Apache SIS.
 If there is any issue with this deployment, the staging repository can easily be dropped and recreated.</p>
-<div class="codehilite"><pre><span class="nb">cd</span> <span class="nv">$SIS_RC_DIR</span>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> <span class="nv">$SIS_RC_DIR</span>
 mvn clean deploy --activate-profiles apache-release --define maven.test.skip<span class="o">=</span><span class="nb">true</span>
 <span class="nb">cd</span> ../non-free
-mvn clean deploy --activate-profiles apache-release
-</pre></div>
-
-
-<h2 id="nexus-close">Verify and close the Nexus release artifacts<a class="headerlink" href="#nexus-close" title="Permanent link">&para;</a></h2>
+mvn clean deploy --activate-profiles apache-release</code></pre></div>
+<h2 id="nexus-close">Verify and close the Nexus release artifacts   </h2>
 <p>Verify the staged artifacts in the <a href="https://repository.apache.org/index.html">Nexus repository</a>.
 The artifacts can be found under <em>Build Promotion</em> → <em>Staging repositories</em>, and searching for <code>org.apache.sis</code> in the <em>Repository</em> column.
 Navigate through the artifact tree and make sure that all javadoc, source and jar files have <code>.asc</code> (GPG signature) and <code>.md5</code> files.
@@ -409,14 +371,14 @@ so try to see at least one code snippet.</p>
 <p>Additional cleaning:</p>
 <ul>
 <li>Delete all <code>org/apache/sis/parent/$NEW_VERSION/parent-$NEW_VERSION-source-release.zip.*</code> files on the Nexus repository.
-    They should not be there - source release will be deployed on an other repository later.</li>
+They should not be there - source release will be deployed on an other repository later.</li>
 </ul>
 <p>Close the Nexus staging repository:</p>
 <ul>
 <li>Click the checkboxes for the open staging repositories (<code>org.apache.sis-&lt;id&gt;</code>) and press <em>Close</em> in the menu bar.</li>
-<li>In the description field, enter "<code>SIS $NEW_VERSION-RC$RELEASE_CANDIDATE</code>"
-    (replace <code>$NEW_VERSION</code> and <code>$RELEASE_CANDIDATE</code> by appropriate values.
-    This will not be done automatically since this field box is not our bash shell!).</li>
+<li>In the description field, enter &ldquo;<code>SIS $NEW_VERSION-RC$RELEASE_CANDIDATE</code>&rdquo;
+(replace <code>$NEW_VERSION</code> and <code>$RELEASE_CANDIDATE</code> by appropriate values.
+This will not be done automatically since this field box is not our bash shell!).</li>
 <li>Click on the <code>org.apache.sis-&lt;id&gt;</code> link in order to get the URL to the temporary Maven repository created by Nexus.</li>
 </ul>
 <p>We will announce later (in the <cite>Put the release candidate up for a vote</cite> section) on the <code>dev@</code> mailing list
@@ -427,85 +389,58 @@ the availability of this temporary repository for testing purpose.</p>
 <li>In the <code>sis-epsg-$NEW_VERSION.jar</code> file, verify that <code>META-INF/LICENSE</code> contain the EPSG terms of use.</li>
 <li>Close the repository and take note of its URL.</li>
 </ul>
-<h2 id="nexus-text">Test the Nexus release artifacts<a class="headerlink" href="#nexus-text" title="Permanent link">&para;</a></h2>
+<h2 id="nexus-text">Test the Nexus release artifacts   </h2>
 <p>Go to the test Maven project.
 Open the root <code>pom.xml</code> file and set the <code>&lt;version&gt;</code> number to the SIS release to be tested.
 Then go to the <code>&lt;url&gt;</code> declaration of the first <code>&lt;repository&gt;</code> and replace value by the URL
 of the temporary Maven repository created by Nexus.
 Usually, only the 3 last digits need to be updated.</p>
-<div class="codehilite"><pre><span class="nb">cd</span> ../releases/integration-test/maven
-<span class="c"># Edit &lt;url&gt; in pom.xml before to continue.</span>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> ../releases/integration-test/maven
+<span class="c1"># Edit &lt;url&gt; in pom.xml before to continue.</span>
 mvn compile
-svn commit -m <span class="s2">&quot;Test project for SIS $NEW_VERSION-RC$RELEASE_CANDIDATE&quot;</span>
-</pre></div>
-
-
+svn commit -m <span class="s2">&#34;Test project for SIS </span><span class="nv">$NEW_VERSION</span><span class="s2">-RC</span><span class="nv">$RELEASE_CANDIDATE</span><span class="s2">&#34;</span></code></pre></div>
 <p>Create a temporary directory where Apache SIS will write the EPSG dataset.</p>
-<div class="codehilite"><pre>mkdir target/SpatialMetadata
-<span class="nb">export </span><span class="nv">SIS_DATA</span><span class="o">=</span><span class="sb">`</span><span class="nb">pwd</span><span class="sb">`</span>/target/SpatialMetadata
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mkdir target/SpatialMetadata
+<span class="nb">export</span> <span class="nv">SIS_DATA</span><span class="o">=</span><span class="sb">`</span><span class="nb">pwd</span><span class="sb">`</span>/target/SpatialMetadata</code></pre></div>
 <p>Clear the local Maven repository in order to force downloads from the Nexus repository, then test.
 This will also verify the checksums.</p>
-<div class="codehilite"><pre>rm -r ~/.m2/repository/org/apache/sis
-mvn package --strict-checksums
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">rm -r ~/.m2/repository/org/apache/sis
+mvn package --strict-checksums</code></pre></div>
 <p>Verify that the EPSG dataset has been created, then cleanup:</p>
-<div class="codehilite"><pre>ll <span class="nv">$SIS_DATA</span>/Databases/SpatialMetadata
-mvn clean
-</pre></div>
-
-
-<h1 id="stage">Stage the source, binary and javadoc artifacts<a class="headerlink" href="#stage" title="Permanent link">&para;</a></h1>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">ll <span class="nv">$SIS_DATA</span>/Databases/SpatialMetadata
+mvn clean</code></pre></div>
+<h1 id="stage">Stage the source, binary and javadoc artifacts   </h1>
 <p>Generate the Javadoc:</p>
-<div class="codehilite"><pre><span class="nb">cd</span> <span class="nv">$SIS_RC_DIR</span>
-git checkout .            <span class="c"># Discard local changes, in particular the hack for excluding test files.</span>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> <span class="nv">$SIS_RC_DIR</span>
+git checkout .            <span class="c1"># Discard local changes, in particular the hack for excluding test files.</span>
 mvn clean install --activate-profiles apache-release
 mvn javadoc:aggregate
-<span class="nb">cd </span>target/site
+<span class="nb">cd</span> target/site
 zip -9 -r apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip apidocs
-<span class="nb">cd</span> ../..
-</pre></div>
-
-
-<h2 id="dist">Initialize the distribution directory<a class="headerlink" href="#dist" title="Permanent link">&para;</a></h2>
+<span class="nb">cd</span> ../..</code></pre></div>
+<h2 id="dist">Initialize the distribution directory   </h2>
 <p>Create the directory for the new version and release candidate within the distribution directory.
 The <code>$RELEASE_CANDIDATE</code> variable shall be the number of current release attempt.</p>
-<div class="codehilite"><pre><span class="nb">cd</span> ../releases/distribution
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> ../releases/distribution
 svn update
 mkdir -p <span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>
 svn add <span class="nv">$NEW_VERSION</span>
 <span class="nb">cd</span> <span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>
-<span class="nb">export </span><span class="nv">DIST_DIR</span><span class="o">=</span><span class="sb">`</span><span class="nb">pwd</span><span class="sb">`</span>
-</pre></div>
-
-
+<span class="nb">export</span> <span class="nv">DIST_DIR</span><span class="o">=</span><span class="sb">`</span><span class="nb">pwd</span><span class="sb">`</span></code></pre></div>
 <p>Copy the <code>HEADER.html</code> file from the previous release.
 Update the file content if necessary.</p>
-<div class="codehilite"><pre>svn copy https://dist.apache.org/repos/dist/release/sis/<span class="nv">$OLD_VERSION</span>/HEADER.html .
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">svn copy https://dist.apache.org/repos/dist/release/sis/<span class="nv">$OLD_VERSION</span>/HEADER.html .</code></pre></div>
 <p>Move the files generated by Maven to the distribution directory:</p>
-<div class="codehilite"><pre>mv <span class="nv">$SIS_RC_DIR</span>/target/sis-<span class="nv">$NEW_VERSION</span>-* .
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mv <span class="nv">$SIS_RC_DIR</span>/target/sis-<span class="nv">$NEW_VERSION</span>-* .
 mv <span class="nv">$SIS_RC_DIR</span>/target/site/apache-sis-<span class="nv">$NEW_VERSION</span>-* .
-mv <span class="nv">$SIS_RC_DIR</span>/target/distribution/apache-sis-<span class="nv">$NEW_VERSION</span>.zip .
-</pre></div>
-
-
+mv <span class="nv">$SIS_RC_DIR</span>/target/distribution/apache-sis-<span class="nv">$NEW_VERSION</span>.zip .</code></pre></div>
 <p>Rename the files to something more conform to the convention seen in other Apache projects:</p>
-<div class="codehilite"><pre>mv apache-sis-<span class="nv">$NEW_VERSION</span>.zip             apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mv apache-sis-<span class="nv">$NEW_VERSION</span>.zip             apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip
 mv sis-<span class="nv">$NEW_VERSION</span>-source-release.zip     apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip
-mv sis-<span class="nv">$NEW_VERSION</span>-source-release.zip.asc apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.asc
-</pre></div>
-
-
-<h2 id="sign">Sign and commit<a class="headerlink" href="#sign" title="Permanent link">&para;</a></h2>
+mv sis-<span class="nv">$NEW_VERSION</span>-source-release.zip.asc apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.asc</code></pre></div>
+<h2 id="sign">Sign and commit   </h2>
 <p>Sign the source, javadoc and binary artifacts:</p>
-<div class="codehilite"><pre>shas512um apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip &gt; apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.sha
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">shas512um apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip &gt; apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.sha
 md5sum    apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip &gt; apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.md5
 
 gpg --armor --detach-sign --default-key <span class="nv">$SIGNING_KEY</span> apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip
@@ -514,67 +449,47 @@ md5sum    apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip &gt; apache-si
 
 gpg --armor --detach-sign --default-key <span class="nv">$SIGNING_KEY</span> apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip
 sha512sum apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip &gt; apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip.sha
-md5sum    apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip &gt; apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip.md5
-</pre></div>
-
-
+md5sum    apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip &gt; apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip.md5</code></pre></div>
 <p>Verify checksums and signatures:</p>
-<div class="codehilite"><pre>find . -name <span class="s2">&quot;*.md5&quot;</span> -exec md5sum    --check <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
-find . -name <span class="s2">&quot;*.sha&quot;</span> -exec sha512sum --check <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
-find . -name <span class="s2">&quot;*.asc&quot;</span> -exec gpg      --verify <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">find . -name <span class="s2">&#34;*.md5&#34;</span> -exec md5sum    --check <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
+find . -name <span class="s2">&#34;*.sha&#34;</span> -exec sha512sum --check <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
+find . -name <span class="s2">&#34;*.asc&#34;</span> -exec gpg      --verify <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span></code></pre></div>
 <p>Commit:</p>
-<div class="codehilite"><pre>svn add apache-sis-<span class="nv">$NEW_VERSION</span>-*
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">svn add apache-sis-<span class="nv">$NEW_VERSION</span>-*
 <span class="nb">cd</span> ../..
-svn commit --message <span class="s2">&quot;SIS release candidate $RELEASE_CANDIDATE&quot;</span>
-</pre></div>
-
-
-<h2 id="apidocs">Update online Javadoc<a class="headerlink" href="#apidocs" title="Permanent link">&para;</a></h2>
+svn commit --message <span class="s2">&#34;SIS release candidate </span><span class="nv">$RELEASE_CANDIDATE</span><span class="s2">&#34;</span></code></pre></div>
+<h2 id="apidocs">Update online Javadoc    </h2>
 <p>Copy the Javadoc to the web site staging directory:</p>
-<div class="codehilite"><pre><span class="nb">cd</span> ../site/content
-rm -r apidocs
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> ../site/javadoc
+rm -r *
+git reset README.md
+git checkout README.md
 unzip <span class="nv">$DIST_DIR</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-doc.zip
-</pre></div>
-
-
-<p>Execute <code>svn add</code> for new files and <code>svn remove</code> for deleted files:</p>
-<div class="codehilite"><pre><span class="nb">cd </span>apidocs
-svn status | gawk <span class="s1">&#39;/^\?.*/ {print $2}&#39;</span> | xargs svn add
-svn status | gawk <span class="s1">&#39;/^\!.*/ {print $2}&#39;</span> | xargs svn remove
-svn commit --message <span class="s2">&quot;Update javadoc for SIS $NEW_RELEASE.&quot;</span>
-</pre></div>
-
-
-<h2 id="test">Test the release<a class="headerlink" href="#test" title="Permanent link">&para;</a></h2>
+mv apidocs/* .
+rmdir apidocs
+git add -A
+git commit --message <span class="s2">&#34;Update javadoc for SIS </span><span class="nv">$NEW_RELEASE</span><span class="s2">.&#34;</span></code></pre></div>
+<h2 id="test">Test the release   </h2>
 <p>Execute the following commands in any temporary directory for testing the sources:</p>
-<div class="codehilite"><pre>wget https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip <span class="se">\</span>
-     https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.asc
-<span class="c"># Test</span>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">wget https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip <span class="se">\
+</span><span class="se"></span>     https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.asc
+<span class="c1"># Test</span>
 gpg --verify apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip.asc
 unzip apache-sis-<span class="nv">$NEW_VERSION</span>-src.zip
-<span class="nb">cd </span>sis-<span class="nv">$NEW_VERSION</span>
-mvn install
-</pre></div>
-
-
+<span class="nb">cd</span> sis-<span class="nv">$NEW_VERSION</span>
+mvn install</code></pre></div>
 <p>Execute the following commands in any temporary directory for testing the binary:</p>
-<div class="codehilite"><pre>wget https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip <span class="se">\</span>
-     https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip.asc
-<span class="c"># Test</span>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">wget https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip <span class="se">\
+</span><span class="se"></span>     https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span>/apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip.asc
+<span class="c1"># Test</span>
 gpg --verify apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip.asc
 unzip apache-sis-<span class="nv">$NEW_VERSION</span>-bin.zip
-<span class="nb">cd </span>apache-sis-<span class="nv">$NEW_VERSION</span>
-<span class="nb">unset </span>SIS_DATA
+<span class="nb">cd</span> apache-sis-<span class="nv">$NEW_VERSION</span>
+<span class="nb">unset</span> SIS_DATA
 bin/sis about --verbose
 bin/sis metadata https://github.com/opengeospatial/geoapi/raw/master/geoapi-netcdf/src/test/resources/org/opengis/wrapper/netcdf/NCEP-SST.nc
-bin/sis crs http://svn.apache.org/repos/asf/sis/trunk/core/sis-referencing/src/test/resources/org/apache/sis/referencing/crs/ProjectedCRS.xml --format WKT
-</pre></div>
-
-
-<h1 id="openoffice">Prepare OpenOffice add-in<a class="headerlink" href="#openoffice" title="Permanent link">&para;</a></h1>
+bin/sis crs http://svn.apache.org/repos/asf/sis/trunk/core/sis-referencing/src/test/resources/org/apache/sis/referencing/crs/ProjectedCRS.xml --format WKT</code></pre></div>
+<h1 id="openoffice">Prepare OpenOffice add-in   </h1>
 <p>The OpenOffice add-in source code can be distributed under Apache 2 license only.
 But the binary may contain non-free resources, notably the EPSG geodetic dataset.
 For now, the release manager should apply the following local modifications before
@@ -582,10 +497,10 @@ to build the add-in:</p>
 <ul>
 <li>Move to the <code>application/sis-openoffice</code> directory.</li>
 <li>Replace the <code>src/main/unopkg/license.txt</code> file by EPSG terms of use.
-    A copy is found in the <code>non-free</code> group of SIS modules.</li>
+A copy is found in the <code>non-free</code> group of SIS modules.</li>
 <li>Run <code>mvn package --activate-profiles non-free</code>.</li>
 </ul>
-<h1 id="prepare-website">Prepare Web site<a class="headerlink" href="#prepare-website" title="Permanent link">&para;</a></h1>
+<h1 id="prepare-website">Prepare Web site   </h1>
 <p>Review and update the <code>content/DOAP.rdf</code> file on the <code>site</code> source code repository.
 Add a new <code>&lt;release&gt;</code> block for the new release with the estimated release date.</p>
 <p>Update the version numbers from the old one to <code>$NEW_VERSION</code> in the following files.</p>
@@ -597,46 +512,38 @@ Add a new <code>&lt;release&gt;</code> block for the new release with the estima
 <li><code>content/epsg.mdtext</code> (be aware that the version number may sometime be behind the SIS version number)</li>
 </ul>
 <p>Commit:</p>
-<div class="codehilite"><pre>svn commit --message <span class="s2">&quot;Prepare documentation for the $NEW_VERSION release.&quot;</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">svn commit --message <span class="s2">&#34;Prepare documentation for the </span><span class="nv">$NEW_VERSION</span><span class="s2"> release.&#34;</span></code></pre></div>
 <p>The new web site will be published in the <a href="http://sis.staging.apache.org">staging area</a>.
 It will not yet be published on <code>http://sis.apache.org</code>.</p>
-<h1 id="vote">Put the release candidate up for a vote<a class="headerlink" href="#vote" title="Permanent link">&para;</a></h1>
+<h1 id="vote">Put the release candidate up for a vote   </h1>
 <ul>
 <li>Create a VOTE email thread on <code>dev@</code> to record votes as replies.
-    A template is available <a href="templates/release-vote.txt">here</a>.</li>
+A template is available <a href="templates/release-vote.txt">here</a>.</li>
 <li>Create a DISCUSS email thread on <code>dev@</code> for any vote questions.
-    A template is available <a href="templates/release-discuss.txt">here</a>.</li>
+A template is available <a href="templates/release-discuss.txt">here</a>.</li>
 <li>Perform a review of the release and cast your vote:</li>
 <li>a -1 vote does not necessarily mean that the vote must be redone, however it is usually a good idea
-    to rollback the release if a -1 vote is received. See <em>Recovering from a vetoed release</em> below.</li>
+to rollback the release if a -1 vote is received. See <em>Recovering from a vetoed release</em> below.</li>
 <li>After the vote has been open for at least 72 hours, has at least three +1 PMC votes and no -1 votes,
-    then post the results to the vote thread:<ul>
-<li>Reply to the initial email and prepend to the original subject "[RESULT]"</li>
+then post the results to the vote thread:
+<ul>
+<li>Reply to the initial email and prepend to the original subject &ldquo;[RESULT]&rdquo;</li>
 <li>Include a list of everyone who voted +1, 0 or -1.</li>
 </ul>
 </li>
 </ul>
-<h2 id="veto">Recovering from a vetoed release<a class="headerlink" href="#veto" title="Permanent link">&para;</a></h2>
+<h2 id="veto">Recovering from a vetoed release   </h2>
 <p>Reply to the initial vote email and prepend to the original subject:</p>
-<div class="codehilite"><pre>[CANCELED]
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">[CANCELED]</code></pre></div>
 <p>Delete the svn tag created by the release:perform step:</p>
-<div class="codehilite"><pre>svn delete https://svn.apache.org/repos/asf/sis/tags/<span class="nv">$NEW_VERSION</span> --message <span class="s2">&quot;deleting tag from rolled back release&quot;</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">svn delete https://svn.apache.org/repos/asf/sis/tags/<span class="nv">$NEW_VERSION</span> --message <span class="s2">&#34;deleting tag from rolled back release&#34;</span></code></pre></div>
 <p>Drop the Nexus staging repository:</p>
 <ul>
 <li>Go to <a href="https://repository.apache.org/index.html">Nexus repository</a> → <em>Build Promotion</em> → <em>Staging repositories</em> and search for <code>org.apache.sis</code> in the <em>Repository</em> column.</li>
 <li>Right click on the closed staging repositories (<code>org.apache.sis-&lt;id&gt;</code>) and select <em>Drop</em>.</li>
 </ul>
 <p>Make the required updates that caused the vote to be canceled during the release cycle.</p>
-<h1 id="finalize">Finalize the release<a class="headerlink" href="#finalize" title="Permanent link">&para;</a></h1>
+<h1 id="finalize">Finalize the release   </h1>
 <p>The artificats in the repository are not yet mirrored and available for Maven to download.
 Promote the staged Nexus artifacts, by releasing them.</p>
 <ul>
@@ -646,94 +553,90 @@ Promote the staged Nexus artifacts, by releasing them.</p>
 <p>Check in the source and binary artifacts into distribution svn which will be pulled by all mirrors within 24 hours.
 The <code>dist/dev</code> svn is not mirrored, but the <code>dist/release</code> is.
 From any directory:</p>
-<div class="codehilite"><pre>svn move https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span> <span class="se">\</span>
-         https://dist.apache.org/repos/dist/release/sis/<span class="nv">$NEW_VERSION</span> <span class="se">\</span>
-    --message <span class="s2">&quot;Committing SIS Source and Binary Release Candidate $RELEASE_CANDIDATE for SIS-$NEW_VERSION.&quot;</span>
-
-svn delete https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span> <span class="se">\</span>
-    --message <span class="s2">&quot;Delete SIS $NEW_VERSION staging repository after release.&quot;</span>
-</pre></div>
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">svn move https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span>/RC<span class="nv">$RELEASE_CANDIDATE</span> <span class="se">\
+</span><span class="se"></span>         https://dist.apache.org/repos/dist/release/sis/<span class="nv">$NEW_VERSION</span> <span class="se">\
+</span><span class="se"></span>    --message <span class="s2">&#34;Committing SIS Source and Binary Release Candidate </span><span class="nv">$RELEASE_CANDIDATE</span><span class="s2"> for SIS-</span><span class="nv">$NEW_VERSION</span><span class="s2">.&#34;</span>
 
+svn delete https://dist.apache.org/repos/dist/dev/sis/<span class="nv">$NEW_VERSION</span> <span class="se">\
+</span><span class="se"></span>    --message <span class="s2">&#34;Delete SIS </span><span class="nv">$NEW_VERSION</span><span class="s2"> staging repository after release.&#34;</span></code></pre></div>
 <p>Update <a href="http://issues.apache.org/jira/browse/SIS">JIRA</a>:</p>
 <ul>
-<li>Update the JIRA versions to mark the version as "released".</li>
+<li>Update the JIRA versions to mark the version as &ldquo;released&rdquo;.</li>
 <li>Set the date to the date that the release was approved.</li>
-<li>Prepare for the next release:<ul>
+<li>Prepare for the next release:
+<ul>
 <li>Make a new release entry in JIRA for the next release.</li>
 <li>Update the <a href="https://cwiki.apache.org/confluence/display/SIS/Roadmap">Roadmap</a> wiki page.</li>
 </ul>
 </li>
 </ul>
-<h2 id="verify">Verify release signatures<a class="headerlink" href="#verify" title="Permanent link">&para;</a></h2>
+<h2 id="verify">Verify release signatures   </h2>
 <p>Download all source and binary artifacts into a new directory, then execute in that directory:</p>
-<div class="codehilite"><pre>find . -name <span class="s2">&quot;*.asc&quot;</span> -exec gpg --verify <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">find . -name <span class="s2">&#34;*.asc&#34;</span> -exec gpg --verify <span class="s1">&#39;{}&#39;</span> <span class="se">\;</span></code></pre></div>
 <p>The output shall report only good signatures.</p>
-<h2 id="announce">Announce the release<a class="headerlink" href="#announce" title="Permanent link">&para;</a></h2>
+<h2 id="announce">Announce the release   </h2>
 <ul>
 <li>WAIT 24 hours after committing releases for mirrors to replicate.</li>
-<li>Publish the web site updates:<ul>
+<li>Publish the web site updates:
+<ul>
 <li>Login to the <a href="https://cms.apache.org/sis/">ASF Content Management System</a>.</li>
 <li>Click on <em>Publish sis site</em>.</li>
 </ul>
 </li>
 <li>Make an announcement about the release on the <code>dev@</code>, <code>users@</code>, and <code>announce@</code> mailing lists.
-    A template is available <a href="templates/release-announce.html">here</a>.
-    The email needs to be sent from an <code>@apache.org</code> email address.</li>
+A template is available <a href="templates/release-announce.html">here</a>.
+The email needs to be sent from an <code>@apache.org</code> email address.</li>
 </ul>
 <p>Delete the prior version:</p>
-<div class="codehilite"><pre>svn delete https://dist.apache.org/repos/dist/release/sis/<span class="nv">$OLD_VERSION</span> <span class="se">\</span>
-    --message <span class="s2">&quot;Archive SIS-$OLD_VERSION after release of SIS-$NEW_VERSION.&quot;</span>
-</pre></div>
-
-
-<h1 id="next-release">Update master for the next development cycle<a class="headerlink" href="#next-release" title="Permanent link">&para;</a></h1>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">svn delete https://dist.apache.org/repos/dist/release/sis/<span class="nv">$OLD_VERSION</span> <span class="se">\
+</span><span class="se"></span>    --message <span class="s2">&#34;Archive SIS-</span><span class="nv">$OLD_VERSION</span><span class="s2"> after release of SIS-</span><span class="nv">$NEW_VERSION</span><span class="s2">.&#34;</span></code></pre></div>
+<h1 id="next-release">Update master for the next development cycle   </h1>
 <p>On the development branch (usually JDK8),
 update the version numbers in the <code>pom.xml</code> files on master with the following command:</p>
-<div class="codehilite"><pre>mvn clean
-mvn release:update-versions --define <span class="nv">autoVersionSubmodules</span><span class="o">=</span><span class="nb">true</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mvn clean
+mvn release:update-versions --define <span class="nv">autoVersionSubmodules</span><span class="o">=</span>true</code></pre></div>
 <p>This change will need to be merged manually on the JDK7 branch and on the master.
 Then on the development branch:</p>
 <ul>
 <li>Edit the version number in the <code>application/sis-console/src/main/artifact/README</code> file.</li>
 <li>Edit the value of the <code>MAJOR_VERSION</code> or <code>MINOR_VERSION</code> constant in the
-    <code>core/sis-utility/src/main/java/org/apache/sis/internal/system/Modules.java</code> file.</li>
+<code>core/sis-utility/src/main/java/org/apache/sis/internal/system/Modules.java</code> file.</li>
 </ul>
-<h2 id="nexus-clean">Delete old artifacts on Maven snapshot repository<a class="headerlink" href="#nexus-clean" title="Permanent link">&para;</a></h2>
+<h2 id="nexus-clean">Delete old artifacts on Maven snapshot repository   </h2>
 <p>Login in the <a href="https://repository.apache.org/index.html">Nexus repository</a>. In the <em>Repositories</em> tag, select <em>Snapshots</em> of type <em>hosted</em>
 (not to be confused with <em>Snapshots</em> of type <em>group</em>). Navigate to the <code>org/apache/sis</code> directory and delete
 all directories starting with the old version number. The sub-directories need to be cleaned too.</p>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
-    </div>
-  </footer>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+        </article>
+      </section>
+    </div>
+  </div>
+</div>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
+
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/release-notes/0.7.html b/release-notes/0.7.html
index 50b7fc1..be06351 100644
--- a/release-notes/0.7.html
+++ b/release-notes/0.7.html
@@ -14,7 +14,7 @@
 <h2>Summary</h2>
 <p>The main new features of Apache SIS 0.7 are:</p>
 <ul>
-  <li>Creation of Coordinate Reference System (CRS) objects from an <a href="http://www.epsg.org/">EPSG</a> code.
+  <li>Creation of Coordinate Reference System (CRS) objects from an <a href="https://epsg.org/">EPSG</a> code.
       The list of EPSG codes supported by latest SIS release can be viewed <a href="../tables/CoordinateReferenceSystems.html">here</a>.
   <li>Find coordinate operation paths from a pair of CRS, using the EPSG geodetic dataset if possible.</li>
   <li>Completion of <cite>Geographic Markup Language</cite> (GML) version 3.2 (ISO 19136) for
diff --git a/robots.txt b/robots.txt
new file mode 100644
index 0000000..00ba0ce
--- /dev/null
+++ b/robots.txt
@@ -0,0 +1,6 @@
+User-agent: *
+
+Disallow: /404/
+Disallow: 404.html
+
+SITEMAP: https://sis.apache.org/sitemap.xml
diff --git a/site-management.html b/site-management.html
index ac85149..94cd548 100644
--- a/site-management.html
+++ b/site-management.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Site management</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Site management</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,53 +37,90 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Site management</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Site management</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<!-- TODO: remove? -->
 <p>This page explains how the Apache SIS web site is created and how to update the site.
 The intended audiences are SIS release managers and SIS web site maintainers.</p>
 <p>General documentation about Apache Content Management System (CMS) can be found in the <a href="http://www.apache.org/dev/cmsref.html">CMS reference</a> page.
 The remaining of this page is specific to the SIS project.</p>
-<div class="toc">
-<ul>
-<li><a href="#directory-layout">Directory layout</a></li>
-<li><a href="#content">Content</a></li>
-<li><a href="#style-sheets">Style sheets</a><ul>
-<li><a href="#bootstrap">Updating bootstrap</a></li>
-</ul>
-</li>
-</ul>
-</div>
-<h1 id="directory-layout">Directory layout<a class="headerlink" href="#directory-layout" title="Permanent link">&para;</a></h1>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#directory-layout">Directory layout   </a></li>
+    <li><a href="#content">Content   </a></li>
+    <li><a href="#style-sheets">Style sheets</a>
+      <ul>
+        <li><a href="#bootstrap">Updating bootstrap   </a></li>
+      </ul>
+    </li>
+  </ul>
+</nav>
+<h1 id="directory-layout">Directory layout   </h1>
 <p>The source files for the Apache SIS web site can be fetched from Subversion using the following command:</p>
-<div class="codehilite"><pre>svn checkout https://svn.apache.org/repos/asf/sis/site/trunk site
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">svn checkout https://svn.apache.org/repos/asf/sis/site/trunk site</code></pre></div>
 <p>The directory layout is as below, omitting version numbers in file names.
 The <code>*</code> character stands for an arbitrary amount of files having the given extension.</p>
-<div class="codehilite"><pre>site
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text">site
 ├─ css
 │  ├─ bootstrap.min.css
 │  └─ sis.css
@@ -133,10 +133,7 @@ The <code>*</code> character stands for an arbitrary amount of files having the
 │  └─ *.mdtext
 └─ templates
    ├─ single_narrative.html
-   └─ skeleton.html
-</pre></div>
-
-
+   └─ skeleton.html</code></pre></div>
 <p>All files with the <code>.mdtext</code> extension use the Markdown format, which is described there:</p>
 <ul>
 <li><a href="http://daringfireball.net/projects/markdown/syntax">General markup syntax</a></li>
@@ -153,34 +150,25 @@ Once a staging site has been approved, it can be published to
 <li>Login to the <a href="https://cms.apache.org/sis/">ASF Content Management System</a>.</li>
 <li>Click on <em>Publish sis site</em>.</li>
 </ul>
-<h1 id="content">Content<a class="headerlink" href="#content" title="Permanent link">&para;</a></h1>
+<h1 id="content">Content   </h1>
 <p>All <code>.mdtext</code> files should start as below (replace the <code>&lt;...&gt;</code> block by the corresponding content):</p>
-<div class="codehilite"><pre><span class="n">Title</span><span class="p">:</span>  <span class="o">&lt;</span><span class="n">put</span> <span class="n">the</span> <span class="n">page</span> <span class="n">title</span> <span class="n">here</span><span class="o">&gt;</span>
-<span class="n">Notice</span><span class="p">:</span> <span class="o">&lt;</span><span class="n">copy</span> <span class="n">the</span> <span class="n">notice</span> <span class="n">from</span> <span class="n">an</span> <span class="n">existing</span> <span class="n">page</span><span class="o">&gt;</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-markdown" data-lang="markdown">Title:  <span class="p">&lt;</span><span class="nt">put</span> <span class="na">the</span> <span class="na">page</span> <span class="na">title</span> <span class="na">here</span><span class="p">&gt;</span>
+Notice: <span class="p">&lt;</span><span class="nt">copy</span> <span class="na">the</span> <span class="na">notice</span> <span class="na">from</span> <span class="na">an</span> <span class="na">existing</span> <span class="na">page</span><span class="p">&gt;</span></code></pre></div>
 <p>The title will appear both in the browser window title bar, and as a header at the beginning of the generated HTML page.
 The notice should be followed by a short abstract of the page content (typically a single paragraph),
 then a <em>Table Of Content</em> to be automatically generated:</p>
-<div class="codehilite"><pre><span class="p">[</span><span class="n">TOC</span><span class="p">]</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-markdown" data-lang="markdown">[TOC]</code></pre></div>
 <p>The first header appears after the table of content.
 For each header, and anchor should be specified using the <code>{#...}</code> syntax.
 Do not rely on automatically generated anchors, since they may not be stable if some text in the header is modified.
 Example:</p>
-<div class="codehilite"><pre><span class="n">My</span> <span class="n">first</span> <span class="n">header</span> <span class="n">in</span> <span class="n">my</span> <span class="n">page</span>    <span class="p">{</span>#<span class="n">firstHeader</span><span class="p">}</span>
-<span class="o">============================================</span>
-</pre></div>
-
-
-<h1 id="style-sheets">Style sheets<a class="headerlink" href="#style-sheets" title="Permanent link">&para;</a></h1>
+<div class="highlight"><pre class="chroma"><code class="language-markdown" data-lang="markdown">My first header in my page    {#firstHeader}
+============================================</code></pre></div>
+<h1 id="style-sheets">Style sheets</h1>
 <p>The following table lists the style sheets used by Apache SIS.
 The Maven and Javadoc style sheets are mentioned for completeness, but are not located on the web site repository.
 They are rather located together with the SIS library source code.</p>
-<table class="table">
+<table>
 <thead>
 <tr>
 <th>Page set</th>
@@ -194,7 +182,7 @@ They are rather located together with the SIS library source code.</p>
 <td>Web site</td>
 <td><code>content/css/bootstrap.min.css</code></td>
 <td>Main appearance</td>
-<td>Generated from the <a href="http://twitter.github.io/bootstrap/customize.html">Twitter's Bootstrap project</a>.</td>
+<td>Generated from the <a href="http://twitter.github.io/bootstrap/customize.html">Twitter&rsquo;s Bootstrap project</a>.</td>
 </tr>
 <tr>
 <td>Web site</td>
@@ -222,30 +210,35 @@ They are rather located together with the SIS library source code.</p>
 </tr>
 </tbody>
 </table>
-<h2 id="bootstrap">Updating bootstrap<a class="headerlink" href="#bootstrap" title="Permanent link">&para;</a></h2>
+<h2 id="bootstrap">Updating bootstrap   </h2>
 <p>If the <code>bootstrap.min.css</code> file needs to be updated, then visit the <a href="http://twitter.github.io/bootstrap/customize.html">Bootstrap</a> web site
 and select the following options:</p>
 <ul>
-<li>Scaffolding<ul>
+<li>Scaffolding
+<ul>
 <li>Body type and links</li>
 <li>Grid system</li>
 <li>Layouts</li>
 </ul>
 </li>
-<li>Components<ul>
+<li>Components
+<ul>
 <li>Navs, tabs, and pills</li>
 <li>Navbar</li>
 </ul>
 </li>
-<li>Miscellaneous<ul>
+<li>Miscellaneous
+<ul>
 <li>Wells</li>
 </ul>
 </li>
-<li>Base CSS<ul>
+<li>Base CSS
+<ul>
 <li>Code and pre</li>
 </ul>
 </li>
-<li>JS Components<ul>
+<li>JS Components
+<ul>
 <li>Dropdowns</li>
 </ul>
 </li>
@@ -260,36 +253,41 @@ Then:</p>
 <li>Add the following comment in <code>css/bootstrap.min.css</code>, just below the copyright header:</li>
 </ul>
 <p><code>bootstrap.min.css</code>:</p>
-<div class="codehilite"><pre><span class="c">/*</span>
-<span class="c"> * This file is automatically generated - DO NOT EDIT.</span>
-<span class="c"> * See http://sis.apache.org/site-management.html</span>
-<span class="c"> */</span>
-</pre></div>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
+<div class="highlight"><pre class="chroma"><code class="language-css" data-lang="css"><span class="c">/*
+</span><span class="c"> * This file is automatically generated - DO NOT EDIT.
+</span><span class="c"> * See http://sis.apache.org/site-management.html
+</span><span class="c"> */</span></code></pre></div>
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
+
+        </article>
+      </section>
     </div>
-  </footer>
+  </div>
+</div>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/sitemap.xml b/sitemap.xml
new file mode 100644
index 0000000..bc3d02f
--- /dev/null
+++ b/sitemap.xml
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
+  xmlns:xhtml="http://www.w3.org/1999/xhtml">
+  
+  <url>
+    <loc>https://sis.apache.org/downloads.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/team-list.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/gdal.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/build.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/source.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/command-line.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/faq.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/epsg.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/mail-lists.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/contributor.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/faq_fr.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/code-patterns.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/release-management.html</loc>
+    <lastmod>2021-05-13T12:05:57+02:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/release-management-setup.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/site-management.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/coding-conventions.html</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+  <url>
+    <loc>https://sis.apache.org/</loc>
+    <lastmod>2021-05-12T09:45:16+12:00</lastmod>
+  </url>
+  
+</urlset>
diff --git a/source.html b/source.html
index 4dc2548..01c03c7 100644
--- a/source.html
+++ b/source.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Checkout source code</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Checkout source code</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,31 +37,69 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Checkout source code</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>Apache SIS source code is maintained using <a href="http://git-scm.com">Git</a> version control,
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Checkout source code</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<p>Apache SIS source code is maintained using <a href="http://git-scm.com">Git</a> version control,
 completed by optional data maintained using <a href="http://subversion.apache.org">Subversion</a> version control.
 Optional data include in particular the <a href="epsg.html">EPSG geodetic dataset</a>,
 which is subject to licensing terms different than Apache ones.
@@ -106,70 +107,65 @@ This page describes two ways to checkout Apache SIS source code:</p>
 <ul>
 <li>A basic checkout with only the main repository, the most stable branch, and no configuration requirement.</li>
 <li>A more advanced configuration for active SIS developments, using uncommitted (for now) API
-    and including optional data for more extensive tests.</li>
+and including optional data for more extensive tests.</li>
 </ul>
 <p>It is possible to start with the basic checkout and migrate to the advanced configuration later,
 or to cherry-pick only the interesting parts of the advanced configuration.</p>
-<div class="toc">
-<ul>
-<li><a href="#basic">Basic installation</a></li>
-<li><a href="#advanced">Advanced installation</a><ul>
-<li><a href="#data">Create data directory</a></li>
-<li><a href="#non-free">Checkout non-free data</a></li>
-<li><a href="#postgres">Configure PostgreSQL</a></li>
-<li><a href="#tests">Running extensive tests</a></li>
-<li><a href="#branches">Switch to development branch</a></li>
-</ul>
-</li>
-<li><a href="#netbeans">Opening Apache SIS in NetBeans</a></li>
-<li><a href="#history">History</a></li>
-</ul>
-</div>
-<h1 id="basic">Basic installation<a class="headerlink" href="#basic" title="Permanent link">&para;</a></h1>
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#basic">Basic installation   </a></li>
+    <li><a href="#advanced">Advanced installation   </a>
+      <ul>
+        <li><a href="#data">Create data directory   </a></li>
+        <li><a href="#non-free">Checkout non-free data   </a></li>
+        <li><a href="#postgres">Configure PostgreSQL   </a></li>
+        <li><a href="#tests">Running extensive tests   </a></li>
+        <li><a href="#branches">Switch to development branch   </a></li>
+      </ul>
+    </li>
+    <li><a href="#netbeans">Opening Apache SIS in NetBeans   </a></li>
+    <li><a href="#history">History   </a></li>
+  </ul>
+</nav>
+<h1 id="basic">Basic installation   </h1>
 <p>Create an empty directory for the Apache SIS project.
 We use <code>ApacheSIS</code> directory name in this page, but that name can be anything;
 replace that name in the shell commands below if another name is used.
 The Apache SIS source code can be cloned in that directory as below
 (lines starting with <code>#</code> are comments and can be ignored):</p>
-<div class="codehilite"><pre>mkdir ApacheSIS
-<span class="nb">cd </span>ApacheSIS
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mkdir ApacheSIS
+<span class="nb">cd</span> ApacheSIS
 git clone https://gitbox.apache.org/repos/asf/sis
-<span class="c">#</span>
-<span class="c"># Alternatively, GitHub mirror can also be used:</span>
-<span class="c"># git clone https://github.com/apache/sis</span>
-<span class="c">#</span>
-<span class="c"># or Subversion (read-only):</span>
-<span class="c"># svn checkout https://github.com/apache/sis/trunk</span>
-</pre></div>
-
-
+<span class="c1">#</span>
+<span class="c1"># Alternatively, GitHub mirror can also be used:</span>
+<span class="c1"># git clone https://github.com/apache/sis</span>
+<span class="c1">#</span>
+<span class="c1"># or Subversion (read-only):</span>
+<span class="c1"># svn checkout https://github.com/apache/sis/trunk</span></code></pre></div>
 <p>That is all. Apache SIS can be built by running <code>mvn install</code> in the <code>sis</code> subdirectory.
 At this stage, the <code>ApacheSIS</code> parent directory is redundant with the <code>sis</code> subdirectory,
 but we recommend to create that parent directory anyway in anticipation
 for more subdirectories to be created later, when desired.
 The remaining of this page describes those optional configurations for more advanced developments.</p>
-<h1 id="advanced">Advanced installation<a class="headerlink" href="#advanced" title="Permanent link">&para;</a></h1>
+<h1 id="advanced">Advanced installation   </h1>
 <p>This section assumes that above-described basic checkout has been done.
 All subsections below are optional. It is not mandatory to execute all of them,
 but we recommend to at least create the data directory described below
 because some other optional services depend on it.</p>
-<h2 id="data">Create data directory<a class="headerlink" href="#data" title="Permanent link">&para;</a></h2>
+<h2 id="data">Create data directory   </h2>
 <p>Apache SIS needs a directory where to store database, datum shift files and other optional data.
 That directory is specified by the <code>SIS_DATA</code> environment variable and can be located anywhere.
-A convenient location is a subdirectory of the <code>ApacheSIS</code> directory created in the "basic checkout" section.
+A convenient location is a subdirectory of the <code>ApacheSIS</code> directory created in the &ldquo;basic checkout&rdquo; section.
 For example (with <code>ApacheSIS</code> as the current directory):</p>
-<div class="codehilite"><pre>mkdir Data
-<span class="nb">export </span><span class="nv">SIS_DATA</span><span class="o">=</span><span class="nv">$PWD</span>/Data
-<span class="c">#</span>
-<span class="c"># For making that environment variable available in future shell sessions,</span>
-<span class="c"># the output of following command can be added to .bash_profile or .bashrc</span>
-<span class="c"># file in user home directory.</span>
-<span class="c">#</span>
-<span class="nb">echo export </span><span class="nv">SIS_DATA</span><span class="o">=</span><span class="nv">$SIS_DATA</span>
-</pre></div>
-
-
-<h2 id="non-free">Checkout non-free data<a class="headerlink" href="#non-free" title="Permanent link">&para;</a></h2>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mkdir Data
+<span class="nb">export</span> <span class="nv">SIS_DATA</span><span class="o">=</span><span class="nv">$PWD</span>/Data
+<span class="c1">#</span>
+<span class="c1"># For making that environment variable available in future shell sessions,</span>
+<span class="c1"># the output of following command can be added to .bash_profile or .bashrc</span>
+<span class="c1"># file in user home directory.</span>
+<span class="c1">#</span>
+<span class="nb">echo</span> <span class="nb">export</span> <span class="nv">SIS_DATA</span><span class="o">=</span><span class="nv">$SIS_DATA</span></code></pre></div>
+<h2 id="non-free">Checkout non-free data   </h2>
 <p>The EPSG geodetic dataset is recommended for operations related to Coordinate Reference Systems.
 Without the EPSG database, only a <a href="apidocs/org/apache/sis/referencing/CRS.html#forCode-java.lang.String-">small subset</a>
 of coordinate reference systems can be created from EPSG codes.
@@ -177,24 +173,18 @@ The EPSG database can be <a href="epsg.html">installed in various ways</a>,
 but this section describes an alternative way more suitable to Apache SIS development.
 Before to continue, make sure to agree with <a href="https://epsg.org/terms-of-use.html">EPSG terms of use</a>.
 Then following command can be executed with <code>ApacheSIS</code> as the current directory:</p>
-<div class="codehilite"><pre><span class="c"># Executing this command imply agreement with EPSG terms of use.</span>
-svn checkout https://svn.apache.org/repos/asf/sis/data/non-free/
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="c1"># Executing this command imply agreement with EPSG terms of use.</span>
+svn checkout https://svn.apache.org/repos/asf/sis/data/non-free/</code></pre></div>
 <p>Then copy or link the EPSG scripts in the directory where Apache SIS looks for optional data.
 Adjust the relative paths as needed if the <code>SIS_DATA</code> environment variable
 points to another location than the one used in above section:</p>
-<div class="codehilite"><pre>mkdir <span class="nv">$SIS_DATA</span>/Databases
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash">mkdir <span class="nv">$SIS_DATA</span>/Databases
 mkdir <span class="nv">$SIS_DATA</span>/Databases/ExternalSources
 <span class="nb">cd</span> <span class="nv">$SIS_DATA</span>/Databases/ExternalSources
 ln -s ../../../non-free/sis-epsg/src/main/resources/org/apache/sis/referencing/factory/sql/epsg/Data.sql    EPSG_Data.sql
 ln -s ../../../non-free/sis-epsg/src/main/resources/org/apache/sis/referencing/factory/sql/epsg/FKeys.sql   EPSG_FKeys.sql
 ln -s ../../../non-free/sis-epsg/src/main/resources/org/apache/sis/referencing/factory/sql/epsg/Tables.sql  EPSG_Tables.sql
-<span class="nb">cd</span> -
-</pre></div>
-
-
+<span class="nb">cd</span> -</code></pre></div>
 <p>This is sufficient for allowing Apache SIS to create the geodetic database
 without the need for <code>sis-epsg</code> or <code>sis-embedded-data</code> module on the classpath.
 This setting is not done automatically because Apache projects can not introduce
@@ -202,7 +192,7 @@ non-free dependencies without explicit action from user.
 If this action is not taken, some JUnit tests requiring EPSG data may be skipped.
 If any EPSG file is updated, deleting the <code>$SIS_DATA/​Databases/​SpatialMetadata</code> directory
 is sufficient for causing Apache SIS to recreate the Derby database with new data.</p>
-<h2 id="postgres">Configure PostgreSQL<a class="headerlink" href="#postgres" title="Permanent link">&para;</a></h2>
+<h2 id="postgres">Configure PostgreSQL   </h2>
 <p>Apache SIS is tested with Derby, HSQL and PostgreSQL databases.
 Derby and HSQL are tested automatically using temporary databases in memory.
 But testing on PostgreSQL requires the creation of a dedicated database on the developer platform.
@@ -210,7 +200,7 @@ The requirements are:</p>
 <ul>
 <li>PostgreSQL server running and listening to <code>localhost</code> on default port (5432).</li>
 <li>A role with the same name than Unix user name of the developer running tests.</li>
-<li>An empty database named <code>"SpatialMetadataTest"</code>.</li>
+<li>An empty database named <code>&quot;SpatialMetadataTest&quot;</code>.</li>
 <li>Above-cited role can connect to <code>SpatialMetadataTest</code> database without password.</li>
 <li><code>org.apache.sis.test.extensive</code> Java property set to <code>true</code>.</li>
 </ul>
@@ -219,41 +209,32 @@ because Apache SIS always delete the temporary schema after tests completion,
 regardless if the tests were successful or not.
 The role and database can be created by the following SQL instructions
 (replace <code>my_unix_user_name</code> by your actual user name):</p>
-<div class="codehilite"><pre><span class="k">CREATE</span> <span class="k">ROLE</span> <span class="n">my_unix_user_name</span> <span class="n">LOGIN</span><span class="p">;</span>
-<span class="k">CREATE</span> <span class="k">DATABASE</span> <span class="ss">&quot;SpatialMetadataTest&quot;</span> <span class="k">WITH</span> <span class="k">OWNER</span> <span class="o">=</span> <span class="n">my_unix_user_name</span><span class="p">;</span>
-<span class="k">COMMENT</span> <span class="k">ON</span> <span class="k">DATABASE</span> <span class="ss">&quot;SpatialMetadataTest&quot;</span> <span class="k">IS</span> <span class="s1">&#39;For Apache SIS tests only.&#39;</span><span class="p">;</span>
-</pre></div>
-
-
+<div class="highlight"><pre class="chroma"><code class="language-sql" data-lang="sql"><span class="k">CREATE</span> <span class="k">ROLE</span> <span class="n">my_unix_user_name</span> <span class="n">LOGIN</span><span class="p">;</span>
+<span class="k">CREATE</span> <span class="k">DATABASE</span> <span class="s2">&#34;SpatialMetadataTest&#34;</span> <span class="k">WITH</span> <span class="k">OWNER</span> <span class="o">=</span> <span class="n">my_unix_user_name</span><span class="p">;</span>
+<span class="k">COMMENT</span> <span class="k">ON</span> <span class="k">DATABASE</span> <span class="s2">&#34;SpatialMetadataTest&#34;</span> <span class="k">IS</span> <span class="s1">&#39;For Apache SIS tests only.&#39;</span><span class="p">;</span></code></pre></div>
 <p>For opening access to that database without password, it may be necessary
 to add following line (ignoring comment lines) in the <code>pg_hba.conf</code> file.
 Location of this file is system-dependent; it may be <code>/var/​lib/​pgsql/​data</code>:</p>
-<div class="codehilite"><pre># IPv4 local connections:
+<div class="highlight"><pre class="chroma"><code class="language-text" data-lang="text"># IPv4 local connections:
 # TYPE  DATABASE               USER                 ADDRESS         METHOD
-host    SpatialMetadataTest    my_unix_user_name    127.0.0.1/32    trust
-</pre></div>
-
-
+host    SpatialMetadataTest    my_unix_user_name    127.0.0.1/32    trust</code></pre></div>
 <p>The last step for allowing Apache SIS to run tests on PostgreSQL is to set the
 <code>org.apache.sis.test.extensive</code> Java property to <code>true</code> (see next section).
 This requirement has been added for avoiding undesired interference with host.
 Note that this step is likely to change after Apache SIS upgrade to JUnit 5.</p>
-<h2 id="tests">Running extensive tests<a class="headerlink" href="#tests" title="Permanent link">&para;</a></h2>
+<h2 id="tests">Running extensive tests   </h2>
 <p>A simple <code>mvn install</code> execution in the <code>sis</code> directory
 will build and test Apache SIS with the default set of JUnit tests.
 Some tests are skipped by default, either because they would have some effects outside
 the <code>sis</code> directory (for example writing in <code>SpatialMetadataTest</code> database on PostgreSQL),
 or because those tests take a long time to execute.
 For enabling all tests, use the following command:</p>
-<div class="codehilite"><pre><span class="nb">cd </span>sis
-mvn install -Dorg.apache.sis.test.extensive<span class="o">=</span><span class="nb">true</span>
-</pre></div>
-
-
-<h2 id="branches">Switch to development branch<a class="headerlink" href="#branches" title="Permanent link">&para;</a></h2>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> sis
+mvn install -Dorg.apache.sis.test.extensive<span class="o">=</span>true</code></pre></div>
+<h2 id="branches">Switch to development branch   </h2>
 <p>The source code repository contains <code>master</code>, <code>geoapi-3.1</code> and <code>geoapi-4.0</code> branches.
 Apache SIS releases are created from <code>master</code>, which depends on the latest GeoAPI version
-released by the Open Geospatial Consortium (<abbr title="Open Geospatial Consortium">OGC</abbr>), currently <a href="http://www.geoapi.org/3.0/index.html">GeoAPI 3.0.1</a>.
+released by the Open Geospatial Consortium (OGC), currently <a href="http://www.geoapi.org/3.0/index.html">GeoAPI 3.0.1</a>.
 However daily developments occur on the <code>geoapi-4.0</code> branch before to be merged (indirectly) to <code>master</code>.
 Those branches exist in order to experiment early new API and technologies — since they may impact
 the library design — while keeping the releases compatible with officially released API.
@@ -266,18 +247,19 @@ In summary:</p>
 <p>Developments on <code>geoapi-4.0</code> branch are merged to <code>geoapi-3.1</code> branch, which is then merged to <code>master</code>.
 When commits reach <code>master</code> they become unmodifiable; the <code>git push --force</code> command is not allowed on that branch.
 Contributors to Apache SIS project should switch to the current development branch before submitting patches:</p>
-<div class="codehilite"><pre><span class="nb">cd </span>sis
-git checkout geoapi-4.0
-</pre></div>
+<div class="highlight"><pre class="chroma"><code class="language-bash" data-lang="bash"><span class="nb">cd</span> sis
+git checkout geoapi-4.0</code></pre></div>
+<p>Note that those <code>geoapi-xxx</code> branches may disappear or be replaced by something else
+after 
 
 
-<p>Note that those <code>geoapi-xxx</code> branches may disappear or be replaced by something else
-after <abbr title="Open Geospatial Consortium">OGC</abbr> releases the corresponding GeoAPI versions.</p>
-<h1 id="netbeans">Opening Apache SIS in NetBeans<a class="headerlink" href="#netbeans" title="Permanent link">&para;</a></h1>
+<abbr title="Open Geospatial Consortium">OGC</abbr>
+ releases the corresponding GeoAPI versions.</p>
+<h1 id="netbeans">Opening Apache SIS in NetBeans   </h1>
 <p>Apache SIS build is defined by Maven <code>pom.xml</code> files.
 All major IDE, including NetBeans, can open a project defined by those files.
 However in the particular case of NetBeans IDE, we also provide a way to open Apache SIS using Ant configuration files.
-Compared to "Java with Maven" project, the "Java with Ant" project is faster to build and debug,
+Compared to &ldquo;Java with Maven&rdquo; project, the &ldquo;Java with Ant&rdquo; project is faster to build and debug,
 makes easier to see all modules at once, and provides more configuration options.
 Those configuration files are available in the <code>ide-project/NetBeans</code> directory.
 This project will fetch dependencies directly from the <code>.m2/repository</code> local directory,
@@ -288,41 +270,44 @@ before opening the project and after any change in the project dependencies or i
 The <code>private</code> directory is excluded by the versioning system, so it okay to put user-specific information there.
 For example in order to overwrite the default location of the local Maven repository and to define a system property at execution time,
 one can use:</p>
-<div class="codehilite"><pre><span class="na">maven.repository</span> <span class="o">=</span> <span class="s">/path/to/my/local/repository</span>
-<span class="na">run.jvmargs</span> <span class="o">=</span> <span class="s">-DmyProperty=myValue</span>
-</pre></div>
-
-
-<h1 id="history">History<a class="headerlink" href="#history" title="Permanent link">&para;</a></h1>
+<div class="highlight"><pre class="chroma"><code class="language-ini" data-lang="ini"><span class="na">maven.repository</span> <span class="o">=</span> <span class="s">/path/to/my/local/repository</span>
+<span class="na">run.jvmargs</span> <span class="o">=</span> <span class="s">-DmyProperty=myValue</span></code></pre></div>
+<h1 id="history">History   </h1>
 <p>All developments and tags prior Apache SIS 1.0 were done on a <a href="http://subversion.apache.org">Subversion</a> repository
 and can be <a href="http://svn.apache.org/viewvc/sis/">browsed online</a>.
 Tags for Apache SIS versions 0.1 to 0.8 should be fetched from the <a href="https://svn.apache.org/repos/asf/sis/tags/">SVN repository</a>.
 The development branches on that repository were named <code>JDK8</code>, <code>JDK7</code>, <code>JDK6</code> and <code>trunk</code>.</p>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
+
+        </article>
+      </section>
     </div>
-  </footer>
+  </div>
+</div>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
+
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>
diff --git a/tables/CoordinateOperationMethods.html b/tables/CoordinateOperationMethods.html
index 32b4e15..9e538d2 100644
--- a/tables/CoordinateOperationMethods.html
+++ b/tables/CoordinateOperationMethods.html
@@ -23,8 +23,8 @@
           The <code>semi-major</code> and <code>semi-minor</code> parameters are needed for all map projections,
           but usually do not need to be specified explicitly since they are inferred from the ellipsoid
           (unless <a href="http://sis.apache.org/apidocs/org/apache/sis/referencing/operation/transform/DefaultMathTransformFactory.html">creating parameterized transforms directly</a>).
-          For this reason, those parameters are usually not shown in <a href="http://www.epsg-registry.org">EPSG registry</a>
-          or <a href="http://docs.opengeospatial.org/is/12-063r5/12-063r5.html">Well Known Text</a> (WKT) definitions.
+          For this reason, those parameters are usually not shown in <a href="https://epsg.org/">EPSG registry</a>
+          or <a href="https://docs.ogc.org/is/12-063r5/12-063r5.html">Well Known Text</a> (WKT) definitions.
         </li><li>
           The <code>earth_radius</code> and <code>inverse_flattening</code> parameters (not shown below) are implicitly supported by all map projections.
           They are other ways to specify the ellipsoid (actually rarely used).
diff --git a/team-list.html b/team-list.html
index 809e265..1abd8a9 100644
--- a/team-list.html
+++ b/team-list.html
@@ -1,72 +1,35 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <title>Apache SIS team</title>
-    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
-    <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+<head>
+  
 
-    
+  <title>Apache SIS - Apache SIS team</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    
-    <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.  See the NOTICE file distributed with this work for additional information regarding copyright ownership.  The ASF licenses this file to you under the Apache License, Version 2.0 (the &quot;License&quot;); you may not use this file except in compliance with the License.  You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applic [...]
-  </head>
+  <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/syntax.css">
+  <link rel="stylesheet" type="text/css" media="screen" href="css/sis.css">
+</head>
 
-  <body>
-    <div class="navbar navbar-inverse navbar-fixed-top">
-      <div class="navbar-inner">
-        <div class="container">
-          <a class="brand" href="/index.html"> Apache SIS&trade;</a>
-          <div class="nav-collapse">
-            <ul class="nav">
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org/licenses/">License</a></li>
-                  <li><a href="mail-lists.html">Mailing Lists</a></li>
-                  <li><a href="team-list.html">Project Team</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="book/index.html">Developer Guide</a></li>
-                  <li><a href="apidocs/index.html">Online Javadoc</a></li>
-                  <li><a href="downloads.html">Downloads</a></li>
-                  <li><a href="source.html">Checkout Sources</a></li>
-                  <li><a href="epsg.html">EPSG Database</a></li>
-                  <li><a href="faq.html">FAQ</a></li>
-                  <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-                </ul>
-              </li>
-              <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
-                <ul class="dropdown-menu">
-                  <li><a href="http://www.apache.org">The Foundation</a></li>
-                  <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
-                  <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
-                  <li><a href="http://www.apache.org/security/">Security</a></li>
-                </ul>
-              </li>
-            </ul>
-          </div><!-- /.nav-collapse -->
-        </div><!-- /.container -->
-      </div><!-- /.navbar-inner -->
-    </div>
+<body>
 
-    <div class="container-fluid">
-      <div class="row-fluid">
-        <div class="span2">
-          <div class="apache-con">
-            <a href="https://www.apache.org/events/current-event.html">
-              <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
-            </a>
-          </div>
-          <div class="well sidebar-nav">
-            <ul class="nav nav-list">
-              <li><a href="index.html">Home</a></li>
+<div class="navbar navbar-inverse navbar-fixed-top">
+  <div class="navbar-inner">
+    <div class="container">
+      <a class="brand" href="/index.html"> Apache SIS&trade;</a>
+      <div class="nav-collapse">
+        <ul class="nav">
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">About<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org/licenses/">License</a></li>
               <li><a href="mail-lists.html">Mailing Lists</a></li>
               <li><a href="team-list.html">Project Team</a></li>
-              <li class="nav-header">Project Documentation</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">Project Documentation<b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="book/index.html">Developer Guide</a></li>
               <li><a href="apidocs/index.html">Online Javadoc</a></li>
               <li><a href="downloads.html">Downloads</a></li>
@@ -74,31 +37,69 @@
               <li><a href="epsg.html">EPSG Database</a></li>
               <li><a href="faq.html">FAQ</a></li>
               <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
-              <li class="nav-header">ASF</li>
+            </ul>
+          </li>
+          <li class="dropdown"> <a class="dropdown-toggle" data-toggle="dropdown">ASF <b class="caret"></b></a>
+            <ul class="dropdown-menu">
               <li><a href="http://www.apache.org">The Foundation</a></li>
               <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
               <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
               <li><a href="http://www.apache.org/security/">Security</a></li>
             </ul>
-          </div><!--/.well -->
-        </div><!--/span-->
-        <div class="span10">
-          <section id="content" class="row">
-            <article class="span12">
-              <img src="img/logo.png" class="sis-logo" align="left"/>
-              <p class="page-title">Apache SIS team</p>
-              <style type="text/css">
-/* The following code is added by mdx_elementid.py
-   It was originally lifted from http://subversion.apache.org/style/site.css */
-/*
- * Hide class="elementid-permalink", except when an enclosing heading
- * has the :hover property.
- */
-.headerlink, .elementid-permalink {
-  visibility: hidden;
-}
-h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<h2 id="pmc">Project Management Committee (PMC)<a class="headerlink" href="#pmc" title="Permanent link">&para;</a></h2>
+          </li>
+        </ul>
+      </div>
+    </div>
+  </div>
+</div>
+
+
+<div class="container-fluid">
+  <div class="row-fluid">
+    <div class="span2">
+      <div class="apache-con">
+        <a href="https://www.apache.org/events/current-event.html">
+          <img src="https://www.apache.org/events/current-event-234x60.png" alt="ApacheCon"/>
+        </a>
+      </div>
+      <div class="well sidebar-nav">
+        <ul class="nav nav-list">
+          <li><a href="index.html">Home</a></li>
+          <li><a href="http://www.apache.org/licenses/">License</a></li>
+          <li><a href="mail-lists.html">Mailing Lists</a></li>
+          <li><a href="team-list.html">Project Team</a></li>
+          <li class="nav-header">Project Documentation</li>
+          <li><a href="book/index.html">Developer Guide</a></li>
+          <li><a href="apidocs/index.html">Online Javadoc</a></li>
+          <li><a href="downloads.html">Downloads</a></li>
+          <li><a href="source.html">Checkout Sources</a></li>
+          <li><a href="epsg.html">EPSG Database</a></li>
+          <li><a href="faq.html">FAQ</a></li>
+          <li><a href="https://issues.apache.org/jira/browse/SIS">Issue Tracker</a></li>
+          <li class="nav-header">ASF</li>
+          <li><a href="http://www.apache.org">The Foundation</a></li>
+          <li><a href="http://www.apache.org/foundation/sponsorship.html">Donate</a></li>
+          <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+          <li><a href="http://www.apache.org/security/">Security</a></li>
+        </ul>
+      </div>
+    </div>
+    <div class="span10">
+      <section id="content" class="row">
+        <article class="span12">
+          <img src="img/logo.png" class="sis-logo" align="left"/>
+          <p class="page-title">Apache SIS team</p>
+          
+          <style type="text/css">
+               
+               
+              .headerlink, .elementid-permalink {
+                  visibility: hidden;
+              }
+              h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
+          </style>
+          
+	<h2 id="pmc">Project Management Committee (PMC)   </h2>
 <p>The Project Management Committee (PMC) is the group of people with formal oversight of the project.</p>
 <ul>
 <li>Adam Estrada</li>
@@ -111,7 +112,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
 <li>Martin Desruisseaux</li>
 <li>Nga Thien Chung</li>
 <li>Olivier Nouguier</li>
-<li>Patrick O'Leary</li>
+<li>Patrick O&rsquo;Leary</li>
 <li>Paul Michael Ramirez</li>
 <li>Peter Karich</li>
 <li>Ross Laidlaw</li>
@@ -119,7 +120,7 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
 <li><a href="http://people.apache.org/~smarru/">Suresh Marru</a></li>
 <li>Travis Pinney</li>
 </ul>
-<h2 id="committers">Committers<a class="headerlink" href="#committers" title="Permanent link">&para;</a></h2>
+<h2 id="committers">Committers   </h2>
 <p>Committers are peoples with write access to the source code repository.
 All PMC members are implicitly committers.</p>
 <ul>
@@ -127,7 +128,7 @@ All PMC members are implicitly committers.</p>
 <li>Christina Hough</li>
 <li>Rémi Maréchal</li>
 </ul>
-<h2 id="contributors">Contributors<a class="headerlink" href="#contributors" title="Permanent link">&para;</a></h2>
+<h2 id="contributors">Contributors   </h2>
 <p>Contributors are peoples who contributed to the project through emails, patches, merge requests, mentoring
 or other means.</p>
 <ul>
@@ -141,7 +142,7 @@ or other means.</p>
 <li>Thi Phuong Hao Nguyen</li>
 <li>Touraïvane</li>
 </ul>
-<h2 id="emeritus">Emeritus members<a class="headerlink" href="#emeritus" title="Permanent link">&para;</a></h2>
+<h2 id="emeritus">Emeritus members   </h2>
 <p>Emeritus members are peoples who are no longer active (for example because they no longer have time to work on the project)
 but are still entitled to many of the rights and privileges of the position.
 Emeritus status indicates interest but not activity, as opposed to having resigned.</p>
@@ -150,31 +151,37 @@ Emeritus status indicates interest but not activity, as opposed to having resign
 <li>Ian Holsman</li>
 <li>Joe Schaefer</li>
 </ul>
-            </article>
-          </section>
-        </div><!--/span-->
-      </div><!--/row-fluid-->
-    </div><!--/container-fluid-->
 
-  <footer class="footer">
-    <div class="container">
-      <p>Copyright &copy; 2013-2019 The Apache Software Foundation, Licensed under the
-        <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br />
-          Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.</p>
+
+        </article>
+      </section>
     </div>
-  </footer>
+  </div>
+</div>
+
+<footer class="footer">
+  <div class="container">
+    <p>
+      Copyright &copy; 2013-2021 The Apache Software Foundation, Licensed under the
+      <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+    </p>
+    <p>
+      Apache SIS, Apache, the Apache feather logo are trademarks of The Apache Software Foundation.
+    </p>
+  </div>
+</footer>
 
-  <script src="js/jquery-1.9.1.min.js"></script>
-  <script src="js/bootstrap.min.js"></script>
+<script src="js/jquery-1.9.1.min.js"></script>
+<script src="js/bootstrap.min.js"></script>
 
-  <!-- for marking links as active in the navbar-menu -->
-  <script type="text/javascript">
-    var pathname = this.location.pathname;
-    pathname = pathname.substring(1, pathname.length);
-    var link = $('a[href="' + pathname + '"]');
-    if (link != undefined)
-      link.parents('li,ul').addClass('active');
-  </script>
+<script type="text/javascript">
+const pathname = window.location.pathname
+const current_path = pathname.substring(1, pathname.length)
+const link = $('a[href="' + current_path + '"]')
+if (link !== undefined) {
+  link.parents('li,ul').addClass('active')
+}
+</script>
 
 </body>
 </html>