Re: makeinfo with utf-8 support

2007-01-04 Thread Karl Hammar 
[EMAIL PROTECTED]:
> Le jeudi 04 janvier 2007 à 00:33 +0100, Karl Hammar a écrit :
> > Hmm, when building I get:
> > 
> >  out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'.
...
> > Does anybody know where the makeinfo with utf-8 support is, a patch ?
> 
> AFAIK Texinfo does no character encoding conversion for the Info and
> HTML output, so the LilyPond devels have decided to use the modern
> character set UTF-8, not Latin1. This will really become a problem for
> the PDF (outputted by Texinfo/TeX) when we decide to make PDF of Lily
> docs translation.
> 
> Well, you can safely ignore these warnings.
> 
> See also 
> http://lists.gnu.org/archive/html/lilypond-devel/2007-01/msg00047.html

Tried cvs version [1] of texinfo/makeinfo

  $ makeinfo --version
  makeinfo (GNU texinfo) 4.8.90

But the warning persist. Well, never mind.

Regards
/Karl

[1] http://savannah.gnu.org/cvs/?group=texinfo




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

Re: [Fwd: German translation help file]

2007-01-04 Thread Johannes Schindelin 
Hi,

On Wed, 3 Jan 2007, John Mandereau wrote:

> Till Rettig wrote:
> 
> > Do I now understand right that when problems emerge the git pull will 
> > save files under different names (or insert the problem signs, as you 
> > had it) and then you have to change them and make git update-index on 
> > the very file (this was in a message to Daniel T C. today). I think 
> > this is also an important remark, these kind of difficulties will 
> > probably appear to the beginner especially often. At least for me, if 
> > I changed I file that was already there and made the commit nothing 
> > happened. If I would git add it, then I get the mistake that the file 
> > is already added. Only with update-index I had success. But this might 
> > also be that my version of git is so old...
> 
> See my last message to Daniel Tonda C. about too old Git/Cogito
> versions.

Yes, this is a real problem. And I think that it is a pity this difference 
exists altogether (discussions revolve around cogito hiding the "index" of 
git, where most users of git will not see the index at all). But I think 
that the upcoming version of git will be a lot more user-friendly.

The thing to keep in mind is that you should only pull the upstream branch 
when you committed _all_ of your changes. So, "git status" is a very 
important command.

If you have conflicts, then these conflicts will be visible enclosed in 
conflict markers ("", "" and ""). To see if you resolved all 
conflicts, just do a "git diff" to see if there are still conflict 
markers. If there are no conflicts left, just do a "git commit -a" and it 
will automagically commit all, as a merge.

> Anyway, I think I was wrong to tell you to pull with web/master as local 
> name of the remote branch, whereas you may not already have this name. 
> Johannes?

That is why I keep stressing that you should pull "web/master:web/master" 
into your current branch, which should _not_ be named "web/master". If you 
do that, not only will the upstream "web/master" be merged (this is the 
left part, i.e. before the ":"), but the local branch "web/master" will be 
updated to the upstream version (this is the right part).

> > So this update-index was the only thing I find still somehow important, 
> > despite Johannes S. thinks it is not a good idea.
> 
> It's not a bad idea, it's only more complicated. When resolving
> conflicts, I don't know if there are other ways than using update-index.

$ git commit -a

commits all changes (of files git knows about). I think this is really 
easy, and telling people about update-index is only confusing.

Ciao,
Dscho



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

Re: new German patch

2007-01-04 Thread Johannes Schindelin 
Hi,

On Wed, 3 Jan 2007, Till Rettig wrote:

> so here comes the new German patch. As for now when making format-patch 
> I get three patches.

If you want just the last one, "git format-patch HEAD^" is what you want.

Ciao,
Dscho


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

disconnect coverage

2007-01-04 Thread Han-Wen Nienhuys 

Hi Erik,

browsing the coverage reports, I see

**
uncovered chunk in out-cov/score-performer.cc.gcov
   #:  77:Score_performer::disconnect_from_context ()
   -:  78:{
   #:  79:  Dispatcher *d = context ()->get_global_context 
()->event_source ();
   #:  80:  d->remove_listener (GET_LISTENER (one_time_step), 
ly_symbol2scm ("OneTimeStep"));
   #:  81:  d->remove_listener (GET_LISTENER (prepare), ly_symbol2scm 
("Prepare"));
   #:  82:  d->remove_listener (GET_LISTENER (finish), ly_symbol2scm 
("Finish"));
   -:  83:
   #:  84:  Performer_group::disconnect_from_context ();
   #:  85:}
