kicad-doc-devs team mailing list archive

[Nick Østergaard <oe.nick@xxxxxxxxx>]

I assume he made the change locally before the git transition.

2016-08-25 15:20 GMT+02:00 starfort <starfort@xxxxxxxxx>:
> jp-charras committed yesterday on KiCad/kicad-i18n.
> https://github.com/KiCad/kicad-i18n/commits/master
>
>
>> -----Original Message-----
>> From: Nick Østergaard [mailto:oe.nick@xxxxxxxxx]
>> Sent: Thursday, August 25, 2016 10:15 PM
>> To: starfort <starfort@xxxxxxxxx>
>> Cc: kinichiro inoguchi <kinichiro.inoguchi@xxxxxxxxx>; Carsten Schoenert
>> <c.schoenert@xxxxxxxxxxx>; kicad-doc-devs@xxxxxxxxxxxxxxxxxxx; Melroy
>> van den Berg <webmaster1989@xxxxxxxxx>
>> Subject: Re: [Kicad-doc-devs] Translation workflow, switch to central
>> generated POT files?
>>
>> Where do you see BZR 7089?
>>
>> 2016-08-25 12:39 GMT+02:00 starfort <starfort@xxxxxxxxx>:
>> > Hi Nick,
>> > Thank you for your reply. It sounds good to me.
>> >
>> > I have one question.
>> > How can I identify the revision? Only hash or date? I wonder where BZR
>> 7089 comes from...
>> >
>> > Thanks and best regards,
>> >
>> > starfort-jp
>> >
>> >
>> >> From: Nick Østergaard [mailto:oe.nick@xxxxxxxxx]
>> >> Sent: Thursday, August 25, 2016 7:14 PM
>> >> To: starfort <starfort@xxxxxxxxx>
>> >> Cc: kinichiro inoguchi <kinichiro.inoguchi@xxxxxxxxx>; Carsten
>> >> Schoenert <c.schoenert@xxxxxxxxxxx>;
>> >> kicad-doc-devs@xxxxxxxxxxxxxxxxxxx; Melroy van den Berg
>> >> <webmaster1989@xxxxxxxxx>
>> >> Subject: RE: [Kicad-doc-devs] Translation workflow, switch to central
>> generated POT files?
>> >>
>> >> Maybe we should just auto update it on the stable branch against the
>> stable branch. And if people want > to keep translations on master in sync,
>> maybe they can commit it if they so desire?
>> >>
>> >> Den 25/08/2016 12.11 skrev "starfort" <starfort@xxxxxxxxx>:
>> >> Hi all,
>> >>
>> >> I reckon if "someone" always updates the POT file whenever
>> >> programmers update source code on dev, it's > too frequent. What do you
>> think about an interval and identifying the revision? I don't want to be
>> flung into confusion.
>> >> On the other hand, I really appreciate the POT file on every release.
>> >>
>> >> With kind regards.
>> >>
>> >> starfort-jp
>> >>
>> >>
>> >>> From: kinichiro inoguchi [mailto:kinichiro.inoguchi@xxxxxxxxx]
>> >>> Sent: Thursday, August 25, 2016 4:30 PM
>> >>> To: Nick Østergaard <oe.nick@xxxxxxxxx>
>> >>> Cc: starfort > <starfort@xxxxxxxxx>; Carsten Schoenert
>> >>> <c.schoenert@xxxxxxxxxxx>; Melroy van den Berg
>> >>> <webmaster1989@xxxxxxxxx>; kicad-doc-devs@xxxxxxxxxxxxxxxxxxx
>> >>> Subject: Re: [Kicad-doc-devs] Translation workflow, switch to central
>> generated POT files?
>> >>>
>> >>> Hi,
>> >>> Carsten,
>> >>> thanks for clarification and I also think about "who does that".
>> >>> Now, I am thinking of new GUI translation processes like below; 1.
>> >>> programmers update source code  on dev or 4.0 branches on LP.
>> >>> 2.
>> >>> "someone" let the script to run to update POT file and check if it
>> >>> updated or not, and commit it to the  kicad-i18n repo on GitHub.
>> >>> 3.
>> >>> translators pull from kicad-i18n on GitHub, refresh PO file of their
>> >>> language by POT file, translate PO and post PR to kicad-i18n on
>> >>> GitHub.
>> >>> POT should be managed at kicad-i18n in this processes since it is a
>> source code of GUI, I think.
>> >>> I need to think more of "someone".
>> >>> Nick,
>> >>> thanks for heads up for update_po_files.sh on kicad-i18n.
>> >>> I also wanted to ease the translators job.
>> >>> Best regards,
>> >>> Kinichiro
>> >
>