Re: lilypond documentation build issue (both 2.18.2 and 2.19.16)

2015-07-07 Thread Graham Percival
On Tue, Jul 07, 2015 at 12:22:27PM +0200, Dave Plater wrote:
 On 7/7/15, Dave Plater dplater.l...@gmail.com wrote:
  Oh, there's a pretty big chunk of custom stuff in lilypond
  texi2html.  See past discussion here:
  https://code.google.com/p/lilypond/issues/detail?id=1000

  is this issue likely to be resolved soon or is it as complex as the
  guile 2.x issue and I'm going to have to create texi packages to build
  the documentation?
  See https://bugzilla.novell.com/show_bug.cgi?id=936870

It's not as complex as guile 2.x.  If somebody has basic knowledge
of perl (which isn't hard to acquire) and texinfo (essentially
just knowing it's a doc format with @commands), and is good at
diagnosing and communicating problems, then I would cautiously
estimate 20 hours for this task.  10 hours of investigation and
rewriting by oneself, plus another 10 hours of creating minimal
examples, sending them to the texinfo list to ask for help, then
integrating the solutions into the updated thing.

This could very feasibly be done by somebody new to lilypond
development.

oh, two slight snags:
1) once it was updated to the new texinfo, our build scripts will
probably need some slight adjustment.  That is not do-able by
somebody new to lilypond, but I'd estimate 1 hour from a current
lilypond developer to get that done.

2) it is possible (or even likely) that texinfo will need to be
changed in order for us to do what we want.  I'm certain that if
somebody has a minimal example of the problem, and a compelling
justification for why we want to achieve the desired output, the
texinfo people will be happy to add whatever features or bugfixes
are required in texinfo.  But this *would* add another delay for
being able to build lilypond on a stock distribution with texinfo
5.x.
(that said, if I'm correct about requiring texinfo changes, this
will need to happen at some point so all the more reason to jump
on this now)

- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: lilypond documentation build issue (both 2.18.2 and 2.19.16)

2015-07-07 Thread Dave Plater
On 7/7/15, Dave Plater dplater.l...@gmail.com wrote:
 is this issue likely to be resolved soon or is it as complex as the
 guile 2.x issue and I'm going to have to create texi packages to build
 the documentation?
 See https://bugzilla.novell.com/show_bug.cgi?id=936870

 Regards
 Dave

 On 3/9/15, Graham Percival gra...@percival-music.ca wrote:
 On Mon, Mar 09, 2015 at 01:29:39PM +0100, David Kastrup wrote:
 Petr Gajdos pgaj...@suse.cz writes:
  If this is relevant, texi2html-5.0/texi2html.pl do not contain
  sub get_index in contrast of texi2html-1.82/texi2html.pl.

 Whoa.

 That one certainly looks like it will need attention soonish.  I did not
 realize that we had what amounts to such a large modification of
 texi2html in our code base.

 Oh, there's a pretty big chunk of custom stuff in lilypond
 texi2html.  See past discussion here:
 https://code.google.com/p/lilypond/issues/detail?id=1000

 Cheers,
 - Graham

 ___
 lilypond-devel mailing list
 lilypond-devel@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-devel


On 7/7/15, Dave Plater dplater.l...@gmail.com wrote:
 is this issue likely to be resolved soon or is it as complex as the
 guile 2.x issue and I'm going to have to create texi packages to build
 the documentation?
 See https://bugzilla.novell.com/show_bug.cgi?id=936870

 Regards
 Dave

Excuse this email mess, I'm forced to use gmail's web site.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: lilypond documentation build issue (both 2.18.2 and 2.19.16)

2015-03-09 Thread David Kastrup
Petr Gajdos pgaj...@suse.cz writes:

 On Fri, Mar 06, 2015 at 03:33:21PM +0100, Petr Gajdos wrote:
 On Fri, Mar 06, 2015 at 03:09:36PM +0100, David Kastrup wrote:
  So the problem is not one with fretted-strings.texi but rather with what
  causes your build procedure to run texi2pdf on it in the first place.
 
 Thanks for the pointer, will try to look in this direction.

 The issue in question begins sooner:

 $ cat internals.bigtexi.log 
 Undefined subroutine main::get_index called at
 /home/abuild/rpmbuild/BUILD/lilypond-2.18.2/Documentation/lilypond-texi2html.init
 line 2127.

 If this is relevant, texi2html-5.0/texi2html.pl do not contain
 sub get_index in contrast of texi2html-1.82/texi2html.pl.

Whoa.

That one certainly looks like it will need attention soonish.  I did not
realize that we had what amounts to such a large modification of
texi2html in our code base.

Reinhold, any idea how to proceed here?

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: lilypond documentation build issue (both 2.18.2 and 2.19.16)

2015-03-09 Thread Petr Gajdos
On Fri, Mar 06, 2015 at 03:33:21PM +0100, Petr Gajdos wrote:
 On Fri, Mar 06, 2015 at 03:09:36PM +0100, David Kastrup wrote:
  So the problem is not one with fretted-strings.texi but rather with what
  causes your build procedure to run texi2pdf on it in the first place.
 
 Thanks for the pointer, will try to look in this direction.

