On Thu, 14 May 2026, 14:15 Dan Eble, <[email protected]> wrote: > > There could be outdated unvetted machine translations as well. >
Sure but isn't that "just a software problem"? To me the unvetted autotranslation might as well be part of the build. Also, "no documentation" is not a fair label for my earlier suggestion: > Absolutely, what I said wasn't meant to imply that. Forgive me if it came across that way "Not provided as part of the LilyPond project" is not the same as "no > documentation." > Well sure, but not providing it from the project makes it hard to find and keep associated with the right version. It's another hurdle for the final user I guess I'm saying. In saying all this, I wonder if the website could do this "live": when requested page X in language Y, if not present it would just on the fly synthesize it for you and render it with appropriate markings indicating what happened, so it's even clearer that it was never touched by a human L >
