[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 15:01:40
Message-ID: 2d3489a280aa49937c0282b105ce0cd9 () localhost ! localdomain
[Download RAW message or body]
[Attachment #2 (text/plain)]
clel added a comment.
In T13514#237910 <https://phabricator.kde.org/T13514#237910>, @yurchor wrote:
> In T13514#237909 <https://phabricator.kde.org/T13514#237909>, @clel wrote:
>
> > Alright. Then I don't really understand what problems you have with Weblate. \
The things you wrote are too general for me to understand what the concrete problems \
are that you experience. >
>
> Sure. Just one thing that I do not understand is that people who do not really \
understand how the translation system works eagerly want to change that system.
When you write "Sure", I expect some more insights :) You wrote about problems you \
had but did not really give much detail about them. You talk about Weblate being much \
slower than offline tools while not mentioning which parts of the workflow you are \
talking about (admin stuff, translation itself, downloading and uploading PO files?). \
What leads to the merge conflicts? Uploading PO files while the same lines have been \
changed through the online interface? You wrote you would have to work with KDE \
translations "through a web interface". What tasks are you referring to when you say \
"work"? Translation itself apparently not, since you say you are aware that you can \
download and upload PO files. So what is taking so long there? You mention uploading \
translations takes "~15 minutes a day", can you give some details? Are we talking \
about some maintenance stuff or actually contributions to translations? Why do you \
imply that translations themselves are slower with Weblate?
This were some of the questions coming to my mind when I tried to understand which \
problems you face with Weblate. I wrote them down explicitly now, so you hopefully \
can understand better what has been unclear to me.
Regarding your question, which I felt was a bit insulting and implying things that \
are not true: There has been a long discussion already that contribution to \
translations should be made easier, possibly by a web-based system like Weblate. This \
task however is not about that. My question here mainly was why one central \
repository for all translations is needed instead of for example hosting them \
together in each project's repository. Currently I have not really seen a reason why \
that would cause a problem, but knowing that I don't know how the entire system is \
setup, I of course think there might be reasons why that is not a good idea. That is \
why I asked for such reasons.
I prefer to have those discussions factual and hopefully leading to an increase of \
available information to make better decisions.
In T13514#237911 <https://phabricator.kde.org/T13514#237911>, @woltherav wrote:
> Because they want to change it into something they might have an actual chance of \
understanding?
Speaking for me, I don't "want to change it", I just want to elaborate possible \
improvements. I guess the benefits of storing PO files in each project's repository \
are clear (but I am willing to enumerate them again). What is not so clear (at least \
to me) are the possible disadvantages or blockers of that concept.
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#237910" style="background-color: #e7e7e7; \
border-color: #e7e7e7; border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">T13514#237910</a>, <a \
href="https://phabricator.kde.org/p/yurchor/" style=" border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@yurchor</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><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#237909" style="background-color: #e7e7e7; \
border-color: #e7e7e7; border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">T13514#237909</a>, <a \
href="https://phabricator.kde.org/p/clel/" style=" border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@clel</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>Alright. Then I don't really understand \
what problems you have with Weblate. The things you wrote are too general for me to \
understand what the concrete problems are that you experience.</p></div> \
</blockquote>
<p>Sure. Just one thing that I do not understand is that people who do not really \
understand how the translation system works eagerly want to change that \
system.</p></div> </blockquote>
<p>When you write "Sure", I expect some more insights :) You wrote about \
problems you had but did not really give much detail about them. You talk about \
Weblate being much slower than offline tools while not mentioning which parts of the \
workflow you are talking about (admin stuff, translation itself, downloading and \
uploading PO files?). What leads to the merge conflicts? Uploading PO files while the \
same lines have been changed through the online interface? You wrote you would have \
to work with KDE translations "through a web interface". What tasks are you \
referring to when you say "work"? Translation itself apparently not, since \
you say you are aware that you can download and upload PO files. So what is taking so \
long there? You mention uploading translations takes "~15 minutes a day", \
can you give some details? Are we talking about some maintenance stuff or actually \
contributions to translations? Why do you imply that translations themselves are \
slower with Weblate?</p>
<p>This were some of the questions coming to my mind when I tried to understand which \
problems you face with Weblate. I wrote them down explicitly now, so you hopefully \
can understand better what has been unclear to me.</p>
<p>Regarding your question, which I felt was a bit insulting and implying things that \
are not true: There has been a long discussion already that contribution to \
translations should be made easier, possibly by a web-based system like Weblate. This \
task however is not about that. My question here mainly was why one central \
repository for all translations is needed instead of for example hosting them \
together in each project's repository. Currently I have not really seen a reason \
why that would cause a problem, but knowing that I don't know how the entire \
system is setup, I of course think there might be reasons why that is not a good \
idea. That is why I asked for such reasons.</p>
<p>I prefer to have those discussions factual and hopefully leading to an increase of \
available information to make better decisions.</p>
<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#237911" style="background-color: #e7e7e7; \
border-color: #e7e7e7; border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">T13514#237911</a>, <a \
href="https://phabricator.kde.org/p/woltherav/" style=" border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@woltherav</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>Because they want to change it into \
something they might have an actual chance of understanding?</p></div> </blockquote>
<p>Speaking for me, I don't "want to change it", I just want to \
elaborate possible improvements. I guess the benefits of storing PO files in each \
project's repository are clear (but I am willing to enumerate them again). What \
is not so clear (at least to me) are the possible disadvantages or blockers of that \
concept.</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