localization file

For non-English speakers attempting localization, the lack of a language folder and hard-coded text indicates an issue. Please provide a separate localization file (e.g., XML).

Quote
"Vaquero
March 18, 2014, 06:56:26 pm

I'm wondering why you didn't go for a full localization file. At the moment all the text is hardcoded, and for some tools, if a user version is present, the text gets replaced.
Why not replace all text in the code with keys, which content is then loaded according to the chosen language? Additionally I always used a parsing function to determine if the key contains text or a reference to another key in another section or the default if there is none in the selected language. It's a good thing you've already written a frontend to manipulate XML data. But with the current implementation one can't localize menu items for example.
I know at this point it is a huge workload to replace all hardcoded text, which is why I do this stuff early on in a project. I still wish, you would consider it.
For some unknown reason I can't copy the helptext from the tool search, but from the tools customization.  But the "User Tool Text" just works in the tool search and not in the tool customization..."

https://digitalfossils.com/nvil-forum//index.php?topic=528.msg1987#msg1987
https://digitalfossils.com/nvil-forum//index.php?topic=2247.msg7453#msg7453