Replacing ResX Localization with Json/XML/Csv
rasyidf opened this issue · comments
We can see that Edi uses ResX Localization that it must be compiled to get the language available.
I think this approach can be used, or we could improve it with Json / XML. so that users can add their own translation without having VS and the source code.
I agree - Json/XML sounds more trustworthy than CSV in my ears :-) but I am not sure how this is supposed to work when you load a static string in an XAML View how does it get looked up at runtime and is being translated correctly.
Do you know a good reference project to better understand localization based on Json/XAML?
Currently I am working on UFSJ (File Splitter and Joiner) that uses Language pack like this:
<?xml version="1.0" encoding="utf-8" ?>
<UFSJ>
<Language Name="English" LCID="1033" Local="United States">
<Author Name ="Rasyid" Contact = "http://rasyidufa.github.io/UFSJ/" />
</Language>
<!--Add Language Window-->and it's run smoothly
It can translate language without restarting.
see last frame, the .gifs actually showing theming support.. just re-pick..
yes, it looks good to me - I just need a complete demo project with code :-) to really understand how it works...
Soon after my Exam. :) I'll try to simplify the code.
I see you mean this project:
https://github.com/RasyidUFA/UFSJ
I can have a look at it - no problem - its just confusing because you have 2 github logins and there was no url so for :-)
Here is a demo WPF project called SettingsModelWPFDemo + Documentation
which is also translated with resx files:
- When you have the time - do you think you could develop this into a 2.0 version that uses Json / XML?
This would allow us to have both versions side by side and compare their function on a much smaller and more simplified scale :-)
I've pushed new repo that uses my framework, Json and XML.
Here
as you've said, I'm working on 2.0 version.