Point to the new location of the ZeroXML library that contains xmlgrep

[flightgear.git] / utils / metarproxy / README

diff --git a/utils/metarproxy/README b/utils/metarproxy/README
index 9782dc11482bc17f90e5a82ffa413e4e68b64333..bb2e4f1645f59330bbabc39b7d12d63edc154d8d 100644 (file)
--- a/utils/metarproxy/README
+++ b/utils/metarproxy/README
@@ -4,7 +4,7 @@
 
 
 metarproxy is a caching proxy server for METAR data strings written in
 
 
 metarproxy is a caching proxy server for METAR data strings written in

-Perl. It can be used from the FlightGear flight simulator to:
+Perl. It can be used to:

 
 - provide METAR data for machines without internet connection
 - centralize METAR fetching: one machine in a network runs the proxy, all
 
 - provide METAR data for machines without internet connection
 - centralize METAR fetching: one machine in a network runs the proxy, all


@@ -88,11 +88,11 @@ systems, and is, for instance, used by the lynx browser), or none if
 unset. To set a particular proxy server for HTTP download, use one of
 these methods:
 
 unset. To set a particular proxy server for HTTP download, use one of
 these methods:
 

-- set http_proxy globally:     EXPORT http_proxy=http://localhost:3128/
+- set http_proxy globally:     export http_proxy=http://localhost:3128/

 - or on the command line:      $ http_proxy=http://localhost:3128/ metarproxy
 - unset http_proxy:            $ http_proxy= metarproxy
 - use the command line option: $ metarproxy --proxy=http://localhost:3128/
 - or on the command line:      $ http_proxy=http://localhost:3128/ metarproxy
 - unset http_proxy:            $ http_proxy= metarproxy
 - use the command line option: $ metarproxy --proxy=http://localhost:3128/

-- set the option globally:     EXPORT METARPROXY="-yhttp://localhost:3128"
+- set the option globally:     export METARPROXY="-yhttp://localhost:3128"

 
 
 
 
 
 


@@ -129,7 +129,7 @@ Ranges are allowed, too:
   $ metarproxy --download 0-2     ... download first three hours after
                                       midnight GMT
 
   $ metarproxy --download 0-2     ... download first three hours after
                                       midnight GMT
 

-These three methods can be use in combination:
+These three methods can be used in combination:

 
   $ metarproxy --download 6h 0-2 4
 
 
   $ metarproxy --download 6h 0-2 4
 


@@ -176,7 +176,7 @@ stored in the cache. Additionally, you can specify one or more files
 with station IDs:
 
   $ metarproxy --record --file=$FG_HOME/station-list
 with station IDs:
 
   $ metarproxy --record --file=$FG_HOME/station-list

-  $ metarproxy --record EDDM --file=tmp/Austria --file=/tmp/Hungary
+  $ metarproxy --record EDDM --file=/tmp/Austria --file=/tmp/Hungary

 
 These files simply contain station IDs separated by spaces in one
 or more lines:
 
 These files simply contain station IDs separated by spaces in one
 or more lines:


@@ -232,7 +232,8 @@ All you need to do is point FlightGear to the metar proxy and let
 it run at a simulated time for which you actually have cached METAR
 data:
 
 it run at a simulated time for which you actually have cached METAR
 data:
 

-  $ fgfs --proxy=localhost:5509 --start-date-lat=2005:01:12:12:00:00
+  $ fgfs --enable-real-weather-fetch --proxy=localhost:5509 \
+         --start-date-lat=2005:01:12:12:00:00

 
 FlightGear will then fetch the metar data from the proxy as if it
 were weather.noaa.gov. If no appropriate data set is found at all,
 
 FlightGear will then fetch the metar data from the proxy as if it
 were weather.noaa.gov. If no appropriate data set is found at all,


@@ -276,5 +277,5 @@ stations:
 
 
 $Id$
 
 
 $Id$

-Melchior FRANZ <mfranz@aon.at>, 2005/1/24
+Melchior FRANZ <mfranz # aon : at>, 2005/1/24