You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rs...@hyperreal.org on 2000/02/05 12:34:39 UTC
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
rse 00/02/05 03:34:38
Modified: htdocs/manual/mod mod_mime.html
Log:
Enhance AddCharset description.
Submitted by: Youichirou Koga <y-...@isoternet.org>
PR: 5554
Revision Changes Path
1.35 +5 -5 apache-1.3/htdocs/manual/mod/mod_mime.html
Index: mod_mime.html
===================================================================
RCS file: /home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- mod_mime.html 2000/01/08 19:57:29 1.34
+++ mod_mime.html 2000/02/05 11:34:36 1.35
@@ -139,12 +139,12 @@
</pre>
<P>
-Then the document <samp>xxxx.ja.jis</samp> will be treated as being a
+Then the document <CODE>xxxx.ja.jis</CODE> will be treated as being a
Japanese document whose charset is ISO-2022-JP (as will the document
-<samp>xxxx.jis.ja</samp>). Although the content charset is reported to
-the client, the browser is unlikely to use this information. The
-AddCharset directive is more useful for
-<A HREF="../content-negotiation.html">content negotiation</A>, where
+<CODE>xxxx.jis.ja</CODE>). The AddCharset directive is useful for both
+to inform the client about the character encoding of the document so
+that the document can be interpreted and displayed appropriately, and
+for <A HREF="../content-negotiation.html">content negotiation</A>, where
the server returns one from several documents based on the client's
charset preference.
</P>