On Tue, 2026-05-12 at 21:17 +0800, Kunpeng He via Discussions on LilyPond development wrote: > Over the past few days, I used DeepSeek V4 Pro to translate the entire > LilyPond documentation into Chinese. The result is a modification > spanning 462 files, with roughly +63,215/−668 lines. It compiles > successfully and looks fine in my local environment > (https://gitlab.com/duskmoon314/lilypond/-/commit/6c4d0dabd659a09c004283d3c9ca7c46f82dd9fc). > > I'd love to contribute this work back to the project, but I would like > to ask for your guidance first: > > - 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?
Can you please clarify to what extent you used the AI to translate the documentation? Using LLMs to translate (parts of) phrases that were later checked by a human is fine, I guess. Such machine translators exist since a long time (Google Translate etc.) and in the end could be considered "better dictionaries". On the other hand, just running an LLM on the entire documentation without careful checking is different in my opinion: What do we gain by integrating such translation? Users could already translate the English documentation on-the-fly and an "official" translation would look like it was vetted by a human. You are writing "few days", which is very little for careful checks. This leads me to believe that it's the latter, and in that case I personally would be against accepting it. Jonas
signature.asc
Description: This is a digitally signed message part
