Internationalize tool

[pslh]

It would be very useful to be able to use the tool in the native language of the user and to be able to select the language of choice for the user interface, while at the same time producing sql and csv files which are language neutral (except for free text notes).

It is important to note that currently, many of the displayed strings are stored in the SQLite database and not in the Java code or strings.xml files. We must extract these strings from the DB into I18N ready files and update the code to retrieve the translated string rather than using DB lookups. This is probably quite a large body of work.

[pslh]

The approach taken by Corporacion OSSO to switch DBs based on language makes a lot of sense, but has the downside that the user loses access to any information stored in the English language DB. I think this is an acceptable limitation for now, but this is clearly not ideal.

Alternatives include:

• separating the read-only, language-specific database from the user-supplied data (which should now be considered language neutral);
• adding a language specific column to the lookup tables, one for each supported language
• extracting all translatable text from the DB into I18N files