Studio 6.x – Localization / String Tables
Strange you should ask that question now. We have 10 different
libraries, thick, thin, RESTful, and have just completed a project to
move all our string tables into Postgres. We have created a library
(number 11) to manage them which also has an interface to the Google
translate API.* This has greatly improved and simplified the management
of our string tables, especially where there are common objects between
libraries. We still use Omnis’ string table functions to translate the
objects’ $text but the Startup_Task of each application builds its own
in-memory string table from the database.
* Yes, I know Google’s translations are far from perfect but it gives us
a starting point since Omnis’ String Table Editor lost this functionality.
On 10/07/2017 18:59, Andrew Stolarz wrote:
> We are looking into translating an app into another language (Omnis thick
> ie. buttons, text, grids, menus etc.
> Omnis has the “built in” String tables.
> However im just curious if others are using a different approach?, such as
> creating your own string table in a SQL database etc.
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com