sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1018786 - in /websites/staging/sis/trunk/content: ./ faq.html release-management-setup.html
Date Wed, 27 Sep 2017 08:51:44 GMT
Author: buildbot
Date: Wed Sep 27 08:51:43 2017
New Revision: 1018786

Log:
Staging update by buildbot for sis

Modified:
    websites/staging/sis/trunk/content/   (props changed)
    websites/staging/sis/trunk/content/faq.html
    websites/staging/sis/trunk/content/release-management-setup.html

Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Sep 27 08:51:43 2017
@@ -1 +1 @@
-1807804
+1809817

Modified: websites/staging/sis/trunk/content/faq.html
==============================================================================
--- websites/staging/sis/trunk/content/faq.html (original)
+++ websites/staging/sis/trunk/content/faq.html Wed Sep 27 08:51:43 2017
@@ -206,7 +206,7 @@ According that widely-used format, WKT d
 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>
-<p>Many softwares still use the old (<em>x</em>, <em>y</em>)
axis order, sometime because it is easier to implement.
+<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>

Modified: websites/staging/sis/trunk/content/release-management-setup.html
==============================================================================
--- websites/staging/sis/trunk/content/release-management-setup.html (original)
+++ websites/staging/sis/trunk/content/release-management-setup.html Wed Sep 27 08:51:43 2017
@@ -165,7 +165,7 @@ Add or modify the following line in the
 
 <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 softwares - not for daily emails.</p>
+signing Apache software packages - not for daily emails.</p>
 <div class="codehilite"><pre>gpg --gen-key
 </pre></div>
 



Mime
View raw message