Re: [Lilypond-auto] Patchy report

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

Re: [Lilypond-auto] Patchy report

John Mandereau
Dear Pavel,
Il giorno ven, 31/08/2012 alle 04.01 +0000, [hidden email] ha
scritto:

> 01:00:01 (UTC) Begin LilyPond compile, previous commit at e593c62a665b8d3a8e095da059595301585c2163
> 01:00:38 Merged translation, now at: e593c62a665b8d3a8e095da059595301585c2163
> 01:00:40 Success: sudo -u lilybuild ./autogen.sh --noconfigure
> 01:01:14 Success: sudo -u lilybuild /home/lilybuild/translation/configure --disable-optimising
> 01:01:33 Success: sudo -u lilybuild nice make clean
> 01:16:43 Success: sudo -u lilybuild nice make -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> 01:36:36 Success: sudo -u lilybuild nice make test -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> 04:01:51 *** FAILED BUILD ***
> sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> Previous good commit: 201be86ae2d8e616b6e661d4dfaac792fd999312
> Current broken commit: e593c62a665b8d3a8e095da059595301585c2163

The failure came from Czech Learning Manual:
$ cat /home/lilybuild/build-translation/Documentation/cs/learning.bigtexi.log
** Node following `Přeložení zdrojového souboru' in menu `Jak se píší vstupní soubory' and in sectionning `Zadání not' differ
** `Cvičení' is up for `Zadání not', but has no menu entry for this node
** `Cvičení' is up for `MacOS X', but has no menu entry for this node
** `Cvičení' is up for `Windows', but has no menu entry for this node
** `Cvičení' is up for `Příkazový řádek', but has no menu entry for this node
** `Přezkoušení taktů' doesn't appear in menus
** `Notový zápis v jedné notové osnově' is up for `Přezkoušení taktů', but has no menu entry for this node
** No node following `Přezkoušení taktů' in menu, but `Předznamenání a označení tóniny (předznamenání)' follows in sectionning
WARNING: Unable to find node 'Předznamenání' in book notation.
WARNING: Unable to find node 'Názvy not v jiných řečích' in book notation.
WARNING: Unable to find node 'Nastavení výšek tónů' in book notation.
WARNING: Unable to find node 'Zadání rytmu' in book notation.
WARNING: Unable to find node 'Zadání pomlk' in book notation.
WARNING: Unable to find node 'Udání taktu' in book notation.
WARNING: Unable to find node 'Notový klíč' in book notation.
WARNING: Unable to find node 'Řešení potíží' in book usage.
WARNING: Unable to find node 'Časté chyby' in book usage.
WARNING: Unable to find node 'Přezkoušení taktů a počtu taktů' in book notation.
WARNING: Unable to find node 'Označení not v jiných jazycích' in book notation.
WARNING: Unable to find node 'Automatické předznamenání' in book notation.
WARNING: Unable to find node 'Označení not v jiných jazycích' in book notation.
WARNING: Unable to find node 'Předznamenání' in book notation.
WARNING: Unable to find node 'Automatické předznamenání' in book notation.
WARNING: Unable to find node 'Označení tóniny' in book notation.
WARNING: Unable to find node 'Ligatury' in book notation.
WARNING: Unable to find node 'Legatové obloučky' in book notation.
WARNING: Unable to find node 'Obloučky frázování' in book notation.
WARNING: Unable to find node 'Artikulační znaménka a ozdoby' in book notation.
WARNING: Unable to find node 'Příkazy pro prstoklad' in book notation.
WARNING: Unable to find node 'Dynamika' in book notation.
WARNING: Unable to find node 'Zadání textu' in book notation.
WARNING: Unable to find node 'Automatické trámce' in book notation.
WARNING: Unable to find node 'Ruční trámce' in book notation.
WARNING: Unable to find node 'Ozdoby' in book notation.
WARNING: Unable to find node 'Jiná rytmická rozdělení' in book notation.
WARNING: Unable to find node 'Předtaktí' in book notation.
WARNING: Unable to find node 'Klávesové nástroje a jiné nástroje s více notovými osnovami' in book notation.
WARNING: Unable to find node 'Nechat ukázat osnovy' in book notation.
WARNING: Unable to find node 'Akordové noty' in book notation.
WARNING: Unable to find node 'Současně se objevující noty' in book notation.
WARNING: Unable to find node 'Notový zápis zpěvu' in book notation.
WARNING: Unable to find node 'Notový zápis zpěvu' in book notation.
WARNING: Unable to find node 'Vytvoření názvu' in book notation.
WARNING: Unable to find node 'Stavba souboru' in book notation.
WARNING: Unable to find node 'Stavba souboru' in book notation.
WARNING: Unable to find node 'Rozvržení notového zápisu' in book notation.
WARNING: Unable to find node 'Vytváření souborů MIDI' in book notation.
WARNING: Unable to find node 'Více notových zápisů v knize' in book notation.
WARNING: Unable to find node 'Stavba souboru' in book notation.
WARNING: Unable to find node 'Stavba souboru' in book notation.
WARNING: Unable to find node 'Vstupní režimy' in book notation.
WARNING: Unable to find node 'Stavba notového zápisu' in book notation.
WARNING: Unable to find node 'Osnovy ossia' in book notation.
WARNING: Unable to find node 'Více hlasů' in book notation.
WARNING: Unable to find node 'Více hlasů' in book notation.
WARNING: Unable to find node 'Notový zápis zpěvu' in book notation.
WARNING: Unable to find node 'Vysvětlení prostředí' in book notation.
WARNING: Unable to find node 'Vytvoření prostředí' in book notation.
WARNING: Unable to find node 'Die Standardeinstellungen von Kontexten ändern' in book notation.
WARNING: Unable to find node 'Der set-Befehl' in book notation.
WARNING: Unable to find node 'Umgebungs-Plugins verändern' in book notation.
WARNING: Unable to find node 'Die Standardeinstellungen von Kontexten ändern' in book notation.
WARNING: Unable to find node 'Grundlagen zum Verändern von Eigenschaften' in book notation.
WARNING: Unable to find node 'Updating old input files with convert-ly' in book usage.
WARNING: Unable to find node 'Schwierige Korrekturen' in book extending.
WARNING: Unable to find node 'Der tweak-Befehl' in book notation.
WARNING: Unable to find node 'Scheme-Übung' in book extending.
WARNING: Unable to find node 'Scheme-Übung' in book extending.
WARNING: Unable to find node 'Scheme-Übung' in book extending.
WARNING: Unable to find node 'Objekte weiß malen' in book notation.
WARNING: Unable to find node 'Liste der Farben' in book notation.
WARNING: Unable to find node 'Liste der Farben' in book notation.
WARNING: Unable to find node 'Text mit Verbindungslinien' in book notation.
*** Undefined node `Přímo vyjádřené začátky hlasů' in @ref (in out-www/learning/tweaks.texi l. 3769)

I could spot one error in Documentation/cs/learning/tutorial.itely: in

@node Přeložení zdrojového souboru
@subsection Přeložení zdrojového souboru
@translationof Compiling a file

@subsection should be @section instead.  I'm not sure there are other
errors in Czech documentation, I'm rebuilding with this fix included.

I know it takes a while to build LilyPond and the documentation, but
when you only work in the Czech manual and want to quickly check your
changes, you can just do "make doc-clean" from within Documentation/cs,
then "make doc" from the top build directory to quickly test your
changes (although if there are many changes when you pull from Git, you
also need "make" and "make doc-clean" at toplevel).

Best,
John



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

Re: [Lilypond-auto] Patchy report

John Mandereau
Il giorno ven, 31/08/2012 alle 12.20 +0200, Pavel Fric ha scritto:
> I focus on translation, and for the time being have no technical
> knowledge about texinfo. The way the changes come further is via
> patches. The recent problem for me was, that I unintentionally opend,
> changed and saved any from files in my lilypond-git working directory,
> and hen git pull continued only after (my decision) to git stash
> changes.

I'm not sure I understood correctly; in case you wanted to commit the
stashed changes, have you popped/applied them (git stash pop/git stash
apply) and pushed?


> *** Undefined node `Přímo vyjádřené začátky hlasů' in @ref (in
> out-www/learning/tweaks.texi l. 3769)
>
> I´ve changed Přímo vyjádřené začátky hlasů, but in the next change I
> would like to come back to this translation.