The issue in question begins sooner:

$ cat internals.bigtexi.log 
Undefined subroutine main::get_index called at
/home/abuild/rpmbuild/BUILD/lilypond-2.18.2/Documentation/lilypond-texi2html.init
line 2127.

If this is relevant, texi2html-5.0/texi2html.pl do not contain
sub get_index in contrast of texi2html-1.82/texi2html.pl.

Petr



signature.asc
Description: Digital signature
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: lilypond documentation build issue (both 2.18.2 and 2.19.16)

2015-03-09 Thread Graham Percival
On Mon, Mar 09, 2015 at 01:29:39PM +0100, David Kastrup wrote:
 Petr Gajdos pgaj...@suse.cz writes:
  If this is relevant, texi2html-5.0/texi2html.pl do not contain
  sub get_index in contrast of texi2html-1.82/texi2html.pl.
 
 Whoa.
 
 That one certainly looks like it will need attention soonish.  I did not
 realize that we had what amounts to such a large modification of
 texi2html in our code base.

Oh, there's a pretty big chunk of custom stuff in lilypond
texi2html.  See past discussion here:
https://code.google.com/p/lilypond/issues/detail?id=1000

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: lilypond documentation build issue (both 2.18.2 and 2.19.16)

2015-03-06 Thread Petr Gajdos
On Fri, Mar 06, 2015 at 03:09:36PM +0100, David Kastrup wrote:
  fretted-strings.texi2pdf.log reads:
 
 So the problem is not one with fretted-strings.texi but rather with what
 causes your build procedure to run texi2pdf on it in the first place.

Thanks for the pointer, will try to look in this direction.

Thanks,
Petr



signature.asc
Description: Digital signature
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: lilypond documentation build issue (both 2.18.2 and 2.19.16)

2015-03-06 Thread David Kastrup
Petr Gajdos pgaj...@suse.cz writes:

 Hello,

 please help me with debugging following build failure:

 https://build.opensuse.org/build/multimedia:apps/openSUSE_Factory/x86_64/lilypond-doc/_log

 fretted-strings.texi2pdf.log reads:

 ---
 
 This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/TeX Live
 for SUSE Linux)
  restricted \write18 enabled.
 entering extended mode
 (./fretted-strings.texi
 ./fretted-strings.texi:10: Undefined control sequence.
 l.10 @c \version
  2.19.2
 ? 
 ./fretted-strings.texi:10: Emergency stop.
 l.10 @c \version
  2.19.2
 ./fretted-strings.texi:10:  == Fatal error occurred, no output PDF
 file produc
 ed!
 Transcript written on fretted-strings.log.
 /usr/bin/texi2dvi: pdfetex exited with bad status, quitting.
 ---

 Interesting for me as texinfo noob is, that the failure happens while
 processing a comment.

Top-level Texinfo files generally start with a line

\input texinfo

and it is only that line that causes the file to be processed as a
Texinfo file.  fretted-strings.texi is not a toplevel info file and does
not contain such a line.  It is intended for inclusion by notation.texi
(generated from notation.tely).  If your build procedure is running
texi2pdf on fretted-strings.texi, nothing useful can come of that.

So the problem is not one with fretted-strings.texi but rather with what
causes your build procedure to run texi2pdf on it in the first place.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


lilypond documentation build issue (both 2.18.2 and 2.19.16)

2015-03-06 Thread Petr Gajdos
Hello,

please help me with debugging following build failure:

https://build.opensuse.org/build/multimedia:apps/openSUSE_Factory/x86_64/lilypond-doc/_log

fretted-strings.texi2pdf.log reads:

---
 
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/TeX Live
for SUSE Linux)
 restricted \write18 enabled.
entering extended mode
(./fretted-strings.texi
./fretted-strings.texi:10: Undefined control sequence.
l.10 @c \version
 2.19.2
? 
./fretted-strings.texi:10: Emergency stop.
l.10 @c \version
 2.19.2
./fretted-strings.texi:10:  == Fatal error occurred, no output PDF
file produc
ed!
Transcript written on fretted-strings.log.
/usr/bin/texi2dvi: pdfetex exited with bad status, quitting.
---

Interesting for me as texinfo noob is, that the failure happens while
processing a comment.

Please find exact versions of packages used for build in the log,
including texinfo-5.2.

Thanks!
Petr



signature.asc
Description: Digital signature
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: lilypond documentation build issue (both 2.18.2 and 2.19.16)

2015-03-06 Thread James Lowe
On 06/03/15 14:33, Petr Gajdos wrote:
 On Fri, Mar 06, 2015 at 03:09:36PM +0100, David Kastrup wrote:
 fretted-strings.texi2pdf.log reads:
 
 So the problem is not one with fretted-strings.texi but rather
 with what causes your build procedure to run texi2pdf on it in
 the first place.
 
 Thanks for the pointer, will try to look in this direction.
 
 Thanks, Petr
 

If it helps, also see:

http://lilypond.org/doc/v2.19/Documentation/usage/integrating-music-and-text

James


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel