D17739: Add a po file for the list of words in GCompris

Karl Ove Hufthammer noreply at phabricator.kde.org
Sat Jan 12 14:27:36 GMT 2019

huftis requested changes to this revision.
huftis added a comment.
This revision now requires changes to proceed.

  Yes, it is **very** useful to have it in the PO format instead of the JSON format.
  The information seems sufficient. But could you split it over two lines instead, and add space after colon? I recommend:
  #. Description: "alphabet"
  #. Image: https://www.gcompris.net/incoming/lang/lang/words/alphabet.png
  (Lokalize currently displays the two lines as a single-line string, but that’s a bug (and it’s not a big problem here): https://bugs.kde.org/show_bug.cgi?id=403142)
  It’s not clear what the strings will be used for. Will the text be used even if there isn’t an audio file in the given language?
  And if so, shouldn’t it be taken from `content-en.json` (if not empty) instead of from the file name (e.g. "seven" instead of U0037)? And if the English string in ‘content-en.json’ is missing, at least the underscore in the filename should be converted to a space (e.g. ‘air_horn’ → ‘air horn’).

  R2 GCompris


To: jjazeix, #gcompris, #localization, huftis
Cc: huftis, aacid, kde-edu, harrymecwan, ganeshredcobra, nityanandkumar, echarruau, rahulyadav, narvaez, scagarwal, apol, timotheegiet, hkaelberer, jjazeix, bcoudoin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-edu/attachments/20190112/e7b4f2ce/attachment.html>

More information about the kde-edu mailing list