I am working on a piece of software and want to use the License Field feature to distribute extra access options. We have a scheme that will produce an alphanumeric string where individual characters turn on or off certain features. That all looks sound to me (unless I've missed something?). However, my question is this: we have a number of users across the world whose computers use different regional settings/character sets. I am thinking about e.g Israeli, Japanese, Urdu etc. If I produce a License field key of, say, Arje6=7uuiTM1O5 in a UK system, how will that be handled in e.g Israel on a system set to use Hebrew? Does it use exactly the same ascii character codes, do we need to produce individual codes for each system e.g in Hebrew, or is there some interpolation that we need to take account of.
tia
Neil Turp
Hey Neil,
We use Unicode everywhere. So the data is stored and transferred as UTF8. And on Windows the data is returned as UTF16 (the "default" Unicode for the system) when the GetFeatureValue() function is called and on other platforms (Mac OS X / Linux / etc.) the data is returned as UTF-8.
In other words, you'll get the exact same data no matter what region or language settings your customers use.
Excellent, thanks Sam. That should make life so much easier.
Neil
