updated patch for learning manual translated into german

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

updated patch for learning manual translated into german

Michael Gerdau
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.

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.

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.


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 ?

Kind regards,
Michael
--
 Michael Gerdau       email: [hidden email]
 GPG-keys available on request or at public keyserver

0004-Doc-de-updated-learning-adjusted-a-couple-of-cross-l.patch (254K) Download Attachment
0005-Doc-de-removed-dublicated-line-in-learning-fundament.patch (879 bytes) Download Attachment
0006-Doc-de-learning-fixed-non-macthing-links-notation-fi.patch (35K) Download Attachment
signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: updated patch for learning manual translated into german

Jean-Charles MALAHIEUDE
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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: updated patch for learning manual translated into german

Michael Gerdau
> I always check MANUAL.splittexi.log and, despite a successful build, I
> get many warnings (nonstanding links towards snippets and internals):

So do I. I had checked those for learning and they both are "correct"
in that they do indeed point to dead links, stuff that is deliberately
commented out in the english original. Thus I decided not to do
anything about them.

However I wasn't aware that changing stuff in learning could produce
such warnings for other manuals.

> in extending.bigtexi.log:
> Unable to find node 'Eigenschaften von Musikobjekten' in book internals.

This one I don't understand (as to why it occurs)...

> 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.

These I have fixed. Will prepare a patch later.

> 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.

As I wrote above:
They are "correct" in that the corresponding nodes seem to be commented
out in the english original as well.

> 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.
I had seen lots of warnings regarding the book snippets and did not
realize, there are othes as well. Since I had and still have no idea
what to do about the warnings regarding book snippets I decided to
ignore them

I seem to be able to get rid of most (all?) those, that don't refer to
book snippets. I'm in the process of doing so.

However there is at least one warning I don't understand in notation.
Both in learning and notation is a node called "Clef" which I
translated into "Notenschlüssel" . To me both seem properly defined.
I don't understand that warning. It might be the same as with the one
warning in extending I did not get rid of.

I'd like help on both of these - probably after I've created a patch
to get rid of all the other warnings.

Finally what am I supposed to do with the warnings regarding
 book snippets ?

> in usage.bigtexi.log:
> Unable to find node 'Tipparbeit durch Variablen und Funktionen ersparen'
> in book learning.

Fixed as well.


[suggestions for an improvement in my workflow snipped]

That is valueable information. Thank you for sharing.

Kind regards,
Michael
--
 Michael Gerdau       email: [hidden email]
 GPG-keys available on request or at public keyserver

signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: updated patch for learning manual translated into german

Michael Gerdau
In reply to this post by Jean-Charles MALAHIEUDE
Dear translators,

find attached a patch that fixes most of the remaining broken links
as pointed out by Jean-Charles Malahieude. It is supposed to be
applied on top of the previous patches.

However there remain a few unmatched links.

in extending.bigtexi.log:
Unable to find node 'Eigenschaften von Musikobjekten' in book internals.

- a node 'Eigenschaften von Musikobjekten' (Music properties) exists
in extending (is this the same as internals?).
I have no idea how to solve this. I'm probably too blind to see what's
wrong.


in learning.bigtexi.log:
Unable to find node 'Updating old input files with convert-ly' in book
usage.
Unable to find node 'Optimierungen mit Scheme' in book extending.

- these broken links seem to exist in the english original as well


in notation.bigtexi.log:
Unable to find node 'Notenschlüssel' in book internals.
Unable to find node 'Tonumfang' in book internals.
Unable to find node 'Dynamik' in book internals.
Unable to find node 'Dynamik' in book internals.

- a node 'Notenschlüssel' (Clef) exists in both internals and
notation reference
- a node "'Tonumfang'" (Ambitus) exists in notation reference but
not in internals
- a node 'Dynamik' (Dynamics) exists in both internals and notation
reference
Again I have no idea how to solve these.
[I ignored all those referring to book snippets]


I'd be grateful if someone more knowledgeable than me would be so kind
and shed some light on this.

Kind regards,
Michael
--
 Michael Gerdau       email: [hidden email]
 GPG-keys available on request or at public keyserver

