headers
Trevor Daniels | 1 Feb 2009 13:35
Picon

Fw: \crescTextCresc... 2.10 vs 2.12


Forwarded for the archive ...

Trevor

----- Original Message ----- 
From: "Carl D. Sorensen" <c_sorensen <at> byu.edu>
To: "Trevor Daniels" <t.daniels <at> treda.co.uk>; "Frédéric Bron" 
<frederic.bron <at> m4x.org>
Sent: Saturday, January 31, 2009 9:36 PM
Subject: Re: \crescTextCresc... 2.10 vs 2.12

This sounds like a good Frog task to me.

There are a few things that need to be done before we make the patch.

1) Make a table of all the crescendo and decrescendo forms, so we can
see at a glance the missing/broken pieces.

2) Make a patch for the docs for v. 2.12.

3) Make a patch for v. 2.13 (when it's started) to get the appropriate
symmetry for all forms.  This will require posting the table from 1)
on -user and getting feedback from users.

4) Make a patch for convert-ly, which will do two things:
a) fix the problem you've identified for the previous convert-ly rule for
2.12
b) Make a correct convert-ly rule for 2.13.
(Continue reading)

Permalink | Reply | 501 comments |
headers
Graham Percival | 1 Feb 2009 14:08
Picon
Favicon

Re: Fw: \crescTextCresc... 2.10 vs 2.12

On Sun, Feb 01, 2009 at 12:35:22PM -0000, Trevor Daniels wrote:
> ----- Original Message ----- From: "Carl D. Sorensen" 
> <c_sorensen <at> byu.edu>
> To: "Trevor Daniels" <t.daniels <at> treda.co.uk>; "Frédéric Bron"  
> <frederic.bron <at> m4x.org>
> Sent: Saturday, January 31, 2009 9:36 PM
> Subject: Re: \crescTextCresc... 2.10 vs 2.12
>
>
> 2) Make a patch for the docs for v. 2.12.

Don't bother.

> Frederic, are you up for it?

The rest of the plans look great.

Cheers,
- Graham
Permalink | Reply | 501 comments |
headers
Graham Percival | 1 Feb 2009 14:09
Picon
Favicon

starting 2.13 soon

Has anything urgent happened since 2.12.2 was released?  I can't
think of anything.

Unless anybody complains within the next 48 hours, we'll switch to
2.13 and get started with all the major changes.  If somebody
complains, then we'll wait until 2.12.3 is out, and then move to
.13.

Cheers,
- Graham
Permalink | Reply | 12 comments |
headers
John Mandereau | 1 Feb 2009 18:20
Picon

Re: CG texi2html command

Hi Graham,
Graham Percival a écrit :
> How hard would it be to compile the CG with
>   --split=sections
> instead of the current setting?

I have the following in my compilation log on Jan 24th:

make[3]: Entering directory `/home/lilydev/git/lily/master/Documentation/devel'
cp -f contrib-guide.texi out-www/contrib-guide.texi
/home/lilydev/git/lily/master/scripts/build/out/extract_texi_filenames -o 
/home/lilydev/git/lily/master/out/xref-maps out-www/contrib-guide.texi
extract_texi_filenames.py: Processing out-www/contrib-guide.texi
mkdir -p out-www/contrib-guide/
texi2html -I /home/lilydev/git/lily/master/Documentation/user 
--I=/home/lilydev/git/lily/master/out/xref-maps  --I=. --I=./out-www 
--output=out-www/contrib-guide/ --prefix=index --split=section 
--init-file=/home/lilydev/git/lily/master/lilypond-texi2html.init 
out-www/contrib-guide.texi

I guess "--split=section" is ignored by our custom init file, so we should
reenable Texi2HTML defaults there if this option is caught.

Cheers,
John
Permalink | Reply | 0 comments |
headers
John Mandereau | 1 Feb 2009 18:22
Picon

Re: starting 2.13 soon

Graham Percival a écrit :
> Has anything urgent happened since 2.12.2 was released?  I can't
> think of anything.
> 
> Unless anybody complains within the next 48 hours, we'll switch to
> 2.13 and get started with all the major changes.

What major changes are expected?  Are there already significant changes that 
deserve switching to 2.13 very soon?  Minor syntax changes are not 
worthwhile IMHO.

Best,
John
Permalink | Reply | 1 comment |
headers
John Mandereau | 1 Feb 2009 18:39
Picon

Re: starting 2.13 soon

>> Yes, the Japanese translation.  I think it deserves a 2.12.3.
> 
> Good point.  OK, we'll wait a week or so.

That's perfect.

> Yes, that's totally my job.  Umm... do you mean about 2.12.2, or
> about 2.13 when that happens?

Talking from my little experience in announcing releases, it may be too late 
for posting to info-lilypond more than two days after the release is out, 
but I think an even late new item on lilypond.org is appropriate.

Cheers,
John
Permalink | Reply | 0 comments |
headers
Reinhold Kainhofer | 1 Feb 2009 19:13
Favicon
Gravatar

Re: starting 2.13 soon


On Sonntag, 1. Februar 2009 18:22:28 John Mandereau wrote:
> Graham Percival a écrit :
> > Has anything urgent happened since 2.12.2 was released?  I can't
> > think of anything.
> >
> > Unless anybody complains within the next 48 hours, we'll switch to
> > 2.13 and get started with all the major changes.
>
> What major changes are expected?  Are there already significant changes
> that deserve switching to 2.13 very soon?  Minor syntax changes are not
> worthwhile IMHO.

Since Graham does not allow any syntax changes (which require a convert-ly 
rule), I'm all for opening 2.13...

What I have for the new version are basically minor syntax changes, but 
strictly speaking, they change the syntax, so they are not allowed right now:
-) Fix reversed keySignature property alist (so the accidentals appear really 
in the order in which you give them)
-) Implement thick barline usingn \bar ".". Unfortunately \bar "." already 
existed and produced a pretty useless single dot, which I can't imagine was 
used anywhere, so strictly speaking that's a syntax change, too.

Cheers,
Reinhold
--

-- 
------------------------------------------------------------------
Reinhold Kainhofer, reinhold <at> kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Mandereau | 1 Feb 2009 19:50
Picon

Re: CG texi2html command

Hi Reinhold,
Reinhold Kainhofer a écrit :
> Do I understand it correctly, that for the CG, you want e.g. all subsections 
> of "1.1 Gettin the source code" in the same html file, all subsections of "1.2 
> Updating the source code" in another html file, etc.?

Yes.

> The quick and dirty fix would be to add a check for the manual name in the if 
> clause quoted above. However, I'd like to keep the .init file rather clean and 
> not add such special cases...

Agreed.

> However, the other part of our splitting algorithm is implemented in the 
> extract_texi_filenames.py script (which generates the file names for the 
> output html files), we might find a solution by tweaking that script, so it 
> places all subsections into the same html file...

Let's got for hacking extract_texi_filenames.py; unless you prefer to do it, 
I plan to do it before Wednesday.

Cheers,
John
Permalink | Reply | 1 comment |
headers
John Mandereau | 1 Feb 2009 20:32
Picon

Re: starting 2.13 soon

Graham Percival a écrit :
> IIRC there were already two patches that are waiting to be applied
> that were put off until 2.13.  Trevor was talking about
> reshuffling the text crescendo commands.

OK, this is probably enough to start 2.13 in one week.

>  I just finished
> unpacking today (yeah, 3.5 weeks after I arrived :)

This not so exaggerated in case you had to start studies just after you 
arrived :-)

I suck at the CG, I'll strive to do something an evening after midnight, I 
have no other free time next week (including next week-end).

> Most of all, the stability rule about 2.12 was imposed too quickly
> and came as a shock to most developers.  We'll have a much longer
> stable 2.14, but I think it's better to move to 2.13 sooner rather
> than later.  About a month ago, I said that we'd move to 2.13 at
> the beginning of Feb.

Oh yes, time has flown so quickly...

Cheers,
John
Permalink | Reply | 0 comments |
headers
Reinhold Kainhofer | 1 Feb 2009 20:34
Favicon
Gravatar

Re: CG texi2html command


On Sonntag, 1. Februar 2009 19:50:45 John Mandereau wrote:
> Reinhold Kainhofer a écrit :
> > However, the other part of our splitting algorithm is implemented in the
> > extract_texi_filenames.py script (which generates the file names for the
> > output html files), we might find a solution by tweaking that script, so
> > it places all subsections into the same html file...
>
> Let's got for hacking extract_texi_filenames.py; unless you prefer to do
> it, I plan to do it before Wednesday.

I took a quick look, and currently it is very much tied to our splitting 
algorithm (i.e. on each node, but place unnumbered sections and the like 
together with the previous section).
I'm attaching a patch to add a --split=MODE (or -s MODE) command-line option 
to the script as a starting point, but I haven't implemented its effect yet 
(in extract_sections and process_sections). I don't think I'll be able to 
implement it in the next few days, so I'll leave that to you ;)

Cheers,
Reinhold
--

-- 
------------------------------------------------------------------
Reinhold Kainhofer, reinhold <at> kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
Attachment (extract_texi_filenames-split-option.patch): text/x-patch, 1617 bytes
(Continue reading)






Permalink
| Reply
| 0 comments  
| 



  

  

  

  


  





    



Gmane