Localization

Q:
What is the map and format of the config.db ?
The map (C:\lianja\cloudserver\tenants\public\) is still empty.
config.db is not present in the lianja-structure.
I tried “set currency to ..” in just one page in an init-event.
But of cours, it belongs in a config or setting-screen..
A:
For development purposes you can create a config.db in the .\Lianja\conf\ directory and put your SET commands there.


Each database has a different way of handling the character collating sequence which is one of the reasons Lianja uses unicode/utf-8 which is the recommended encoding for apps that need to share data between desktop and web/mobile apps.

Lianja does not support changing the collation sequence in the scripting language.
VFP does not support unicode/utf-8 but uses the rather old style of windows codepages.

The SET COLLATE “GENERAL” is primarily for US and Western European characters and will not work correctly with DBCS or unicode/utf-8.
So, if you want to query data using SQL then convert the string literals


Q:
I can put a “set date to german” by the Console and it works ok in DeskView.
But how and where I must write it in Javascript UI?
A:
Dates in the Web Client are displayed in ANSI format so to be independent of the locale of the user.
The format is:
yyyy-mm-dd or yyyy-mm-dd hh:ii:ss

Q:
in WebView (report) it’s displayed ok (e.g. “German”)…
A:
the WebView report is generated server side using a dynamic server page which is why it can display an alternative date format to ANSI.


Lianja is all UTF8 if you put the –unicode command line switch on the desktop shortcut.
This is auto detected for Chinese, japanese, korean, russian and other locales.


App has a page with id “Catalogo_de_Almacenes” containing spanish characters.
That is the “id” NOT the “caption“.

In the app directory look for the file with a .lianja extension then search for that name and remove the accented character.
You cannot use accented characters for the id or any of the UI elements.
you have –utf8 on the app builder command line switch but that particular app had been saved with a codepage locale set.


It is much better to use Unicode UTF8 as this works better in web and mobile apps too.
You cannot use accented characters in page, section or formitems id. They can be used in captions and other attributes.


Q:
(Gant chart) When I type any text that has an accent (i.e. “cámara”) in any text label or text box it doesn’t recognize the letter and it changes it by a ? symbol.
A:
Set the Locale on your Lianja App Builder and desktop Lianja App Center to utf-8.

You can use the Command Line Switches –locale or –utf8, e.g.

Code:
C:\lianja\bin\lianja.exe --utf8
C:\lianja\bin\lianja.exe --locale utf-8

and

Code:
C:\lianja\bin\lianjaruntime.exe --utf8
C:\lianja\bin\lianjaruntime.exe --locale utf-8

.rsp page that generates the Gantt chart probably needs to have the following in the <head>
<meta charset=”UTF-8″>
File is graph_gantt.rsp in the Library.



Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s