uncovered chunk in out-cov/score-engraver.cc.gcov
   #: 103:Score_engraver::disconnect_from_context ()
   -: 104:{
   #: 105:  Dispatcher *d = context ()->get_global_context 
()->event_source ();
   #: 106:  d->remove_listener (GET_LISTENER (one_time_step), 
ly_symbol2scm ("OneTimeStep"));
   #: 107:  d->remove_listener (GET_LISTENER (prepare), ly_symbol2scm 
("Prepare"));
   #: 108:  d->remove_listener (GET_LISTENER (finish), ly_symbol2scm 
("Finish"));
   -: 109:
   #: 110:  Engraver_group::disconnect_from_context ();
   #: 111:}
**

it seems this is never executed. Can you check this out, and either 
remove the code, or fix it? 

-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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

Re: makeinfo with utf-8 support

2007-01-04 Thread Werner LEMBERG 

> Tried cvs version [1] of texinfo/makeinfo
> 
>   $ makeinfo --version
>   makeinfo (GNU texinfo) 4.8.90
> 
> But the warning persist. Well, never mind.

Please report this to bug-texinfo, together with a small example (if
possible).


Werner


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

Re: makeinfo with utf-8 support

2007-01-04 Thread Karl Hammar 
[EMAIL PROTECTED]:
> > Tried cvs version [1] of texinfo/makeinfo
> > 
> >   $ makeinfo --version
> >   makeinfo (GNU texinfo) 4.8.90
> > 
> > But the warning persist. Well, never mind.
> 
> Please report this to bug-texinfo, together with a small example (if
> possible).

Done.

Regards
/Karl




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

Re: position of staccato dots if above stems (some examples)

2007-01-04 Thread Graham Percival 

Wilbert Berendsen wrote:
I have added some examples. I think it would be a nice improvement. It also 
solves the beam collision, although that should be checked with other 
articulation signs as well.


I agree; added as
http://code.google.com/p/lilypond/issues/detail?id=218

Could you monitor that bug report?  Somebody may want more details of 
these scans (publisher/editor, exact piece names, etc).


Cheers,
- Graham


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

Re: disconnect coverage

2007-01-04 Thread Erik Sandberg 
On Thursday 04 January 2007 14:43, Han-Wen Nienhuys wrote:
> Hi Erik,
>
> browsing the coverage reports, I see
>
> **
> uncovered chunk in out-cov/score-performer.cc.gcov
>#:  77:Score_performer::disconnect_from_context ()
>-:  78:{
>#:  79:  Dispatcher *d = context ()->get_global_context
> ()->event_source (); #:  80:  d->remove_listener (GET_LISTENER
> (one_time_step), ly_symbol2scm ("OneTimeStep")); #:  81: 
> d->remove_listener (GET_LISTENER (prepare), ly_symbol2scm ("Prepare"));
> #:  82:  d->remove_listener (GET_LISTENER (finish), ly_symbol2scm
> ("Finish")); -:  83:
>#:  84:  Performer_group::disconnect_from_context ();
>#:  85:}
> uncovered chunk in out-cov/score-engraver.cc.gcov
>#: 103:Score_engraver::disconnect_from_context ()
>-: 104:{
>#: 105:  Dispatcher *d = context ()->get_global_context
> ()->event_source (); #: 106:  d->remove_listener (GET_LISTENER
> (one_time_step), ly_symbol2scm ("OneTimeStep")); #: 107: 
> d->remove_listener (GET_LISTENER (prepare), ly_symbol2scm ("Prepare"));
> #: 108:  d->remove_listener (GET_LISTENER (finish), ly_symbol2scm
> ("Finish")); -: 109:
>#: 110:  Engraver_group::disconnect_from_context ();
>#: 111:}
> **
>
> it seems this is never executed. Can you check this out, and either
> remove the code, or fix it?

They are there for completeness. I think the reason they are never called, is 
that score contexts aren't explicitly destroyed. I think this is because 
contexts below Score are destroyed during iteration, while scores themselves 
aren't (probably because they contain references to the typeset score, which 
is needed later). Scores and score-translators are therefore only removed by 
the GC, so the destructors are never executed.

I don't think this is a problem, and if we remove the code, we may create 
leaks if score translators can be connected/disconnected some time in the 
future.

-- 
Erik


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

Error in the spanish web site in es.po

2007-01-04 Thread Daniel Tonda 

Hi:

There's a link at the very bottom of the index file in the spanish web
site, which is the equivalent of the About automatic language
selection.

It appears:

Acerca deselección automática de idioma.
It should appear as:

Acerca de selección automática de idioma.

It's an error in the es.po file, I send here the patch to that file as
a gzipped text file:

I'm sort of getting the hang of this (git), very slowly, but there is progress!

--
Daniel Tonda C.


0001-A-space-added-in-es.po.txt.gz
Description: GNU Zip compressed data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

adding installation for windows in German

2007-01-04 Thread Till Rettig 

Hi,

I just found out that the installation advices for windows are not 
anymore cygwin, but windows. So I renamed the file and created a patch. 
Seems git works now for me (this time with the git format-patch HEAD^ -- 
shouldn't we add this also to the README, or does it only confuse people?).


Well, by the way, how is it about the installation of lilypond on 
windows and mac? Aren't there (at least for windows) extra binaries 
available via the download page, so you won't need to install the whole 
cygwin (which, if I remember correctly, is linux for windos)? Where is 
there some explanation about this? Its kind of by chance what you get... 
the clicker will find first the windows binary, but the one who read 
more will discover the "install instructions for windows" wonder, why he 
has to download 60mb and maybe will download this or then will he just 
stop installing this programm...


Or is there something I miss?

Greetings
Till
From dff5d173940a60b2385e8ec68d9a8742c560eddc Mon Sep 17 00:00:00 2001
From: Till Rettig <[EMAIL PROTECTED]>
Date: Thu, 4 Jan 2007 21:02:35 +0200
Subject: [PATCH] adding correct German windows.html
---
 de/install/windows.html |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/de/install/windows.html b/de/install/windows.html
index 725ae11..44a6c94 100644
--- a/de/install/windows.html
+++ b/de/install/windows.html
@@ -1,5 +1,5 @@

Re: disconnect coverage

2007-01-04 Thread Han-Wen Nienhuys 
Erik Sandberg escreveu:
> They are there for completeness. I think the reason they are never called, is 
> that score contexts aren't explicitly destroyed. I think this is because 
> contexts below Score are destroyed during iteration, while scores themselves 
> aren't (probably because they contain references to the typeset score, which 
> is needed later). Scores and score-translators are therefore only removed by 
> the GC, so the destructors are never executed.

No, that's incorrect. Removal of contexts is different reclaiming the memory.
Can you have a look at 

  Global_context::run_iterator_on_me

why the check_removal doesn't trigger for the Score context?

-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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

LilyPond suggestions

2007-01-04 Thread Jesse Engle 
Hi everyone. While I am a decent programmer, I have never been part of 
a large project such as this, so I would not know where to begin in 
attempting to add the following features that I've listed.


I am a drummer, and while I love that I can finally use free notation 
software instead of Finale for many melodic instruments, I've realized 
that the percussion features of LilyPond are lacking.


1) There is no way that I have yet discovered to notate rhythms for all 
four limbs, but this doesn't seem to be possible due to the fact that 
many drum set rhythms use overlapping stems. I have provided an example 
of this here:


http://jengle.waferbaby.com/tmp/lp/drnot.png

For reference, the bottom lines used are the bass drum and the hi-hat 
and the top two lines are the cymbal and snare drum. This example was 
notated by my uncle in MS Paint, in '96!


2) LilyPond does not provide ratio-notation for odd groupings. For 
instance, if I notate a group five sixteenths in the place of four 
sixteenths, I like to write "5:4" rather than just "5".


3) LilyPond will not bracket an odd grouping that is within an odd 
grouping correctly. The only way that LilyPond will notate the rhythm 
correctly is if the internal odd grouping is bracketed separately from 
the rest of the grouping. You may see what I mean in the following 
examples. The first one shows a grouping that looks better, separated 
by LilyPond, but is not correct.


http://jengle.waferbaby.com/tmp/lp/oddbetter.png

The second one shows what is intended (the entire grouping bracketed) 
but exemplifies how LilyPond fouls it up slightly with the "7", which 
should not overlap at all:


http://jengle.waferbaby.com/tmp/lp/oddbad.png

4.) There is no way to create an entire page of exercises (a feature 
that would be incredibly useful for music teachers such as myself) like 
this:


http://jengle.waferbaby.com/tmp/lp/exercises.png

I hope that I have shed some light on features or bugs that haven't 
been thought of or noticed before.


Jesse Engle



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

Re: LilyPond suggestions

2007-01-04 Thread Kieren MacMillan 

Hi, Jesse!


add the following features that I've listed.


No need -- everything can, I believe, already be done. Just read the  
relevant parts of the wonderful documentation.


For example

2) LilyPond does not provide ratio-notation for odd groupings.


Just use
\override TupletNumber #'text = #tuplet-number::calc-fraction-text

See  for more details.


With the possible exception of the particular multi-exercise page- 
layout suggestion, I would be *very* surprised if there is something  
on your list which isn't possible in the current version of  
Lilypond.  =)


Good luck!
Kieren.


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

Re: LilyPond suggestions

2007-01-04 Thread Michael Welsh Duggan 
Jesse Engle <[EMAIL PROTECTED]> writes:

> I am a drummer, and while I love that I can finally use free notation
> software instead of Finale for many melodic instruments, I've realized
> that the percussion features of LilyPond are lacking.
>
> 1) There is no way that I have yet discovered to notate rhythms for
> all four limbs, but this doesn't seem to be possible due to the fact
> that many drum set rhythms use overlapping stems. I have provided an
> example of this here:
>
> http://jengle.waferbaby.com/tmp/lp/drnot.png
>
> For reference, the bottom lines used are the bass drum and the hi-hat
> and the top two lines are the cymbal and snare drum. This example was
> notated by my uncle in MS Paint, in '96!

You may want to consider looking at the example at:

http://lilypond.org/doc/v2.11/input/regression/collated-files#drums.ly

If you click on the example, you will get the source code used to
produce it.

It looks to me like drummode is undocumented.  You can use the listed
example and the contents of .../ly/drumpitch-init.ly in order to
figure out what is happening.  In particular, use the value of
drumPitchNames in order to figure out the naming aliases, and the
various "styles" (such as drums-style) at the bottom of the file in
order to see how they are matched to head style, marking, and position.

Examples (based on a 5-line staff):

  (bassdrum () #f -3)  -> Normal notehead, no marking, -3
  offset from center

  (halfopenhihat xcircle #f 3) -> Circled-cross notehead, no marking,
  3 offset from center

  (openhihat cross "open" 3)   -> Cross notehead, "open" marking, 
  3 offset from center


The position is mapped from the center of the staff.  On a 5-line
staff, the positions are notated like this:

   5
-  4
   3
-  2
   1
-  0
  -1
- -2
  -3
- -4
  -5


On a 2-line staff, they are notated like this:

   2
-  1
   0
- -1
  -2

-- 
Michael Welsh Duggan
([EMAIL PROTECTED])


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

forbidding \glissando from being at a page break

2007-01-04 Thread Graham Percival 

With this code,
\relative c' {
  \repeat unfold 6 { c4 c c c }
  c1\glissando
  d'1
  \repeat unfold 7 { d4 d d d }
}

the \glissando occurs at a page break.  Is there any way to 
(automatically) force linebreaks to avoid this?


I currently have \glissando \noBreak everywhere in my music; I'm trying 
to eliminate the extra \noBreak commands.


Cheers,
- Graham


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

Re: LilyPond suggestions

2007-01-04 Thread Michael Welsh Duggan 
Michael Welsh Duggan <[EMAIL PROTECTED]> writes:

> It looks to me like drummode is undocumented.  You can use the listed
> example and the contents of .../ly/drumpitch-init.ly in order to
> figure out what is happening.  In particular, use the value of
> drumPitchNames in order to figure out the naming aliases, and the
> various "styles" (such as drums-style) at the bottom of the file in
> order to see how they are matched to head style, marking, and position.

I take this back.  This can be found in section 7.4.2 and section
7.4.3 of the manual: "Entering percussion", and "Percussion staves".

> Examples (based on a 5-line staff):
>
>   (bassdrum () #f -3)  -> Normal notehead, no marking, -3
>   offset from center
>
>   (halfopenhihat xcircle #f 3) -> Circled-cross notehead, no marking,
>   3 offset from center
>
>   (openhihat cross "open" 3)   -> Cross notehead, "open" marking, 
>   3 offset from center
>
>
> The position is mapped from the center of the staff.  On a 5-line
> staff, the positions are notated like this:
>
>5
> -  4
>3
> -  2
>1
> -  0
>   -1
> - -2
>   -3
> - -4
>   -5
>
>
> On a 2-line staff, they are notated like this:
>
>2
> -  1
>0
> - -1
>   -2

-- 
Michael Welsh Duggan
([EMAIL PROTECTED])


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

Re: LilyPond suggestions

2007-01-04 Thread Rune Zedeler 

Jesse Engle wrote:
1) There is no way that I have yet discovered to notate rhythms for all 
four limbs,


Where did you look?
http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Percussion-staves

2) LilyPond does not provide ratio-notation for odd groupings. For 
instance, if I notate a group five sixteenths in the place of four 
sixteenths, I like to write "5:4" rather than just "5".


Kieren covered this one.

3) LilyPond will not bracket an odd grouping that is within an odd 
grouping correctly.


