Multi-lingual support

[Corentin-Aulagnet]

I added support for french but tried to do it in a way that it is relatively easy to add other Latin-alphabet-based languages.

It works with a new class Translator, it stores all the translations for the part names (like string, barrel, etc) in a dictionary.

What did you fix?

I tried to fix Multi-Language OCR Support
closes #67

Evidence/screenshot/link to line

Considerations

• It still need some polish, since all displays are not translated but the detection is good
• Does this contain a new dependency? [No]
• Does this introduce opinionated data formatting or manual data entry? [Yes] I think this is not ideal.
• Have I run the linter? [No]
• Is is a bug fix, feature request, or enhancement? [Enhancement]

[dimon222]

Interesting approach, but one of the reasons we don't use this kind of mechanics is that we want use out of the box translation payloads provided by Warframe.market (you might be able to see it in source draft PR). Is there a reason you don't use same way and instead manually translate the part names?

[Corentin-Aulagnet]

I completely understand the problem with my solution. But I wasn't able to reproduce the request to the warfame.market API but in french. For exemple : "https://api.warframestat.us/wfinfo/filtered_items" which is (I believe) the base data set.

I will try working on another solution with the data from warframe.market. Could you explain how the custom "wfinfo" request was made ?

[D1firehail]

The ReloadItems function takes care of fetching the translation data according to the locale setting (which your change to SettingsWindow.xaml should already take care of). getLocaleNameData accepts the english name and returns it translated according to the WFM translation data for use in language-specific levenshtein distance functions. You can see #231 for a mostly correct implementation and my comment there for what's missing (although note that Master It is currently broken due to in-game UI changes)

[Corentin-Aulagnet]

I just pushed another version similar to the one from #231. As I said in the commit message, I did not check either Master It or the translation of the displays.

I will work on understanding how Master It works.

[Corentin-Aulagnet]

Ok ok, some news from here. I had a bit of trouble with git after the release of 9.5.4
I tried to get the cleanest history I could after the mistakes I made.

The last interesting commits are focused on UX.
The displays in the equipment window are now in the correct language (locale data come from the market_item.json files.
I implemented resources files called "strings" and "strings.fr" They can be used to translate all hard coded texts such as status messages etc. I am working on a way to translate the UI (all ard coded texts in the .xaml).
If you have any clues on how to do this, I would appreciate it.

I also have, at the time when I write this message modified the output texts of the Snap-It to display the local names of the parts. I will refactor it to work for all displays.

I think this version is production ready, as long as the users speak a bit of english (UI) but I assume they do if they end up downloading this tool. What do you think ?

[KuzyXD]

I want it to merge!

[dimon222]

Conflict, sadly.