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

List:       kde-i18n-doc
Subject:    Re: Words list for GCompris
From:       Jeremy Whiting <jpwhiting () kde ! org>
Date:       2014-12-24 13:41:52
Message-ID: CADWV2K67qTyojHeG9-tn6MsegBu7KK9gGdCxXtLbLOFo-G0vUw () mail ! gmail ! com
[Download RAW message or body]

Bruno,

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

Hope that helps,
Jeremy

On Wed, Dec 24, 2014 at 4:54 AM, Bruno Coudoin <bruno.coudoin@gcompris.net>
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
>>> wiki
>>> 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/Localization/List_of_Non-PO_
>> Localizable_Resources
>>
>>  Hi,
>
> Thanks for the information, I have not realized this. If this is more
> practical for translators we can move the files and update our build chai=
n
> accordingly.
>
> While we are on it, we also have a large voice set that we have not yet
> migrated to kde svn but should be. Where would be the best place for it,
> this takes about 160MB.
>
> Bruno.
>
>

[Attachment #3 (text/html)]

<div dir="ltr">Bruno,<div><br></div><div>I highly suggest the svn location Alexander \
pointed out. That&#39;s where klettres keeps it&#39;s voice files for different \
languages and also where kanagram/khangman keep their word lists translated into \
different languages as well as non ascii letters khangman adds to the standard 26 \
letters in khangman specific language.txt files.</div><div><br></div><div>Hope that \
helps,</div><div>Jeremy</div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Wed, Dec 24, 2014 at 4:54 AM, Bruno Coudoin <span \
dir="ltr">&lt;<a href="mailto:bruno.coudoin@gcompris.net" \
target="_blank">bruno.coudoin@gcompris.net</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><br> Le 24/12/2014 12:05, Alexander Potashev a écrit \
:<div><div class="h5"><br> <blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> 2014-12-24 3:36 GMT+03:00 Bruno \
Coudoin &lt;<a href="mailto:bruno.coudoin@gcompris.net" \
target="_blank">bruno.coudoin@gcompris.net</a>&gt;:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> First step is to check if the files are already present for \
your locale<br> with:<br>
ls src/activities/*/resource/<u></u>default-&lt;you locale code&gt;.json<br>
<br>
If you have 2 files your are done. If not, read the instructions on our wiki<br>
to create them:<br>
<a href="http://gcompris.net/wiki/Word_Lists_Qt" \
target="_blank">http://gcompris.net/wiki/Word_<u></u>Lists_Qt</a><br> </blockquote>
Hi Bruno,<br>
<br>
In the KDE 3 and KDE 4 ages, non-PO localizable data used to be<br>
submitted by translators to l10n-kde4/[langcode]/data/ and then added<br>
to the respective tarballs. See [1]. In this way the resources you<br>
mention will be easier to find and localize by our language teams.<br>
<br>
I understand you are new to KDE l10n infrastructure, that is why I<br>
would expect some feedback on this idea from the experts - Burkhard,<br>
Yuri and/or Albert :)<br>
<br>
[1] <a href="https://techbase.kde.org/Localization/List_of_Non-PO_Localizable_Resources" \
target="_blank">https://techbase.kde.org/<u></u>Localization/List_of_Non-PO_<u></u>Localizable_Resources</a><br>
 <br>
</blockquote></div></div>
Hi,<br>
<br>
Thanks for the information, I have not realized this. If this is more practical for \
translators we can move the files and update our build chain accordingly.<br> <br>
While we are on it, we also have a large voice set that we have not yet migrated to \
kde svn but should be. Where would be the best place for it, this takes about \
160MB.<span class="HOEnZb"><font color="#888888"><br> <br>
Bruno.<br>
<br>
</font></span></blockquote></div><br></div>



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