Fwd: Structure of translation files on Subversion (question for all teams)

[Josep Ma. Ferrer]

Hola a tothom,

Jo estic per l'opció "a". Com ho veieu?


---------- Forwarded message ----------
From: "Luigi Toscano" <luigi.toscano at tiscali.it>
Date: Jul 14, 2017 23:06
Subject: Structure of translation files on Subversion (question for all
teams)
To: "KDE i18n-doc" <kde-i18n-doc at kde.org>
Cc:

Hi all,
>
> hoping to discuss about this in person during the Akademy (see the other
> email: when is it better to book a BoF?), I have a question about the
> structure of the translations file on the Subversion repository.
>
> Right now the structure follow the old modules:
>
> <lang>
> --> <messages/docmessages/docs/etc>
> -----> <module>
> --------> <po files of all repository in the module>
>
> where module is kdegraphics, extragear-multimedia, kde-workspace,
> frameworks, etc.
>
> This structure comes from the times when the modules were the basic unit
> of work.
> Nowadays each program is more independent, and this structure does not
> allow
> to distinguish which translations belong to which repository (see the big
> bucket which is kde-workspace aka Plasma). Also it complicates a bit the
> maintenance when a repositories moves from one logical module to another.
>
> The advantage is that it provides some grouping that can help us to divide
> the
> work and prioritize it.
>
> Now, let's consider this structure instead:
> <lang>
> --> <messages/docmessages/docs/etc>
> -----> <repository name>
> --------> <po files of the repository>
>
> where repository is kconfig, okular, kile, etc
>
> The question is: would this structure be acceptable for you? Please
> consider
> the following answers, and it would be nice to have answers from a relevant
> group of languages :)
>
> a) I don't care, fine by me/my language team, I can get the logical module
> from sysadmin/repo-metadata.git;
> b) yes, but in our team we need to see some structure, like which set of
> repositories are shipped together, but if the website shows this it's fine;
> c) absolutely not, our team need the current structure because <please
> write a
> reason>;
> d) other (please write a reason);
>
> Now up to you!
>
> Ciao
> --
> Luigi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-i18n-ca/attachments/20170715/283758d7/attachment.html>