kicad-doc-devs team mailing list archive
-
kicad-doc-devs team
-
Mailing list archive
-
Message #00008
Re: Translation workflow, switch to central generated POT files?
Remember that the update-po-files.sh script has an option to not
delete the POT file.
I am not too concerned on what way you want to do it. I would just
like to make it easy for the translators. If it takes that the POT
file is always up to date, we can start doing that.
2016-08-25 7:25 GMT+02:00 Carsten Schoenert <c.schoenert@xxxxxxxxxxx>:
> Hi Kinichiro,
>
> Am 25.08.2016 um 05:39 schrieb kinichiro inoguchi:
>> Or someone needs to update POT file by hand in appropriate timing.
>
> this depends how someone is "automatic" define. ;)
>
>> Automatic POT update seems good though, there is a issue that how to
>> reflect that change to the repo.
>> Do you mean that the git-hook post the commit to update POT file in the
>> repo directly ?
>> I feel hesitation for automatic commit ;-)
>
> Yes, I'm also very conservative in such automatism. So in the end the
> first decision would be to do such a post-commit hook or not. Obviously not.
>
> So how to automate such thinks?
> If you want to automate something you will need a post-commit hook. So I
> would create a script that will be called automatically and do the
> update of a POT file, but the final commit has to be done by myself. I
> have to check the changes an if there are no i18n related changes than
> there is no commit for kicad-i18n needed.
>
> --
> Regards
> Carsten Schoenert
>
> --
> Mailing list: https://launchpad.net/~kicad-doc-devs
> Post to : kicad-doc-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-doc-devs
> More help : https://help.launchpad.net/ListHelp
Follow ups
References