meikpiep
Translating Gauguin to many languages
That's pretty impressive.
Would you be willing to translate this App into other additional languages?
I just commited localization into German, but it the first time into Android localization for me. Plus, a have included all languages which I am able to deal with by myself.
If you have any further recommendations, don't hesitate.
I recommend to look into some web based translation service as it makes it easier to develop, IMO. You can then update the english source file only and the website will notify translators and update the translations. Some services also offer AI assistance which I often use to translate my apps.
@mueller-ma Thanks for explaining. @mondlicht-und-sterne Do you need anything from my side? Code changes? I read about the per-app locale choice from Android 13 on, but I didn't implement it yet - would this help? Should we discuss here or switch the medium?
@mueller-ma Thanks for explaining. @mondlicht-und-sterne Do you need anything from my side? Code changes? I read about the per-app locale choice from Android 13 on, but I didn't implement it yet - would this help? Should we discuss here or switch the medium?
We can also discuss this elsewhere. However, I don't have Discord. Can only offer telegram, xmpp and matrix.
Good. I will comment here when I have one of these channels ready to use, this will probably not happen before the next weekend, I hope you don't mind.
@mondlicht-und-sterne would be nice if you leave me a message via https://github.com/meikpiep/gauguin/blob/main/gauguin-app/src/main/play/contact-email.txt
Closing this issue after not receiving an answer for three weeks.
@mondlicht-und-sterne If you change you mind, feel free to contact me. Sorry if I unintentionally decreased your motivation to participate in any way.
Hi @meikpiep, this is a different user joining the translations discussion. I would like to contribute with translation.
Did you look into some web-based tool? I recently started using weblate to collaborate to other apps' translations.
If you don't have anything like that in place you can let me know what needs to be translated. According to my very limited knowledge of Android apps structure, I believe that I would need to create a new strings.xml file inside src/main/res/values/.
Please let me know how I can help.
Sounds great. I have not looked at such a tool and never used one before, so weblate may do the race. :-)
I've reopened this issue to not oversee it. I'm currently kind of deep dived into Azure Cloud as Microsoft sponsored Gauguin with computing power to generate the game difficulties. This is time boxed until end of may from Microsoft's side.
This does not mean that this topic here has to wait until then, just a small 'heads up' that my head is under some mental load.
I'm glad you like to join, weblate sounds good. I have one concern, maybe I'm a bit old school: I would try to avoid translations which exclusively build of ai. Is that realistic, what are your experiences? Are there native speakers on weblate etc. to fill such gaps? How is quality assurance to be done?
Thanks for reopening the issue. I must say that I have just a little experience with Weblate so I might not be the best one to advise on this (I just joined recently and helped to translate one app into my native language, which was still pending).
As far as I've seen, Weblate translations are mostly done by volunteers. I see there is an option for automatic suggestions powered by different machine translation services, but this can be enabled/disabled by the developer. For other FOSS apps, I have seen the developer encouraging users to contribute with translations, either on the README file or on release notes.
As for the Quality Assurance, Weblate has an automatic Quality Check for small common mistakes (like missing plurals, commas, full stops...), but more importantly the developer can choose how to handle it for their app. There are 2 main modes:
- The project accepts direct translations
- The project only accepts suggestions, which later need to be validated
In the first mode, any user can edit translations. Users can also submit suggestions to suggest changes, when they are not sure about some terms.
In the second mode you can either have:
2.a any user can submit suggestions. Any user can vote for suggestions. Suggestions that have been voted X times become accepted translations. 2.b any user can translate. These are unapproved translations. A group of reviewers can approve, decline or edit those translations. Once the reviewers approve the translations, those become the accepted translations and cannot be edited.
This is better explained in the Weblate documentation on translation workflows.
Thanks a lot, that sounds promising, I will have a look at the link and will provide further details here.
I added Gauguin to Weblate yesterday, but in a rudimentary state, just having the strings.XML file with the main texts. I realized that the keys of the texts should be updated to include more context infos. I locked the project because of that.
https://hosted.weblate.org/projects/gauguin/
@nach0 Do you want to become an admin at Weblate? Is your username the same as in GitHub?
I will try to optimize the strings in the next few days to enable Weblate usage without the risk to brake many translations by doing that later.
I added Gauguin to Weblate yesterday, but in a rudimentary state, just having the strings.XML file with the main texts. I realized that the keys of the texts should be updated to include more context infos. I locked the project because of that.
https://hosted.weblate.org/projects/gauguin/
@nach0 Do you want to become an admin at Weblate? Is your username the same as in GitHub?
Thank you ;)
I added Gauguin to Weblate yesterday, but in a rudimentary state, just having the strings.XML file with the main texts. I realized that the keys of the texts should be updated to include more context infos. I locked the project because of that.
https://hosted.weblate.org/projects/gauguin/
@nach0 Do you want to become an admin at Weblate? Is your username the same as in GitHub?
Cool. Thanks for getting this moving. It is fine if it's just a rudimentary state, it's a beginning.
I am happy to be an admin in Weblate (I use login via GitHub so, yes, my username is the same), but as I pointed out before I am not very experienced with this tool (just joined 1 month ago and helped translate 1 app). I am happy to learn along the way, but I might not be the most efficient help. I can also help with including more context info (which I think I would be able to infer in most cases by checking the app and identifying the string).
Please note that I will be away for the next 10 days, so I won't be active on GitHub nor Weblate, but count on me to contribute on this issue.
@nach0 Great. I will log my actions here to keep you and the rest informed. I'm eager to get Weblate going - raise your hands if I'd do things that you want to do on your own. I'm happy to have any help and I'm optimistic that we can manage the translations together.
@mondlicht-und-sterne Greetings! Do you have stakes to help in whatever form fits?
@mondlicht-und-sterne Greetings! Do you have stakes to help in whatever form fits?
@meikpiep
I have already translated into 75 languages ...
I renamed most strings to get more detailed translation keys: https://github.com/meikpiep/gauguin/commit/fbdd6441561e5012146c9b00a9227b506fbafdce
I mentioned Weblate in the readme file and submitted the Weblate project to Weblate itself to get the free plan for free software projects. Currently, the strings get covered there in one single component, meta data have to be added via another component.
Weblate creates pull requests at least every 24 hours to submit the translations, this works fine.
I switched the options so that (beside the admins) every user may submit suggestions and every user may vote for suggestions. Each translation needs two suggestions (e.g. from the original translator and one additional user) to be submitted. Users may begin to translate to additional languages as they want to.
Currently there is only the glossary, which is created automatically, i.e. nothing can be translated yet. So I'll be checking in from time to time to see whether it works or not.
Currently there is only the glossary, which is created automatically, i.e. nothing can be translated yet. So I'll be checking in from time to time to see whether it works or not.
@mondlicht-und-sterne That's strange, as an admin I could translate and suggest German texts. Can you supply a screenshot and a corresponding URL?
Here is another project, not from me, just as an example:
https://hosted.weblate.org/projects/wrye-bash/
You can see 1. the project and 2. the glossary.
In your project there is only the glossary. And I was always told that this is an automatic image of your project.
Conclusion: If there is only a glossary, you cannot translate it.
Not sure what's the actual problem. I've just logged into Weblate for the first time ever, opened a random string among the 155 ones the project has for English and it allows me to suggest a different translation:
So all is fine?
@mondlicht-und-sterne Nobody stated that this is no Weblate glossary - the point is if this setup allows a translation which obviously seems to work (would be nice) or @mccartney and I do oversee something (which we could only check if you share more details).
@2013ZRZ translated Gauguin into Simplified Chinese via Weblate! Yay, the process obviously works.