kicad-doc-devs team mailing list archive

[kinichiro inoguchi <kinichiro.inoguchi@xxxxxxxxx>]

Nick,

>I don't consider the actions needed for the GUI i18n any different

I thought about using .pot file for GUI i18n to translators can to their work
without accessing source code.
In future, I would like to talk about this as an another topic.

>The announcement about 4.0.5 was made a month ago in the 7th of
>November [1],

Yes, you are right, and this was my mistake.
Also, we might not need to urgent update for python sample this time.

>Also remember, none of
>us are paid or signed a contract, so none of us can guarantee
>anything, but can try to do a best effort and help each other reach a
>common goal, that is improve KiCad, respect each other, and be proud
>of it. :)

Sure it is :-)


Marco,

>Yes especially the pcbnew and eeschema manuals are HUGE!

The manuals that have several .adoc tend to generate HUGE diffs.
I wonder if this might be caused by cmake updatepo logic.
Old Makefile and New cmake bring different .adoc file order.
I havn't tested yet, though, numbering .adoc could solve these kind of trouble.
(e.g. pcbnew_01_intro.adoc, pcbnew_02_install, ... like that)

And thanks a lot for maintaining these, and sorry for you left alone :-)

>The thing is: if some translators have some work uncommitted, updating
>even just the python scripts strings (that are normal translatable
>strings) generate a conflict. So really that freeze period is necessary
>>and it was violated by this issue. To avoid this we should ask all
>translators to commit every uncommitted changes they may still have, wait
>for all active translators to respond, update  the doc source and _then_
>declare a new freeze period.

Absolutely +1


Wayne,

>Week 1: Last call for documentation and UI string changes.
>Week 2: Freeze documentation and UI strings to allow two weeks for
>        translations to catch up.
>Week 5: Translation freeze and tag to begin packaging.

Yes, it is good.
All developers, writers, translators and packagers are the one KiCad team.
I always would like to think about whole process and every person.


Best regards,

Kinichiro