On 5/27/09 11:11 AM, "John Mandereau" <john.mander...@gmail.com> wrote:
> Carl D. Sorensen a écrit :
>> Mark,
>>
>> I appreciate your good work on these patches.
>>
>
> So do I :-)
>
>
>> 2) I'm not sure how to handle patches to translated documents. I know that
>> the translations need to follow a particular commit of the english docs. If
>> the change in the translated documents reflects a change in the english
>> documents, the committish needs to change in the source file, I think. I'm
>> not sure exactly how to evaluate the changes you've proposed, and what the
>> proper means of handling them is. Translators, please speak up here. Note
>> that if we had separate commits for each language, it would be easier for a
>> translator to review.
>>
>
> There is a specific policy on po/ (not Documentation/po), explained in
> either the CG or po/README: lilypond.pot may be updated only through
> "make po-replace", which is obvisouly not the case in this patch, as the
> POT creation date isn't changed, and every change to *.po files must
> come from the Free Translation Project unless I give explicit permission
> to do otherwise (which I should only do on advice from the FTP team). In
> short, I don't accept changes to files in po/ in this patch.
>
> Typos in translated Texinfo documentation may be applied without asking
> prior permission. I may have a look at simplifying the committishes
> update in case the translation was previsouly up to date, but there is
> much more urgent and important work to do first.
OK, so to make sure I understand correctly,
a) The changes to Documentation/de/* that move Lilypond -> LilyPond are OK
to commit, even though the commitish in the header of this file won't be
updated.
b) the changes to po/* are NOT Ok to commit.
Is this right?
Thanks,
Carl
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
