Fix trailing whitespace and end-of-file errors (#853)

src/Makefile

@@ -15,4 +15,3 @@ SUBDIRS = \
 include $(MODULE_TOPDIR)/include/Make/Dir.make
 
 default: parsubdirs
-

src/display/d.frame/d.frame.html

@@ -20,15 +20,15 @@ <h2>NOTES</h2>
 monitor's lower-right corner is always at 100,100.
 
 <p>
-If the user has created multiple display frames that overlap one another, 
-whatever the user displays in the active frame will overwrite 
-those portions of the underlying frame where these frames overlap. 
+If the user has created multiple display frames that overlap one another,
+whatever the user displays in the active frame will overwrite
+those portions of the underlying frame where these frames overlap.
 
 <p>
 <b>Important note:</b> This version of <em>d.frame</em> works only
 with GRASS 7.0. Further versions of GRASS come with their own
 built-in <em>d.frame</em> module.
-  
+
 <h2>EXAMPLE</h2>
 
 <div class="code"><pre>
@@ -84,7 +84,7 @@ <h2>SEE ALSO</h2>
 <p>
   <a href="https://grass.osgeo.org/grass-stable/manuals/variables.html#list-of-selected-grass-environment-variables-for-rendering">GRASS environment variables for
   rendering</a> (GRASS_RENDER_FRAME)
-  
+
 <h2>AUTHORS</h2>
 
 Martin Landa, Czech Technical University in Prague, Czech Republic
@@ -93,5 +93,5 @@ <h2>AUTHORS</h2>
 Based on <em>d.frame</em> from GRASS 6:<br>
 James Westervelt, U.S. Army Construction Engineering Research
 Laboratory<br>
-Michael Shapiro, U.S. Army Construction Engineering 
+Michael Shapiro, U.S. Army Construction Engineering
 Research Laboratory

src/display/d.vect.colbp/d.vect.colbp.html

@@ -1,38 +1,38 @@
 <h2>DESCRIPTION</h2>
 
 <p>
-<em>d.vect.colbp</em> draws a boxplot of the values in a vector 
-<em>map</em> attribute <em>column</em>. The user can use the 
-<em>where</em> option to only select a subset of the attribute table. 
-There is also the option to group the values of the column according to 
-the categories in a second column (<em>group_by</em> and create one plot 
+<em>d.vect.colbp</em> draws a boxplot of the values in a vector
+<em>map</em> attribute <em>column</em>. The user can use the
+<em>where</em> option to only select a subset of the attribute table.
+There is also the option to group the values of the column according to
+the categories in a second column (<em>group_by</em> and create one plot
 with for each group a separate boxplot.
 
 <p>
-By default, the resulting plot is displayed on screen (default). 
-However, the user can also save the plot to file using the 
-<em>plot_output</em> option. The format is determined by the extension 
-given by the user. So, if plot_output = outputfile.png, the plot will 
+By default, the resulting plot is displayed on screen (default).
+However, the user can also save the plot to file using the
+<em>plot_output</em> option. The format is determined by the extension
+given by the user. So, if plot_output = outputfile.png, the plot will
 be saved as a png file.
 
 <p>
-There are a few additonal layout options, including the option to rotate 
-the plot and the x-axis labels. Furthermore, the user can optinally plot 
+There are a few additonal layout options, including the option to rotate
+the plot and the x-axis labels. Furthermore, the user can optinally plot
 the boxplot(s) with notches and without outliers.
 
 <h2>NOTE</h2>
 <p>
-This script, based on d.vect.colhist, is a quick and dirty solution 
-sing basic matplotlib, and will need some further fine-tuning and 
+This script, based on d.vect.colhist, is a quick and dirty solution
+sing basic matplotlib, and will need some further fine-tuning and
 testing.
 
 <h2>EXAMPLE</h2>
 
 <h3>Example 1</h3>
-Use the vector layer <em>schools_wake</em> from the 
-<a href="https://grass.osgeo.org/download/data/">NC sample 
-dataset</a> to create boxplots of the core capacity of the schools in 
-Wake County, North Carolina. Use the <em>Where</em> clause to exclude 
+Use the vector layer <em>schools_wake</em> from the
+<a href="https://grass.osgeo.org/download/data/">NC sample
+dataset</a> to create boxplots of the core capacity of the schools in
+Wake County, North Carolina. Use the <em>Where</em> clause to exclude
 all records with no data.
 
 <div class="code"><pre>
@@ -46,11 +46,11 @@ <h3>Example 1</h3>
 
 
 <h3>Example 2</h3>
-Use the vector layer <em>schools_wake</em> from the 
-<a href="https://grass.osgeo.org/download/data/">NC sample 
-dataset</a> to create boxplots of the core capacity of the schools in 
-Wake County, North Carolina, grouped by city. Use the <em>Where</em> 
-clause to exclude all records with no data. 
+Use the vector layer <em>schools_wake</em> from the
+<a href="https://grass.osgeo.org/download/data/">NC sample
+dataset</a> to create boxplots of the core capacity of the schools in
+Wake County, North Carolina, grouped by city. Use the <em>Where</em>
+clause to exclude all records with no data.
 
 <div class="code">
 <pre>
@@ -66,4 +66,4 @@ <h3>Example 2</h3>
 <h2>AUTHOR</h2>
 
 Paulo van Breugel<br>
-Based on the d.vect.colhist addon by Moritz Lennert  
+Based on the d.vect.colhist addon by Moritz Lennert

src/display/d.vect.colhist/d.vect.colhist.html

@@ -1,17 +1,17 @@
 <h2>DESCRIPTION</h2>
 
 <p>
-<em>d.vect.colhist</em> draws a histogram of the values in a vector 
+<em>d.vect.colhist</em> draws a histogram of the values in a vector
 <em>map</em> attribute <em>column</em>. The user use the <em>where</em>
-option to only select a subset of the attribute table and can determine the 
+option to only select a subset of the attribute table and can determine the
 number of <em>bins</em> (bars) used for the histogram. The <em>plot_output</em>
 parameter determines whether the result is displayed on screen (default) or
 exported to a graphics file.
 
 <h2>NOTE</h2>
 <p>
-This is a quick and dirty solution using basic matplotlib. In future, this 
-should be integrated into the g.gui, possibly together with the raster 
+This is a quick and dirty solution using basic matplotlib. In future, this
+should be integrated into the g.gui, possibly together with the raster
 histogram tool.
 
 <h2>EXAMPLE</h2>

src/display/d.vect.thematic2/d.vect.thematic2.html

@@ -44,7 +44,7 @@ <h2>NOTES</h2>
 contains 'label' commands which allow to create a legend directly in the map by
 adding a 'vlegend' command. See the <em><a href="ps.map">ps.map</a></em> manual
 page for more details.
- 
+
 <p>
 The algorithm currently uses the <em><a href="https://grass.osgeo.org/grass-stable/manuals/v.univar.html">v.univar</a></em> to calculate basic
 descriptive statistics needed for thematic mapping (minimum, maximum, mean,

src/general/g.copyall/g.copyall.html

@@ -1,7 +1,7 @@
 <h2>DESCRIPTION</h2>
 
 <em><b>g.copyall</b></em> copies maps/files of a specified from a selected mapset
-to the current working mapset. All maps/files can be copied or a subset of 
+to the current working mapset. All maps/files can be copied or a subset of
 maps/files specified by a wildcard pattern or regular expression. Optionally, a
 prefix can be added to all files copied and vector topology can be rebuilt to match
 currently running version of GRASS.

src/gui/wxpython/wx.metadata/config/default-sample.cfg

@@ -95,4 +95,3 @@ conformity_service=notEvaluated
 contact_name=Organization Name
 contact_email=Email Address
 temp_extent=YYYY-MM-DD/YYYY-MM-DD
-

src/gui/wxpython/wx.metadata/config/xml_highlight.html

@@ -10,4 +10,4 @@
     <body>
     {{ body }}
     </body>
-</html>
+</html>

src/gui/wxpython/wx.metadata/g.gui.cswbrowser/g.gui.cswbrowser.html

@@ -8,7 +8,7 @@ <h2>DESCRIPTION</h2>
 
 <h2>NOTES</h2>
 
-For dependencies and installation instructions see the dedicated 
+For dependencies and installation instructions see the dedicated
 <a href="http://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support">wiki page</a>.
 
 <h3>Setting up connection</h3>

src/gui/wxpython/wx.metadata/g.gui.metadata/g.gui.metadata.html

@@ -4,24 +4,24 @@ <h2>DESCRIPTION</h2>
 to <a href="http://www.iso.org/iso/catalogue_detail.htm?csnumber=26020">ISO 19115</a>.
 
 <p>
-The metadata editor includes a graphical interface for converting metadata 
-from r.info and v.info into ISO based metadata, editing metadata files and 
-creating metadata templates. In addition, the graphical module allows validating 
+The metadata editor includes a graphical interface for converting metadata
+from r.info and v.info into ISO based metadata, editing metadata files and
+creating metadata templates. In addition, the graphical module allows validating
 INSPIRE and GRASS Basic profile.
 
 <h2>NOTES</h2>
 
-For dependencies and installation instructions see the dedicated 
+For dependencies and installation instructions see the dedicated
 <a href="http://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support">wiki page</a>.
 
 <h3>Naming of metadata files and storage</h3>
 
-Default location for exported metadata files is the <i>metadata</i> directory 
-in the map's mapset. For raster maps, the prefix derived from the current 
-nomenclature is <em>raster</em>, and for vector maps <em>vector</em>. The files 
+Default location for exported metadata files is the <i>metadata</i> directory
+in the map's mapset. For raster maps, the prefix derived from the current
+nomenclature is <em>raster</em>, and for vector maps <em>vector</em>. The files
 end with <em>.xml</em> extension.
 <p>
-For example, default metadata file name for the vector map &quot;roads&quot; 
+For example, default metadata file name for the vector map &quot;roads&quot;
 is <em>vector_roads.xml</em>.
 
 <h3>Metadata profile</h3>
@@ -31,78 +31,78 @@ <h3>Metadata profile</h3>
 intersect (subset) includes all available GRASS metadata. Metadata
 which cannot be assigned to ISO based attributes are stored in
 metadata attribute <em>abstract</em>. The <i>inspire</i> profile
-fulfills the criteria of INSPIRE profile. Values that cannot be read from 
-native GRASS metadata are filled by the text string <tt>'$NULL'</tt>. 
+fulfills the criteria of INSPIRE profile. Values that cannot be read from
+native GRASS metadata are filled by the text string <tt>'$NULL'</tt>.
 This rule applies for both profiles.
 
 <h4>Profile for temporal dataset</h4>
 
-This function is based on t.info.iso which allows to create ISO based metadata 
-for temporal maps. Product of this function cannot be compiled by INSPIRE profile 
+This function is based on t.info.iso which allows to create ISO based metadata
+for temporal maps. Product of this function cannot be compiled by INSPIRE profile
 because an additional attribute from ISO 19115 package have been added.
 <!-- have or have not? -->
 
 <h3>Creation of metadata</h3>
 
-The editor offers two editing modes. The first one allows to create metadata 
-from selected GRASS maps from an active location. The second one allows editing 
+The editor offers two editing modes. The first one allows to create metadata
+from selected GRASS maps from an active location. The second one allows editing
 of an external metadata file.
 
 <h4>Metadata editor for spatial and temporal maps</h4>
 
-The basis of this editor is similar to r|v.info.iso. After the selection of the 
-map, the editor converts native metadata of map to ISO based metadata. 
-By exported xml file is metadata editor initialized. 
+The basis of this editor is similar to r|v.info.iso. After the selection of the
+map, the editor converts native metadata of map to ISO based metadata.
+By exported xml file is metadata editor initialized.
 <!-- This last sentence is not clear-->
 There are three options to select:
-<b>basic</b>, <b>inspire</b> or <b>load custom</b>. The last one allows to load 
-a metadata profile from a file, for example in the case of using a predefined 
-template. The intersection of GRASS Basic profile (all the available metadata 
+<b>basic</b>, <b>inspire</b> or <b>load custom</b>. The last one allows to load
+a metadata profile from a file, for example in the case of using a predefined
+template. The intersection of GRASS Basic profile (all the available metadata
 for the selected map) and loaded custom profile will proceed with this selection.
 <!-- This last sentence is not clear-->
 
 <h4> External metadata editor</h4>
 
-This editor mode allows to load user own templates and xml files for editing. 
+This editor mode allows to load user own templates and xml files for editing.
 This option does not support any connection with GRASS maps metadata.
 
 <h3>Defining templates</h3>
 
 <p>
-This function allows to create pattern of metadata profile. In other words it 
-supports defining fixed values to template. When using created template, the 
-editor does not initialize texts inputs of defined values. These attributes are 
-only visible in the Tree Browser in the editor. Direct link on this function is 
+This function allows to create pattern of metadata profile. In other words it
+supports defining fixed values to template. When using created template, the
+editor does not initialize texts inputs of defined values. These attributes are
+only visible in the Tree Browser in the editor. Direct link on this function is
 multiple editing mode (see below).
 <p>
-If the check-box of metadata attribute is checked, the OWSLib object in the 
-template will be replaced by value. Unchecked attributes will not change this 
+If the check-box of metadata attribute is checked, the OWSLib object in the
+template will be replaced by value. Unchecked attributes will not change this
 'part' of the template.
 <p>
-The yellow background of the text fields indicates metadata attributes that 
+The yellow background of the text fields indicates metadata attributes that
 cannot be read from GRASS map information.
 
 <h3>Editing metadata of multiple map selection</h3>
 
-This option can be used by selecting multiple maps in the data catalog. It is 
-possible to use predifined templates with this editing mode. 
+This option can be used by selecting multiple maps in the data catalog. It is
+possible to use predifined templates with this editing mode.
 <!--To use pre-defined template for this editing mode is suitable-->
 
 <h3>Validation of metadata profile </h3>
 
-On the right side of editor there is a validator of metadata. Currently, 
-validator is able to validate two build-in profiles. 
+On the right side of editor there is a validator of metadata. Currently,
+validator is able to validate two build-in profiles.
 <!--For selection of profile “Load custom” is set by default the inspire profile.-->
 
 <h3>Updating GRASS native metadata </h3>
 
-The g.gui.metadata module allows to update native GRASS metadata with the 
-modules r.support and v.support. The intersection between ISO based metadata 
+The g.gui.metadata module allows to update native GRASS metadata with the
+modules r.support and v.support. The intersection between ISO based metadata
 and r|v.support is limited by the available parameters for these modules.
 
 <h3>Creating reports for GRASS maps in PDF format</h3>
 
-This function allows to automatically generate metadata reports as PDF documents. 
+This function allows to automatically generate metadata reports as PDF documents.
 Missing values are replaced by "Unknown" string.
 
 <h2>SEE ALSO</h2>

src/gui/wxpython/wx.metadata/profiles/basicProfile.xml

@@ -155,4 +155,3 @@
     </gmd:DQ_DataQuality>
   </gmd:dataQualityInfo>
         </gmd:MD_Metadata>
-

src/gui/wxpython/wx.metadata/profiles/inspireProfile.xml

@@ -125,7 +125,7 @@
             <gmd:descriptiveKeywords>
                 <gmd:MD_Keywords>
           {% for kw in k["keywords"] -%}{# tag='for kw in k["keywords"]',group = "Keywords",inbox="Free keywords",inboxmulti=1 #}
-                    
+
                     <gmd:keyword>
                         <gco:CharacterString>{{ kw }}{# tag="kw",ref="Part B 3.1", name ="Keyword",example="Land cover (INSPIRE Spatial Data Theme),humanCatalogueViewer (spatial data service,subcategory), water springs (AGROVOC), freshwater (GEMET Concepts)", desc ="Commonly used word(s) or formalised word(s) or phrase(s) used to describe the subject." , type = "string",inboxmulti=1, multi = 1, group = "Keywords", multiline=False, inbox="Free keywords",database="keywords" #} </gco:CharacterString>
                     </gmd:keyword>
@@ -188,7 +188,7 @@
             </gmd:spatialResolution>
       {% endfor -%}
       {% endif -%}
-      
+
       {% for lan in md.identification.resourcelanguage -%}{# tag="for lan in md.identification.resourcelanguage" , group= "Identification" ,inbox='Languages',inboxmulti=1, multiline= False, database="language" #}
             <gmd:language>
                 <gmd:LanguageCode codeList="http://www.isotc211.org/2005/resources/Codelist/ML_gmxCodelists.xml#LanguageCode" codeListValue="{{ lan }}{# tag="lan" , name="Metadata language" , ref= "Part B 10.3" , desc= "Language used for documenting metadata." , example = "eng" , type ="LanguageCode (ISO/TS 19139)" ,multi=0,inbox='Languages',inboxmulti=1, group= "Identification" , multiline= False, database="language" #}">{{ lan }}</gmd:LanguageCode>
@@ -331,4 +331,4 @@
       </gmd:lineage>
     </gmd:DQ_DataQuality>
   </gmd:dataQualityInfo>
-</gmd:MD_Metadata>
+</gmd:MD_Metadata>

src/gui/wxpython/wx.metadata/profiles/temporalProfile.xml

@@ -134,18 +134,18 @@
                <gmd:temporalElement>
                   <gmd:EX_TemporalExtent>
                      <gmd:extent>
-                        <gml:timeLength xsi:type="gml:TimePeriodType">	
+                        <gml:timeLength xsi:type="gml:TimePeriodType">
                         	<gml:timeInterval xsi:type="gml:TimeIntervalLengthType">
                         	<gml:unit>
                 							<gml:TimeUnitType>{{ md.identification.timeUnit }}{# tag="md.identification.timeUnit" , name="Granularity" , ref= "ISO/DIS 19108" , desc= "CharacterString is the name of the unit of measure used to express the length of the interval" ,inbox="Temporal Resolution", example = "month" , type ="string" , group= "Temporal" ,multi=0 , inboxmulti= 0, multiline= False #}</gml:TimeUnitType>
                 							</gml:unit>
                 							<radix>
                 							<gco:positiveInteger>{{ md.identification.radixT }}{# tag="md.identification.radixT" , name="Multiplier" , ref= "ISO/DIS 19108" , desc= "Integer is a positive integer that is the base of the multiplier of the unit" ,inbox="Temporal Resolution", example = "10" , type ="integer" , group= "Temporal" ,multi=0 , inboxmulti= 0, multiline= False #}</gco:positiveInteger>
-                							</radix>	
+                							</radix>
                 							<factor>
                 							<gco:Integer>{{ md.identification.factor }}{# tag="md.identification.factor" , name="Factor" , ref= "ISO/DIS 19108" , desc= "Factor is an integer that is the exponent of the base" , example = "3" , type ="string" ,inbox="Temporal Resolution", group= "Temporal" ,multi=0 , inboxmulti= 0, multiline= False #}</gco:Integer>
-                							</factor>	
-							</gml:timeInterval>			
+                							</factor>
+							</gml:timeInterval>
 						</gml:timeLength>
                      </gmd:extent>
                   </gmd:EX_TemporalExtent>