scelts / gees

Landing rate calculation for the Microsoft Flight Simulator 2020

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Language selection + resource for easy translation

wolfie24 opened this issue · comments

Hi, my name is Daniel ("Wolf " for the fellows) and I an enthusiast of flight simulators.
I have contributed on several occasions to translate programs or articles into Spanish that I found interesting.
Thanks to a YouTube channel on MSFS2020 in Spanish (https://www.youtube.com/results?search_query=%23MSFS2020) I have found out about your program, and of the two shown on that site, yours seemed the most practical and easy to use.
I would be interested in having the possibility of having it in my native language, Spanish (Spanish from Argentina, which also works for any other country that speaks my language).
If you are interested, you only need to send me the sentences to translate and I will gladly do so. This will not only benefit the community I am in but it will broaden the horizon of dysfusion of your program.
I have not seen a separate file with text strings, maybe this would allow you to add many other languages ​​as the flight simulation community grows day by day.
Among the programs that I translated into Spanish (at that time only usable by X-Plane) are LittleNavMap, Landing Rate, some Ortho4XP manuals, AlpilotX meshes, etc.
I remain at your disposal if you are interested, cordial greetings from the South of Argentina!

Hi Wolf,
Gladly, thanks! I'll keep this open since I would need to create some kind of resource where one can change the language so that you can easily update it for Spanish.
Will ping you once it's done, I didn't have much time to work on this the last days.

Hi again,

Today I was working on some bugs and features and was also thinking to implement the language change, but I came to a realisation: The interface will change, this is by no means a finished app or anything!

So, the problem with the translation will be - I change functionality, and this requires an interface change to reflect it (i.e. today I changed the string "Auto close after" to "Auto close - bounce timer". If I have one language I understand, I can change this easily. But, if I have 5, of which 4 I can't understand, this becomes a problem! I would need to ping all the translators before publishing anything, to translate all the changes to all the languages, and this will be an issue if it would even be possible. Especially with an app like this, where it's much more important to have a quick fix or functionality update, than a translated interface.

Hope you understand, but I'm closing this for now. Once (if ever) there is a fixed interface and a long-run plan, I will for sure implement multi-language support and notify everyone.

Hi,

No this is not a problem - I was thinking of doing it this way, or using some .net feature where this could be done automatically.

The problem is that I will be changing the strings themself often. So in your example, for example, I change the string
001: Options
to
001: System Settings
And in translations, it stays 001: opções

This will happen at this stage of the app. Especially for sentences. Just now with the latest update I have changed:

Auto close after (seconds):
to
Auto close - Bounce timer (s):

And I cannot publish the update until people translate this string to each of the languages.

So for now, multi-language support is not really something I can handle. This can be done only when the interface is more less fixed, and there are no plans to do much, often.

Thanks Daniel!

I'll make sure to reopen this and ping you once the multi-language support is on the table.