Pārlūkot izejas kodu

html: replace less than by < to fix displaying manual in gui

git-svn-id: https://svn.osgeo.org/grass/grass/trunk@54965 15284696-431f-4ddb-bdfa-cd5b030d7da7
Anna Petrášová 12 gadi atpakaļ
vecāks
revīzija
f607c13ea9

+ 1 - 1
db/db.execute/db.execute.html

@@ -49,7 +49,7 @@ db.execute sql="UPDATE dourokukan SET testc=50 WHERE testc is NULL"
 
 Delete selected rows from attribute table:
 <div class="code"><pre>
-db.execute sql="DELETE FROM gsod_stationlist WHERE latitude < -91"
+db.execute sql="DELETE FROM gsod_stationlist WHERE latitude &lt; -91"
 </pre></div>
 
 Add new column to attribute table:

+ 1 - 1
db/db.select/db.select.html

@@ -60,7 +60,7 @@ db.select sql="SELECT x(geo),y(geo) FROM localizzazione"
 <div class="code"><pre>
 cat file.sql
 SELECT * FROM busstopsall WHERE cat = 1
-SELECT cat FROM busstopsall WHERE cat > 4 AND cat < 8
+SELECT cat FROM busstopsall WHERE cat > 4 AND cat &lt; 8
 
 db.select input=file.sql
 </pre></div>

+ 1 - 1
display/d.graph/d.graph.html

@@ -183,7 +183,7 @@ echo "symbol basic/star 20 2264417 5413182 black red" | d.graph -m
 <div class="code"><pre>
 d.frame -s full_screen
 
-d.graph << EOF
+d.graph &lt;&lt; EOF
   color 80:80:120
   polygon
    0 49.75

+ 1 - 1
display/d.text/d.text.html

@@ -71,7 +71,7 @@ active frame's vertical space per line:
 <p>
 
 <pre>
-<b>d.text</b> << EOF
+<b>d.text</b> &lt;&lt; EOF
 .C yellow
 .G grey
 .S 4 

+ 1 - 1
raster/r.category/r.category.html

@@ -141,7 +141,7 @@ values in the output.
 <dl>
 <dt>Example defining category labels:
 <dd><div class="code"><pre>
-r.category diseasemap rules=- << EOF
+r.category diseasemap rules=- &lt;&lt; EOF
 1:potential absence
 2:potential presence
 EOF

+ 1 - 1
raster/r.mapcalc/r.mapcalc.html

@@ -432,7 +432,7 @@ if(x,a,b) = a		otherwise (i.e. x is neither NULL nor 0).
 if(x,a,b,c) = NULL	if x is NULL
 if(x,a,b,c) = a		if x > 0
 if(x,a,b,c) = b		if x = 0
-if(x,a,b,c) = c		if x < 0
+if(x,a,b,c) = c		if x &lt; 0
 </pre></div>
 More generally, all operators and most functions return NULL if *any*
 of their arguments are NULL.

+ 1 - 1
raster/r.mapcalc/r3.mapcalc.html

@@ -339,7 +339,7 @@ if(x,a,b) = a		otherwise (i.e. x is neither NULL nor 0).
 if(x,a,b,c) = NULL	if x is NULL
 if(x,a,b,c) = a		if x > 0
 if(x,a,b,c) = b		if x = 0
-if(x,a,b,c) = c		if x < 0
+if(x,a,b,c) = c		if x &lt; 0
 </pre></div>
 More generally, all operators and most functions return NULL if *any*
 of their arguments are NULL.

+ 1 - 1
raster/r.out.mat/r.out.mat.html

@@ -34,7 +34,7 @@ copied between different system architectures without binary translation.
 As there is no IEEE value for <tt>NaN</tt> for integer maps, GRASS's null 
 value is used to represent it within these maps. You'll have to do something 
 like this to clean them once the map is loaded into Matlab:
-<pre>    map_data(find(map_data < -1e9)) = NaN;</pre>
+<pre>    map_data(find(map_data &lt; -1e9)) = NaN;</pre>
 
 Null values in maps containing either floating point or double-precision 
 floating point data should translate into <tt>NaN</tt> values as expected.

+ 3 - 3
raster/r.out.pov/r.out.pov.html

@@ -26,9 +26,9 @@ An example Povray script file may look like this:
 light_source { <40000, Scale*3000, 5000> color MainLight }
  
 camera {
-   location < 23000, Scale*2000, 0>
+   location &lt; 23000, Scale*2000, 0>
    angle  90
-   look_at < 23000, Scale*1400, 5000>
+   look_at &lt; 23000, Scale*1400, 5000>
 }
  
 height_field  {
@@ -52,7 +52,7 @@ height_field  {
           specular 0.5
           roughness 0.05
    }
-   scale < 14500, Scale*6553.6, 13000 >
+   scale &lt; 14500, Scale*6553.6, 13000 >
    translate <18300, 0, 1100>
 }
 </pre></div>

