W3C home > Mailing lists > Public > www-international@w3.org > April to June 2004

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

From: Asmus Freytag <asmusf@ix.netcom.com>
Date: Wed, 07 Apr 2004 14:45:29 -0700
Message-Id: <>
To: "Richard Ishida" <ishida@w3.org>
Cc: <www-international@w3.org>, <www-i18n-comments@w3.org>
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

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"


"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.


PS: a novel combination like "Unicode encoding" besides being confusing,
is strictly speaking in violation of Unicode's trademarks. 
Received on Wednesday, 7 April 2004 17:47:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:40:49 UTC