> Le 11 mars 2022 à 11:43, Werner Arnhold <wer...@arnhold-berlin.de> a écrit : > > Am Donnerstag, den 10.03.2022, 19:40 +0100 schrieb Jean Abou Samra: >> Le 09/03/2022 à 09:08, c.bu...@posteo.jp a écrit : >>> Betreff: German Notation documentation out of date and buggy >>> example code >>> Datum: 09.03.2022 09:07 >>> Von: c.bu...@posteo.jp >>> An: bug-lilypond-requ...@gnu.org >>> >>> This is about the German version of the Notation reference. >>> >>> Please compare the example code in that German and English version: >>> https://lilypond.org/doc/v2.22/Documentation/notation/displaying-rhythms.de.html#upbeats >>> >>> >>> https://lilypond.org/doc/v2.22/Documentation/notation/displaying-rhythms.en.html#upbeats >>> >>> >>> >>> The German version does not user { }. But the 2.22 release does >>> need >>> them. The example in the German version throws errors. >> >> >> I can't say I like this practice of the documentation, but this >> is not a bug. Have a look at >> >> https://lilypond.org/doc/v2.22/Documentation/learning/entering-input.html >> >> “They [braces] may be omitted in some examples in this manual, >> but don’t forget them in your own music!” >> >> It is true, however, that the German documentation is generally >> not up-to-date (here the braces seem to have been added at some >> point). For several years, there has been nobody to update it. >> Werner Arnhold seemed interested at some point, not sure if that's >> still the case; CCing him. Like everything in LilyPond, translating >> the documentation is a volunteer effort. Consider volunteering >> yourself if you want up-to-date documentation in your native >> language. >> >> Best regards, >> Jean > > Hello, > > I am busy on changing ties and slurs. Some semantic or syntactic > oddities too. > > I think consistency is important, so all examples in the doc should be > treated in the same way. That is, be sourrounded by {} or \relative {}. > Some are, some are not. The code should procude the picture below. So I > will check the files I change to obey this rule too, is that ok?
In my opinion, that is a very good idea. Even better would be to convert all of the examples in batch, but this is not really a job for translators, although I definitely do not want to stop you from doing it if you are familiar with some scripting language. > I will > try first to change ties and slurs and then look further. Perfect! If you encounter any issues, feel free to ask. Jean _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
