RE: Publishing in UTF-8?

[I apologize if some of the text in this mail got garbled. Martin.]

Hi Mieko,
NCRs and UTF-8 are individual solutions to display a multilingual document.
Character set equals to ISO 8859 standards can provide you to display all
the European languages without any problem. But to display occasional
characters such as trademark sign ((tm)) or alpha (?), you need to use NCRs.

For instance,if you are using ISO 8859-1 to display ? , you need to use NCR
(Σ equivilent to ? ) . The disadvantage is that it is hard to handle,
difficult to manipulate for a search engine.

HTML using NCRs:
Netscape 4.x browser has problem in displaying correctly.

Solution:
Change/ upgrade browser to 6 or above. Or use UTF-8.

The best solution is UTF-8. It is far easier for us to work with the text
than with the codepoints.
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
set the character set to utf-8 as shown in the above meta tag

I hope I have explained you your question and please do not hesitate to
pursue for additional inquiries.

Cheers,
Yun-Fang


 >===== Original Message From Mieko Komagata <MiekoK@trellix.com>(by way of
\"Martin J. Duerst\" <duerst@w3.org>) =====
 >Hello all,
 >
 >We have a web based application in English and are working on localizing it
 >to French, Italian, German, and Spanish. We are considering publishing
pages
 >in UTF-8 in these languages. I would like to know the advantages and
 >disadvantages on using UTF-8 over ISO-8859-1. How common UTF-8 is? I
 >randomly visited some sites in France and Italy, but I did not find a site
 >in UTF-8.
 >I saw a Netscape 4.x browser bug using NCR in UTF-8 on
 >http://www.unicode.org/unicode/faq/unicode_web.html. Any input would be
 >appreciated.
 >
 >Thank you,
 >Mieko

Received on Monday, 11 September 2000 03:55:17 UTC