Child pages
  • Internationalization - I18N

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
i18n.setI18NMessage('servoy.lbl.date', utils.stringReplace(i18n.getI18NMessage('servoy.lbl.date'),'/','-'))

...

Separators

Formatting defaults need to be specified. In the English(US) format, the dot ('.') is decimal separator (and comma is 1000 separator). Decimal values within code need to be specified in English format as well. This will automatically be translated to the end users format when they run the code.

...

A complete table with the supported values of the timezone property can be found on IBM's WebSphere Application Server page.

For NGClient solutions, use the format property (Use as LocalDateTime checkbox) per field to dictated if the timezone should be used in client or not.
For the old web clients and smart clients, Servoy has 2 modes for working with Timezones. Switching between these two modes can be done by toggling the servoy.use.client.timezone property on the Servoy Application Server's Servoy Server Home page, under Locale Settings.
Take note, that this setting is ignored by the NGClient solutions.

Property set to true:

A datetime entered will be presented exactly the same in each client, regardless of the timezone of the clientclient 

Example: Any client, regardless of which timezone they are in, sees a datetime entered as 8pm as 8pm. Servoy makes corrections under the hood to achieve this.  (like birthday)

Property set to false:

Servoy performs no calculation and the dates are automatically converted by Java to match the user's timezone. 

Example: A client in UTC + 5 enters 10pm. The server runs in UTC, so stores 5pm. And a client in UTC - 2 sees 3pm. Since databases do not store a timezone with a date, everything will be mixed up when the database is started in another timezone.

The first scenario (having client timezone property set to true) is the preferred way of operating, because this gives the most consistent outcome. (like calendar item)

 

So For NGClient checking the "Use as LocalDateTime" property has the same affect as the property set to true above but just for that dataprovider