Congratulations you found a bug.

4.) There is no way to create an entire page of exercises 


Sounds like you should use lilypondbook for this.

-Rune


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

Re: adding installation for windows in German

2007-01-04 Thread John Mandereau 
Le jeudi 04 janvier 2007 à 21:10 +0200, Till Rettig a écrit :
> I just found out that the installation advices for windows are not 
> anymore cygwin, but windows.

Where have you seen that???

>  So I renamed the file and created a patch. 
> Seems git works now for me (this time with the git format-patch HEAD^ -- 
> shouldn't we add this also to the README, or does it only confuse people?).

I suppose knowing how to make a patch against latest fetch of remote
branch (locally named web/master if you follow README from scratch), but
I may mention "git format-patch HEAD^" too. I'll also add a short
explanation about branches (what is a branch, remote/local branches).


> Well, by the way, how is it about the installation of lilypond on 
> windows and mac? Aren't there (at least for windows) extra binaries 
> available via the download page, so you won't need to install the whole 
> cygwin (which, if I remember correctly, is linux for windos)? Where is 
> there some explanation about this? Its kind of by chance what you get... 
> the clicker will find first the windows binary, but the one who read 
> more will discover the "install instructions for windows" wonder, why he 
> has to download 60mb and maybe will download this or then will he just 
> stop installing this programm...
> 
> Or is there something I miss?

cygwin.html and macos.html have not been updated for a while; macos.html
is clearly outdated, but cygwin.html is still valuable (Cygwin provides
2.10.7), so it should't be renamed to windows.html. You're right it
should be clearly mentioned there are 2 LilyPond flavours on Windows
(native and Cygwin).

Cheers
-- 
John Mandereau <[EMAIL PROTECTED]>



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

Backporting doc changes to stable/2.10 [was: Re: Docs check-translation]

2007-01-04 Thread John Mandereau 
Graham Percival wrote:
> For the backporting of docs, I'd just start by copying everything and 
> trying to build it with stable.  The skyline spacing docs obviously 
> won't work (so remove them from the backported docs), but AFAIK there 
> aren't any other new features in 2.11 that affect the docs.

Copying everything is an idea. I prefer making a patch with Git, so it
is easier to isolate changes and remove the hunks you don't want. That's
what I did.

Now, I must check with 'make web' before committing. Work in progress...
In the future, I'll try to sync doc improvements as they are committed.

Greetings
-- 
John Mandereau <[EMAIL PROTECTED]>



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

Re: adding installation for windows in German

2007-01-04 Thread till Rettig 


> 
> cygwin.html and macos.html have not been updated for a while; macos.html
> is clearly outdated, but cygwin.html is still valuable (Cygwin provides
> 2.10.7), so it should't be renamed to windows.html. You're right it
> should be clearly mentioned there are 2 LilyPond flavours on Windows
> (native and Cygwin).
Yes, sorry, I meant I just renamed the file cygwin.html into windows.html so it 
would be found with the link. This is the patch I sent.
Would be good to have also some installation advices in general, like about 
dependencies and so on (or how is that now, doesn't also the native windows 
version need gostscript?).

greetings
till

-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


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

Re: LilyPond suggestions

2007-01-04 Thread Mats Bengtsson 



Jesse Engle wrote:


4.) There is no way to create an entire page of exercises (a feature 
that would be incredibly useful for music teachers such as myself) 
like this:


http://jengle.waferbaby.com/tmp/lp/exercises.png

Actually, you could do this too within LilyPond, since you can use
\markup commands to create several columns and you can embed scores
into a \markup command. Here's a simple example:

\layout{
 ragged-right = ##t
}

\markup{
 \column{
   \score{\relative c'{ c4 d e f g f e d c1 }\layout{}}
   \score{\relative c'{ \key c \minor c4 d es f g f es d c1 }\layout{}}
 }
 \column{
   \score{\relative c'{ \key d \major d4 e fis g a g fis e d1 }\layout{}}
   \score{\relative c'{ \key c \minor d4 e f g a g f e d1 }\layout{}}
 }
}

You can easily fix the numbering, either by specifying in as an instrument
name or using markup commands.
However, as far as I know there is no way to specify a fixed line width 
for the
separate scores without at the same time specifying the same line width 
for the

full document (which doesn't make sense, of course).

To conclude; It is possible within LilyPond but probably much more 
convenient

to use lilypond-book in a two column LaTeX document.

  /Mats


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