[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: T13514: Migrate KDE translations to Git
From: Claudius Ellsel <noreply () phabricator ! kde ! org>
Date: 2020-08-22 16:41:54
Message-ID: 8f56f36adb547d9e7929782ab8384411 () localhost ! localdomain
[Download RAW message or body]
[Attachment #2 (text/plain)]
clel added a comment.
In T13514#237941 <https://phabricator.kde.org/T13514#237941>, @ltoscano wrote:
> I already wrote it: a central place is needed so that
Thanks for those points. As I said, if you already wrote that, I'd also been happy \
with just a link to that.
> - people *NOT* using weblate don't have to checkout tons of repositories to \
contribute. That's enough in itself.
I guess I wasn't aware of this workflow. So people basically checkout the \
repository currently and then go around different projects offline to then translate? \
I understand that this is more efficient when doing alot of translation work across \
several projects. I have been thinking from my perspective where I'd look for a \
project first and then download maybe the PO file to complete the translation and \
upload it again (without ever checking out any repository) and then uploading it \
through a webinterface or directly using that webinterface to translate a project \
through the browser.
> - we may use posummit even with weblate to provide a single branch to everyone, \
which means that some logic to inject the translations to each branch will be needed \
somewhere else
This might become a valid reason, however I think currently this is not really a \
blocker.
> - it will be the only interface that weblate would have to deal with (because in \
5 years we may change again tool, and we don't lose the history)
Somewhat valid. But note that also having the projects store the translation files \
there will be an interface. Just spread across a large number of projects. In fact, I \
guess this interface to the projects is also there today, but in a different way, \
since it is needed to sync them with the translations repository.
> - even in the case were part of the web tool would be the central place, still \
that would be the reference point, not the content of each repository which would be \
a mirror once we solve T12268 <https://phabricator.kde.org/T12268>.
The task you linked seems to be wrong. That makes it hard for me to understand what \
you are saying here.
TASK DETAIL
https://phabricator.kde.org/T13514
To: clel
Cc: yurchor, zerg, clel, xyquadrat, woltherav, subins2000, huftis, rempt, \
kamathraghavendra, thiagosueto, #localization, dkazakov, nalvarez, aacid, pino, \
ltoscano, aspotashev, fbampaloukas, sdepiets, skadinna, pshinjo
[Attachment #3 (text/html)]
<table><tr><td style="">clel added a comment.
</td></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a \
href="https://phabricator.kde.org/T13514#237941" style="background-color: #e7e7e7; \
border-color: #e7e7e7; border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">T13514#237941</a>, <a \
href="https://phabricator.kde.org/p/ltoscano/" style=" border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@ltoscano</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>I already wrote it: a central place is \
needed so that</p></div> </blockquote>
<p>Thanks for those points. As I said, if you already wrote that, I'd also been \
happy with just a link to that.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: \
italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><ul \
class="remarkup-list"> <li class="remarkup-list-item">people *NOT* using weblate \
don't have to checkout tons of repositories to contribute. That's enough in \
itself.</li> </ul></blockquote>
<p>I guess I wasn't aware of this workflow. So people basically checkout the \
repository currently and then go around different projects offline to then translate? \
I understand that this is more efficient when doing alot of translation work across \
several projects. I have been thinking from my perspective where I'd look for a \
project first and then download maybe the PO file to complete the translation and \
upload it again (without ever checking out any repository) and then uploading it \
through a webinterface or directly using that webinterface to translate a project \
through the browser.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: \
italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><ul \
class="remarkup-list"> <li class="remarkup-list-item">we may use posummit even with \
weblate to provide a single branch to everyone, which means that some logic to inject \
the translations to each branch will be needed somewhere else</li> </ul></blockquote>
<p>This might become a valid reason, however I think currently this is not really a \
blocker.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: \
italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><ul \
class="remarkup-list"> <li class="remarkup-list-item">it will be the only interface \
that weblate would have to deal with (because in 5 years we may change again tool, \
and we don't lose the history)</li> </ul></blockquote>
<p>Somewhat valid. But note that also having the projects store the translation files \
there will be an interface. Just spread across a large number of projects. In fact, I \
guess this interface to the projects is also there today, but in a different way, \
since it is needed to sync them with the translations repository.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: \
italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><ul \
class="remarkup-list"> <li class="remarkup-list-item">even in the case were part of \
the web tool would be the central place, still that would be the reference point, not \
the content of each repository which would be a mirror once we solve <a \
href="https://phabricator.kde.org/T12268" style="background-color: #e7e7e7; \
border-color: #e7e7e7; border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: line-through;">T12268</a>.</li>
</ul></blockquote>
<p>The task you linked seems to be wrong. That makes it hard for me to understand \
what you are saying here.</p></div></div><br /><div><strong>TASK \
DETAIL</strong><div><a \
href="https://phabricator.kde.org/T13514">https://phabricator.kde.org/T13514</a></div></div><br \
/><div><strong>To: </strong>clel<br /><strong>Cc: </strong>yurchor, zerg, clel, \
xyquadrat, woltherav, subins2000, huftis, rempt, kamathraghavendra, thiagosueto, \
Localization, dkazakov, nalvarez, aacid, pino, ltoscano, aspotashev, fbampaloukas, \
sdepiets, skadinna, pshinjo<br /></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic