Carl D. Sorensen a écrit :
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?
Yes. I thought all this policy was explained in the CG for a) and in
po/README for b).
In 3.6.4 Translations management policies, Managing documentation
translation with Git, you can read
"General maintenance may be done by anybody who knows what he does in
documentation in all languages, without informing translators first.
General maintenance include simple text substitutions (e.g. automated by
sed), compilation fixes, updating Texinfo or lilypond-book commands,
updating macros, updating ly code, fixing cross-references"
I highly recommend reading these policies to anybody that may apply
patches in the future, whatever the time it takes to understand it
(maybe more than one hour), so we don't pollute the list with
rediscussing procedures that are direct consequences of the policies.
However, you're welcome to discuss or help clarifying the policies after
having read them. I know they may not be clear to non translators, but I
need your feedback to improve them: sentences that need clarification or
expanding, details that should be added.
Best,
John
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
