| Re: [translations] updated patch for learning manual translated into german |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
Le 18/09/2015 03:49, Michael Gerdau a écrit :
Dear translators,
Find attached a patch to bring the learning manual up-to-date with the
english one. This one builds successfully on my system.
On my fresh repo, it builds completes but…
While fixing the problems I had encountered with the previous version
of this patch I finally got a rough understanding how links work.
As a consequence I also started fixing a few suspicious links in the
german version of the notation manual. However there remains much more
to be done.
I always check MANUAL.splittexi.log and, despite a successful build, I
get many warnings (nonstanding links towards snippets and internals):
in extending.bigtexi.log:
Unable to find node 'Eigenschaften von Musikobjekten' in book internals.
Unable to find node 'Kontexte erstellen' in book notation.
Unable to find node 'Vordefinierte Typenprädikate' in book notation.
Unable to find node 'Vordefinierte Typenprädikate' in book notation.
Unable to find node 'Vordefinierte Typenprädikate' in book notation.
Unable to find node 'Vordefinierte Typenprädikate' in book notation.
in learning.bigtexi.log:
nable to find node 'Updating old input files with convert-ly' in book usage.
Unable to find node 'Optimierungen mit Scheme' in book extending.
in notation.bigtexi.log:
Unable to find node 'Tonhöhen und Tonartbezeichnung (Vorzeichen)' in
book learning.
Unable to find node 'Beispiel aus dem Leben' in book learning.
Unable to find node 'Stücke durch Bezeichner organisieren' in book learning.
Unable to find node 'Tonhöhen und Tonartbezeichnung (Vorzeichen)' in
book learning.
Unable to find node 'Partituren und Stimmen' in book learning.
Unable to find node 'Partituren und Stimmen' in book learning.
Unable to find node 'Stücke durch Bezeichner organisieren' in book learning.
Unable to find node 'Stücke durch Bezeichner organisieren' in book learning.
Unable to find node 'Stücke durch Bezeichner organisieren' in book learning.
Unable to find node 'Optionen auf der Kommandozeile für lilypond' in
book usage.
in usage.bigtexi.log:
Unable to find node 'Tipparbeit durch Variablen und Funktionen ersparen'
in book learning.
launching, from Documentation/de
$ git grep -n 'Tipparbeit durch Variablen'
learning/fundamental.it$ git grep -n 'Tipparbeit durch Variablen'
learning/fundamental.itely:263:@ref{Tipparbeit durch Variablen und
Funktionen einsparen}. Die genauen
learning/fundamental.itely:2331:* Tipparbeit durch Variablen und
Funktionen einsparen::
learning/fundamental.itely:3216:@node Tipparbeit durch Variablen und
Funktionen einsparen
learning/fundamental.itely:3217:@subsection Tipparbeit durch Variablen
und Funktionen einsparen
usage/suggestions.itely:106:Noten. Siehe auch @rlearning{Tipparbeit
durch Variablen und Funktionen ersparen}
Once you've modified a node's name is changing its reference all over
the different manuals. "git grep -n '{old name'" returns me where I have
to adapt.
One thing I regularly do when I'm finished with a file is regenerating
the list of node translations
grep -B1 @translationof Documentation/fr/*.* Documentation/fr/*/*.* >
.../nodes
which creates (or overwrites) a file containing lines like
Documentation/fr/learning/common-notation.itely-@unnumberedsubsubsec Doigté
Documentation/fr/learning/common-notation.itely:@translationof Fingerings
that I later use when I search a cross-reference.
Anyway, from my PoV the Learning Manual now is up-to-date w/r to the
english version and I will now move on to the usage manual, unless I
hear otherwise.
Please correct the above mentioned links. If you can't manage it, just
let me know and I'll try to find a way to deal with it.
I'd like to repeat a question from my last email (see below):
One of the attached Patchfiles is fairly large. That leads to the
question what is the desired way of preparing these patches:
1) one (or very few) big patches ?
2) many small incremental patches ?
In the case you are facing, I would make one patch per file, i.e.
common-notation.patch containing the changes made to
learning/common-notation.itely as well as notation/piches.italy and
notation/world/itely because of
$ git grep -n 'Tonhöhen und Tonartbezeichnung'
learning/common-notation.itely:57:* Tonhöhen und Tonartbezeichnungen
(Vorzeichen)::
learning/common-notation.itely:128:@node Tonhöhen und
Tonartbezeichnungen (Vorzeichen)
learning/common-notation.itely:129:@subsection Tonhöhen und
Tonartbezeichnungen (Vorzeichen)
notation/pitches.itely:329:Mehr Information dazu in @rlearning{Tonhöhen
und Tonartbezeichnungen (Vorzeichen)}.}
notation/pitches.itely:443:@rlearning{Tonhöhen und Tonartbezeichnungen
(Vorzeichen)}.
notation/pitches.itely:1256:Mehr Information dazu in @rlearning{Tonhöhen
und Tonartbezeichnungen (Vorzeichen)}.}
notation/pitches.itely:1334:@rlearning{Tonhöhen und Tonartbezeichnung
(Vorzeichen)}.
notation/world.itely:347:@rlearning{Tonhöhen und Tonartbezeichnung
(Vorzeichen)}.
BTW, I won't normally have any connection between Sunday 20th and
Thursday 24th in the evening.
Cheers,
Jean-Charles