+ 1 - 1
raster/r.profile/r.profile.html

@@ -94,7 +94,7 @@ d.where | r.profile elevation.dem
 <b>Example 4</b><br>
 Pipe coordinates into r.profile
 <div class="code"><pre>
-r.profile elevation.dem res=1000 << EOF
+r.profile elevation.dem res=1000 &lt;&lt; EOF
  591243,4926344
  592509,4922156
  594100,4920793

+ 1 - 1
raster/r.series.interp/r.series.interp.html

@@ -34,7 +34,7 @@ r.series.interp --o --v input=prec_1,prec_5 datapos=0.0,1.0\
 First prepare the input file:
 <br>
 <div class="code"><pre>
-cat > outfile.txt << EOF
+cat > outfile.txt &lt;&lt; EOF
 prec_2|0.25
 prec_3|0.5
 prec_4|0.75

+ 2 - 2
raster/r.series/r.series.html

@@ -105,7 +105,7 @@ r.series in=one,two out=result_avg,res_slope,result_count meth=sum,slope,count
 
 <p>Example to use the file option of r.series:
 <div class="code"><pre>
-cat > input.txt << EOF
+cat > input.txt &lt;&lt; EOF
 map1
 map2
 map3
@@ -117,7 +117,7 @@ r.series file=input.txt out=result_sum meth=sum
 <p>Example to use the file option of r.series including weights. The weight 0.75
 should be assigned to map2. As the other maps do not have weights we can leave it out:
 <div class="code"><pre>
-cat > input.txt << EOF
+cat > input.txt &lt;&lt; EOF
 map1
 map2|0.75
 map3

+ 1 - 1
raster/r.univar/r.univar.html

@@ -74,7 +74,7 @@ db.execute input=fields_stats_sqlcmd.txt
 
 #### convert text file table to a database table
 # not safe for commas in the label
-tr '|' ',' < fields_stats.txt > fields_stats.csv
+tr '|' ',' &lt; fields_stats.txt > fields_stats.csv
 echo '"Integer","String","Real","Real","Real"' > fields_stats.csvt
 
 # import table

+ 2 - 2
raster/r.watershed/front/r.watershed.html

@@ -310,7 +310,7 @@ Zero (0) and negative values will be treated as elevation data (not no_data).
 Problem areas, i.e. those parts of a basin with a likely underestimate of
 flow accumulation, can be easily identified with e.g.
 <div class="code"><pre>
-  r.mapcalc "problems = if(flow_acc < 0, basin, null())"
+  r.mapcalc "problems = if(flow_acc &lt; 0, basin, null())"
 </pre></div>
 If the region of interest contains such problem areas, and this is not
 desired, the computational region must be expanded until the catchment
@@ -374,7 +374,7 @@ Set a different color table for the accumulation map:
   stddev_x_2=`echo $stddev | awk '{print $1 * 2}'`
   stddev_div_2=`echo $stddev | awk '{print $1 / 2}'`
 
-  r.colors $MAP col=rules << EOF
+  r.colors $MAP col=rules &lt;&lt; EOF
     0% red
     -$stddev_x_2 red
     -$stddev yellow

+ 3 - 3
raster/r.what/r.what.html

@@ -58,7 +58,7 @@ as follows. If we have a file called <i>input_coord.txt</i> containing the
 coordinates and labels given in the example above:
 
 <div class="code"><pre>
-r.what map=soils,aspect < input_coord.txt
+r.what map=soils,aspect &lt; input_coord.txt
 
 635342.21|7654321.09|site 1|45|21
 653324.88|7563412.42|site 2|44|20
@@ -70,7 +70,7 @@ Input coordinates may be given directly from standard input (<tt>stdin</tt>), fo
 (input data appears between the "<tt>EOF</tt>" markers):
 
 <div class="code"><pre>
-r.what map=soils,aspect << EOF
+r.what map=soils,aspect &lt;&lt; EOF
 635342.21 7654321.09 site 1
 653324.88 7563412.42 site 2
 EOF
@@ -102,7 +102,7 @@ Here we use the <b>-f</b> label flag to enable the output of category labels
 associated with the raster cell(s), as well as values (categorical maps only).
 
 <div class="code"><pre>
-r.what -f map=soils,aspect << EOF
+r.what -f map=soils,aspect &lt;&lt; EOF
 635342.21 7654321.09 site 1
 653324.88 7563412.42 site 2
 EOF

+ 3 - 3
raster3d/r3.gwflow/r3.gwflow.html

