Error in generate-documentation.log

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Error in generate-documentation.log

Walter Garcia-Fontes
I've been working on fixing unstralated node references in the
learning directory of the Catalan translation. I believe I fixed all
of them, but now the build is aborting with an error message in
generate-documentation.log:

fatal error: define-grob-properties.scm: cannot find interface for property:
voiced-position

Anybody can give me a hint on where I have to look for the culprit of
this?

Thanks a lot,

--
Walter Garcia-Fontes



Reply | Threaded
Open this post in threaded view
|

Re: Error in generate-documentation.log

Jean-Charles MALAHIEUDE
Le 24/01/2015 20:05, Walter Garcia-Fontes a écrit :

> I've been working on fixing unstralated node references in the
> learning directory of the Catalan translation. I believe I fixed all
> of them, but now the build is aborting with an error message in
> generate-documentation.log:
>
> fatal error: define-grob-properties.scm: cannot find interface for property:
> voiced-position
>
> Anybody can give me a hint on where I have to look for the culprit of
> this?
>

I've no such a file generated during the build process, but here is how
I usually proceed: since files other than concerning documentation have
changed, I first run a "make" to update the "binaries".

When "master" has been merged into "translation", I usually clean
everything (make doc-clean && make clean) and rebuild everything from
scratch.

Let me know if it persists.

Cheers,
Jean-Charles


Reply | Threaded
Open this post in threaded view
|

Re: Error in generate-documentation.log

Walter Garcia-Fontes
* Jean-Charles Malahieude, [hidden email] [25/01/15 16:29]:

> Le 24/01/2015 20:05, Walter Garcia-Fontes a écrit :
> >I've been working on fixing unstralated node references in the
> >learning directory of the Catalan translation. I believe I fixed all
> >of them, but now the build is aborting with an error message in
> >generate-documentation.log:
> >
> >fatal error: define-grob-properties.scm: cannot find interface for property:
> >voiced-position
> >
> >Anybody can give me a hint on where I have to look for the culprit of
> >this?
> >
>
> I've no such a file generated during the build process, but here is how I
> usually proceed: since files other than concerning documentation have
> changed, I first run a "make" to update the "binaries".
>
> When "master" has been merged into "translation", I usually clean everything
> (make doc-clean && make clean) and rebuild everything from scratch.
>

Yes, that was it, after cleaning and running "make" and "make doc" the
error disappeared.

Here is a new set of patches trying to fix the interpunct problem and
broken cross-references:

http://puna.upf.edu/0001-Doc-ca-Fix-of-interpunct-and-broken-cross-references.patch

AFAIK it builds cleanly.

I'm still getting some messages about undefined cross-references in
the logs, but I checked those and they seem to be fine, so I presume
they are produced before the indices are produced, otherwise I don't
know what is producing them.

I'm also exchanging with the texinfo developers about the Catalan
interpunct, and it seems there will be some progress there soon, for
the time being I have substituted all of them by "l.l" instead of
"l·l". On the other hand, "txi-ca.tex" has been accepted upstream.

--
Walter Garcia-Fontes




Reply | Threaded
Open this post in threaded view
|

Re: Error in generate-documentation.log

David Kastrup
Walter Garcia-Fontes <[hidden email]> writes:

> I'm also exchanging with the texinfo developers about the Catalan
> interpunct, and it seems there will be some progress there soon, for
> the time being I have substituted all of them by "l.l" instead of
> "l·l". On the other hand, "txi-ca.tex" has been accepted upstream.

Great!  Good to see this in determined hands.

--
David Kastrup


Reply | Threaded
Open this post in threaded view
|

Re: Error in generate-documentation.log

Jean-Charles MALAHIEUDE
In reply to this post by Walter Garcia-Fontes
Le 29/01/2015 07:26, Walter Garcia-Fontes a écrit :

> * Jean-Charles Malahieude, [hidden email] [25/01/15 16:29]:
>> When "master" has been merged into "translation", I usually clean everything
>> (make doc-clean && make clean) and rebuild everything from scratch.
>>
>
> Yes, that was it, after cleaning and running "make" and "make doc" the
> error disappeared.
>
> Here is a new set of patches trying to fix the interpunct problem and
> broken cross-references:
>
> http://puna.upf.edu/0001-Doc-ca-Fix-of-interpunct-and-broken-cross-references.patch
>
> AFAIK it builds cleanly.
>

Not for me.
Have you made the changes I gathered in "correcting-ca-links.patch"?

ass-link --prepend-suffix .ca hard ./out-www
/home/jcharles/GIT/Traduc/Documentation/./out-www

Please check the logfile learning.splittexi.log for errors

/home/jcharles/GIT/Traduc/stepmake/stepmake/texinfo-rules.make:54:
recipe for target 'out-www/learning/index.html' failed


learning.splittexi.log:
** `Lligadures d'unió' doesn't appear in menus
** `Lligadures d'unió i d'expressió' is up for `Lligadures d'unió', but
has no menu entry for this node
** No node following `Lligadures d'unió' in menu, but `Lligadures
d'expressió' follows in sectionning
** `Lligadures d'expressió' doesn't appear in menus
** `Lligadures d'unió i d'expressió' is up for `Lligadures d'expressió',
but has no menu entry for this node


> I'm still getting some messages about undefined cross-references in
> the logs, but I checked those and they seem to be fine, so I presume
> they are produced before the indices are produced, otherwise I don't
> know what is producing them.
>

You've to be careful:
1-What is in the @menu is literally what follows @node:
  @menu
  * Lligadures de unió::
  @endmenu

  @node Lligadures d'unió

This is wrong. Either "de unió" or "d'unió" in both places!

2- What is in @ref{…} must be what is after @node, literally, with one
exception: when referring to an untranslated node, you may use the
@rMANUALnamed variant, so to say:

@ref{Lligadures d'unió} and rlearningnamed{Tie,Corbata} are both valid
and will link to the same node in
/Documentation/ca/learning/common-notation.itely.

In Documentation/ca/web/manuals.itexi, @rprogramnamed{Troubleshooting,
Solució de problemes} may be replaced by @ruser{Solució de problemes}
only once you'll have translated Documentation/ca/usage/suggestions.tely


Cheers,
Jean-Charles


Reply | Threaded
Open this post in threaded view
|

Re: Error in generate-documentation.log

Walter Garcia-Fontes
* Jean-Charles Malahieude, [hidden email] [29/01/15 20:41]:
> >AFAIK it builds cleanly.
> >
>
> Not for me.

Still working on these, I'm getting now few warning on broken cross
references, but still getting some. For instance in
learning/tutorial.itely I have a menu, with associated node called
"Indicació de compàs". Further down I have

@rusernamed{Time signature,Indicació de compàs}

since I have translated that reference.

But I'm still getting:

WARNING: Unable to find node 'Indicació de compàs' in book notation.

I also see some @notation{Indicació de compàs} but those aren't cross
references, right?

Any hint on where to look to fix this is greatly appreciated,

--
Walter Garcia-Fontes



Reply | Threaded
Open this post in threaded view
|

Re: Error in generate-documentation.log

Jean-Charles MALAHIEUDE
Le 01/02/2015 20:10, Walter Garcia-Fontes a écrit :

> * Jean-Charles Malahieude, [hidden email] [29/01/15 20:41]:
>>> AFAIK it builds cleanly.
>>>
>>
>> Not for me.
>
> Still working on these, I'm getting now few warning on broken cross
> references, but still getting some. For instance in
> learning/tutorial.itely I have a menu, with associated node called
> "Indicació de compàs". Further down I have
>
> @rusernamed{Time signature,Indicació de compàs}
>
> since I have translated that reference.
>
> But I'm still getting:
>
> WARNING: Unable to find node 'Indicació de compàs' in book notation.
>

We have a node in learning/tutorial.itely that gets the same name as in
notation/rhythms.itely but there won't be any problem once you'll have
dealt with rhythms. It's just a warning -- as a matter of fact, I've
plenty of those warnings concerning "internals" or "snippets" -- and it
doesn't break the build.

> I also see some @notation{Indicació de compàs} but those aren't cross
> references, right?
>

This one is like @emph or @strong or @code, just a way to present what
is embraced. Have a look at CG-5.4 Texinfo introduction and usage policy

> Any hint on where to look to fix this is greatly appreciated,
>

I don't know about other editors, but emacs allows you to see the
"sectioning" (see CG-5.9.4 Translations management policies).

Let me know if this helps.

Cheers,
Jean-Charles


Reply | Threaded
Open this post in threaded view
|

Re: Error in generate-documentation.log

Walter Garcia-Fontes
* Jean-Charles Malahieude, [hidden email] [03/02/15 20:00]:

> Le 01/02/2015 20:10, Walter Garcia-Fontes a écrit :
> >Still working on these, I'm getting now few warning on broken cross
> >references, but still getting some. For instance in
> >learning/tutorial.itely I have a menu, with associated node called
> >"Indicació de compàs". Further down I have
> >
> >@rusernamed{Time signature,Indicació de compàs}
> >
> >since I have translated that reference.
> >
> >But I'm still getting:
> >
> >WARNING: Unable to find node 'Indicació de compàs' in book notation.
> >
>
> We have a node in learning/tutorial.itely that gets the same name as in
> notation/rhythms.itely but there won't be any problem once you'll have dealt
> with rhythms. It's just a warning -- as a matter of fact, I've plenty of
> those warnings concerning "internals" or "snippets" -- and it doesn't break
> the build.

Thanks, in my last try I thought it was building cleanly but it was
not. So, if you have this type of warnings it is normal to still get
some *.log" produced even if the build is clean, apart from these
warnings?

> >I also see some @notation{Indicació de compàs} but those aren't cross
> >references, right?
> >
>
> This one is like @emph or @strong or @code, just a way to present what is
> embraced. Have a look at CG-5.4 Texinfo introduction and usage policy

Thanks, I'll do.

> >Any hint on where to look to fix this is greatly appreciated,
> >
>
> I don't know about other editors, but emacs allows you to see the
> "sectioning" (see CG-5.9.4 Translations management policies).

I'm also using emacs, but haven't explored all the texinfo-mode capabilities.

>
> Let me know if this helps.
>

Yes, greatly, thank you very much. I will revise my patches and submit
them in a couple of days.

--
Walter Garcia-Fontes



Reply | Threaded
Open this post in threaded view
|

Re: Error in generate-documentation.log

Jean-Charles MALAHIEUDE
Le 04/02/2015 07:27, Walter Garcia-Fontes a écrit :
> * Jean-Charles Malahieude, [hidden email] [03/02/15 20:00]:
>>
>
> Thanks, in my last try I thought it was building cleanly but it was
> not. So, if you have this type of warnings it is normal to still get
> some *.log" produced even if the build is clean, apart from these
> warnings?
>

Yes. You get one log-file per manual. I usually just check that those
warning concern only "internals" or "snippets".


>>
>> I don't know about other editors, but emacs allows you to see the
>> "sectioning" (see CG-5.9.4 Translations management policies).
>
> I'm also using emacs, but haven't explored all the texinfo-mode capabilities.
>

It makes coloring, which is not so bad, and lets you have in a buffer
the structure of your texi or tely file (with <C>c <C>s if you don't
have auctex) and you can then navigate by clicking on the display. Here
it is for your tutorial:
---8<---
24 matches for
"^\(?:@\(top\>\|chapter\>\|section\>\|subsection\>\|subsubsection\>\|unnumbered\>\|unnumberedsec\>\|unnumberedsubsec\>\|unnumberedsubsubsec\>\|appendix\>\|appendixsec\>\|appendixsection\>\|appendixsubsec\>\|appendixsubsubsec\>\|majorheading\>\|chapheading\>\|heading\>\|subheading\>\|subsubheading\>\)\)"
in buffer: tutorial.itely
      16:@chapter Tutorial
      29:    @section Compilació d'un fitxer
      44: @subsection Escriptura del codi d'entrada
      97:    @unnumberedsubsubsec Generació del resultat
     136: @subsection MacOS X
     145: @subsection Windows
     154: @subsection Línia d'ordres
     163:    @section Com escriure fitxers d'entrada
     176: @subsection Notació senzilla
     208:    @unnumberedsubsubsec Altures
     329:    @unnumberedsubsubsec Duracions (valors rítmics)
     380:    @unnumberedsubsubsec Silencis
     401:    @unnumberedsubsubsec Indicació de compàs
     427:    @unnumberedsubsubsec Indicacions de tempo
     459:    @unnumberedsubsubsec Clau
     496:    @unnumberedsubsubsec Tot a l'hora
     525: @subsection Treball sobre els fitxers d'entrada
     673:    @section Gestió dels errors
     688: @subsection Consells generals de solució de problemes
     699: @subsection Alguns errors comuns
     710:    @section Com llegir els manuals
     725: @subsection Material omès
     774: @subsection Exemples amb enllaç
     816: @subsection Panoràmica dels manuals

--->8---

Cheers,
Jean-Charles