lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: syntax changes before beta version


From: John Mandereau
Subject: Re: syntax changes before beta version
Date: Sat, 19 Jul 2008 18:11:31 +0200

On 2008/07/19 17:13 +0200, Reinhold Kainhofer wrote:
> The big disadvantage of using an external script to generate the file names 
> is 
> that I basically have to duplicate the code (for generating the file name and 
> deciding into which files to put the subsections) that is also in the 
> texi2html init file. Plus, I'll have to write a basic texinfo parser, too 
> (well, at least it needs to extract @node, @chapter, @(sub)*section, 
> @unnumbered((sub)*sec)?, @translationof, @include, @ignore, @ifhtml, and of 
> course all texinfo constructs used in any of the section titles...).

I see.  You can't avoid fully running texi2html unless you hack
texi2html itself.  This kind of issue will have to be solved in future
texi2html development.


> Yes, that would be great. Unfortunately, in Lilypond we are restrained to 
> using the released version, so for lilypond it will be a little more into the 
> future:(

It will be more in the future for all software anyway...


> > I generally agree about not hurrying too much.  I vote for merging
> > dev/texi2html into master as soon as the docs look good enough: no or
> > very few broken links, decent (even if non-perfect) graphical design.
> 
> hehe, which brings us to the point: Who is going to create the design?

As Graham has already proposed, just ask on -user :-)


> No, what I meant was that even if 2.12 was released before merging in 
> dev/texi2html, the online docs can always be replaced by the ones generated 
> by texi2html. I don't know how others work, but I mainly use the online docs 
> (at kainhofer.com/~lilypond/texi2html-out) when working with lilypond, rather 
> than locally installed docs.

dev/texi2html can be merged into stable/2.12 too; it has already been a
mess in early 2.10 releases, when I rewrote the HTML post-processing
scripts, locally installed docs had been completely broken for 2 weeks
and online docs had a lot of problems too, so I can't see this becoming
a real problem.


> Hmm, I thought the German and Spanish translations are basically complete 
> (maybe not right now for GDP, but at least for the latest released version)

Spanish translation of LM is actually the only complete translation, so
I should have a look at making a big HTML page of it sooner or later.

Cheers,
John





reply via email to

[Prev in Thread] Current Thread [Next in Thread]