Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This version of language translation reverts to using a simple table to store translations instead of the approach used by Microsoft's Multilingual Application Toolkit.
The strings to be translated are first extracted from the
*.Designer.vb
files. These have then initially be ran through Google Translate and stored in a local table.The code in this PR accesses the local table to change translation text at run time. The user can change language whilst the software is running and all of the forms that are currently open will be updated.
Due to limitations with resource files, the translations are being stored in a single binary file that is in SQLite format. The advantage of this file format is that it can be queried in exactly the same way as an SQL database, but does not require database server software to be installed. This approach is to ensure that we do not make thousands of queries to the central database each time we need to display text in another language. The approach is in improvement and also a simplification, on the solution that we proposed in Kitale in March
Next steps: