from:"Fairchild"

See also LSR File Information http://lsr.dsi.unimi.it/LSR/Browse?s=50m=10
.

 - Bruce

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Toine Schreurs
Sent: Thursday, July 20, 2006 10:50 PM
To: Charles Cave
Cc: lilypond-user@gnu.org
Subject: Re: How to print the date and time in the footer of a score?


See (the thread of)
http://lists.gnu.org/archive/html/lilypond-user/2006-04/msg00141.html
and
http://lists.gnu.org/archive/html/lilypond-user/2006-06/msg00272.html

Toine Schreurs

 I would like to print the date and time in the footer of the score so I
can
 tell which of two printed copies is the most recent.
 
 I searched the Lilypond documentation (PDF) (I used version 2.8.3)
 for the word date and could not find any mention.  
 
 Printing dates and times in Word processing documents is a standard
 feature and I would like to do the same with Lilypond.
 
 By the way, I started using SubVersion to manage my scores under version
 control. 
 


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





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

font metric

In several places, documentation refers to font metric but I have not
found a syntax definition or an example of its use.  

Specifically, in the function: ly:font-filename font (given the font metric
font, return the corresponding file name) what is the syntax for font?

- Bruce






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

RE: Uniformly flat beam layer

Trevor -

LSR candidate?

If you agree and don't want to do it, say OK and I will.

 - Bruce

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Trevor Baca
Sent: Monday, July 17, 2006 11:36 PM
To: lilypond-user
Subject: Uniformly flat beam layer


Hi,

Here's a snippet to get a uniformly flat beam layer throughout a piece
or throughout a region of a piece.

%%% BEGIN SNIPPET %%%

\version 2.9.11

\new Staff {
   \override Stem #'direction = #down
   \override Beam #'positions = #'(-6 . -6)
   c'16[ d'16 e'16 f'16]
   c''16[ d''16 e''16 f''16]
}

%%% END SNIPPET %%%

The effect comes from setting Beam #'positions equal to some pair (m .
n) with m == n.

Classical engraving forbids this, of course, though there's something
a tendency here in highly parametric scores.

Thought I'd pass along into the archives ...

-- 
Trevor Bača
[EMAIL PROTECTED]
like the dew or like lightning




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

RE: Uniformly flat beam layer

Check it out: http://lsr.dsi.unimi.it/LSR/Item?u=1id=203

  - Bruce

-Original Message-
From: Trevor Baca [mailto:[EMAIL PROTECTED] 
Sent: Friday, July 21, 2006 12:56 PM
To: Fairchild; lilypond-user
Subject: Re: Uniformly flat beam layer

On 7/21/06, Fairchild [EMAIL PROTECTED] wrote:
 Trevor -

 LSR candidate?

 If you agree and don't want to do it, say OK and I will.

Buce,

Sure, go ahead!

Trevor.

 Hi,

 Here's a snippet to get a uniformly flat beam layer throughout a piece
 or throughout a region of a piece.

 %%% BEGIN SNIPPET %%%

 \version 2.9.11

 \new Staff {
\override Stem #'direction = #down
\override Beam #'positions = #'(-6 . -6)
c'16[ d'16 e'16 f'16]
c''16[ d''16 e''16 f''16]
 }

 %%% END SNIPPET %%%

 The effect comes from setting Beam #'positions equal to some pair (m .
 n) with m == n.

 Classical engraving forbids this, of course, though there's something
 a tendency here in highly parametric scores.

 Thought I'd pass along into the archives ...

 --
 Trevor Bača
 [EMAIL PROTECTED]
 like the dew or like lightning

-- 
Trevor Bača
[EMAIL PROTECTED]
... like the dew, or like lightning ...

Click here to call me:
http://try.click-and-connect.com/cnc/4/1753206736/

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

RE: Evolutionary User Strategery

Alexander -

Best proposal I've understood.  If/when implemented I see only two
continuing costs.  The user must maintain selected multiple versions - seems
reasonable.  Developers must make stable versions available in perpetuity,
but continuing support is not necessary - also seems reasonable.

Anybody willing and able to implement?

- Bruce

-Original Message-
From: Alexander Brock [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 17, 2006 3:42 PM
To: Fairchild
Cc: lilypond-user@gnu.org
Subject: Re: Evolutionary User Strategery


Hello,

 However, modifying 'finished' scores to be acceptable by the 
 latest version is not reasonable.  Upgrade modifications require 
 significant effort.  The convert-ly program helps, but misses a lot. 

One solution could be to write a wrapper which reads the \version and 
decides which installation of lilypond must be used. If there is no 
exact match just use the next higher version. That would increase 
execution time by something like 1/20sec on normal PCs.

Alexander





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

RE: Coexisting 2.8 with 2.4

2006-07-18 Thread Fairchild

Aha!  Not ecmr but ecrm.  I.e., the default seems to be ecrm10, slightly
different than cmr10.  Found the available list by searching for *.tfm
files.

Another year to find the 2.8 equivalent?

 - Bruce

-Original Message-
From: Fairchild [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 03, 2006 7:59 PM
To: 'Mats Bengtsson'
Cc: 'Karl Hammar'; 'lilypond-user@gnu.org'
Subject: RE: Coexisting 2.8 with 2.4


The attached pdf shows the 2.4 default font set and cmr10.  Doesn't seem to
be any ecmr10, at least not with \override TextScript #'font-name =
#ecmr10

  - Bruce

-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED] 
Sent: Sunday, July 02, 2006 3:56 PM
To: Fairchild
Cc: 'Karl Hammar'; lilypond-user@gnu.org
Subject: RE: Coexisting 2.8 with 2.4


The fonts in 2.4 belonged to the European Computer Modern family, i.e. 
a version of cmr extended with all Latin1 characters.
For lyrics, the bold-narrow version was used, but for text scripts and
titling it was ecmr as far as I can remember, so it should be identical to
cmr.

  /Mats

Quoting Fairchild [EMAIL PROTECTED]:

 Karl -

 Thanks for the pointers.

 I have many 2.4 scores with default font text tediously sized and 
 positioned, so would like to use, in 2.8, exactly the 2.4 default 
 font. I've been unable to determine what that is.  It looks very close 
 to, but not exactly, cmr10 (roman upright medium).

 - Bruce

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf 
 Of Karl Hammar
 Sent: Sunday, July 02, 2006 9:14 AM
 To: lilypond-user@gnu.org
 Subject: Re: Coexisting 2.8 with 2.4



 [EMAIL PROTECTED]:
 Quoting Fairchild [EMAIL PROTECTED]:
 ...
  3)  How to get the 2.4 default font in 2.8?

 In 2.4, the only(!?) available fonts were the TeX fonts. In 2.8, you 
 have access to all the fonts that are available in your other windows 
 programs. However, I'm not sure how to install the TeX fonts, so that
 they are found via the Pango library that LilyPond now uses.
 The question has popped up a number of times on the mailing list, but
 it seems that nobody has managed to do it, even though I'm sure
 it's fully possible if you know how it works.
 ...

 The most common TeX fonts are available as type1 fonts, see:

  http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfchoice

 Follow the links at the bottom.

 (Which font was used by lilypond 2.4, was it computer modern?) If you 
 are after the computer modern, get:

  http://www.tex.ac.uk/tex-archive/fonts/amsfonts/ps-type1/amsps-pc.zip

 Regards,
 /Karl




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





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









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

RE: How do you align a segno over a Repeat Sign?

2006-07-13 Thread Fairchild

Haven't stumbled on the terminology you want, but this snippet may show a
way to get the result you want.

%

{ R1*12 \bar ||: \break
\once\override Script   #'extra-offset = #'(4.0 . 4.0)
c''1 \segno R1*11 }

%

Seems \segno won't attach to a rest.

HTH

- Bruce

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Saturday, July 01, 2006 6:34 PM
To: lilypond-user@gnu.org
Subject: Re: How do you align a segno over a Repeat Sign?


Remove the \once ... line which is what is causing the offset?

No it's not causing the offset, because it doesn't even work.  The code is
wrong in that line.  When it is commented out the Segno Sign is to the right
of the repeat sign on top of a chord symbol.  I need to move it to the left
and up.  Perferable on top of the repeat sign.  But I don't know the correct
terminology to address the segno sign to offset it.  

-Original Message-
From: Paul Scott [EMAIL PROTECTED]
Sent: Jul 1, 2006 3:25 PM
To: [EMAIL PROTECTED]
Cc: lilypond-user@gnu.org
Subject: Re: How do you align a segno over a Repeat Sign?

[EMAIL PROTECTED] wrote:
 % 
 % Beginning of the actual notation code
 %  
 % Melody - Line 1
 R1*12 \bar || \break
 \once \override Score.RehearsalMark scripts.segno #'extra-offset =
#'(-2.0 . 0.0)
 \mark \markup { \musicglyph #scripts.segno } \bar |:

 Right now the Segno is to the right of the Repeat sign
 Ideally I would like it over the top.

 I don't know the correct terminologly and after researching the docs, I
haven't come up with anything either.
Remove the \once ... line which is what is causing the offset?

Paul Scott





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





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

RE: Evolutionary User Strategery

2006-07-10 Thread Fairchild

Erik -

Thanks for contributing to this thread.  It is attempting to deal with an
important unresolved issue: seamless evolutionary transitioning of ly files.

Your suggested solution requires n versions residing entirely in the
user's machine, which would, as you point out, increase resident code by a
factor of n.  The code switching option requires parallel code only for
features that are interpreted differently for different versions, only
marginally increasing the size of the newer versions - far less size, and
hassle, than retaining several versions.

Marginally increasing the single package size is not a concern.  Through the
generations, memory and speed have increased to accommodate applications -
or maybe the other way around.  The first computer I used had 2000
bi-quinary ten-digit words on a drum.  Long-term memory was punched cards.
It was a fantastic improvement over its predecessor, the Card Programmed
Calculator.

Increasing processing time is a consideration, but testing a flag to select
from version-specific code segments would be barely measurable.

 - Bruce

-Original Message-
From: Erik Sandberg [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 10, 2006 3:12 AM
To: Fairchild
Cc: lilypond-user@gnu.org
Subject: Re: Evolutionary User Strategery


On 7/9/06, Fairchild [EMAIL PROTECTED] wrote:
 New scores could use new features and not have to work around the bugs 
 of earlier versions.  Older scores that have been carefully tuned, 
 compensating for earlier bugs, would continue to produce the intended 
 result without having to be overhauled.  There would be no need to 
 maintain multiple versions.

This basically implies that all old versions of lily must be included in the
new versions, so e.g. lilypond 2.10 will contain both version 2.10, 2.8, 2.6
and 2.4. Which means that the lilypond package grows by a factor 4. I think
a better solution would be that you create a script locally, which parses
the input ly file, reads the \version statement, and picks which lilypond
version to use to compile your ly file.

Erik





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

RE: Evolutionary User Strategery

2006-07-10 Thread Fairchild

I wonder if the varied opinions represented in this thread are based in
differing interests and ways Lily is used.

The developer's interest is in usability of the latest stable version.

A composer's interest is in an elegant score presentation of a very few
scores, maybe never changing when 'finished'.

I have talent for neither.  I'm attempting to transcribe many public domain
compositions and make many of them publicly available.   A set of such
scores takes me months to years to complete.  I expect to provide both the
ly source and pdf result.  Without upward compatibility, these are obsolete
before they are ready for posting.  Mutopia suffers from such obsolescence.

I also use Lily to transpose published charts for my personal use, finding
ways to improve them as they are used.

So I represent a user quite different from a composer.  Spending time to
repetitively adapt many ly files is overly burdensome.

- Bruce

-Original Message-
From: Simon Dahlbacka [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 10, 2006 10:24 AM
To: Fairchild
Cc: lilypond-user@gnu.org
Subject: Re: Evolutionary User Strategery


Bruce, sorry to be rude but:

Being forced to absolute backward compatibility sucks, and having to keep
compatibility with e.g. 2.4 2.6 and 2.8 sucks even more, and makes the code
base bloated, less maintainable and probably a lot of #ifdefs of what not
that leads to more bugs..

Put it another way, you don't want to write your .ly files in such a way
that you can use whatever lilypond version to compile them and get a
perfect result. The developers most certainly does not want absolute
backwards compatibility, and they even bother so much as to provide
convert-ly to make the transition forward easier. Whose arguments do you
thing weigh more? Most developers develop lilypond in their spare time just
for the fun of it for all I know..

After all, this is free software, if you like, you can make your own
compatible-with-everything-even-all-the-bugs fork project..

/S

On 7/10/06, Fairchild [EMAIL PROTECTED] wrote:
 Erik -

 Thanks for contributing to this thread.  It is attempting to deal with 
 an important unresolved issue: seamless evolutionary transitioning of 
 ly files.

 Your suggested solution requires n versions residing entirely in the 
 user's machine, which would, as you point out, increase resident code 
 by a factor of n.  The code switching option requires parallel code 
 only for features that are interpreted differently for different 
 versions, only marginally increasing the size of the newer versions - 
 far less size, and hassle, than retaining several versions.

 Marginally increasing the single package size is not a concern.  
 Through the generations, memory and speed have increased to 
 accommodate applications - or maybe the other way around.  The first 
 computer I used had 2000 bi-quinary ten-digit words on a drum.  
 Long-term memory was punched cards. It was a fantastic improvement 
 over its predecessor, the Card Programmed Calculator.

 Increasing processing time is a consideration, but testing a flag to 
 select from version-specific code segments would be barely measurable.

  - Bruce

 -Original Message-
 From: Erik Sandberg [mailto:[EMAIL PROTECTED]
 Sent: Monday, July 10, 2006 3:12 AM
 To: Fairchild
 Cc: lilypond-user@gnu.org
 Subject: Re: Evolutionary User Strategery


 On 7/9/06, Fairchild [EMAIL PROTECTED] wrote:
  New scores could use new features and not have to work around the 
  bugs of earlier versions.  Older scores that have been carefully 
  tuned, compensating for earlier bugs, would continue to produce the 
  intended result without having to be overhauled.  There would be no 
  need to maintain multiple versions.

 This basically implies that all old versions of lily must be included 
 in the new versions, so e.g. lilypond 2.10 will contain both version 
 2.10, 2.8, 2.6 and 2.4. Which means that the lilypond package grows by 
 a factor 4. I think a better solution would be that you create a 
 script locally, which parses the input ly file, reads the \version 
 statement, and picks which lilypond version to use to compile your ly 
 file.

 Erik





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






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

Directory in Windows

2006-07-10 Thread Fairchild

Title: Directory in Windows






In the version 2.8.5 installation this portion of the tree contains no files at any level:


. . . \Users\lilytest\testing\gub-devel\target\mingw\install\gcc-root\usr\cross\i686-mingw32\lib\debug


Anybody know why? Just curious.


 - Bruce



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

RE: Evolutionary User Strategery

2006-07-09 Thread Fairchild

New scores could use new features and not have to work around the bugs of
earlier versions.  Older scores that have been carefully tuned, compensating
for earlier bugs, would continue to produce the intended result without
having to be overhauled.  There would be no need to maintain multiple
versions.

- Bruce

-Original Message-
From: Erik Sandberg [mailto:[EMAIL PROTECTED] 
Sent: Saturday, July 08, 2006 3:55 PM
To: Fairchild
Cc: lilypond-user@gnu.org
Subject: Re: Evolutionary User Strategery


On Saturday 08 July 2006 18:58, Fairchild wrote:
 The 3.0 processor could note the 2.4 version flag and treat the ly 
 file in the 2.4 way, maintaining upward compatibility without a need 
 for convert-ly.

In what way would that be different from installing two different versions
of 
lily? If you don't want the bugfixes from 3.0, why do you upgrade to 3.0?

-- 
Erik






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

RE: Evolutionary User Strategery

2006-07-09 Thread Fairchild

Kieren -

With all due respect - and you are due a lot.  The work you did on my score
is impressive, especially that you did it so quickly.

My home made header was for two overwhelming reasons.  First, \header code
could only be used once.  Second, I found no way to override the default
vertical positioning and font.  When I started, \header didn't allow
embedded \markup.  This is a good example where newer capabilities are
welcome, but old code should survive.

As a learning experiment, I've set about to code Stances in the your style
for 2.4.6, then see what needs to change for 2.8.5.  I've spent about an
hour just trying to convert the title line, not succeeding yet.

 - Bruce 

-Original Message-
From: Kieren MacMillan [mailto:[EMAIL PROTECTED] 
Sent: Sunday, July 09, 2006 10:51 AM
To: Fairchild
Cc: [EMAIL PROTECTED]; lilypond-user@gnu.org
Subject: Re: Evolutionary User Strategery


Bruce:

 Older scores that have been carefully tuned, compensating for
 earlier bugs

With all due respect, this implies something about Lilypond that  
simply isn't true.

Carefully tuned is one thing. My scores are also carefully tuned;  
from your work I've seen so far, I dare say I'm far more obsessive- 
compulsive than you in my engraving standards. Nothing personal, mind  
you: I'm the most OC engraver I've ever met!  ;-)

That being said, I spent over an hour cleaning up your bug- 
compensating code yesterday, as an instructional example. What you  
were (are) doing -- e.g., adding title information directly to  
skipped notes in a \partial bar before the music actually begins, and  
then filling the \markup code with offset and spacing tweaks to move  
it back where it really belongs (i.e., in the header and not attached  
to the music) -- does not [compensate] for earlier bugs. It's poor  
coding, plain and simple.

Are there bugs in older (and current) versions of Lilypond?  
Absolutely. Will many be fixed in upcoming versions? I sure hope so.

Ironically, the way that the header block acts as a music system is  
one of the things I hope changes in a future version... but the fact  
that my titles are all *in* headers already (instead of counter- 
intuitively attached to invisible notes between the key signature and  
the first visible note of my score) will make the migration very easy  
for me, if and when it happens.

Based on the example of your work I helped you with, my conservative  
estimate is that 90% of your migration woes would disappear if you  
just wrote proper Lilypond code. I think it's quite telling that,  
like most on this list, I've had essentially no problems moving  
forward with Lilypond as it evolves and improves (n.b., I started  
with v1.8), and you apparently have had nothing but headaches.

Ultimately, I would feel it a great loss if HW et al. decided to  
allow Lilypond to become bloatware in some vain quest for the  
Backwards Compatibility Grail.

Fortunately, I know they're too smart to do that.  =)

Regards,
Kieren.

p.s. When Microsoft ruined Word for Mac v5.1 by improving it (v6.0  
and beyond), I didn't upgrade -- perhaps you might consider taking  
the same approach with Lilypond?





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

RE: Evolutionary User Strategery

2006-07-08 Thread Fairchild

The 3.0 processor could note the 2.4 version flag and treat the ly file in
the 2.4 way, maintaining upward compatibility without a need for convert-ly.

   - Bruce

-Original Message-
From: Erik Sandberg [mailto:[EMAIL PROTECTED] 
Sent: Saturday, July 08, 2006 5:08 AM
To: lilypond-user@gnu.org
Cc: Fairchild
Subject: Re: Evolutionary User Strategery

On Friday 07 July 2006 16:46, Fairchild wrote:
 LilyPonders -

 The only reasonable solution is to maintain upward compatibility in 
 the LilyPond processor.  New features should be added without changing 
 existing syntax.  If it is deemed absolutely necessary to change 
 semantics or define conflicting syntax, provide for optional 
 interpretations based on the version specified.  Older ly files should 
 generate consistent results as LilyPond migrates.  More exhaustive 
 regression tests are necessary.

This one is not possible either: Let's say that you typeset a score in v2.4,

and that lily, due to a bug, makes some text collide with some notes. Let's 
say that you work around this by tweaking the extra-offset of the text. If 
now the bug is fixed in v3.0, your text will look ugly when compiled in 3.0,

and you will have to remove the tweak manually, regardless of how clever 
convert-ly is.

Conclusion: Full backward compatibility is not desirable.

-- 
Erik

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

Evolutionary User Strategery

2006-07-07 Thread Fairchild

Title: Evolutionary User Strategery

LilyPonders -

Users dealing with LilyPond as it evolves are presented with difficult choices, none good.

If one knows a score will be completed quickly, never be revisited, and components of the code structure never will be reused, the choice is easy: save and share graphics only, dump the ly files for completed scores, and move on to the latest stable version. I'm not that prescient.

Constantly adopting the latest version allows use of the latest features, feedback helps the developers, and the developers provide support. However, modifying 'finished' scores to be acceptable by the latest version is not reasonable. Upgrade modifications require significant effort. The convert-ly program helps, but misses a lot.

It is tempting to select a stable version and stick with it. Scores can be revisited easily. Syntax and semantics are stable. Downside: the feature set never gets better and support will fade away unless a sufficient number of users make the same choice and help each other.

It is possible to maintain multiple LilyPond versions. This allows revisiting old scores, but at a price. The operational environment becomes more and more confusing as versions accumulate.

I have coded tens of scores, most with version 2.4.6, and spent several hours attempting to move just one (a smaller one) of them to 2.8.5. After using convert-ly and correcting for its errors, much remains to be done, especially to position the right text font. Conclusion: repetitive conversion of scores is untenable.

The only reasonable solution is to maintain upward compatibility in the LilyPond processor. New features should be added without changing existing syntax. If it is deemed absolutely necessary to change semantics or define conflicting syntax, provide for optional interpretations based on the version specified. Older ly files should generate consistent results as LilyPond migrates. More exhaustive regression tests are necessary.

If you can identify a better way, or have other comments, please respond.

- Bruce

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

RE: Reading the fine manual.. hint [was Re: MultiMeasureRest - trying tobe clever ...]

2006-07-07 Thread Fairchild

Title: Message



In Adobe Reader 
it is necessary to switch from Hand Tool to Text Tool to copy text (Tools - 
Basic - Select Text). Note that the apostrophe doesn't copy to please 
Lily.

 
 
- Bruce

  
  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Simon DahlbackaSent: Wednesday, July 05, 2006 2:58 
  AMTo: Anthony YoungmanCc: 
  lilypond-user@gnu.orgSubject: Reading the fine manual.. hint [was 
  Re: MultiMeasureRest - trying tobe clever ...]
  
  And 
no disrespect, but I think Thibault is spot on with his firstsentence. 
The lilypond documentation is the size of a small novel! Finding what 
you're looking for isn't easy.
  Personally, I find it easier to work with the one page html version 
  and just let the browser search for hopefully good keywords. (The pdf 
  version does not work as well due to the search being slower and I cannot seem 
  to copy text from it..) /Simon 

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

RE: Coexisting 2.8 with 2.4

2006-07-04 Thread Fairchild

** Karl -

** Thanks for the response.  See ** below.

**  - Bruce

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Karl Hammar
Sent: Tuesday, July 04, 2006 12:03 PM
To: lilypond-user@gnu.org
Subject: Re: Coexisting 2.8 with 2.4 

[EMAIL PROTECTED]:
 The attached pdf shows the 2.4 default font set and cmr10.  Doesn't 
 seem to be any ecmr10, at least not with \override TextScript 
 #'font-name = #ecmr10
 
   - Bruce
...

Please don't toppost or cc me, I'm on the list.

** Necessary to bypass the moderator.

A quick look through your pdf gives me that you are showing the 
difference between the original TeX encoding (OT1) and the newer one 
with latin-1 characters (T1, dc, ec or cork encoding).

The glyphs seem to be identical.

Your problem above is that you cannot refer to the font 
with ecmr10. You have them somewhere since lilypond uses them.

** That's what I have thought.  Any idea what the file name is, where it
lives, or how to access it if the default is changed?

Use the link provided earlier to get the corresponding type1 fonts.

** I'm font-challenged.  Other than the links you have provided, can you
recommend an educational source?

Regards,
/Karl




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





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

RE: Coexisting 2.8 with 2.4

2006-07-02 Thread Fairchild

Karl -

Thanks for the pointers.

I have many 2.4 scores with default font text tediously sized and
positioned, so would like to use, in 2.8, exactly the 2.4 default font.
I've been unable to determine what that is.  It looks very close to, but not
exactly, cmr10 (roman upright medium).

 - Bruce

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Karl Hammar
Sent: Sunday, July 02, 2006 9:14 AM
To: lilypond-user@gnu.org
Subject: Re: Coexisting 2.8 with 2.4 



[EMAIL PROTECTED]:
 Quoting Fairchild [EMAIL PROTECTED]:
...
  3)  How to get the 2.4 default font in 2.8?
 
 In 2.4, the only(!?) available fonts were the TeX fonts. In 2.8, you
 have access to all the fonts that are available
 in your other windows programs. However, I'm not sure how to install 
 the TeX fonts, so that
 they are found via the Pango library that LilyPond now uses.
 The question has popped up a number of times on the mailing list, but 
 it seems that nobody has managed to do it, even though I'm sure
 it's fully possible if you know how it works.
...

The most common TeX fonts are available as type1 fonts, see:

  http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfchoice

Follow the links at the bottom.

(Which font was used by lilypond 2.4, was it computer modern?)
If you are after the computer modern, get:

  http://www.tex.ac.uk/tex-archive/fonts/amsfonts/ps-type1/amsps-pc.zip

Regards,
/Karl




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





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

RE: Coexisting 2.8 with 2.4

2006-07-02 Thread Fairchild

Mats -

Thanks for your usual thoughtful response.

IMO, at 2.4 LilyPond achieved four stars.

Many have invested extensive effort in creating quality scores with various
versions.  To encourage upgrading there should be some automated mechanism
for upward compatibility, or earlier versions should be supported.

The string replacement capabilities in convert-ly are useful, but far from
adequate.

While added Lily features are welcome, many changes are effort-consuming to
convert with no apparent gain.  An trivial example: \markup { \column  {A
B } { C D }  }  has changed syntax and result.

See ** inserts below.

 - Bruce

-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED] 
Sent: Sunday, July 02, 2006 7:21 AM
To: Fairchild
Cc: 'Thomas Scharkowski'; lilypond-user@gnu.org
Subject: RE: Coexisting 2.8 with 2.4


Quoting Fairchild [EMAIL PROTECTED]:

 Thomas, et. al. -

 Successfully installed 2.8.5-1.  Some findings and questions:

 1)  2.8 adds to the PATH at installation - doesn't seem necessary.

Maybe not if you only access it via jEdit, but it's certainly very
convenient if you want to call LilyPond from a command prompt. Not to
mention if you want to use midi2ly or convert-ly or any of the 
other programs that you can't reach via any menu or double-clicking.

** Yes, but.  It would be polite to ask or inform, not change the PATH
surreptitiously.


 2)  2.8 changes the ly file association and icon - annoying.

The file association and icon (which you can drag your .ly files
to) is very convenient for the 99% of LilyPond users who don't want to have
multiple versions installed at the same time (or maybe I 
missed what you found annoying).

** Clicking an ly file should open in an editor of choice, not initiate
processing - my opinion.

** Not for the desktop shortcut icon - for ly files.  An icon was assigned.
Why change it?

 3)  How to get the 2.4 default font in 2.8?

In 2.4, the only(!?) available fonts were the TeX fonts. In 2.8, you 
have access to all the fonts that are available
in your other windows programs.

** Including the TeX fonts?

 However, I'm not sure how to install 
the TeX fonts, so that
they are found via the Pango library that LilyPond now uses. The question
has popped up a number of times on the mailing list, but 
it seems that nobody has managed to do it, even though I'm sure it's fully
possible if you know how it works.

 4)  Trying to set up a second jEdit doesn't seem possible.  Don't try 
 it naively - the result is confusing to unwind.

 5)  Don't find a flavor switch in LilyTool 0.2.8.  Haven't upgraded to 
 0.2.9.

 6)  Thanks for the suggestion to use the command line - awkward but 
 tolerable - it works sometimes - sometimes Lily crashes - haven't 
 nailed a discriminator.

 7)  What's a correct command line to get dvi?  Using  . . . 
 usr/bin/lilypond-windows.exe -b=tex --dvi test finds an error in 
 init.ly.