0007-Doc-de-fixed-more-non-macthing-links.patch (10K) Download Attachment
signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: updated patch for learning manual translated into german

Jean-Charles MALAHIEUDE
Le 19/09/2015 09:31, Michael Gerdau a écrit :

>
> in extending.bigtexi.log:
> Unable to find node 'Eigenschaften von Musikobjekten' in book internals.
>
> - a node 'Eigenschaften von Musikobjekten' (Music properties) exists
> in extending (is this the same as internals?).
> I have no idea how to solve this. I'm probably too blind to see what's
> wrong.
>
>

As long as they belong to different manuals, nodes can addopt the same
name. That's the reason why you have, in LM, "Fingerings" in
common-notation.itely and "Fingering" in tweaks.itely.


> in learning.bigtexi.log:
> Unable to find node 'Updating old input files with convert-ly' in book
> usage.

First guess: the text in @program{} hasn't been translated; I should
otherwise have been warned in German (something like: Unable to find
node 'Alte Dateien mit convert-ly aktualisieren' in book usage.)

Locate the culprit:
$ git grep -n '{Updating old input'
learning/fundamental.itely:3331:ändern sollte (siehe auch
@rprogram{Updating old input files

Guess where another xref might be:
Documentation] (translation)$ git grep -n '{Updating '
contributor/doc-work.itexi:1912:@ref{Updating documentation translation}.
contributor/doc-work.itexi:2001:completely updated, see @ref{Updating
translation committishes}.}
contributor/doc-work.itexi:2335:@item Each maintenance task except
@q{Updating PO files} can be done by
cs/learning/fundamental.itely:3316:ändern sollte (siehe auch
@rprogram{Updating old input files
de/learning/fundamental.itely:3331:ändern sollte (siehe auch
@rprogram{Updating old input files
hu/learning/common-notation.itely:1212:fájlt. Erről bővebb információ a
@rprogram{Updating files with convert-ly}
hu/learning/fundamental.itely:3075:@rprogram{Updating files with
convert-ly}).  If
learning/fundamental.itely:3102:@rprogram{Updating files with
convert-ly}).  If
nl/learning/fundamental.itely:3119:@rprogram{Updating files with
convert-ly}).  If
usage/suggestions.itely:64:when @ref{Updating files with convert-ly}
command (which requires the
web/news.itexi:401:latest version, see @rprogram{Updating files with
convert-ly}.

This is of some help: there is a node somewhere in Documentation/usage
labeled "Updating files with convert-ly".
I open my magic file Deutsche_Knoten and search for the string "Updating
files with convert-ly". This brings me to
--
Documentation/de/usage/updating.itely-@chapter Dateien mit
@command{convert-ly} aktualisieren
Documentation/de/usage/updating.itely:@translationof Updating files with
convert-ly
--

And i say "Bingo!" or "Gucke mal hier!"
and adapt line 3331 of de/learning/fundamental to read
  ändern sollte (siehe auch @rprogram{Dateien mit aktualisieren}).



> Unable to find node 'Optimierungen mit Scheme' in book extending.
>

Documentation] (translation)$ git grep -n '{Optimierungen '
cs/learning/tweaks.itely:4561:Schnittstelle zeigen, finden sich in
@rextend{Optimierungen mit Scheme}.
de/learning/tweaks.itely:5002:Schnittstelle zeigen, finden sich in
@rextend{Optimierungen mit Scheme}.

Viel zu einfach! Letzte Linie in tweaks.itely. Schau mal was git in English:
  can be found in @rextend{Callback functions}.

Suche mal in Deutsche_Knoten:
--
Documentation/de/extending/programming-interface.itely-@section
Callback-Funktionen
Documentation/de/extending/programming-interface.itely:@translationof
Callback functions
--
Hier ist's! Überschrift und Schluß, eins weniger!

> - these broken links seem to exist in the english original as well
>
>
> in notation.bigtexi.log:
> Unable to find node 'Notenschlüssel' in book internals.
> Unable to find node 'Tonumfang' in book internals.
> Unable to find node 'Dynamik' in book internals.
> Unable to find node 'Dynamik' in book internals.
>
> - a node 'Notenschlüssel' (Clef) exists in both internals and
> notation reference
> - a node "'Tonumfang'" (Ambitus) exists in notation reference but
> not in internals
> - a node 'Dynamik' (Dynamics) exists in both internals and notation
> reference
> Again I have no idea how to solve these.
> [I ignored all those referring to book snippets]
>

You may as well ignore all warnings referring to "internals" which, as
programmatically generated, are not translated at all.


Tschußle!
Jean-Charles


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: updated patch for learning manual translated into german

Jean-Charles MALAHIEUDE
Le 19/09/2015 14:56, Jean-Charles Malahieude a écrit :

> Le 19/09/2015 09:31, Michael Gerdau a écrit :
>>
>> in learning.bigtexi.log:
>> Unable to find node 'Updating old input files with convert-ly' in book
>> usage.
> [...]
>
> This is of some help: there is a node somewhere in Documentation/usage
> labeled "Updating files with convert-ly".
> I open my magic file Deutsche_Knoten and search for the string "Updating
> files with convert-ly". This brings me to
> --
> Documentation/de/usage/updating.itely-@chapter Dateien mit
> @command{convert-ly} aktualisieren
> Documentation/de/usage/updating.itely:@translationof Updating files with
> convert-ly
> --
>
Forgot the bonus file


deutsche_Knoten (201K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: updated patch for learning manual translated into german

Michael Gerdau
In reply to this post by Jean-Charles MALAHIEUDE
Thanks alot for your support,

find attached the hopefully last addition to the patches. Only missing
links left are either to snippets or to internals.

I understand that is nothing to worry about.

Now shall I merge all the patches into a single patch or is it
acceptable to have them as a set of several patches?

Or shall I prepare an email with all patches together ?

Kind regards,
Michael
--
 Michael Gerdau       email: [hidden email]
 GPG-keys available on request or at public keyserver

0008-Doc-de-fixed-more-non-macthing-links-2.patch (1K) Download Attachment
signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: updated patch for learning manual translated into german

Jean-Charles MALAHIEUDE
Le 19/09/2015 15:20, Michael Gerdau a écrit :
> Thanks alot for your support,
>
> find attached the hopefully last addition to the patches. Only missing
> links left are either to snippets or to internals.
>

Well done!

> I understand that is nothing to worry about.
>

Correct.

> Now shall I merge all the patches into a single patch or is it
> acceptable to have them as a set of several patches?
>
> Or shall I prepare an email with all patches together ?
>

I've modified your commit-ID in learning in order they appear as up to
date when running check-translation and committed everything.

I also updated translation-status and pushed everything upstream.

By the way, don't modify Documentation/de/translations.itexi as it gets
updated by a script.

Thanks for your work.

Cheers,
Jean-Charles



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: updated patch for learning manual translated into german

Michael Gerdau
> I've modified your commit-ID in learning in order they appear as up to
> date when running check-translation and committed everything.

I thought I had done that - at least I had meant to do it, i.e. used
the result of
git rev-list HEAD | head -1

Apparently something went wrong there.

> I also updated translation-status and pushed everything upstream.

Thank you.

Kind regards,
Michael
--
 Michael Gerdau       email: [hidden email]
 GPG-keys available on request or at public keyserver

signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: updated patch for learning manual translated into german

Federico Bruni-3
Il giorno sab 19 set 2015 alle 23:16, Michael Gerdau <[hidden email]> ha
scritto:
>>  I've modified your commit-ID in learning in order they appear as up
>> to
>>  date when running check-translation and committed everything.
>
> I thought I had done that - at least I had meant to do it, i.e. used
> the result of
> git rev-list HEAD | head -1
>
> Apparently something went wrong there.

The command above takes the commit-ID of the latest _local_ commit, not
the latest _remote_ commit. If you had write access on the repository,
that ID would be the same you have in your local copy. But, as you do
not have write access and Jean-Charles pushed your patches, the
commit-ID changed and the one used in your file cannot work.

If you try `git show <your-wrong-commit-id>` on your local copy you
should get an error, if you have updated your local copy correctly..
which involves resetting to the commit-id previous to your commits aand
then pulling.

Next time use this command to get the commit id:
git rev-parse origin/translation





Loading...