>Yes there really is no reason NOT to use UTF-8 that I can think of. Browsers default to it and UTF-8 can represent just about any character set. The only time you don't want to use it is if your HTTP client (like FoxPro maybe :-)) doesn't understand how to parse the UTF-8 natively. In that case a specific code page can be useful but even then it's usually easy enough to do the conversion (it's a pain to do manually in VFP unfortunately though).

Thanks for the additional information