W3C home > Mailing lists > Public > www-i18n-comments@w3.org > April 2004

RE: New Tutorial: Character sets & encodings in XHTML, HTML and CSS

From: Richard Ishida <ishida@w3.org>
Date: Thu, 8 Apr 2004 13:57:06 +0100
To: "'Asmus Freytag'" <asmusf@ix.netcom.com>
Cc: <www-international@w3.org>, <www-i18n-comments@w3.org>
Message-ID: <E1BBZ5e-0004du-U6@dr-nick.w3.org>

Thanks, Asmus,

I'll fix it.

RI 
 


============
Richard Ishida
W3C

contact info:
http://www.w3.org/People/Ishida/

W3C Internationalization:
http://www.w3.org/International/



 


________________________________

	From: www-international-request@w3.org
[mailto:www-international-request@w3.org] On Behalf Of Asmus Freytag
	Sent: 07 April 2004 22:45
	To: Richard Ishida
	Cc: www-international@w3.org; www-i18n-comments@w3.org
	Subject: RE: New Tutorial: Character sets & encodings in XHTML, HTML
and CSS
	
	
	At 02:56 AM 4/6/2004, Richard Ishida wrote:
	
	

		Do you mean use 'encoding form' where it says 'Unicode
encoding' or where it
		says 'and forms'?  See the text at
	
http://www.w3.org/International/tutorials/tutorial-char-enc.html#choosing



	The text reads:
	
	

	Consider using a Unicode encoding

	A Unicode encoding can support many languages and can accommodate
pages and forms in any mixture of those languages. Its use also eliminates
the need for server-side logic to individually determine the character
encoding for each page served or each incoming form submission. This
significantly reduces the complexity of dealing with a multilingual site or
application.
	
	A Unicode encoding also allows many more languages to be mixed on a
single page than almost any other choice.
	
	It is not much of an issue to move to Unicode these days.
	
	Note that although there are other multi-script approaches (such as
ISO-2022), Unicode generally provides the best combination of extensibility
and script support.
	
	
	If you want to say no more than "use Unicode", but want
	to use the word 'encoding' then you should use
	
	"Consider using Unicode as the encoding" 
	
	or
	
	"Consider using a Unicode-based encoding"
	
	however, as the latter is merely a Unicode encoding form (or
scheme?)
	you might be better off saying "Consider a Unicode encoding form",
	except that I can tell your text is too high level at that point
	to explain this in detail. Continuing:
	
	"Any of the [three] Unicode encoding forms can..."
	
	with or without the word in [ ] might do the trick.
	
	Or, if you go with the first of the suggested headers,
	simply continue:
	
	"Unicode can..."
	
	In either case, you also have to fix the second paragraph.
	
	A./
	
	PS: a novel combination like "Unicode encoding" besides being
confusing,
	is strictly speaking in violation of Unicode's trademarks. 
Received on Thursday, 8 April 2004 08:57:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:32:34 GMT