Closed mx1up closed 6 months ago
Merging #442 (2a5d9fc) into feature (2f5f3ba) will not change coverage. Report is 2 commits behind head on feature. The diff coverage is
n/a
.
This would definitely require translation to other languages currently supported by the application. There is no automatic translation workflow available in this project, if you know of any automatic translation you are welcome to implement it.
The other choice could be implementation of the universal icons (no translation required), ie:
ok, I will just update the translation files. For the languages that I do not know, should I provide an English stub in each language file or do I leave it out so there is fall back on the language agnostic strings.xml
?
Or maybe I can use google translate as it is a quite short translation? (though maybe not easy for google translate to interpret correctly..)
As a translation workflow, Transifex comes to mind, which is free for open source projects. However, I don't have experience implementing it and as this project is as good as finished, the return on investment seems quite low.
Or maybe I can use google translate as it is a quite short translation? (though maybe not easy for google translate to interpret correctly..)
Probably Google Translate is good enough for now.
I have added translation, based on google translate and wikipedia. I also verified that longer strings don't pose a problem.
Is it okay to rebase?
Since there are not conflicts, rebase is not necessary.
Okay, so I guess I'm ready then..
Thank you for your contribution
thanks for accepting 👍
What does this implement/fix? Please describe.
Does this close any currently open issues? fixes #441
Additional context
Where has this been tested?