At 1:19 PM +0100 1/9/08, Nisse Engström wrote:
On Mon, 7 Jan 2008 10:29:45 -0500, tedd wrote:
At 12:03 PM +0100 1/7/08, Nisse Engström wrote:
How does the following pages compare? The display
should be identical:
>><http://luden.se/test/t-1252.html>
>><http://luden.se/test/t-utf8.html>
Nisse:
No, there is quite a difference depending upon
the text encoding used in my browser (Safari).
You said that there was no windows-1252 setting
in Safari, so I am curious to know if it is capable
of mapping the 1252-encoded page to the correct
characters. If you set your browser to detect the
encoding *automatically*, does the two pages display
identically, or are there differences?
According to the mappings at unicode.org, there
are a lot of difference between MACROMAN and CP1252,
for instance, the first character on the page (0x80)
is A-DIARESIS in MACROMAN and EURO SIGN in 1252.
Nisse:
Yes, I said that there is no "windows-1252"
setting for Safari. It does not offer that
"named" setting in it's list of text encodings
available. There is no 1252 mentioned either --
however, that does not mean that it's not there
under a different name. Understandably, I don't
think Apple wants to use the term "windows" in
it's list of text encodings.
There is no Automatic setting. You set whatever
you want the default to be and that's it.
The:
<http://luden.se/test/t-utf8.html>
looks good ONLY under UTF-8 setting.
The:
<http://luden.se/test/t-1252.html>
looks good ONLY under Western (ISO Latin 1).
If I use Western (Mac OS Roman) there is
considerable difference, but it's not gibberish.
HTH's
tedd
--
-------
http://sperling.com http://ancientstones.com http://earthstones.com
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
