2012/1/18 David Kastrup <d...@gnu.org>:
> Culprit would be
> commit 44f3e55e3c283ccfdcb32af3ba3f45ec8580ca23
> Author: Yoshiki Sawada <sawada.yosh...@gmail.com>
> Date:   Sun Jan 15 09:00:54 2012 +0900
>
>    Doc-ja: Adding and updating NR
>
>    Doc-ja: Adding and updating NR.
>
>
> merged in from the translation branch.
>
> This is somewhat unfortunate: the newly created translation refers to a
> version that has been semi-fixed after a syntax change by running
> scripts/auxiliar/update-with-convert-ly.sh, and corrected afterwards.
>
> It would seem that rerunning scripts/auxiliar/update-with-convert-ly.sh
> after merging the translation might have fixed that problem this time.
>
> I am not sure it would work in all such cases.
>
> I don't have a better suggestion than doing a test run before pushing a
> translation merge.

You are right. I tested in a system and pushed from another. That made
the mess. Sorry.

Now testing again.

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to