From: Ralf S. Engelschall <rse@apache.org>
Date: Sat, 5 Feb 2000 11:34:36 +0000 (+0000)
Subject: Enhance AddCharset description.
X-Git-Tag: 1.3.12~44
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d306ea8cd4efc533addbebcaf218ad55ba8d6818;p=apache

Enhance AddCharset description.

Submitted by: Youichirou Koga <y-koga@isoternet.org>
PR: 5554


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@84574 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mod_mime.html b/docs/manual/mod/mod_mime.html
index 1693be0211..8cf486e213 100644
--- a/docs/manual/mod/mod_mime.html
+++ b/docs/manual/mod/mod_mime.html
@@ -139,12 +139,12 @@ Example:
 </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>