The TEX and DVI back-ends are more or less unsupported. Why would you want
the DVI.

** Point-and-click and convenient preview from jEdit.

 8)  Why the move to 'native' from cygwin?  What is gained?  Seems 
 development talent would be more productive sweeping jEdit cobwebs.

The reason was that it was too complicated to make the cygwin version work.
The cygwin maintainer gave up and nobody else volounteered to 
take over. Also, it seems that it's very easy for Han-Wen and Jan to produce
the new native package together with all the other versions as soon as they
release a new version.

Please search the mailing list archives for more details on all these
questions. Most of them actually relate to what happened at version 2.6.


   /Mats






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

RE: Coexisting 2.8 with 2.4

2006-07-02 Thread Fairchild

Graham -

Some convert-ly experience, on the file just submitted to LSR as File
Information.  2.4.6 to 2.8.5.

Finding a way to execute convert-ly took several hours of stumbling around.
Haven't succeeded from jEdit.  Expected to find an .exe file.  A way that
works is to invoke with a DOS shell from the directory that contains
convert-ly.py and python.exe (and/or python2.4.exe?).  Documented?

Some details:
- Correctly changed \column  to \column { 
- Incorrectly changed a  to } in scheme code
- Got a second set correctly
- The command-line has changed from
   (lilypond /cygdrive/C/ . . . /file.ly)
