cvs commit: apache-2.0/conf httpd.conf-dist

[dr...@locus.apache.org]

dreid       00/03/17 02:40:20

  Modified:    conf     httpd.conf-dist
  Log:
  sp
  
  Revision  Changes    Path
  1.6       +12 -12    apache-2.0/conf/httpd.conf-dist
  
  Index: httpd.conf-dist
  ===================================================================
  RCS file: /home/cvs/apache-2.0/conf/httpd.conf-dist,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- httpd.conf-dist	2000/03/17 01:14:10	1.5
  +++ httpd.conf-dist	2000/03/17 10:40:19	1.6
  @@ -634,12 +634,12 @@
   # a document. You can then use content negotiation to give a browser a 
   # file in a language the user can understand.
   #
  -# Specify a default langyage. This means that all data
  -# going out without a specific language tag (See below) will 
  -# be marked with this one. You propably do NOT want to set
  +# Specify a default language. This means that all data
  +# going out without a specific language tag (see below) will 
  +# be marked with this one. You probably do NOT want to set
   # this unless you are sure it is correct for all cases.
   #
  -# * It is generally better to not mark a pages as in
  +# * It is generally better to not mark a page as 
   # * being a certain language than marking it with the wrong
   # * language!
   #
  @@ -650,13 +650,13 @@
   # language code is pl) may wish to use "AddLanguage pl .po" to
   # avoid the ambiguity with the common suffix for perl scripts.
   #
  -# Note 2: The example entries below illustrate that in quite
  -# some cases the two character 'Language' abbriviation is not
  +# Note 2: The example entries below illustrate that in 
  +# some cases the two character 'Language' abbreviation is not
   # identical to the two character 'Country' code for its country,
   # E.g. 'Danmark/dk' versus 'Danish/da'.
   #
   # Note 3: In the case of 'ltz' we violate the RFC by using a three char
  -# specifier. But there is 'work in progress' to fix this and get
  +# specifier. There is 'work in progress' to fix this and get
   # the reference data for rfc1766 cleaned up.
   #
   # Danish (da) - Dutch (nl) - English (en) - Estonian (et)
  @@ -698,16 +698,16 @@
   # Specify a default charset for all pages sent out. This is
   # always a good idea and opens the door for future internationalisation
   # of your web site, should you ever want it. Specifying it as
  -# a default does little harm; as the standart dictates that a page
  -# is in iso-8859-1 (latin1) unless specified otherwise. I.e. you
  +# a default does little harm; as the standard dictates that a page
  +# is in iso-8859-1 (latin1) unless specified otherwise i.e. you
   # are merely stating the obvious. There are also some security
   # reasons in browsers, related to javascript and URL parsing
  -# which encourage to always set a default char set.
  +# which encourage you to always set a default char set.
   #
   AddDefaultCharset	ISO-8859-1
   
   #
  -# Commonly used filename extensions to character sets. You propably
  +# Commonly used filename extensions to character sets. You probably
   # want to avoid clashes with the language extensions, unless you
   # are good at carefully testing your setup after each change.
   #
  @@ -725,7 +725,7 @@
   AddCharset ISO-2022-CN .iso2022-cn .cis
   
   # The set below does not map to a specific (iso) standard
  -# but works on a fairly wide range of browser. Note that
  +# but works on a fairly wide range of browsers. Note that
   # capitalization actually matters (it should not, but it
   # does for some browsers).
   #