Some time ago I posted a localization component/tool that I've created but it had some issues. I've fixed them all and it's available on github!
Some time ago I posted a localization component/tool that I've created but it had some issues. I've fixed them all and it's available on github!
https://github.com/albertodev01/TLanguages
You can find everything in the readme of the repo. Basically there is an editor that creates a json file with the localized strings and then this file has to be loaded as resource in the project. In this way the apposite component will be able to localize the strings.
I'm not an expert so this may not be the best approach but I'm using this for my projects and it fits my needs. I have taken inspiration from Qt (C++ side) that uses a localization tool called Qt Linguist in which it creates an xml file and then it's loaded in the project as resource.
https://github.com/albertodev01/TLanguages
https://github.com/albertodev01/TLanguages
You can find everything in the readme of the repo. Basically there is an editor that creates a json file with the localized strings and then this file has to be loaded as resource in the project. In this way the apposite component will be able to localize the strings.
I'm not an expert so this may not be the best approach but I'm using this for my projects and it fits my needs. I have taken inspiration from Qt (C++ side) that uses a localization tool called Qt Linguist in which it creates an xml file and then it's loaded in the project as resource.
https://github.com/albertodev01/TLanguages
While reading the documentation I was confused until I looked up the meaning of 'apposite' (I'd never seen that word before). You may want to use the word 'relevant' or 'corresponding' instead.
ReplyDeleteAlberto Miola can you add some demo to TLanguages package
ReplyDeletefor window/Android.
shlomo abuisak Yes, I will add a demo tomorrow
ReplyDelete