It is not clear what program you are uploading from, or what format the text
is in when you upload. Also, I don't quite understand why you replace some
characters in Word with +ACo- and then switch them back before saving. What are
you doing in between those steps?
If you are saving as HTML from Word2000 (direct to http server, or locally
then ftp), then you will get HTML 4.0, which allows Word to use either named
entities or numeric character references (NCRs) for characters not in the
native charset of the page you are saving. So if you are saving a page as
+ACI-windows-1252+ACI-, then Word will use NCRs for characters not in windows-152,
and named entity for characters in windows-1252 with a value over 0x7F, or
in some cases an NCR when more appropriate for maximum readability on down
level browsers. However, you may find that some browsers do not understand
NCRs (notably Netscape Navigator 4.x and below, and Microsoft IE 2.x and
below), causing some display problems on those browsers. (By the way, this
is a common problem everyone has. It will go away in a few years if not
If you are typing the text in Word, one thing that may help you with
apostrophes is turning off the Word feature that converts +ACI-dumb+ACI- (i.e.
straight) quotation marks into +ACI-smart+ACI- (i.e. typographically correct)
quotation marks. If you do this, you text will not look as good in browsers
that support the extended punctuation, but you will have straight quotes
everywhere at least. Turn this off by going to Tools/AutoCorrect/AutoFormat
as you Type, and check off the box labelled +IBggHA-Straight quotes+IB0- with +IBw-smart
Another approach you can take that solves the problem globally is to save
the file as a different encoding. In Word, go to Tools/Options/General,
click the button labelled +IBw-Web Options+IB0-, and click the tab called
+IBw-Encoding+IB0-. You can pick a different encoding to save, such as Unicode
(UTF-8), which uses no NCRs or named entities. The drawback is that this
encoding is not supported properly except on IE 4.01 and higher, or
Navigator 4.03 and higher. Navigator+IBk-s UTF-8 support is a little flaky if
you try to use UTF-8 for various languages at once, but if you are worried
mainly about apostrophes you should be OK.
Note: I don+IBk-t know much about the current state of internationalization of
browsers on non-Windows platforms +IBM- you might get a response from other
members of the Unicode list on that topic. It is reasonably safe to assume
that Mac and Unix browsers will be slightly less internationalized than
their Windows counterparts in the case of IE and Navigator (ooh, I can feel
the flame mails already, but it is true, especially if you consider the
installed base of older versions of browsers).
Group Program Manager
From: Magda Danish (Unicode) +AFs-mailto:v-magdad+AEA-microsoft.com+AF0-
Sent: Friday, February 25, 2000 8:55 AM
To: Unicode List
Subject: FW: Help please...
From: McGinty +AFs-mailto:McGinty+AEA-onramp.ca+AF0-
Sent: Friday, February 25, 2000 3:05 AM
Subject: Help please...
I'm looking for up-to-date info re www and Unicode vs. Ansi-Asci. Some of
our material that we upload to our Intranet is not translated properly. What
I'm having people do is search and replace certain characters, i.e. an
apostrophe +AFs-'+AF0- in Word and replace with a character that does translate
easily, i.e. +ACIAKgAi- or +ACIAKgAqACI- and then in Word 2000, before saving as a Web
Page, replace with the appropriate character.
We have a deadline to get our site workable by Feb 28th for the rollout on
I hope this is not too ambiguous - can you help me??
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:59 EDT