On this page:
http://lilypond.org/doc/v2.13/input/lsr/lilypond-snippets/index
scroll down to the Staff notation of the navigation bar, and
hover over some links. There are some errors here. For example,
all of the following links point to "Nesting-staves"
* Non-traditional key signatures
* Pr
On Tue, Apr 7, 2009 at 9:25 PM, Mark Polesky wrote:
> Short version: I made some changes to output-ps.scm
> that can safely reduce the file size of ps files. In
> a simple experiment, I was able to reduce non-binary
> ps-code by up to 10%. I also don't know if anyone
> cares! (: See the attachment
Carl D. Sorensen wrote:
> I don't think that it requires programming. It probably requires
> identifying a readily available tool that fixes code up properly. I think
> it's more a finding job than a creating job.
Could we work with this?
http://www.gnu.org/software/guile/manual/html_node/Pret
On Tue, 2009-04-07 at 17:18 -0600, Carl D. Sorensen wrote:
>
>
> On 4/7/09 4:17 PM, "dem...@suffolk.lib.ny.us"
> wrote:
>
>
> >
> > As to LY not accepting tabs, thats a shame, tabs should be treated as
> > white space, along with and other now-disused
> > characters from the days of telet
By the way, something similar could be done
with framework-ps.scm, although you'd only
save something like 35 bytes of file size.
- Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-d
Short version: I made some changes to output-ps.scm
that can safely reduce the file size of ps files. In
a simple experiment, I was able to reduce non-binary
ps-code by up to 10%. I also don't know if anyone
cares! (: See the attachment.
- Mark
Long version (sorry this is so long):
LilyPond gen
Hello,
This patch fixes a few issues with trill spanners and allows them to
be chained together without requiring explicit \stopTrillSpan
commands.
Please review it here:
http://codereview.appspot.com/32142/show
Regards,
Neil
___
lilypond-devel mail
On 4/7/09 4:17 PM, "dem...@suffolk.lib.ny.us"
wrote:
>
> As to LY not accepting tabs, thats a shame, tabs should be treated as
> white space, along with and other now-disused
> characters from the days of teletypes which sometimes find their way into
> ascii files from odd unix and dos s
On 4/7/09 4:46 PM, "Mark Polesky" wrote:
>
>
>> Carl D. Sorensen wrote:
>
>> What version of LilyPond did you get output-ps.scm from? In
>> order to make a patch, I need both the before and after files.
>
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=scm/output-p
> s.
> Carl D. Sorensen wrote:
> What version of LilyPond did you get output-ps.scm from? In
> order to make a patch, I need both the before and after files.
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=scm/output-ps.scm;hb=HEAD
(about 20 minutes ago)
> An automated way to do th
On 4/7/09 4:23 PM, "Mark Polesky" wrote:
> Carl D. Sorensen wrote:
>> LilyPond programming standards call for no tabs in the files.
>>
>> If you convert all the tabs to an appropriate number of spaces to get the
>> indentation right, please submit a patch so we can fix this.
>
> Here's outpu
Carl D. Sorensen wrote:
> LilyPond programming standards call for no tabs in the files.
>
> If you convert all the tabs to an appropriate number of spaces to get the
> indentation right, please submit a patch so we can fix this.
Here's output-ps.scm with spaces instead of tabs.
Is there a way to
On Tue, Apr 7, 2009, Patrick McCarty said:
>> Is there an easy way to address this?
use a programming editor. tabs were invented at a time when fixed-width
was the norm, high-speed printers and teletypes had no other way to put
ink on paper. back then, the tab stops were 8 chars apart.
Progr
LilyPond programming standards call for no tabs in the files.
If you convert all the tabs to an appropriate number of spaces to get the
indentation right, please submit a patch so we can fix this.
Thanks,
Carl
On 4/7/09 1:32 PM, "Mark Polesky" wrote:
>
>
> I was fiddling around with output
On 7 Apr 2009, at 18:37, > wrote:
it is transposed twice in opposite
directions: first by the composer who writes the sheet music
actually, the composer usually scribbles all the music in score at
pitch
and leaves part copying (with appropraite transpositions) to a
specialist
who has a g
On Tue, Apr 7, 2009 at 12:32 PM, Mark Polesky wrote:
>
> I was fiddling around with output-ps.scm (specifically
> the grob-cause procedure on line 159) and was getting
> frustrated with the poor indentation displaying in my
> editor when I realized that this was being caused by
> tab characters in
I was fiddling around with output-ps.scm (specifically
the grob-cause procedure on line 159) and was getting
frustrated with the poor indentation displaying in my
editor when I realized that this was being caused by
tab characters in the source.
Is there an easy way to address this? I don't know
Bravo, Peter,
I say go with this, it is pitched just right for the intended audience.
You've got a note-reference "Bes" in there which will need to be marked
as translatable.
Cheers,
Ian Hulin
Peter Chubb wrote:
I reckon it'd be better to split the whole thing into three entries.
Whether a
On Tue, Apr 7, 2009, Peter Chubb said:
> Here's my rough try at the three entries:
kudos Mr Chubb, trust the son of a son of a scoundrel...
I like em all, but as usual, i do have a couple of quibbles.
> Notes like a, b, c etc., describe a relationship between themselves,
> not an absolute pi
On Tue, Apr 7, 2009, "Anthony W. Youngman"
said:
>>So do we care what reference concert pitch uses? Does it matter if it's
>>A=440, or A=445, or A=450?
>
> It does matter that the reference is accurate.
it also matters that the 'Standard' is not always observed; especially for
the music of Moz
On Tue, Apr 7, 2009, Hans Aberg said:
> On 7 Apr 2009, at 08:18, Peter Chubb wrote:
> it is transposed twice in opposite
> directions: first by the composer who writes the sheet music
actually, the composer usually scribbles all the music in score at pitch
and leaves part copying (with appro
In message <87skkl7zry.wl%pe...@chubb.wattle.id.au>, Peter Chubb
writes
I reckon it'd be better to split the whole thing into three entries.
Whether an instrument transposes or not has nothing to do with concert pitch.
I'm reasonably happy with this, and am happy to wait for Kurt to chime
in
On 7 Apr 2009, at 08:18, Peter Chubb wrote:
Here's my rough try at the three entries:
Concert Pitch:
Notes like a, b, c etc., describe a relationship between themselves,
not an absolute pitch. The nature of the relationship is the
so-called temperament (q.v.). To be in tune, a group instrumen
I've found this thread interesting and informative, but a glossary
to a manual is meant to provide simple definitions and/or
translations of technical terms for novices or users unaccustomed to
the language in which the manual is written. It is not meant to be
an encylopaedia. So, for me, t
In message , Carl D. Sorensen
writes
I'm going to step in here, perhaps where wise men fear to tread.
The LilyPond music glossary isn't intended to be a definitive music
dictionary, is it?
So do we care what reference concert pitch uses? Does it matter if it's
A=440, or A=445, or A=450?
It
25 matches
Mail list logo
