summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2009-03-03 16:21:52 +0000
committerEric S. Raymond <esr@thyrsus.com>2009-03-03 16:21:52 +0000
commit6254aae4cf633ced59d0a8c04272853ee08456f7 (patch)
tree1703d9bd7f3fee8d10d77340297e3ac457a34774
parentc70c5e05feccfca47e5487321060e5ee23ca415b (diff)
downloadgpsd-6254aae4cf633ced59d0a8c04272853ee08456f7.tar.gz
Documentation fixes.
-rw-r--r--TODO2
-rw-r--r--www/references.html24
2 files changed, 14 insertions, 12 deletions
diff --git a/TODO b/TODO
index 67da4b90..45ebe208 100644
--- a/TODO
+++ b/TODO
@@ -80,7 +80,7 @@ addition to the library. Applications will commonly use the file
descriptor to detect incoming data, and this file descriptor will
change on reconnect.
-So I rephrase my wish, and ask for reconnect funcionality in xgps
+So I rephrase my wish, and ask for reconnect functionality in xgps
instead. It will make sure the library support reconnects, and also
provide an example for other clients using the library.
diff --git a/www/references.html b/www/references.html
index 4e9a302a..5675a6b7 100644
--- a/www/references.html
+++ b/www/references.html
@@ -127,11 +127,11 @@ href='http://www.itu.int/rec/recommendation.asp?type=items&amp;lang=e&amp;parent
rtcm-104, the specification used for broadcasting differential-gps
corrections. Unfortunately, its distribution terms are also evil.</dd>
-<dt><a href='galileo_OS_SIS_ICD.pdf'>Galileo Open Service SIS ICD</a></dt>
-<dd>This is draft 0 of the Galileo Open Service Signal In Space Interface
-Control Document. The offical standard could possibly be requested
-<a href='http://www.galileoju.com/page2.cfm'>here</a>, though at the time
-of this writing, the download form was broken.</dd>
+<dt><a href='galileo_OS_SIS_ICD.pdf'>Galileo Open Service SIS
+ICD</a></dt> <dd>This is draft 0 of the Galileo Open Service Signal In
+Space Interface Control Document. The latest version of the official
+standard can be requested <a
+href='http://www.galileoju.com/page2.cfm'>here</a>.</dd>
<dt><a href='http://igs.ifag.de/index_ntrip.htm'>Ntrip home page</a></dt>
<dd>NTRIP is a protocol for shipping DGPS corrections that uses HTTP
@@ -144,10 +144,12 @@ the implementor. With the help of examples in the official standard
implementations, it is however possible to develop a working Ntrip
client.</dd>
-<dt><a href='http://www.topografix.com/gpx.asp'>GPX Exchange Format</a></dt>
-<dd>GPX (the GPS Exchange Format) is a light-weight XML data format
-for the interchange of GPS data (waypoints, routes, and tracks)
-between applications and Web services on the Internet.</dd>
+<dt><a href='http://www.topografix.com/gpx.asp'>GPX Exchange
+Format</a></dt> <dd>GPX (the GPS Exchange Format) is a light-weight
+XML data format for the interchange of GPS data (waypoints, routes,
+and tracks) between applications and Web services on the Internet. The
+GPSD suite incluses a client, <code>gpxlogger</code>, that makes logs
+in this format.</dd>
<dt><a href='NAVSTAR_Global_Positioning_and_Surveying.pdf'>NAVSTAR
Global Positioning and Surveying</a></dt>
@@ -157,7 +159,7 @@ mapping with the NAVSTAR Global Positioning System (GPS). ... Procedural
and quality control standards are defined to establish... uniformity
in the use of GPS..." This document offers significant insight into
error modelling; anyone who dares to ask "so how accurate is my GPS?"
-should be gently encouraged to study this manual.</dd>
+should be gently encouraged to study it.</dd>
</dl>
<h1>Vendor protocols</h1>
@@ -182,7 +184,7 @@ like they are run by the aforementioned sort of idiot. We are blithely
ignoring all this nonsense here. If you are a a GPS vendor
representative, be advised that if you so request, we will (a) remove
your manuals, and then (b) laugh at and publicly mock you
-for having been so stupid as to demand that we remove them.</p>
+for having been so stupid as to demand this.</p>
<h2>SiRF and SiRF variants</h2>