set codepage to "utf-8"
https://www.lianja.com/doc/index.php/SET_CODEPAGE
set codepagedata to utf-8
https://www.lianja.com/doc/index.php/SET_CODEPAGEDATA
Column constraint to prevent code page translation for character and memo fields
ALTER TABLE customer; ALTER COLUMN notes NOCPTRANS
https://www.lianja.com/doc/index.php/NOCPTRANS_Column_Constraint
convertutf8 app myapp convertutf8 database mydatabase convertutf8 table mytable convertutf8 file mygreekfile.txt codepage "Windows-1253" convertutf8 file mygreekfile.txt codepage 1253
NOTE: For .rsp Lianja/VFP Server Pages scripts, include the charset meta head element:
cGreek = filetostr("mygreekfile.txt")
? cGreek
? strconv(cGreek,1253)
? strconv(cGreek,"Windows-1253")
https://www.lianja.com/doc/index.php/STRCONV()
transtext.prg) to handle the translation, so my delegate just calls the script, passing it the default message (‘arg’ passed to the delegate procedure) and any additional parameters, here ‘it’.
////////////////////////////////////////////////////////////////
// Event delegate for 'texttranslator' event
function z_transtextjs_texttranslator(arg)
{
return Lianja.evaluate("transtext('"+arg+"','it')");
};
The equivalent Lianja/VFP delegate procedure for desktop only Apps would be:
//////////////////////////////////////////////////////////////// // Event delegate for 'texttranslator' event proc z_transtext_texttranslator(arg) return transtext(arg,'it') endproc
And here is my transtext.prg in the Library:
// transtext.prg
parameter cText2Trans, cLang
if pcount() < 2
cLang = "fr"
endif
//if isserver()
// // These are message titles in the web/mobile client
// // you may want to handle these differently
// if inlist(cText2Trans,"Error","Information","Message","Success")
// return cText2Trans
// endif
//endif
do case
case len(cLang) = 2
return keylookup("translations!messages_&cLang","original",alltrim(cText2Trans),alltrim(modified),cText2Trans)
case cLang = "annoying"
return cText2Trans + "...just sayin'")
otherwise
return cText2Trans
endcase
// end of transtext.prg
The main case statement:
return keylookup("translations!messages_&cLang","original",alltrim(cText2Trans),alltrim(modified),cText2Trans)
uses the KEYLOOKUP() function (for an SQL equivalent, use SQLLOOKUP()) to look up the default message in the index of a table in the translations database that I have created. Since the cLang parameter received the value ‘it’, the table is messages_it, which I have created with the following values for sample messages from the desktop and web clients:
Record # id original modified
1 0000000001 Success Riuscito
2 0000000002 Information Informazione
3 0000000003 Error Errore
4 0000000004 Message Messaggio
5 0000000005 Record was updated. I dati sono stati aggiornati.
6 0000000006 Record was added. I dati sono stati inseriti.
7 0000000007 Record was updated I dati sono stati aggiornati
8 0000000008 Record was created I dati sono stati inseriti
The KEYLOOKUP() function uses an index on the table, so I have also created an index tag (create it in the Command Window):
index on original tag original
I’ve created a similar table, messages_fr and its original index tag to be used when the cLang is ‘fr’ as shown in the screenshot earlier.
If the message is not found in the table, the KEYLOOKUP() function just returns the original message passed (cText2Trans).
https://www.lianja.com/doc/index.php/Text_Translator
Lianja developer 