At 8:35 AM +0100 3/6/08, David Sveningsson wrote:
Sidenote: If I replace åäö with numerical html
entities it works, but that's not a reasonable
solution to me.
And you're right -- it isn't a reasonable solution .
Whatever is generating your characters should
generating the same characters regardless.
However, some word processing programs, like Word
for example, make substitutions to those
characters that look fine when reviewing the
documents in Word, but when viewed by other
programs don't look right.
One of the most obvious and common ones for me is reviewing things like this:
think that?s another case
I see this all the time in email where people use
some key combination to produce an apostrophe
when it translates to a comma. It would be nice
if our applications would not make substitutions
for us.
This is similar to the PUNYCODE mess that some
browsers make of IDNS. Only three percent of the
Global population use English as their native
language. The rest of the world wants on the
Internet and wants to be able to use their own
language. But some Browser developers (i.e., IE)
don't want other-than-English characters to be
shows in urls but instead show PUNYCODE, which
was never designed to be viewed by the end user.
Arrogance and ignorance are often coupled.
Cheers,
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