to
   (C:\\lilypond\\usr\\bin\\lilypond-windows.exe file.ly)
   so must be analyzed differently to extract the file name.
   Difficult to convert, but ought to be flagged or documented.
- The string 'strftime %T' must be changed to 'strftime %H:%M:%S'.  The
shortcut doesn't work in 2.8.5.  LilyBug?
- \line isn't inserted where required.  Documented.  A biggie.
- Fonts, vertical spacing and horizontal spacing are quite different.  A
show stopper.  See attached files.

  - Bruce (Also wondering The reason why)

-Original Message-
From: Graham Percival [mailto:[EMAIL PROTECTED] 
Sent: Sunday, July 02, 2006 12:55 PM
To: Fairchild
Cc: lilypond-user@gnu.org
Subject: Re: Coexisting 2.8 with 2.4


Fairchild wrote:
 Many have invested extensive effort in creating quality scores with 
 various versions.

The guidelines for writing lilypond files section of the manual attempts
to mitigate this.  By writing lilypond files carefully, you can reduce the
problems associated with upgrading versions.

  To encourage upgrading there should be some automated mechanism for 
 upward compatibility, or earlier versions should be supported.
 
 The string replacement capabilities in convert-ly are useful, but far 
 from adequate.

Additional support for older versions requires more effort.  There are three
reasons that people work on lilypond:
1)  Getting paid for a specific features.  (see the sponsoring links)
2)  Solving a personal problem (ie if I were a programmer and were annoyed
by a bug, I could fix the bug and send my patch in).
3)  Contributing due to a vague sense of owing something to the community.
(such as basically all my doc work)

