#1722: to avoid confusion, call it ReST or reST not Rest
------------------------+---------------------------------------------------
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Compiling | Version: svn-trunk
Keywords: reST, docs | Platform: All
Cpu: All |
------------------------+---------------------------------------------------
Hi,
to avoid confusion with other RESTs (such as representational state
transfer- the RESTful API, a friend of SOAP) please always spell out
reStructuredText completely in comments, and lower-case the "e" and/or "r"
as appropriate when used in abbrv.
e.g.
{{{
FILES="
include/Make/Etc.make
include/Make/Lib.make
include/Make/Module.make
include/Make/Other.make
include/Make/Dir.make
include/Make/Multi.make
include/Make/Script.make
include/Make/DB.make
man/build_rest.py
imagery/i.find/Makefile
lib/gtcltk/Makefile
raster/r.watershed/ram/Makefile
raster/r.watershed/seg/Makefile
tools/timer/Makefile"
sed -i -e 's/Rest/ReST/' $FILES
svn mv include/Make/ReST.make include/Make/ReST.make
svn mv include/Make/NoRest.make include/Make/NoReST.make
}}}
It is rather likely that some part of GRASS will be linked to a RESTful
API interface in the near future, actually that's probably already
happened.
thanks,
Hamish
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1722>
GRASS GIS <http://grass.osgeo.org>