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

List:       kde-i18n-doc
Subject:    Re: GCompris on its way to a public release
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2014-11-19 22:03:37
Message-ID: 5156975.JcEk40lLLX () xps
[Download RAW message or body]

El Dimecres, 19 de novembre de 2014, a les 22:56:02, Bruno Coudoin va 
escriure:
> Le 19/11/2014 22:38, Albert Astals Cid a écrit :
> > El Dimecres, 19 de novembre de 2014, a les 01:30:23, Bruno Coudoin va
> > 
> > escriure:
> >> Le 18/11/2014 12:43, Burkhard Lück a écrit :
> >>> What about http://gcompris.net/wiki/Translation_addons and
> >>> http://gcompris.net/wiki/Word_Lists ?
> >>> 
> >>> The Legacy Gtk+ Version had some resources in xml files to translate, e.
> >>> g.
> >>> wordsgame.xml, gletters.xml, readingv.xml and hangman.xml
> >>> 
> >>> In the new gcompris this seems to be done via json files, e. g.
> >>> activities/gletters/resource/default-[lang].json
> >>> 
> >>> Do we need to integrate the translations of these resources into
> >>> scripty?
> >> 
> >> Hi,
> >> 
> >> Yes, I have not yet mentioned about that but this is the right time to
> >> talk about it.
> >> 
> >> Beside the regular po file we have dataset files for several activities
> >> that have are localized instead of translated. As you mentionned it,
> >> these files have been translated from xml to json file during the port.
> > 
> > How do you see the translation of those datasets happening? I.e. do you
> > want
> > 
> > a) The translation is in the json
> > b) The translation is in the .po file
> > 
> > b) is certainly easier, since you just need to extract the text from the
> > .json to a dummy cpp in Messages.sh time and then just call
> > i18n(theTextInEnglishFromTheJson) and everything works.
> 
> Hi,
> 
> It is a deliberate choice to not put these strings in po files.
> 
> The concept is that the content of these files must be authored for each
> language and not translated. For example a list of 3 letters words for a
> language will contain different words in another language.

You can still use a .po file for that given proper context and a translator 
that reads the context :D

If you don't want to use the .po file there's the question, do you want to put 
the "german 3 letter words" in the same json as the "english 3 letter words"?

Cheers,
  Albert

> 
> Bruno.

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