08:59:09 AM
3K50J9EVE
Point me to where the data from the web ibput field is encoded and I will look at it.
We are still confused with encoding issues, lacking a clear global view and test cases.
Hopefully we'll find some help about that soon.
What ever happened with this?
I recall you and Rick discussing a whole complicated setup. All that is needed is the web fields accept unicode, which they do under utf-8, and you convert them to vfp dcbs.
Not allowing unicode entry is very old fashioned and I am getting many complaints.
It requires specifying, in each form or form class, the Language Identifier and/or Code Page utilized, and to operate the to|from UTF8 conversions accordingly.
Added to roadmap, can be done for version 1.11 scheduled around the 15th of March.
Is there anything I can do to enable that? I made a mistake and told some users it was supported.
We need to add additional support for non-western languages
Normally in VFP the user can enter text in foreign languages thru the standard Windows language input. I can enter Hebrew that way easily. Still a single byte language, it stores fine in standard VFP table.
On a web input field it does not save the correct characters. How do I address this?
