sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From desruisse...@apache.org
Subject svn commit: r1809817 - in /sis/site/trunk: book/en/annex/DesignNotes.html book/en/referencing/ComponentsOfCRS.html content/faq.mdtext content/release-management-setup.mdtext
Date Wed, 27 Sep 2017 08:51:32 GMT
Author: desruisseaux
Date: Wed Sep 27 08:51:32 2017
New Revision: 1809817

URL: http://svn.apache.org/viewvc?rev=1809817&view=rev
Log:
Grammatical correction: "software" has no plural form.

Modified:
    sis/site/trunk/book/en/annex/DesignNotes.html
    sis/site/trunk/book/en/referencing/ComponentsOfCRS.html
    sis/site/trunk/content/faq.mdtext
    sis/site/trunk/content/release-management-setup.mdtext

Modified: sis/site/trunk/book/en/annex/DesignNotes.html
URL: http://svn.apache.org/viewvc/sis/site/trunk/book/en/annex/DesignNotes.html?rev=1809817&r1=1809816&r2=1809817&view=diff
==============================================================================
--- sis/site/trunk/book/en/annex/DesignNotes.html [UTF-8] (original)
+++ sis/site/trunk/book/en/annex/DesignNotes.html [UTF-8] Wed Sep 27 08:51:32 2017
@@ -40,7 +40,7 @@
 
       <h3 id="AffineTransform">Affine transform</h3>
       <p>
-        Among the many kinds of operations performed by <abbr>GIS</abbr> softwares
on spatial coordinates,
+        Among the many kinds of operations performed by <abbr>GIS</abbr> software
products on spatial coordinates,
         <cite>affine transforms</cite>  are both relatively simple and very common.
         Affine transforms can represent any combination of scales, shears, flips, rotations
and translations,
         which are <em>linear</em> operations.

Modified: sis/site/trunk/book/en/referencing/ComponentsOfCRS.html
URL: http://svn.apache.org/viewvc/sis/site/trunk/book/en/referencing/ComponentsOfCRS.html?rev=1809817&r1=1809816&r2=1809817&view=diff
==============================================================================
--- sis/site/trunk/book/en/referencing/ComponentsOfCRS.html [UTF-8] (original)
+++ sis/site/trunk/book/en/referencing/ComponentsOfCRS.html [UTF-8] Wed Sep 27 08:51:32 2017
@@ -140,13 +140,13 @@
       </p><p>
         Recent <abbr>OGC</abbr> standards mandate the use of axis order as defined
by the authority.
         Oldest <abbr>OGC</abbr> standards used the (<var>x</var>,
<var>y</var>) axis order instead, ignoring any authority specification.
-        Many softwares still use the old (<var>x</var>, <var>y</var>)
axis order,
+        Many software products still use the old (<var>x</var>, <var>y</var>)
axis order,
         maybe because such uniformization makes <abbr>CRS</abbr> implementation
and usage <em>apparently</em> easier.
         Apache <abbr>SIS</abbr> supports both conventions with the following
approach:
         by default, <abbr>SIS</abbr> creates <abbr>CRS</abbr> with
axis order <em>as defined by the authority</em>.
         Those <abbr>CRS</abbr> are created by calls to the <code>CRS.forCode(String)</code>
method
         and the actual axis order can be verified after the <abbr>CRS</abbr>
creation with <code>System.out.println(crs)</code>.
-        But if (<var>x</var>, <var>y</var>) axis order is wanted
for compatibility with older <abbr>OGC</abbr> specifications or other softwares,
+        But if (<var>x</var>, <var>y</var>) axis order is wanted
for compatibility with older <abbr>OGC</abbr> specifications or other software
products,
         then <abbr>CRS</abbr> forced to <cite>longitude first</cite>
axis order can be created by a call to the following method:
       </p>
 

Modified: sis/site/trunk/content/faq.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/faq.mdtext?rev=1809817&r1=1809816&r2=1809817&view=diff
==============================================================================
--- sis/site/trunk/content/faq.mdtext (original)
+++ sis/site/trunk/content/faq.mdtext Wed Sep 27 08:51:32 2017
@@ -110,7 +110,7 @@ shall default to (_longitude_, _latitude
 In version 2 of the WKT format, `AXIS[…]` elements are no longer optional
 and should contain an explicit `ORDER[…]` sub-element for making the intended order
yet more obvious.
 
-Many softwares still use the old (_x_, _y_) axis order, sometime because it is easier to
implement.
+Many software products still use the old (_x_, _y_) axis order, sometime because it is easier
to implement.
 But Apache SIS rather defaults to axis order _as defined by the authority_ (except when parsing
a WKT 1 definition),
 but allows changing axis order to the (_x_, _y_) order after CRS creation.
 This change can be done with the following code:

Modified: sis/site/trunk/content/release-management-setup.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/release-management-setup.mdtext?rev=1809817&r1=1809816&r2=1809817&view=diff
==============================================================================
--- sis/site/trunk/content/release-management-setup.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/release-management-setup.mdtext [UTF-8] Wed Sep 27 08:51:32 2017
@@ -94,7 +94,7 @@ Add or modify the following line in the
 
 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.
+signing Apache software packages - not for daily emails.
 
     :::bash
     gpg --gen-key



Mime
View raw message