When you change a node/section name, you must update all references to
it too, this is why you want to find the best translation for these at
the first trial :-)  Note that such a @ref error is fatal, i.e. it
causes the whole documentation build to fail.


> The notation - the nodes for it are from time to time present in
> fundamental.itely (or in another places) - the state was/is 1 1/2 year
> old (I worked on many other projects, part of them connected to
> LilyPond, such as Frescobaldi, Denemo, LilyPond on
> translationproject.org), but generally this is untranslated.

Wow, you are contributing for so many projects.  I'd suggest to
"release" your translation work, i.e. push it to translation branch,
when it's finished  (and ideally proofread, but this is not required
before committing and pushing), because as you have noticed the
translations are released in 2.16 stable series now and so may get a
large audience.


>  When time comes and I will have tutorial finished, I´ll ask Francisco
> to add the file(s) for Notation reference to my cs directory for me to
> be able to continue on translating it. Or maybe better the German
> version of code (translation on notation) - me not to have to focus on
> syntax.

You could do this yourself, preferably on a separate Git branch: make
sure you don't have uncommitted changes (git status), then

git checkout translation
git pull
git checkout translation/cs
cp Documentation/de/[the files you need] Documentation/cs/[use the same directory layout as in de/]
git add Documentation/cs
git commit

This way you don't have to leave German translations lying around in the
official sources (let's not mind for the ones that are already there).
When you want to merge back to translation, commit or stash all
uncommitted changes, then check that LilyPond and the documentation
build succesfully, then do (with the translation/cs branch still checked
out)

git pull
git rebase -i origin/translation

then squash the commits, e.g. keep "pick" for the first one, then put
"s" for all other ones, proceed with rebasing, and finally

git checkout translation
git merge translation/cs
git push origin translation:translation


> So the error messages - could it be ignored during compilation, or
> requires it more handwork, e. g. from say Francisco?

When there are two many warnings or errors, texi2html exits with
non-zero and cause the documentation build to fail, so the errors must
be fixed as soon as possible (which I did this time but some other time
if we're in a hurry for a release or many translators are working at
that time and are annoyed, a commit that breaks the build may be
reverted), and the warnings should be fixed at some point of time.

Best,
John



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

Re: [Lilypond-auto] Patchy report

Federico Bruni-2
Il 31/08/2012 14:02, John Mandereau ha scritto:

>> *** Undefined node `Přímo vyjádřené začátky hlasů' in @ref (in
>> >  out-www/learning/tweaks.texi l. 3769)
>> >
>> >  I´ve changed Přímo vyjádřené začátky hlasů, but in the next change I
>> >  would like to come back to this translation.
> When you change a node/section name, you must update all references to
> it too, this is why you want to find the best translation for these at
> the first trial:-)   Note that such a @ref error is fatal, i.e. it
> causes the whole documentation build to fail.
>

Correct me if I'm wrong: I don't think that we _have to_ translate the
@ref, because the text is translated anyway in the specific language
page and the link works.  See an example here:
http://lilypond.org/doc/v2.16/Documentation/learning/introduction-to-tweaks.it.html

The advantage of leaving it untranslated is that you don't have to
search and fix all the @ref occurrences of a node in case you want to
translate it differently.

> I'd suggest to
> "release" your translation work, i.e. push it to translation branch,
> when it's finished  (and ideally proofread, but this is not required
> before committing and pushing), because as you have noticed the
> translations are released in 2.16 stable series now and so may get a
> large audience.
>

How long it will work this way? (i.e. translation branch merged to 2.16
branch)

Regards
--
Federico


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

Re: [Lilypond-auto] Patchy report

John Mandereau
Il giorno ven, 31/08/2012 alle 14.25 +0200, Federico Bruni ha scritto:
> Correct me if I'm wrong: I don't think that we _have to_ translate the
> @ref, because the text is translated anyway in the specific language
> page and the link works.  See an example here:
> http://lilypond.org/doc/v2.16/Documentation/learning/introduction-to-tweaks.it.html

AFAICS this page isn't translated to Italian, but it seems to work
anyway.


> The advantage of leaving it untranslated is that you don't have to
> search and fix all the @ref occurrences of a node in case you want to
> translate it differently.

Doesn't the automatic translation require adding the definition of an
empty node with a @translationof, or some entry in the PO file in
Documentation/po?

From a quick glance at translations of the Learning Manual, it seems
that in practice, for many languages the argument of @ref is often
translated.


> How long it will work this way? (i.e. translation branch merged to 2.16
> branch)

At least until 2.16.1, and probably not after that: I doubt David will
spend all the energy for, nor delegate to any developer or contributor
backporting some of the documentation changes from master to
stable/2.16.

Best,
John



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

Re: [Lilypond-auto] Patchy report

Federico Bruni-2
Il 31/08/2012 15:06, John Mandereau ha scritto:
> Il giorno ven, 31/08/2012 alle 14.25 +0200, Federico Bruni ha scritto:
>> Correct me if I'm wrong: I don't think that we _have to_ translate the
>> @ref, because the text is translated anyway in the specific language
>> page and the link works.  See an example here:
>> http://lilypond.org/doc/v2.16/Documentation/learning/introduction-to-tweaks.it.html
>
> AFAICS this page isn't translated to Italian, but it seems to work
> anyway.
>

Yes, because it links to a chapter which has been translated and whose
nodes have all a @translationof (I've translated all LM except for
chapter 4, which I'm working on now).

>
>> The advantage of leaving it untranslated is that you don't have to
>> search and fix all the @ref occurrences of a node in case you want to
>> translate it differently.
>
> Doesn't the automatic translation require adding the definition of an
> empty node with a @translationof, or some entry in the PO file in
> Documentation/po?
>

Yes, the @ref refers to a @node which is somehow associated to
@translationof

I guess that the automatic translation is defined here:
scripts/build/extract_texi_filenames.py

right?

>  From a quick glance at translations of the Learning Manual, it seems
> that in practice, for many languages the argument of @ref is often
> translated.
>
>
>> How long it will work this way? (i.e. translation branch merged to 2.16
>> branch)
>
> At least until 2.16.1, and probably not after that: I doubt David will
> spend all the energy for, nor delegate to any developer or contributor
> backporting some of the documentation changes from master to
> stable/2.16.
>

Ok, then it would be nice if translators are informed a bit earlier when
2.16.1 is going to be released.


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

Re: Re: [translations] Re: [Lilypond-auto] Patchy report, work->patch->Francisco Villa->git pull cycle

Pavel Fric
In reply to this post by John Mandereau
Hi,

here is the overview of my translation projects + some dozens more (I didn't make a post about them, like Kadu, Sigil, (...):

http://fripohled.blogspot.cz/

This is probably the reason, I have 1,5 years pause in translating the LilyPond documentation.

Note: The stashed changes -> the only reason for git stash was to continue in git pull and make another patch (I don't know, what unintentonal changes were made, and don't want to use them at all).

Also I make git pull now to be able to make another work->patch->Francisco Villa->git pull cycle.

Greetings, Pavel Fric

Wow, you are contributing for so many projects. I'd suggest to
"release" your translation work, i.e. push it to translation branch,
when it's finished (and ideally proofread, but this is not required
before committing and pushing), because as you have noticed the
translations are released in 2.16 stable series now and so may get a
large audience.


Loading...