cvs commit: apache-2.0/htdocs/manual/mod mod_charset_lite.html

[tr...@locus.apache.org]

trawick     00/06/02 17:17:20

  Modified:    htdocs/manual/mod mod_charset_lite.html
  Log:
  Start a "Common Problems" section in the mod_charset_lite
  documentation.
  
  Revision  Changes    Path
  1.2       +33 -0     apache-2.0/htdocs/manual/mod/mod_charset_lite.html
  
  Index: mod_charset_lite.html
  ===================================================================
  RCS file: /home/cvs/apache-2.0/htdocs/manual/mod/mod_charset_lite.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- mod_charset_lite.html	2000/05/26 17:40:41	1.1
  +++ mod_charset_lite.html	2000/06/03 00:17:19	1.2
  @@ -222,6 +222,39 @@
     <EM>debug</EM>.
     </P>
   
  +  <H2>Common Problems</H2>
  +
  +  <H3>Invalid character set names</H3>
  +
  +  <P>
  +  The character set name parameters of CharsetSourceEnc and CharsetDefault
  +  must be acceptable to the translation mechanism used by APR on the system
  +  where mod_charset_lite is deployed.  These character set names are not 
  +  standardized and are usually not the same as the corresponding values used 
  +  in http headers.  Currently, APR can only use iconv(3), so you can easily
  +  test your character set names using the iconv(1) program, as follows:
  +  </P>
  +
  +  <PRE>
  +  iconv -f charsetsourceenc-value -t charsetdefault-value
  +  </PRE>
  +
  +  <H3>Mismatch between character set of content and translation rules</H3>
  +
  +  <P>
  +  If the translation rules don't make sense for the content, translation
  +  can fail in various ways, including:
  +  </P>
  +
  +  <SL>
  +  <LI>
  +  The translation mechanism may return a bad return code, and the connection
  +  will be aborted.
  +  <LI>
  +  The translation mechanism may silently place special characters (e.g., question
  +  marks) in the output buffer when it cannot translate the input buffer.
  +  </SL>
  +
   <!--#include virtual="footer.html" -->
    </BODY>
   </HTML>