NetTalk Version 5, PR16 or later applies.
update - PR20 adds support for Spanish
Introduction
Many countries use more than the basic ASCII Roman character set. Handling data with extended character sets can be tricky. There are two basic ways your data may be stored. Please read this section and then decide which way needs to be handled in your situation.
Web HTML Charset
Set the HTML Charset on the Advanced tab of the WebServer procedure settings. The following information ONLY applies if you have the HTML Charset set to 'utf-8'.
Regardless of the way your data is stored, I recommend setting the charset to utf-8.
Utf-8 is an encoding scheme for encoding unicode characters. The reasons for choosing utf-8 is outside the scope of this article.
Data Stored as utf-8
If your app is exclusively a web app, and data will be entered via a browser, and displayed via a browser, then the data can be stored in the database in utf-8 format. If you are using a SQL engine it's also possible that other (non Clarion) apps, that support utf-8, will be happy with this approach.
This is the default approach for NetTalk, if the charset is set to utf-8.
Data Stored as a "code page"
If your data has been captured by a Clarion program, or will be displayed by a clarion program (INCLUDING a Clarion Report) then the data must be converted to a specific code page for storage, and converted back to utf-8 when being displayed in a web page. This makes the data limited to one specific code-page - however in most cases that is ok, since your Clarion app was limited in that way anyway.
Support for each language has to be added on a case-by-case basis. So far support has been added for;
Polish (PR16), Spanish (PR20)
If you use an extended characters that aren't in the list of languages above, then please contact me. I may need some minor information from you, but it should be straight-forward to add support for other languages.
At this stage you will need to set a setting, in embed code, in the web server procedure. (ie it isn't yet a template option.) In the web server procedure, in the "Override Default Server Settings" "NetTalk Object After s_web assigned" embed point, add a line of code something like this;
s_web._SitesQueue.Defaults.StoreDataAs = net:StoreAsPolish
or
s_web._SitesQueue.Defaults.StoreDataAs = net:StoreAsSpanish
As more languages are added, more equates will be available as well. It's also possible that regions will be introduced which span multiple countries that share characters.