From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/19532 Path: main.gmane.org!not-for-mail From: Shenghuo ZHU Newsgroups: gmane.emacs.gnus.general Subject: Re: Info on Internationalization Date: 02 Dec 1998 19:06:32 -0500 Organization: Computer Dept of U Rochester Sender: owner-ding@hpc.uh.edu Message-ID: <5blnkqozqv.fsf@brandy.cs.rochester.edu> References: <199812022334.SAA03580@math.gatech.edu> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 X-Trace: main.gmane.org 1035157866 12133 80.91.224.250 (20 Oct 2002 23:51:06 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:51:06 +0000 (UTC) Return-Path: Original-Received: from gizmo.hpc.uh.edu (gizmo.hpc.uh.edu [129.7.102.31]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id TAA09821 for ; Wed, 2 Dec 1998 19:09:03 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@sina.hpc.uh.edu [129.7.3.5]) by gizmo.hpc.uh.edu (8.9.1/8.9.1) with ESMTP id SAA16937; Wed, 2 Dec 1998 18:07:01 -0600 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 02 Dec 1998 18:06:54 -0600 (CST) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id SAA06512 for ; Wed, 2 Dec 1998 18:06:45 -0600 (CST) Original-Received: from cayuga.cs.rochester.edu (cayuga.cs.rochester.edu [192.5.53.209]) by sclp3.sclp.com (8.8.5/8.8.5) with SMTP id TAA09736 for ; Wed, 2 Dec 1998 19:06:37 -0500 (EST) Original-Received: from slate.cs.rochester.edu (slate.cs.rochester.edu [192.5.53.101]) by cayuga.cs.rochester.edu (8.6.9/O) with ESMTP id TAA07229 for ; Wed, 2 Dec 1998 19:06:33 -0500 Original-Received: from brandy.cs.rochester.edu (brandy.cs.rochester.edu [192.5.53.199]) by slate.cs.rochester.edu (8.6.9/O) with ESMTP id TAA25763 for ; Wed, 2 Dec 1998 19:06:33 -0500 Original-Received: (from zsh@localhost) by brandy.cs.rochester.edu (SMI-8.6/N++) id TAA00371; Wed, 2 Dec 1998 19:06:32 -0500 Original-To: ding@gnus.org X-Attribution: ZSH X-Face: 'IF:e51ib'Qbl^(}l^&4-J`'P!@[4~O|&k#:@Gld#b/]oMq&`&FVY._3+b`mzp~Jeve~/#/ ERD!OTe<86UhyN=l`mrPY)M7_}`Ktt\K+58Z!hu7>qU,i.N7TotU[FYE(f1;}`g2xj!u*l`^&=Q!g{ *q|ddto|nkt"$r,K$[)"|6,elPH= GJ6Q In-Reply-To: Richard Coleman's message of "Wed, 02 Dec 1998 18:34:14 -0500" User-Agent: Gnus/5.070061 (Pterodactyl Gnus v0.61) Emacs/20.3 Precedence: list X-Majordomo: 1.94.jlt7 Original-Lines: 68 Xref: main.gmane.org gmane.emacs.gnus.general:19532 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:19532 >>>>> "RC" == Richard Coleman writes: RC> report is available at I just found some recommendations in the page. Can Gnus do these? IMC> Sending UTF-8 IMC> All mail-creating programs created or revised after January 1, 1999, IMC> must be able to create mail using the UTF-8 charset. Another way to IMC> say this is that any program created or revised after January 1, 1999, IMC> that cannot create mail using the UTF-8 charset should be considered IMC> deficient and lacking in standard internationalization IMC> capabilities. Of course, all mail-creating programs should try to meet IMC> this requirement as early as possible. A deadline. I know a package for Emacs 20.x support UTF-8, which is decoding/encoding by an external program. Does XEmacs support UTF-8? IMC> Choosing charsets on creation IMC> All mail-creating programs that are controlled by humans should IMC> allow the sender to choose the charset used to create a message. IMC> These programs should also give advice to the user about the IMC> different charsets, such as about the likelihood that the IMC> recipient will be able to display a particular charset. Gnus does not allow user choose. IMC> Specifying languages IMC> All body parts that are created with a Content-type header that IMC> include human-readable text should also include a IMC> Content-language header. This practice makes it more likely that IMC> programs that process messages where different languages would IMC> process differently will process them correctly. Note that the IMC> MIME media type does not define whether or not the content is IMC> human-readable, and the Content-language header should be used IMC> with all types of human-readable content, not just plain text. Content-language, a header gnus should use. IMC> Multi-language text IMC> All plain text body parts that use UTF-8 and have more than one IMC> language should use Unicode Language Tags in addition to a IMC> Content-language header. However, Unicode Language Tags should IMC> only be used with plain text body parts that have more than one IMC> language; they should not be used with body parts that have a IMC> single language, nor should they be used with structured text IMC> body parts such as those coded with HTML. Although automagical additions of mime parts are cool, gnus should allow user choose UTF-8, if support it. IMC> Displaying UTF-8 IMC> All mail-displaying programs created or revised after January 1, IMC> 1999, must be able to display mail that uses the UTF-8 charset. IMC> Another way to say this is that any program created or revised IMC> after January 1, 1999, that cannot display mail using the UTF-8 IMC> charset should be considered deficient and lacking in standard IMC> internationalization capabilities. Of course, all mail-displaying IMC> programs should try to meet this requirement as early as IMC> possible. -- Shenghuo