DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23474>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23474 MIME charset samples and comments in httpd-std.conf are misleading Summary: MIME charset samples and comments in httpd-std.conf are misleading Product: Apache httpd-2.0 Version: HEAD Platform: All OS/Version: All Status: NEW Severity: Minor Priority: Other Component: Documentation AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] httpd-std.conf has the following lines : AddCharset ISO-8859-8 .iso8859-8 .latin8 .heb AddCharset ISO-8859-9 .iso8859-9 .latin9 .trk AddCharset ISO-2022-JP .iso2022-jp .jis AddCharset ISO-2022-KR .iso2022-kr .kis AddCharset ISO-2022-CN .iso2022-cn .cis AddCharset Big5 .Big5 .big5 # For russian, more than one charset is used (depends on client, mostly): AddCharset WINDOWS-1251 .cp-1251 .win-1251 AddCharset CP866 .cp866 AddCharset KOI8-r .koi8-r .koi8-ru AddCharset KOI8-ru .koi8-uk .ua AddCharset ISO-10646-UCS-2 .ucs2 AddCharset ISO-10646-UCS-4 .ucs4 AddCharset UTF-8 .utf8 # The set below does not map to a specific (iso) standard # but works on a fairly wide range of browsers. Note that # capitalization actually matters (it should not, but it # does for some browsers). # # See http://www.iana.org/assignments/character-sets # for a list of sorts. But browsers support few. # AddCharset GB2312 .gb2312 .gb AddCharset utf-7 .utf7 AddCharset utf-8 .utf8 AddCharset big5 .big5 .b5 AddCharset EUC-TW .euc-tw AddCharset EUC-JP .euc-jp AddCharset EUC-KR .euc-kr AddCharset shift_jis .sjis First of all, NOBODY uses ISO-2022-KR and ISO-2022-CN in web publishing. Moreover, I have never seen suffices 'kis' and 'cis' (apparently after 'jis') be attached to files in ISO-2022-KR and ISO-2022-CN. Therefore, those two entries had better be removed. They are of no practical value and are just taking up spaces in the file to confuse ignorant web administrators. Secondly, EUC-JP, EUC-KR, EUC-CN(GB2312), and EUC-TW are all legitimate character encoding schemes strictly compliant to ISO 2022[1]. Putting them together with Shift_JIS and Big5 that are NOT compliant to ISO 2022 under the category of MIME charsets that are not mapped to a specific standard is misleading. Thirdly, both UTF-7 and UTF-8 are specified in ISO 10646 and Unicode so that they should not be grouped together with Shift_JIS and Big5, either. In case of UTF-7, I doubt it's wise to list it (there might be a handful of sites that use UTF-7, but I'm pretty sure it'd not take many hands to count them all). Finally, I have a reservation about using ISO-10646-UCS-2 and ISO-10646-UCS4. I'd rather list UTF-16(LE|BE) and UTF-32(LE|BE) in their places. [1] They are used to encode ISO-2022 compliant coded character sets, JIS X 0201/ISO 646:JP, KS X 1003/ISO 646:KR, JIS X 0208, JIS X 0212, CNS 11643, KS X 1001, GB2312-80, and so forth in the manner specified by ISO 2022. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
