Posted by: Erik L
« on: September 25, 2014, 12:55:59 PM »You should add this to the official (or semi-official) suggestion thread. Separate threads are good for discussion, but Steve does not always track them.
Now on-topic. Localization in VB requires resource files, one per language and the forms and dialogs all need to be tokenized to accept the translations. As some example code from a program I am working on (intermittently) with localization:
So... tl;dr: It takes more than just a language file of all the strings. It requires a lot of program modifications also.
Now on-topic. Localization in VB requires resource files, one per language and the forms and dialogs all need to be tokenized to accept the translations. As some example code from a program I am working on (intermittently) with localization:
Code: [Select]
'localize the UI
Me.Text = locRM.GetString("[TITLE]")
Label1.Text = locRM.GetString("[LBL_TABLE]")
cmdRead.Text = locRM.GetString("[CMD_READ]")
btnReset.Text = locRM.GetString("[BTN_RESET]")
cmdRunSQL.Text = locRM.GetString("[CMD_RUN]")
rdoNonQuery.Text = locRM.GetString("[RDO_NON]")
rdoDataset.Text = locRM.GetString("[RDO_DATA]")
That is just a small example. In the resource files (I have one for English, which is also the default when a specific language file does not exist; and one for German utilizing online translations, but I know enough German to at least verify most of it.) there are tokens like [TITLE]. This is matched to Design Mode Database Tool in English and Design-Modus-Datenbank-Tool in German. So... tl;dr: It takes more than just a language file of all the strings. It requires a lot of program modifications also.