On 2/22/19 9:28 AM, Jean-Baptiste Holcroft wrote:
Hello Hans, (CC : translation mailing list)
I just read your article  about Flicker Free Boot, and it says translations are
coming soon, which is a great news! Thank your for taking care of multi-lingual support
While this is good new, I'm worried about the f30 schedule . Translators need a
little time to translate, dev to release, packager to produce a new package.
As we already are behind string freeze, can you please make sure to communicate here when
content is ready to translate and tell us the deadline?
Thanks a lot for your help and understanding,
Thank you for getting in touch, I was planning on doing a blog post asking for
but the trans list probably is a better place for this.
Once I've translation support ready (the plan is to work on this starting this Monday
I hope to have it ready Tuesday) I will send another mail. I will do a Dutch translation
myself, to make sure everything works as it should.
This is my first time working with translators, so I've some questions for you :)
Is there some specific infra in which I should "hookup" the plymouth package so
that translators can translate it using there "usual" workflow ?
Or shall I just attach an untranslated .po file to my next mail ?
I've upstream commit access so I can merge the translations upstream myself
if people send me .po files with translation for their language.
Note for now we are only talking about 3 user visible strings:
"Do not turn off your computer"
For how these are used. There are a bunch of other strings in the plymouth
commandline tool which should probably be translated (like --help output),
but my plan for the first version of translation support is to translate just
these 3 strings, as these are shown to every user when doing offline-updates,
where as the commandline util is normally never directly called by the user
(it is called from systemd units only).