With this example the character äöü are ok, but the – or en dash
or – or key [alt -] are not ok.
The browser sends cont=%E4%96
And in A4D_GetHttpBodyCallback the blob has the same value.
You have to make sure that the encoding of your page matches the
'output charset' setting in Active4D.ini. The browser uses the meta
charset to encode the form data. Active4D uses the 'output charset' to
decode form data. If they don't match you'll get junk.
Even if you get that right, if you are using iso-8859-1 you can't use
mdash and ndash -- they actually aren't valid characters in
iso-8859-1. It worked in v4.5 because it used a simple (non-standard)
character mapping to convert from iso-8859-1 to Mac Roman. But in v5
Unicode is more strict about standards, so you end up with junk
because mdash is invalid.
I recommend that all sites using non-Asian characters convert to
utf-8. I have written a python script that will do a recursive
conversion of all files in a directory to utf-8, so the process of
converting source files is painless. I will post the script on the
site this weekend.
Please don't ask me to provide some kind of magical workaround. This
is one of those issues that arises in the conversion to Unicode, it
has nothing to do with Active4D.
BTW, one of the great things about using utf-8 as your character
encoding is that you can write *anything* to the output without
converting to HTML entities.
Kind regards,
Aparajita
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoy.org
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
