Automated localization of embedded databases

What about the thousands of records in my apps SQLite database?


Content rich apps can contain embedded SQL databases that are ignored by most localization systems. There might be one screen used to show, for example, a single selection in a thousand possible menu selections. The translator needs to translate all thousand menu selections but to the app developer, it is one screen. String extraction, visual display of the data, and text overrun detection of embedded SQL database content is frequently a very manual process for the developer.


An SQL database can be created and filled with data using SQL statements run on the developer’s computer. Likewise, all the data in a SQL database can be exported with SQL commands. The solution is to do a SQL export to a text file. The strings from the SQL export are displayed visually to the translators in a browser, in context, with text overruns detected. Once all of the content is translated, language specific SQL databases are recreated using the translated text and then added back into the app.


The technology takes a single screen and expands it out into all the individual versions of that screen that a translator should review and translate. All the visual context and text overrun capabilities are presented to the translator. The developer gets back all the data in a translated embedded SQL database, one for each translated language. Makes it easier for translators to provide correct translations the first time, means the developer does not have to review each database entry, and allows the developer to keep their program structured to use embedded SQL databases.


US Patent Application Number 62065717
Patent Filed 19-OCT-2015