@@ -108,9 +108,9 @@ r3.mapcalc expression="status = if(col() == 1 && depth() == 33, 2, 1)"
 r3.mapcalc expression="well = if(row() == 20 && col() == 20 && depth() == 3, -0.25, 0)"
 r3.mapcalc expression="well = if(row() == 50 && col() == 50 && depth() == 3, -0.25, well)"
 r3.mapcalc expression="hydcond = 0.0025"
-r3.mapcalc expression="hydcond = if(depth() < 30 && depth() > 23 && col() < 60, 0.000025, hydcond)"
-r3.mapcalc expression="hydcond = if(depth() < 20 && depth() > 13 && col() >  7, 0.000025, hydcond)"
-r3.mapcalc expression="hydcond = if(depth() < 10 && depth() >  7 && col() < 60, 0.000025, hydcond)"
+r3.mapcalc expression="hydcond = if(depth() &lt; 30 && depth() > 23 && col() &lt; 60, 0.000025, hydcond)"
+r3.mapcalc expression="hydcond = if(depth() &lt; 20 && depth() > 13 && col() >  7, 0.000025, hydcond)"
+r3.mapcalc expression="hydcond = if(depth() &lt; 10 && depth() >  7 && col() &lt; 60, 0.000025, hydcond)"
 r3.mapcalc expression="syield = 0.0001"
 
 r3.gwflow solver=cg phead=phead status=status hc_x=hydcond hc_y=hydcond  \

+ 1 - 1
raster3d/r3.stats/r3.stats.html

@@ -60,7 +60,7 @@ r3.mapcalc "volmap = if(row() == 5, null(), row())"
 r3.stats input=volmap nsteps=10
 
 #the result should look like this
- num   | minimum <= value   | value < maximum    |     volume    |   perc  | cell count
+ num   | minimum <= value   | value &lt; maximum    |     volume    |   perc  | cell count
       1          1.000000000          1.900000000    60000000.000   10.00000           60
       2          1.900000000          2.800000000    60000000.000   10.00000           60
       3          2.800000000          3.700000000    60000000.000   10.00000           60

+ 1 - 1
vector/v.clean/v.clean.html

@@ -237,7 +237,7 @@ Intersection points are written to 'points' map.
 creating new node if needed. Example:
 
 <div class="code"><pre>
-v.in.ascii -n out=crossed_lines format=standard << EOF
+v.in.ascii -n out=crossed_lines format=standard &lt;&lt; EOF
 L 2
  0 5
  10 5

+ 3 - 3
vector/v.net.iso/v.net.iso.html

@@ -60,9 +60,9 @@ The network is divided into 4 categories:
 v.category myroads_net_iso option=report
 # ... reports 4 categories:
 #cat | distance from point in meters
-#1          0 - < 1000
-#2       1000 - < 2000
-#3       2000 - < 5000
+#1          0 - &lt; 1000
+#2       1000 - &lt; 2000
+#3       2000 - &lt; 5000
 #4             >= 5000
 </pre></div>
 

+ 1 - 1
vector/v.net/v.net.html

@@ -134,7 +134,7 @@ For generating network for given vector point map is required input file in form
 </pre></div>
 
 <div class="code"><pre>
-v.net points=geodetic_swwake_pts output=geodetic_swwake_pts_net operation=arcs file=- << EOF
+v.net points=geodetic_swwake_pts output=geodetic_swwake_pts_net operation=arcs file=- &lt;&lt; EOF
 > 1 28000 28005
 > 2 27945 27958
 > 3 27886 27897

+ 3 - 3
vector/v.segment/v.segment.html

@@ -70,7 +70,7 @@ cat mypoints.txt | v.segment myrailroads out=myrailroads_mypoints
 
 # create parallel 1km long line segments along first 8km of track,
 # offset 500m to the left of the tracks.
-v.segment myrailroads out=myrailroads_segl_side << EOF
+v.segment myrailroads out=myrailroads_segl_side &lt;&lt; EOF
 L 1 1 1000 2000 -500
 L 2 1 3000 4000 -500
 L 3 1 5000 6000 -500
@@ -81,7 +81,7 @@ d.vect myrailroads disp=shape,dir
 d.vect -c myrailroads_segl_side width=2
 
 # A series of points, spaced every 2km along the tracks
-v.segment myrailroads out=myrailroads_pt2km << EOF
+v.segment myrailroads out=myrailroads_pt2km &lt;&lt; EOF
 P 1 1 1000
 P 2 1 3000
 P 3 1 5000
@@ -90,7 +90,7 @@ EOF
 d.vect myrailroads_pt2km icon=basic/circle color=blue fcolor=blue size=5
 
 # A series of points, spaced every 2km along the tracks, offset 500m to the right
-v.segment myrailroads out=myrailroads_pt2kmO500m << EOF
+v.segment myrailroads out=myrailroads_pt2kmO500m &lt;&lt; EOF
 P 1 1 1000 500
 P 2 1 3000 500
 P 3 1 5000 500