Hello Kunpeng,
> Over the past few days, I used DeepSeek V4 Pro to translate the
> entire LilyPond documentation into Chinese.
Great, and thanks for your work!
> - As an amateur music lover, I cannot guarantee the overall quality
> of the translation. Are there any quality standards we should
> meet before merging? Or would a complete version be acceptable,
> with polishing to follow later?
This is a good question that I can't answer easily. My Chinese is too
rusty and rudimentary to check whether the translation is OK.
However, it is not as problematic as it sounds, since...
> - This is a large modification. Should I split it into multiple
> commits or separate pull requests?
... you *must* split it into smaller commits so that the various
commits are (a) manageable by programs like `gitk` and (b) don't
overwhelm readers who want to check the changes.
I suggest that you do one Merge Request per manual, and you use one
commit per chapter (or something similar) in the Merge Request. [Note
that some manuals stay intentionally untranslated, for example, the
Contribors' Guide.]
> I would greatly appreciate any advice on how to properly integrate
> the translations.
First of all, I would like to see a *small* Merge Request so that I
check how it looks like code-wise. So please do that, for example, by
integrating the file `learning/common-notation.itely`.
What I request is that you actually *read* everything you are
submitting. I don't want commits that no human has looked at.
Werner
