[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Structure of translation files on Subversion (question for all teams)
From:       "Josep Ma. Ferrer" <txemaq () gmail ! com>
Date:       2017-07-18 21:02:17
Message-ID: CADXomxtBZGK=boO78Lffs6PRBeGxVz=34qhS=YnPrOtXdw+fEw () mail ! gmail ! com
[Download RAW message or body]

Hi,

for Catalan team, we prefer the "b" option. But option "a" could also be
fine.

Thanks,


2017-07-14 23:05 GMT+02:00 Luigi Toscano <luigi.toscano@tiscali.it>:

> 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
>

[Attachment #3 (text/html)]

<div dir="ltr"><div><div>Hi,<br><br></div>for Catalan team, we prefer the \
&quot;b&quot; option. But option &quot;a&quot; could also be fine.   \
<br><br></div><div></div>Thanks,      <br><div><br></div></div><div \
class="gmail_extra"><br><div class="gmail_quote">2017-07-14 23:05 GMT+02:00 Luigi \
Toscano <span dir="ltr">&lt;<a href="mailto:luigi.toscano@tiscali.it" \
target="_blank">luigi.toscano@tiscali.it</a>&gt;</span>:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi all,<br> <br>
hoping to discuss about this in person during the Akademy (see the other<br>
email: when is it better to book a BoF?), I have a question about the<br>
structure of the translations file on the Subversion repository.<br>
<br>
Right now the structure follow the old modules:<br>
<br>
&lt;lang&gt;<br>
--&gt; &lt;messages/docmessages/docs/<wbr>etc&gt;<br>
-----&gt; &lt;module&gt;<br>
--------&gt; &lt;po files of all repository in the module&gt;<br>
<br>
where module is kdegraphics, extragear-multimedia, kde-workspace, frameworks, \
etc.<br> <br>
This structure comes from the times when the modules were the basic unit of work.<br>
Nowadays each program is more independent, and this structure does not allow<br>
to distinguish which translations belong to which repository (see the big<br>
bucket which is kde-workspace aka Plasma). Also it complicates a bit the<br>
maintenance when a repositories moves from one logical module to another.<br>
<br>
The advantage is that it provides some grouping that can help us to divide the<br>
work and prioritize it.<br>
<br>
Now, let&#39;s consider this structure instead:<br>
&lt;lang&gt;<br>
--&gt; &lt;messages/docmessages/docs/<wbr>etc&gt;<br>
-----&gt; &lt;repository name&gt;<br>
--------&gt; &lt;po files of the repository&gt;<br>
<br>
where repository is kconfig, okular, kile, etc<br>
<br>
The question is: would this structure be acceptable for you? Please consider<br>
the following answers, and it would be nice to have answers from a relevant<br>
group of languages :)<br>
<br>
a) I don&#39;t care, fine by me/my language team, I can get the logical module<br>
from sysadmin/repo-metadata.git;<br>
b) yes, but in our team we need to see some structure, like which set of<br>
repositories are shipped together, but if the website shows this it&#39;s fine;<br>
c) absolutely not, our team need the current structure because &lt;please write a<br>
reason&gt;;<br>
d) other (please write a reason);<br>
<br>
Now up to you!<br>
<br>
Ciao<br>
<span class="HOEnZb"><font color="#888888">--<br>
Luigi<br>
</font></span></blockquote></div><br></div>



[prev in list] [next in list] [prev in thread] [next in thread]