kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #26113
Re: translation code rework
On 9/7/2016 2:27 PM, Nick Østergaard wrote:
> 2016-03-12 1:37 GMT+01:00 Simon Wells <swel024@xxxxxxxxx>:
>> As part of the translation code rework that i am working on (and
>> auto-detection) part of it is moving the need for changing anything in
>> code to add a new language. As part of this involves the flags i was
>> wondering whether anyone would be against moving them into the i18n
>> repo (and distributed in the individual language folders, so that if
>> kicad is compiled with having icons enabled in the menu they could
>> still be used but they will be pulled at runtime so no addtional code
>> nor icons required in the kicad tree
>>
>
> This discussion seem to be related to the other thread:
> https://www.mail-archive.com/kicad-developers@xxxxxxxxxxxxxxxxxxx/msg17648.html
>
> It does not seem anyone is directly against removing the flags all together.
As I stated in the previous thread I'm OK with removing the flags. I'm
just concerned about what text we will use in the language menu.
Translated, English, always the current locale, or something else? I
still haven't seen a good solution to that issue.
>
> I like the idea of validating the available languages runtime as
> mentioned in the related thread.
Makes sense to me. I see no reason to add entries in the language menu
for translations that are not available.
>
>> Something unrelated to the flags but similar is do we need the
>> translations tab with all the translators in the about box? or would a
>> better place be in the i18n repo on github and linked from the website
>> and only the current translation information provided in the about
>> dialog. This can be pulled at runtime from the po files using the
>> Language-Team header in the po file. There are a few ways this could
>> be left how it is, including having a list of all INSTALLED
>> translations in the translations tab instead of only showing current,
>> would just require the program at startup processing all the language
>> files to get the header information.
>>
>> for example the one in the ru po file is
>> "Language-Team: Russian KiCad Translation Team: Andrey Fedorushkov, Eldar "
>> "Khayrullin, Igor Plyatov <andrf@xxxxxxx>\n"
>>
>> As i only know english i haven't had the oppurtunity to use the po
>> utility but i have been advised this is a setting rather than just
>> something that is edited manually
>>
>> the one in the fr po file is
>> "Language-Team: jp-charras\n"
>>
>> which if this idea is implemented jp might need to change his to be a
>> bit more informative, (at least being his full name or something)
>>
>> I think i have mentioned before about making the language list in
>> preferences reliant on whether the i18n files have been installed so
>> that people don't get caught up with wondering why no other languages
>> work.
>>
>
> Lets assume that all contributors have "proper" names here.
>
> What will happen with translators which work might not even be present
> anymore, how are we supposed to detect that? Or are we just going to
> count all contributors from epoch?
>
>> Mainly i am looking for arguments against moving the flags into the
>> i18n repo as that may prove that most of my code is not possible.
>> seeing as some people seem to be against just ditching the flags
>>
>
> Remove the flags. :P
>
> I don't know if the languages maybe sould be written in their
> localized form, maybe?
>
>> thanks
>>
>> Simon
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References