You might argue that all the developers have an obligation to maintain the
input syntax (under #3), but Han-Wen has always been clear that the input
format may change from time to time.  In addition, Erik has been working on
a system which avoids the problem of the changing input syntax.  This should
be available in lilypond 2.10.


Having just updated from 2.4, perhaps you could help to fill in this 
documentation.  According to these docs, the only change that convert-ly 
  cannot handle between 2.4 and 2.8 is the \markup issue and utf-8 
characters.  I'm sure that there are more problems than that, but I 
don't know what they are.

http://lilypond.org/doc/v2.9/Documentation/user/lilypond/Updating-files-with
-convert_002dly.html

 The TEX and DVI back-ends are more or less unsupported. Why would you 
 want the DVI.
 
 ** Point-and-click and convenient preview from jEdit.

Point-and-click now works for ps, and I believe even pdf.  I don't know 
how this fits in with jEdit.

Cheers,
- Graham



FileInfo28.pdf
Description: Adobe PDF document


FileInfo24.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

RE: Coexisting 2.8 with 2.4

2006-07-01 Thread Fairchild

Thomas, et. al. -

Successfully installed 2.8.5-1.  Some findings and questions:

1)  2.8 adds to the PATH at installation - doesn't seem necessary.

2)  2.8 changes the ly file association and icon - annoying.

3)  How to get the 2.4 default font in 2.8?

4)  Trying to set up a second jEdit doesn't seem possible.  Don't try it
naively - the result is confusing to unwind.

5)  Don't find a flavor switch in LilyTool 0.2.8.  Haven't upgraded to
0.2.9.

6)  Thanks for the suggestion to use the command line - awkward but
tolerable - it works sometimes - sometimes Lily crashes - haven't nailed a
discriminator.

7)  What's a correct command line to get dvi?  Using  . . .
usr/bin/lilypond-windows.exe -b=tex --dvi test finds an error in init.ly.

8)  Why the move to 'native' from cygwin?  What is gained?  Seems
development talent would be more productive sweeping jEdit cobwebs.

9)  Your signature tag implies you juggle three LilyPond versions.  How?

TIA for any insights.

- Bruce

-Original Message-
From: Thomas Scharkowski [mailto:[EMAIL PROTECTED] 
Sent: Saturday, July 01, 2006 4:15 AM
To: [EMAIL PROTECTED]
Cc: lilypond-user@gnu.org
Subject: Re: Coexisting 2.8 with 2.4


 I don't see how jEdit can handle both.  Two incarnations of jEdit? Can 
 one instantiation easily flip among multiple installed LilyPond 
 versions?  Alt-l now executes 2.4.  Is there a way to set another 
 shortcut, say Alt-y, to execute 2.8?  (Using jEdit 4.2 and LilyTool
 0.2.8.)
...

  - Bruce
I don't remember for Lilytool 0.2.8, but in 0.2.9 you can choose 
between native and cygwin flavours of LilyPond (Plugin Options).

You can use different windows native versions with jEdit if you 
specify the full path to lilypond each time you change. 
Or you could use the jEdit command window history and change the path 
there.

Hope this helps,

Thomas
--
Windows XP
jEdit 4.2
LilyTool 0.2.9
LilyPond 2.8.5 (native Windows)
LilyPond 2.9.10 (native Windows)
LilyPond 2.4.6 (cygwin)
:-)





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

RE: LSR Execution? Failure

2006-07-01 Thread Fairchild

LSR Execution Success!!!

Several exciting hours beat 2.8 to submission, almost.

See File Information in LSR.

- Bruce

-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 30, 2006 7:10 AM
To: Fairchild
Cc: lilypond-user@gnu.org
Subject: Re: LSR Execution? Failure


Please, this is a very tedious method for your and everybody else to help
you debug .ly files for version 2.8, just because you only have version 2.4
on your own machine.

I know you want to keep your installation of 2.4, but isn't there any way
for you to get access also to a recent version?

If your installation of LilyPond 2.4 is via a cygwin package, then you can
safely install the 2.8 package from www.lilypond.org. It shouldn't interfere
with cygwin, unless you expicitly modify your $PATH so that cygwin sees the
2.8 version that's installed in C:\Program Files\LilyPond\.


Regarding this specific file, I got a backtrace from Guile unless I removed
all lines that refered to stat:size or stat:mtime. Still, it doesn't 
compile
cleanly, but I don't have the time right now to look more into what you are
trying to do.

   /Mats

