[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: Re: Translating docs.krita.org
From: guru guru <guruguru.sp () outlook ! jp>
Date: 2019-01-08 11:52:43
Message-ID: SL2P216MB1001AC99111E33D8F15291F4E48A0 () SL2P216MB1001 ! KORP216 ! PROD ! OUTLOOK ! COM
[Download RAW message or body]
Hi Boud,
My two cents...
If possible I think a website frontend solution would be better - it would =
be more accessible to new translators, I hope.
* put a convenient website such as weblate (https://weblate.org) on top, so
translations can be done in their browser.
Well, the current situation for Japanese is:
I have not seen Tokiedian, the other Japanese contributor for 1+ year(he wa=
s
the one who worked on application, he did website translations, too).
I myself do not have a contact with KDE JP user group at all. (it's mailing=
list and page seem mostly inactive)
I've been really busy lately. I can still work on occasional release announ=
ements(with reduced scope, without full bug fix list translation...),
but I doubt I can tackle on full manual translation right now.
So, if there would be a translation frontend website, and if I can welcome =
new translators there,
probably that can bring... some more hope for Japanese.(I know translator v=
olunteers are kinda rare, though)
That's my current thought, and sorry for not being able to help much,
guruguru
________________________________
From: kimageshop <kimageshop-bounces@kde.org> on behalf of Boudewijn Rempt =
<boud@valdyas.org>
Sent: Monday, January 7, 2019 2:08 PM
To: kimageshop@kde.org
Subject: Translating docs.krita.org
We've had this discussion on translating the manual for quite some time no=
w,
without an effective solution.
The KDE system for working with translations is based on subversion. There =
are
shell scripts that call shell scripts in the git repositories, generate pot
files, submit those to subversion, where teams can start translating them.
There is no provision, other than the release scripts for pulling the
translations back into the git repository.
For the docs.krita.org site we need to have the pot files inside the git
repository, so would make sense to skip the whole subversion step. That bre=
aks
the workflow of the KDE translators, though that workflow is already broken
for wiki sites and wordpress sites, so the question is, how much of a probl=
em
would this be?
We have two options:
* let translators just clone the docs-krita-org repo and make them create
review requests through phabricator.
* put a convenient website such as weblate (https://weblate.org) on top, so
translations can be done in their browser.
Note: we also regularly get questions from people who want to translate Kri=
ta
itself, and who find the current KDE system unworkable.
--
https://www.valdyas.org | https://www.krita.org
[Attachment #3 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} \
</style> </head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> Hi Boud,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> <br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> My two cents...</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> <br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> If possible I think a website frontend solution would be better - it \
would be more accessible to new translators, I hope.</div> <div style="font-family: \
Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <font \
size="2"><span style="font-size:11pt">* put a convenient website such as weblate (<a \
href="https://weblate.org" target="_blank" rel="noopener \
noreferrer">https://weblate.org</a>) on top, so <br>
translations can be done in their browser.</span></font><br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> <br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> Well, the current situation for Japanese is:</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> I have not seen Tokiedian, the other Japanese contributor for 1+ \
year(he was <br> </div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> the one who worked on application, he did website translations, \
too).</div> <div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; \
color: rgb(0, 0, 0);"> I myself do not have a contact with KDE JP user group at all. \
(it's mailing list and page seem mostly inactive)<br> </div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> <br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> I've been really busy lately. I can still work on occasional release \
announements(with reduced scope, without full bug fix list translation...), <br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> but I doubt I can tackle on full manual translation right now. <br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> <br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> So, if there would be a translation frontend website, and if I can \
welcome new translators there, <br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> probably that can bring... some more hope for Japanese.(I know \
translator volunteers are kinda rare, though)<br> </div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> <br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> That's my current thought, and sorry for not being able to help \
much,</div> <div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; \
color: rgb(0, 0, 0);"> <br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: \
rgb(0, 0, 0);"> guruguru<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" \
style="font-size:11pt" color="#000000"><b>From:</b> kimageshop \
<kimageshop-bounces@kde.org> on behalf of Boudewijn Rempt \
<boud@valdyas.org><br> <b>Sent:</b> Monday, January 7, 2019 2:08 PM<br>
<b>To:</b> kimageshop@kde.org<br>
<b>Subject:</b> Translating docs.krita.org</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">We've had this discussion on translating the manual for \
quite some time now, <br>
without an effective solution. <br>
<br>
The KDE system for working with translations is based on subversion. There are <br>
shell scripts that call shell scripts in the git repositories, generate pot <br>
files, submit those to subversion, where teams can start translating them. <br>
There is no provision, other than the release scripts for pulling the <br>
translations back into the git repository.<br>
<br>
For the docs.krita.org site we need to have the pot files inside the git <br>
repository, so would make sense to skip the whole subversion step. That breaks <br>
the workflow of the KDE translators, though that workflow is already broken <br>
for wiki sites and wordpress sites, so the question is, how much of a problem <br>
would this be?<br>
<br>
We have two options:<br>
<br>
* let translators just clone the docs-krita-org repo and make them create <br>
review requests through phabricator.<br>
* put a convenient website such as weblate (<a \
href="https://weblate.org">https://weblate.org</a>) on top, so <br>
translations can be done in their browser.<br>
<br>
Note: we also regularly get questions from people who want to translate Krita <br>
itself, and who find the current KDE system unworkable. <br>
<br>
-- <br>
<a href="https://www.valdyas.org">https://www.valdyas.org</a> | <a \
href="https://www.krita.org"> https://www.krita.org</a><br>
<br>
<br>
</div>
</span></font></div>
</body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic