* Herman Ranes
|
| My observation is that Opera6.0, MSIE6.0 and Mozilla0.9.8(Win)
| interpret not only Win-1252 -tagged 8-bit HTML as Win-1252, but that
| they interpret also US-ASCII and ISO-8859-1 -tagged 8-bit HTML as
| Win-1252.
* Michael Kaplan
|
| It is highly doubtful that they are
From: Herman Ranes [EMAIL PROTECTED]
My observation is that Opera6.0, MSIE6.0 and Mozilla0.9.8(Win)
interpret not only Win-1252 -tagged 8-bit HTML as Win-1252, but that
they interpret also US-ASCII and ISO-8859-1 -tagged 8-bit HTML as
Win-1252.
It is highly doubtful that they are supporting
On Wed, Mar 20, 2002 at 10:31:41AM +0100, Herman Ranes wrote:
Why did Mozilla introduce this 'sloppy' practice in their newer
versions ... ?
Because its users were getting tired of dealing with little boxes where
quotes should be, and it was easier to change it at the browser level than
the
On Wed, 20 Mar 2002, David Starner wrote:
On Wed, Mar 20, 2002 at 10:31:41AM +0100, Herman Ranes wrote:
Why did Mozilla introduce this 'sloppy' practice in their newer
versions ... ?
Because its users were getting tired of dealing with little boxes where
quotes should be, and it was
Hello Stuart Somer,
you wrote:
I find many recomendations not to use unicode characters for entities
like em dashes trademark symbols because there is poor browser support.
According to HTML 4, http://www.w3.org/TR/html401/charset.html#h-5.3,
you may use any NCR (numeric character
to
avoid awkward HTML fixes such as three hyphens for an em dash. I find
many recomendations not to use unicode characters for entities like em
dashes trademark symbols because there is poor browser support. In my
testing and research it looks like there is good browser support for em
dash. I would
6 matches
Mail list logo
