How do we want to ship framework translations
Albert Astals Cid
aacid at kde.org
Thu Apr 10 21:12:03 UTC 2014
El Dijous, 10 d'abril de 2014, a les 21:10:36, Burkhard Lück va escriure:
> Am Donnerstag, 10. April 2014, 09:06:40 schrieb Aurélien Gâteau:
> > Hi,
> >
> > Until now, kdelibs translations have always been released as part of the
> > kde-l10n-$lang tarballs. I was wondering whether it should still be the
> > case with frameworks, or if each frameworks should instead ship with its
> > own translations. The work I have been been doing assumed the later
> > because I did not realize kdelibs tarball does not ship its own
> > translations.
>
> To be sure, your question is only about the translation catalog in
> frameworks repos, not in anythings else like workspace, kate, konsole etc?
>
> What about the translated docbooks for the frameworks repos?
>
> How / who imports the translations (GUI/Docs) into frameworks repos?
Noone, it just works like now.
Cheers,
Albert
> Keep in
> mind that many teams do not have a source code checkout of frameworks
> repos, so the translations would have to be pulled in via anonsvn at build
> time, but anonsvn is not always available.
>
> In case lang docbooks are pulled into frameworks repos there has to be a
> check if docbooks are valid and compile or a frameworks repo will be
> broken.
> > I already have the changes to go back to separate tarballs for
> > translations, but would like to confirm this is the way we want to go
> > before applying the changes.
>
> For my daily work (proofreading translations of de, check i18n errors from
> devels via x-test, check translation bugs reported on b.k.o) I build +
> install the complete translations (gui + docs) of several languages each
> day via l10n- kde4/scripts/autogen.sh, so need that for frameworks as well.
More information about the Kde-frameworks-devel
mailing list