Fairchild wrote:

 The ly file below doesn't function in the LSR environment.

 - Bruce

 %%%
 %{ Display ly file information on the score, including file name, file
 size,
  LilyPond version, date processed, time processed, time last modified, 
 and
  the LilyPond command line. %}
 #( define comml( object-string ( command-line )))
 #( define slashloc ( + ( string-rindex comml #\/ ) 1 ))
 #( define commllen ( - ( string-length comml ) 2 ))
 #( define filen( substring comml slashloc commllen ))
 #( define siz  ( object-string ( stat:size ( stat filen 
 #( define ver  ( object-string (lilypond-version )))
 #( define dat  ( strftime %m/%d/%Y ( localtime ( current-time 
 #( define tim  ( strftime %T ( localtime ( current-time 
 #( define modt ( stat:mtime ( stat filen )))
 #( define modts( strftime %m/%d/%Y %T (localtime modt)))
 \header { dedication = \markup \column 
 { - - - - - - Using Scheme \define\-  - - - - - } % 
 { File Name = \filen }
 { File Size = \siz   }
 { LilyPond Version =  \ver   }
 { Date Processed =\dat   }
 { Time Processed =\tim   }
 { Last Modified = \modts }
 { Command Line =  \comml }
 {  }
 { - - - - - - Using \ly:export\ - - - - - - } % 
 { #( ly:export ( string-appendFile Name = 
( substring ( object-string ( command-line ))
( + ( string-rindex ( object-string ( command-line )) #\/ 
 ) 1 )
( - ( string-length ( object-string ( command-line )) ) 2 
  }
 { #( ly:export ( string-appendFile Size = 
( object-string ( stat:size ( stat filen ) }
 { #( ly:export ( string-appendLilyPond Version = 
( lilypond-version ))) }
 { #( ly:export ( string-appendDate Processed = 
( strftime %m/%d/%Y ( localtime ( current-time ) }
 { #( ly:export ( string-appendTime Processed = 
( strftime %T ( localtime ( current-time ) }
 { #( ly:export ( string-appendLast Modified = 
( strftime %m/%d/%Y %T
( localtime ( stat:mtime ( stat filen )) }
 { #( ly:export ( string-appendCommand Line = 
( object-string ( command-line  }
}
 { c''1_\markup { \column 
 { - - - - - - In \markup\ - - - - - - } % 
 { File Name = \filen }
 { File Size = \siz   }
 { LilyPond Version =  \ver   }
 { Date Processed =\dat   }
 { Time Processed =\tim   }
 { Last Modified = \modts }
 { Command Line =  \comml }
 }}
 

---
-

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


-- 
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=






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

RE: Coexisting 2.8 with 2.4

2006-07-01 Thread Fairchild

Thomas -

Thanks.  You give me confidence.

You might want to check PATH, to be aware that one version might find
another's files.

 - Bruce

-Original Message-
From: Thomas Scharkowski [mailto:[EMAIL PROTECTED] 
Sent: Saturday, July 01, 2006 4:53 PM
To: Fairchild
Cc: lilypond-user@gnu.org
Subject: RE: Coexisting 2.8 with 2.4


 Thomas, et. al. -
 
 9)  Your signature tag implies you juggle three LilyPond versions.
 How?

Hello Bruce,

I have kept the cygwin version (2.4.6) because it does not interfere 
with the native windows version(s) and it still works (indeed I 
haven't used it for some time).
Normally I only use the newest version (2.9.10), if necessary I 
change to the stable version (2.8.5).
You asked how:
I have installed one version normally e.g. 2.8.5, and then copied the 
whole lilypond directory to to a new one e.g. lilypond285
Then I installed the new version.
Now I can choose versions with the command line, or change the 
command in jEdit's plugin options.

I am not competent enough to answer your other questions, perhaps except No.
7: IIRC since version 2.6 ps is produced directly 
and not via tex and dvi.

Thomas





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

LSR Execution? Failure

Title: LSR Execution? Failure






The ly file below doesn't function in the LSR environment.


 - Bruce


%%%

%{ Display ly file information on the score, including file name, file size,

LilyPond version, date processed, time processed, time last modified, and

the LilyPond command line. %}

#( define comml ( object-string ( command-line )))

#( define slashloc ( + ( string-rindex comml #\/ ) 1 ))

#( define commllen ( - ( string-length comml ) 2 ))

#( define filen ( substring comml slashloc commllen ))

#( define siz ( object-string ( stat:size ( stat filen 

#( define ver ( object-string (lilypond-version )))

#( define dat ( strftime %m/%d/%Y ( localtime ( current-time 

#( define tim ( strftime %T ( localtime ( current-time 

#( define modt ( stat:mtime ( stat filen )))

#( define modts ( strftime %m/%d/%Y %T (localtime modt)))

  \header { dedication = \markup \column 

{ - - - - - - Using Scheme \define\- - - - - - } % 

{ File Name =  \filen }

{ File Size =  \siz }

{ LilyPond Version =  \ver }

{ Date Processed =  \dat }

{ Time Processed =  \tim }

{ Last Modified =  \modts }

{ Command Line =  \comml }

{  }

{ - - - - - - Using \ly:export\ - - - - - - } % 

{ #( ly:export ( string-append File Name = 

 ( substring ( object-string ( command-line ))

 ( + ( string-rindex ( object-string ( command-line )) #\/ ) 1 )

 ( - ( string-length ( object-string ( command-line )) ) 2  }

{ #( ly:export ( string-append File Size = 

 ( object-string ( stat:size ( stat filen ) } 

{ #( ly:export ( string-append LilyPond Version = 

 ( lilypond-version ))) } 

{ #( ly:export ( string-append Date Processed = 

 ( strftime %m/%d/%Y ( localtime ( current-time ) }

{ #( ly:export ( string-append Time Processed = 

 ( strftime %T ( localtime ( current-time ) }

{ #( ly:export ( string-append Last Modified = 

 ( strftime %m/%d/%Y %T

 ( localtime ( stat:mtime ( stat filen )) }

{ #( ly:export ( string-append Command Line = 

 ( object-string ( command-line  } 

  }

{ c''1_\markup { \column 

{ - - - - - - In \markup\ - - - - - - } % 

{ File Name =  \filen }

{ File Size =  \siz }

{ LilyPond Version =  \ver }

{ Date Processed =  \dat }

{ Time Processed =  \tim }

{ Last Modified =  \modts }

{ Command Line =  \comml }

}}





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

RE: LSR Execution? Failure

Mats -

I understand your 2.8 vs. 2.4 advice, but suspect the current problem is
operating environment dependency, not ly version.  It works just fine with
my XP.  Others have been asking for the info extraction capability, so am
struggling to make it available by posting to LSR.  Posting to the list for
inclusion in the docs elicited no response.

   - Bruce

-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 30, 2006 7:10 AM
To: Fairchild
Cc: lilypond-user@gnu.org
Subject: Re: LSR Execution? Failure


Please, this is a very tedious method for your and everybody else to help
you debug .ly files for version 2.8, just because you only have version 2.4
on your own machine.

I know you want to keep your installation of 2.4, but isn't there any way
for you to get access also to a recent version?

If your installation of LilyPond 2.4 is via a cygwin package, then you can
safely install the 2.8 package from www.lilypond.org. It shouldn't interfere
with cygwin, unless you expicitly modify your $PATH so that cygwin sees the
2.8 version that's installed in C:\Program Files\LilyPond\.


Regarding this specific file, I got a backtrace from Guile unless I removed
all lines that refered to stat:size or stat:mtime. Still, it doesn't 
compile
cleanly, but I don't have the time right now to look more into what you are
trying to do.

   /Mats

Fairchild wrote:

 The ly file below doesn't function in the LSR environment.

 - Bruce

 %%%
 %{ Display ly file information on the score, including file name, file
 size,
  LilyPond version, date processed, time processed, time last modified, 
 and
  the LilyPond command line. %}
 #( define comml( object-string ( command-line )))
 #( define slashloc ( + ( string-rindex comml #\/ ) 1 ))
 #( define commllen ( - ( string-length comml ) 2 ))
 #( define filen( substring comml slashloc commllen ))
 #( define siz  ( object-string ( stat:size ( stat filen 
 #( define ver  ( object-string (lilypond-version )))
 #( define dat  ( strftime %m/%d/%Y ( localtime ( current-time 
 #( define tim  ( strftime %T ( localtime ( current-time 
 #( define modt ( stat:mtime ( stat filen )))
 #( define modts( strftime %m/%d/%Y %T (localtime modt)))
 \header { dedication = \markup \column 
 { - - - - - - Using Scheme \define\-  - - - - - } % 
 { File Name = \filen }
 { File Size = \siz   }
 { LilyPond Version =  \ver   }
 { Date Processed =\dat   }
 { Time Processed =\tim   }
 { Last Modified = \modts }
 { Command Line =  \comml }
 {  }
 { - - - - - - Using \ly:export\ - - - - - - } % 
 { #( ly:export ( string-appendFile Name = 
( substring ( object-string ( command-line ))
( + ( string-rindex ( object-string ( command-line )) #\/ 
 ) 1 )
( - ( string-length ( object-string ( command-line )) ) 2 
  }
 { #( ly:export ( string-appendFile Size = 
( object-string ( stat:size ( stat filen ) }
 { #( ly:export ( string-appendLilyPond Version = 
( lilypond-version ))) }
 { #( ly:export ( string-appendDate Processed = 
( strftime %m/%d/%Y ( localtime ( current-time ) }
 { #( ly:export ( string-appendTime Processed = 
( strftime %T ( localtime ( current-time ) }
 { #( ly:export ( string-appendLast Modified = 
( strftime %m/%d/%Y %T
( localtime ( stat:mtime ( stat filen )) }
 { #( ly:export ( string-appendCommand Line = 
( object-string ( command-line  }
}
 { c''1_\markup { \column 
 { - - - - - - In \markup\ - - - - - - } % 
 { File Name = \filen }
 { File Size = \siz   }
 { LilyPond Version =  \ver   }
 { Date Processed =\dat   }
 { Time Processed =\tim   }
 { Last Modified = \modts }
 { Command Line =  \comml }
 }}
 

---
-

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


-- 
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=






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

RE: LSR Execution? Failure

Is there a way to post ly and pdf files to LSR, bypassing execution by LSR?

-Original Message-
From: Graham Percival [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 30, 2006 7:21 AM
To: lilypond-user@gnu.org
Cc: Fairchild
Subject: Re: LSR Execution? Failure

Mats Bengtsson wrote:
 Please, this is a very tedious method for your and everybody else to 
 help you debug .ly files for version 2.8, just because you only have 
 version 2.4 on your own machine.

In addition, some scheme commands are disabled on LSR due to security 
concerns (see --safe in the manual about command-line options).

Bruce, please reconsider giving 2.8 a try.  Updating from 2.4 to 2.8 
should not cause too many problems... or at the very least, try 
installing 2.8 in a separate location.

Cheers,
- Graham

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

Coexisting 2.8 with 2.4

I don't see anything LilyPond on the PATH.  So 2.4 and 2.8 should live in
the same house without being aware of each other's existence.

I don't see how jEdit can handle both.  Two incarnations of jEdit?  Can one
instantiation easily flip among multiple installed LilyPond versions?  Alt-l
now executes 2.4.  Is there a way to set another shortcut, say Alt-y, to
execute 2.8?  (Using jEdit 4.2 and LilyTool 0.2.8.)

Any knowledge, experience or documentation to guide me will be appreciated.

Thanks.

  - Bruce

-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 30, 2006 7:10 AM
To: Fairchild
Cc: lilypond-user@gnu.org
Subject: Re: LSR Execution? Failure


Please, this is a very tedious method for your and everybody else to help
you debug .ly files for version 2.8, just because you only have version 2.4
on your own machine.

I know you want to keep your installation of 2.4, but isn't there any way
for you to get access also to a recent version?

If your installation of LilyPond 2.4 is via a cygwin package, then you can
safely install the 2.8 package from www.lilypond.org. It shouldn't interfere
with cygwin, unless you expicitly modify your $PATH so that cygwin sees the
2.8 version that's installed in C:\Program Files\LilyPond\.


Regarding this specific file, I got a backtrace from Guile unless I removed
all lines that refered to stat:size or stat:mtime. Still, it doesn't 
compile
cleanly, but I don't have the time right now to look more into what you are
trying to do.

   /Mats

Fairchild wrote:

 The ly file below doesn't function in the LSR environment.

 - Bruce

 %%%
 %{ Display ly file information on the score, including file name, file
 size,
  LilyPond version, date processed, time processed, time last modified, 
 and
  the LilyPond command line. %}
 #( define comml( object-string ( command-line )))
 #( define slashloc ( + ( string-rindex comml #\/ ) 1 ))
 #( define commllen ( - ( string-length comml ) 2 ))
 #( define filen( substring comml slashloc commllen ))
 #( define siz  ( object-string ( stat:size ( stat filen 
 #( define ver  ( object-string (lilypond-version )))
 #( define dat  ( strftime %m/%d/%Y ( localtime ( current-time 
 #( define tim  ( strftime %T ( localtime ( current-time 
 #( define modt ( stat:mtime ( stat filen )))
 #( define modts( strftime %m/%d/%Y %T (localtime modt)))
 \header { dedication = \markup \column 
 { - - - - - - Using Scheme \define\-  - - - - - } % 
 { File Name = \filen }
 { File Size = \siz   }
 { LilyPond Version =  \ver   }
 { Date Processed =\dat   }
 { Time Processed =\tim   }
 { Last Modified = \modts }
 { Command Line =  \comml }
 {  }
 { - - - - - - Using \ly:export\ - - - - - - } % 
 { #( ly:export ( string-appendFile Name = 
( substring ( object-string ( command-line ))
( + ( string-rindex ( object-string ( command-line )) #\/ 
 ) 1 )
( - ( string-length ( object-string ( command-line )) ) 2 
  }
 { #( ly:export ( string-appendFile Size = 
( object-string ( stat:size ( stat filen ) }
 { #( ly:export ( string-appendLilyPond Version = 
( lilypond-version ))) }
 { #( ly:export ( string-appendDate Processed = 
( strftime %m/%d/%Y ( localtime ( current-time ) }
 { #( ly:export ( string-appendTime Processed = 
( strftime %T ( localtime ( current-time ) }
 { #( ly:export ( string-appendLast Modified = 
( strftime %m/%d/%Y %T
( localtime ( stat:mtime ( stat filen )) }
 { #( ly:export ( string-appendCommand Line = 
( object-string ( command-line  }
}
 { c''1_\markup { \column 
 { - - - - - - In \markup\ - - - - - - } % 
 { File Name = \filen }
 { File Size = \siz   }
 { LilyPond Version =  \ver   }
 { Date Processed =\dat   }
 { Time Processed =\tim   }
 { Last Modified = \modts }
 { Command Line =  \comml }
 }}
 

---
-

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


-- 
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=






___
lilypond-user mailing list
lilypond-user@gnu.org
http

RE: Beaming question

2006-06-27 Thread Fairchild

Seems to be a long-standing bug.  Flaky in 2.4.6.

   - Bruce

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Mats Bengtsson
Sent: Thursday, June 22, 2006 8:07 AM
To: Thomas Scharkowski
Cc: Lilypond bug; lilypond-user@gnu.org
Subject: Re: Beaming question

I don't know, if it's a feature or a bug, but at least it should be 
possible to
override it, which I couldn't manage to do. The following example
illustrates the same phenomenon. As far as I can see, subdivideBeams should
be set to false by default.

\version 2.8.0

\relative c'' {
c16 [ b a g b a8 b16 ]
}   

   /Mats

Thomas Scharkowski wrote:

With and 2.8.5 2.9.10 I get exactly the same result, so perhaps it's
not a bug, but a mistake of mine? Is the code correct for the desired 
result?

Thanks,
Thomas

There have recently been some bugs with the beaming in the development 
versions. I really recommend you to use the latest stable version 
2.8.x for any serious typesetting. Also, if you use the development 
version, please report bugs at bug-lilypond@gnu.org (but first check 
the archives to avoid duplicated bug reports). As far as I know, this 
bug should be fixed in version 2.9.10.

   /Mats

Thomas Scharkowski wrote:

For a long cadenza passage I want to beam all notes together, but 
do not succeed: there is the a subdivision before last 16th note, and 
this note has a small beam in the wrong direction.

code:
--
\version 2.9.9
#(ly:set-option 'point-and-click #f)
\score {
 \relative c'' {
 \key a \major
 \cadenzaOn 
 a64[ gis b32 a gis fis e! dis! cis b ais! b bis cis16 b a gis b a8
fis gis] \cadenzaOff \bar |\break  }
}
--

LilyPond 2.9.9
Windows XP

-
---

Der folgende Teil dieser Nachricht enthält einen Anhang im
sogenannten Internet MIME Nachrichtenformat.
Wenn Sie Pegasus Mail oder ein beliebiges anderes MIME-kompatibles
Email-System verwenden, sollte Sie den Anhang mit Ihrem Email-System
speichern oder anzeigen können. Anderenfalls fragen Sie Ihren
Administrator.

The following section of this message contains a file attachment 
prepared for transmission using the Internet MIME message format. If 
you are using Pegasus Mail, or any another MIME-compliant system, you 
should be able to save it or view it from within your mailer. If you 
cannot, please ask your system administrator for assistance.

   Datei Information/File information ---
Datei/File:  beam299.png
Datum/Date:  20 Jun 2006, 10:26
Größe/Size:  10257 bytes.
Typ/Type:Unbekannt

-
---

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

--
=
 Mats Bengtsson
 Signal Processing
 Signals, Sensors and Systems
 Royal Institute of Technology
 SE-100 44  STOCKHOLM
 Sweden
 Phone: (+46) 8 790 8463  
Fax:   (+46) 8 790 7260
 Email: [EMAIL PROTECTED]
 WWW: http://www.s3.kth.se/~mabe
=

-- 
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=

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

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

RE: AllAbout Examples

2006-06-26 Thread Fairchild

seba -

Just ran a test.  Submitting

\version 2.8.4
{ c''^\markup { abc } }

to LSR worked;

\version 2.8.4
{ c''^\markup { abc \char #65 } }

didn't.

- Bruce

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Fairchild
Sent: Sunday, June 25, 2006 5:26 PM
To: 'Sebastiano Vigna'
Cc: 'lilypond-user Mailinglist'
Subject: RE: AllAbout Examples


I believe the port problem was caused by using \char in a \markup.

  - Bruce

-Original Message-
From: Sebastiano Vigna [mailto:[EMAIL PROTECTED] 
Sent: Sunday, June 25, 2006 5:21 PM
To: Fairchild
Cc: 'lilypond-user Mailinglist'
Subject: RE: AllAbout Examples


On Sun, 2006-06-25 at 17:05 -0500, Fairchild wrote:
 Back to LSR posting.
 
 Since my AllAbout was not acceptable, tried a smaller thing thought to
 be version insensitive.  LSR didn't like the \version 2.4.6 line, so 
 deleted

The current version is 2.8.4, now it's also state in the Contributing
section.

 it.  LSR demanded \version 2.8.4 then complained cryptically about a
 port problem.  Submitted a trivial file; LSR flips out of Netscape; 
 seems to be

mmmhhh... I just moved to 2.8, and moving between LilyPond versions is
always an earthquake, so if you can be more precise I can try to understand
what's happening...

Ciao,

seba






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





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

RE: AllAbout Examples

2006-06-26 Thread Fairchild

Mats -

Really want \char #92 for \.  Maybe \\ has been restored?

- Bruce

-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 26, 2006 6:21 AM
To: Fairchild
Cc: 'Sebastiano Vigna'; 'lilypond-user Mailinglist'
Subject: Re: AllAbout Examples

See http://lists.gnu.org/archive/html/lilypond-user/2005-09/msg00373.html
and http://lists.gnu.org/archive/html/lilypond-user/2005-11/msg00277.html
for some information. In general, there should be no need to specify a
character by its number, just input it directly using an UTF-8 capable text
editor.

   /Mats

Fairchild wrote:

seba -

Just ran a test.  Submitting

\version 2.8.4
{ c''^\markup { abc } }

to LSR worked;

\version 2.8.4
{ c''^\markup { abc \char #65 } }

didn't.

- Bruce

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf 
Of Fairchild
Sent: Sunday, June 25, 2006 5:26 PM
To: 'Sebastiano Vigna'
Cc: 'lilypond-user Mailinglist'
Subject: RE: AllAbout Examples

I believe the port problem was caused by using \char in a \markup.

  - Bruce

-Original Message-
From: Sebastiano Vigna [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 25, 2006 5:21 PM
To: Fairchild
Cc: 'lilypond-user Mailinglist'
Subject: RE: AllAbout Examples

On Sun, 2006-06-25 at 17:05 -0500, Fairchild wrote:

Back to LSR posting.

Since my AllAbout was not acceptable, tried a smaller thing thought to 
be version insensitive.  LSR didn't like the \version 2.4.6 line, so 
deleted

The current version is 2.8.4, now it's also state in the Contributing 
section.

it.  LSR demanded \version 2.8.4 then complained cryptically about a 
port problem.  Submitted a trivial file; LSR flips out of Netscape; 
seems to be

mmmhhh... I just moved to 2.8, and moving between LilyPond versions is 
always an earthquake, so if you can be more precise I can try to 
understand what's happening...

Ciao,

   seba

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

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

-- 
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=

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

RE: AllAbout Examples

Graham -

You imply that convert doesn't upgrade cleanly or that those with newer
versions don't use it.  (I have found significant shortcomings converting ly
files.)  This is just one reason to dread leaving 2.4.6 behind.  (Never
tried 2.6.)  The only identified selfish reason to upgrade is the ability to
use \markup unattached.  Otherwise, 2.4.6 does everything I want to do.  It
is very solid!  Why is it no longer available for download?

There are many concerns supporting procrastination beyond the installation
and setup effort.  Will 2.4.6 and 2.8.? coexist on an XP machine without
interaction?  Including two instantiations of jEdit?  What does convert
leave hanging?  How does functionality change post cygwin?  What is the
effect on fonts?  How will spacing/layout change?  The recent post Moving
to 2.8.4--a nightmare? reinforces my reticence.

For those, like me, building and maintaining a library of scores, changing
ly versions is a big deal.  The AllAbout examples should be welcomed in any
version.  Just need a posting repository available to all.

- Bruce

-Original Message-
From: Graham Percival [mailto:[EMAIL PROTECTED] 
Sent: Saturday, June 24, 2006 8:42 PM
To: Fairchild
Cc: 'lilypond-user Mailinglist'
Subject: Re: AllAbout Examples


On Sat, 24 Jun 2006 17:38:43 -0500
Fairchild [EMAIL PROTECTED] wrote:

 Seems that LSR won't accept 2.4.6.

I've made enquiries about LSR (I think it's still on 2.6), but we cannot
accept anything into the docs if it requires 2.4.  I remember that you had
some problems with 2.6; do they still exist in 2.8?  It would be nice if you
could upgrade to 2.8 and produce examples which everybody can use.

Cheers,
- Graham





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

RE: AllAbout Examples

Back to LSR posting.

Since my AllAbout was not acceptable, tried a smaller thing thought to be
version insensitive.  LSR didn't like the \version 2.4.6 line, so deleted
it.  LSR demanded \version 2.8.4 then complained cryptically about a port
problem.  Submitted a trivial file; LSR flips out of Netscape; seems to be
LSR saying congrats.

Back to the smaller thing, seems 2.8.4 doesn't accept \char, and requires
. instead of - in Feta font name strings.  See result Tramlines and
Feta font caesurae in LSR.

   - Bruce




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

RE: AllAbout Examples

But see http://lilypond.org/doc/v2.8/Documentation/

-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED] 
Sent: Sunday, June 25, 2006 4:06 PM
To: Graham Percival
Cc: Fairchild; 'lilypond-user Mailinglist'
Subject: Re: AllAbout Examples

Quoting Graham Percival [EMAIL PROTECTED]:

 On Sat, 24 Jun 2006 11:37:08 -0500
 Fairchild [EMAIL PROTECTED] wrote:
...
 that haven't made the cut for
 Tips and Tricks or Regression Tests.

 Actually, currently LSR is a mish-mash of lots of small things.  I 
 think it includes some examples from tips and tricks and regressions. 
 Im hoping to change that.

As far as I know, it contains more or less all examples that were present in
the Tips and Tricks and Regression Tests at the time the LSR was initiated
(which includes a number of examples that since then have been removed from
TipsTricks and Regression for good reasons).

  Further, I find the LSR out of
 the mainstream (not linked from the LilyPond documentation page)

It's certainly linked from www.lilypond.org - Documentation!

...

 awkward to use (don't find a way to download as a one-big-page 
 searchable html or pdf).

The idea was that the search features of LSR should make this 
unnecessary, but you can also browse through the examples (though not all on
a single page).

   /Mats

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

RE: AllAbout Examples