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

List:       kde-i18n-doc
Subject:    D17739: Add a po file for the list of words in GCompris
From:       Johnny Jazeix <noreply () phabricator ! kde ! org>
Date:       2018-12-22 17:25:26
Message-ID: b754628330147217179671ccca54c55f () localhost ! localdomain
[Download RAW message or body]

[Attachment #2 (text/plain)]

jjazeix created this revision.
jjazeix added reviewers: GCompris, Localization.
jjazeix added a project: GCompris.
Herald added a project: KDE Edu.
Herald added a subscriber: kde-edu.
jjazeix requested review of this revision.

REVISION SUMMARY
  The aim of this diff would be to add a po containing all the words to be translated in the lang \
activity (https://gcompris.net/incoming/lang/words.json) to ease the work for the translators.  
  Multiple questions:
  
  1. Is it useful for translators to have it in a po format (in KDE translation repository) instead of a \
json file (which is only in GCompris repository)?  2. Which information would be needed to have in the \
translator comments? The images given in comment should help to understand the context, not sure if more \
is needed.  3. I'm really not used to awk, maybe there is some cleaner way to write what I did if someone \
is interested :).

TEST PLAN
  The first idea is to fill the existing po with the words in locales already available (those in \
https://cgit.kde.org/gcompris.git/tree/src/activities/lang/resource) to not lose the existing work or \
duplicate the translators work.  
  Then, once the po files are ok, when there are updates, synchronize the po files with the json files \
(so translators would only need to update the po files, no more updating manually the json files).

REPOSITORY
  R2 GCompris

REVISION DETAIL
  https://phabricator.kde.org/D17739

AFFECTED FILES
  src/Messages.sh

To: jjazeix, #gcompris, #localization
Cc: kde-edu, harrymecwan, ganeshredcobra, nityanandkumar, echarruau, rahulyadav, narvaez, scagarwal, \
apol, timotheegiet, hkaelberer, jjazeix, bcoudoin


[Attachment #3 (text/html)]

<table><tr><td style="">jjazeix created this revision.<br />jjazeix added reviewers: GCompris, \
Localization.<br />jjazeix added a project: GCompris.<br />Herald added a project: KDE Edu.<br />Herald \
added a subscriber: kde-edu.<br />jjazeix requested review of this revision. </td><a \
style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; \
font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to \
bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" \
href="https://phabricator.kde.org/D17739">View Revision</a></tr></table><br /><div><strong>REVISION \
SUMMARY</strong><div><p>The aim of this diff would be to add a po containing all the words to be \
translated in the lang activity (<a href="https://gcompris.net/incoming/lang/words.json" \
class="remarkup-link" target="_blank" rel="noreferrer">https://gcompris.net/incoming/lang/words.json</a>) \
to ease the work for the translators.</p>

<p>Multiple questions:</p>

<ol class="remarkup-list">
<li class="remarkup-list-item">Is it useful for translators to have it in a po format (in KDE translation \
repository) instead of a json file (which is only in GCompris repository)?</li> <li \
class="remarkup-list-item">Which information would be needed to have in the translator comments? The \
images given in comment should help to understand the context, not sure if more is needed.</li> <li \
class="remarkup-list-item">I&#039;m really not used to awk, maybe there is some cleaner way to write what \
I did if someone is interested :).</li> </ol></div></div><br /><div><strong>TEST PLAN</strong><div><p>The \
first idea is to fill the existing po with the words in locales already available (those in <a \
href="https://cgit.kde.org/gcompris.git/tree/src/activities/lang/resource" class="remarkup-link" \
target="_blank" rel="noreferrer">https://cgit.kde.org/gcompris.git/tree/src/activities/lang/resource</a>) \
to not lose the existing work or duplicate the translators work.</p>

<p>Then, once the po files are ok, when there are updates, synchronize the po files with the json files \
(so translators would only need to update the po files, no more updating manually the json \
files).</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R2 GCompris</div></div></div><br \
/><div><strong>REVISION DETAIL</strong><div><a \
href="https://phabricator.kde.org/D17739">https://phabricator.kde.org/D17739</a></div></div><br \
/><div><strong>AFFECTED FILES</strong><div><div>src/Messages.sh</div></div></div><br /><div><strong>To: \
</strong>jjazeix, GCompris, Localization<br /><strong>Cc: </strong>kde-edu, harrymecwan, ganeshredcobra, \
nityanandkumar, echarruau, rahulyadav, narvaez, scagarwal, apol, timotheegiet, hkaelberer, jjazeix, \
bcoudoin<br /></div>



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