Both win and web offers the possibility to substitute a string that is an url. The decision to use url syntax is taken in a couple of ways, a tag in the string, a parameter through COM (win).
But how do we decide which type of encoding we should use? How can we detect what the receiver needs/expects.
How can we make sure it works in as many cases as possible, and not brake existing use.
Before it was all ANSI, characters up to 0x7f (127) was just passed along, characters from 0x7f to 0xff was encoded according to the standard by putting a % before the hex value of the character.
Unicode gives a couple of choices: encode characters with ANSI codepage and then url encode them, encode all characters to utf-8 then prefix each of the characters 1 – 3 bytes hexvalues with %. The last option is according to the new standard http://www.ietf.org/rfc/rfc2279.txt .
It is still possible to pass characters up to 0x7f along.
When you add new webpanels you may choose URL encoding directly in a dropdownlist