Bruno,

I highly suggest the svn locatio= n Alexander pointed out. That's where klettres keeps it's voice fil= es for different languages and also where kanagram/khangman keep their word= lists translated into different languages as well as non ascii letters kha= ngman adds to the standard 26 letters in khangman specific language.txt fil= es.

Hope that helps,

Jeremy

On Wed, Dec 24, 20= 14 at 4:54 AM, Bruno Coudoin <bruno.coudoin@gcompris.net><= /span> wrote:

Le 24/12/2014 12:05, Alexander Potashev a =C3=A9crit :

2014-12-24 3:36 GMT+03:00 Bruno Coudoin <bruno.coudoin@gcompris.net>:

First step is to check if the files are already present for your locale
with:
ls src/activities/*/resource/default-<you locale code>.json
If you have 2 files your are done. If not, read the instructions on our wik= i
to create them:
http:/= /gcompris.net/wiki/Word_Lists_Qt

Hi Bruno,

In the KDE 3 and KDE 4 ages, non-PO localizable data used to be
submitted by translators to l10n-kde4/[langcode]/data/ and then added
to the respective tarballs. See [1]. In this way the resources you
mention will be easier to find and localize by our language teams.

I understand you are new to KDE l10n infrastructure, that is why I
would expect some feedback on this idea from the experts - Burkhard,
Yuri and/or Albert :)

[1] https://techbase.kde.org/Localizat= ion/List_of_Non-PO_Localizable_Resources

Hi,

Thanks for the information, I have not realized this. If this is more pract= ical for translators we can move the files and update our build chain accor= dingly.

While we are on it, we also have a large voice set that we have not yet mig= rated to kde svn but should be. Where would be the best place for it, this = takes about 160MB.

Bruno.