Index: openacs-4/packages/acs-tcl/tcl/utilities-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-tcl/tcl/utilities-procs.tcl,v
diff -u -N -r1.123 -r1.124
--- openacs-4/packages/acs-tcl/tcl/utilities-procs.tcl 23 Jul 2010 01:13:13 -0000 1.123
+++ openacs-4/packages/acs-tcl/tcl/utilities-procs.tcl 23 Jul 2010 14:02:52 -0000 1.124
@@ -1571,17 +1571,36 @@
The "content_type" string points to a "text/*" media subtype,
but does not specify a charset (e.g., "text/xml"). In this case, the
charset defined by ns/parameters/OutputCharset (see config.tcl)
- applies. If this parameter is missing, or [ns_encodingfortype] fails
- to resolve any Tcl encoding name, the general default is
+ applies. If this parameter is missing, the default is
"iso-8859-1" (see tcl/charsets.tcl; this follows from RFC 2616 (HTTP 1.1);
Section 3.7.1).
If neither case 1 or case 2 become effective, the encoding is
resolved to "binary".
+
+ If [ns_encodingfortype] fails to resolve any Tcl encoding name
+ (i.e., returns an empty string), the general fallback is "iso8859-1"
+ for text/* media subtypes and "binary" for any other. This is the
+ case in two situations:
+
+
+ - Invalid IANA/MIME charsets: The name in the "charset" parameter
+ of the content type spec is not a valid name or alias in IANA's
+ charater sets registry (a special variant would be an empty
+ charset value, e.g. "text/plain; charset=")
+
+ - Unknown IANA/MIME charsets: The name in the "charset" parameter
+ of the content type spec does not match any known (= registered)
+ IANA/MIME charset in the MIME/Tcl mappings.
+
+
+
- References:
+ References:
+