Hi Shane,
\version 2.19.11
Even with \smallCaps (how did I miss that!?!!?) the test stays the same.
Bold and Large are both working but not the small caps.
Craig
On Fri Jan 16 2015 at 4:39:22 PM Shane Brandes sh...@grayskies.net wrote:
Which version are you using? and is it not \smallcaps
As I start to gain experience in setting music in Lilypond I am trying
to understand more about how it works internally. As well as personal
satisfaction, this obviously has a practical aim: it will make it easier
for me to modify or correct things without having to ask so many
questions on this
I found a couple of instances in which this crop method too fails:
a) the stem of a b flat;
b) the 8 at the bottom of an octavated clef.
See attached files.
esempio3033-crop.pdf
http://lilypond.1069038.n5.nabble.com/file/n170551/esempio3033-crop.pdf
esempio3064-crop.pdf
Craig,
\caps is just a short-hand command for \smallCaps, but this situation
is obviously a code bug. You CAN put the \caps or \smallCaps in the
header variable itself:
piece = \markup \smallCaps Piece
and then it works, but since it seems that you are trying to create a
custom title that
Am 16.01.2015 um 13:35 schrieb David Sumbler:
As I start to gain experience in setting music in Lilypond I am trying
to understand more about how it works internally. As well as personal
satisfaction, this obviously has a practical aim: it will make it easier
for me to modify or correct things
Dear Craig,
Can you provide an example that compiles on its own? A simplified version
of your code is working for me. Also, what font are you using?
Kevin
On Fri, Jan 16, 2015 at 9:00 AM, Craig Dabelstein
craig.dabelst...@gmail.com wrote:
Hi Shane,
\version 2.19.11
Even with \smallCaps
Is there a possibility to do something like this?
if( custom_cfg_flag)
{
% default score combination
% (e.g. with header and chords)
}
else
{
% some other combination
% (e.g. only melody)
}
I have also always wanted
Kevin,
\caps and \smallCaps should work with any font since they simply
iterate through the string and reduce the font size by a scaling factor
-2 for all characters except those already in upper-case.
The only function, related to this conversation thread, that cares
about the actual font is
David
Join the club - many of us have struggled for many months to get to grips with
the structure and philosophy of Lilypond. Some of the
enlightened have often poured scorn on these attempts or became very defensive
of any suggestion that the documentation
(comprehensive as it is) does not
\caps and \smallCaps should work with any font since they simply
iterate through the string and reduce the font size by a scaling factor -2
for all characters except those already in upper-case.
Does this mean that lilypond doesn't use the true small caps that many
fonts include?
Am 16.01.2015 um 14:46 schrieb Peter Gentry:
David
Join the club - many of us have struggled for many months to get to grips with
the structure and philosophy of Lilypond. Some of the
enlightened have often poured scorn on these attempts or became very defensive
of any suggestion that the
Dear David,
\score {
\new StaffGroup
\override Score.MetronomeMark.padding = #2
\topLine
\bottomLine
}
Here if you replace the `padding' property with `outside-staff-padding' it
should work, i.e.
\override Score.MetronomeMark.outside-staff-padding = #2
I revised lilycrop.sh with two new features:
1. invoke with -e option for EPS output
2. invoke with -l option to write output file names to log file (use
-el for both options)
The script now includes better error checking of command-line arguments.
I don't know how to make it accept shell
\fontCaps attempts to access the fonts smcp flavor the other two
methods are hocus pocus relying on scaling as apposed to a true small
caps set.
Shane
On Fri, Jan 16, 2015 at 8:52 AM, Kevin Barry barr...@gmail.com wrote:
\caps and \smallCaps should work with any font since they simply
iterate
Hi David,
thanks again. You're my hero: now it works.
I've added a few things so far:
- thickness property can be used to control frame thickness, can even be
set to zero (color property and layer property work by default)
- filled property (boolean) controls whether the box is to be filled
Accidentally sent this only to the OP rather than to the list...
Forwarded Message
Subject:Re: small caps
Date: Fri, 16 Jan 2015 20:55:30 +1100
From: Nick Payne nick.pa...@internode.on.net
To: Craig Dabelstein craig.dabelst...@gmail.com
I think you have
Hi Klaus,
On Fri, Jan 16, 2015 at 11:35 AM, Klaus Blum benbigno...@gmx.de wrote:
Hi David,
thanks again. You're my hero: now it works.
I've added a few things so far:
- thickness property can be used to control frame thickness, can even be
set to zero (color property and layer property
Just let me repeat something I wrote a number of times here.
If you manage to understand something with the help of this
list that you think could be a not-so-uncommon issue for many
please consider sharing your experience with a (little or big)
tutorial, for which we have always free space
Hi Peter,
many of us have struggled for many months to get to grips with the structure
and philosophy of Lilypond.
1. Regarding the structure, what are you struggling with exactly?
2. Regarding the philosophy, what are you struggling with exactly?
Hope I can help!
Kieren.
I store two pitches in a pair variable
x = #'(b . cis')
But then I want to retrieve each one as a pitch in a music-function
foo = #(define-music-function (parser location bar) (ly:music?)
(define from (car x))
(define to (cdr x))
#{
\transpose $from $to
Dear David,
as a small addition and a partly similar answer to Urs’, I think the point is:
LilyPond tries to suggest (or even enforce as a default) conventions of classic
music notation. This comprises for example that clefs are repeated for each line
but the time signature isn’t.
In your case,
On Fri, Jan 16, 2015 at 4:02 PM, and...@andis59.se and...@andis59.se wrote:
I store two pitches in a pair variable
x = #'(b . cis')
But then I want to retrieve each one as a pitch in a music-function
foo = #(define-music-function (parser location bar) (ly:music?)
(define from (car
On 2015-01-17 00:16, Jay Anderson wrote:
On Fri, Jan 16, 2015 at 4:02 PM, and...@andis59.se and...@andis59.se wrote:
I store two pitches in a pair variable
x = #'(b . cis')
pitches = #(cons #{ b #} #{ cis' #})
#(display (ly:pitch? (car pitches))) = #t
Ok that works but looks really
Am 17.01.2015 um 00:21 schrieb and...@andis59.se:
On 2015-01-17 00:16, Jay Anderson wrote:
On Fri, Jan 16, 2015 at 4:02 PM, and...@andis59.se
and...@andis59.se wrote:
I store two pitches in a pair variable
x = #'(b . cis')
pitches = #(cons #{ b #} #{ cis' #})
#(display (ly:pitch? (car
2015-01-17 0:21 GMT+01:00 and...@andis59.se and...@andis59.se:
On 2015-01-17 00:16, Jay Anderson wrote:
On Fri, Jan 16, 2015 at 4:02 PM, and...@andis59.se and...@andis59.se
wrote:
I store two pitches in a pair variable
x = #'(b . cis')
pitches = #(cons #{ b #} #{ cis' #})
#(display
2015-01-17 1:20 GMT+01:00 Thomas Morley thomasmorle...@gmail.com:
2015-01-17 0:21 GMT+01:00 and...@andis59.se and...@andis59.se:
On 2015-01-17 00:16, Jay Anderson wrote:
On Fri, Jan 16, 2015 at 4:02 PM, and...@andis59.se and...@andis59.se
wrote:
I store two pitches in a pair variable
x =
2015-01-16 1:42 GMT+01:00 Thomas Morley thomasmorle...@gmail.com:
2015-01-16 0:26 GMT+01:00 Thomas Morley thomasmorle...@gmail.com:
2015-01-15 15:02 GMT+01:00 tisimst tisimst.lilyp...@gmail.com:
On Wed, Jan 14, 2015 at 11:47 PM, Schneidy [via Lilypond] [hidden email]
wrote:
Hi Harm,
2015-01-17 1:59 GMT+01:00 Thomas Morley thomasmorle...@gmail.com:
2015-01-16 1:42 GMT+01:00 Thomas Morley thomasmorle...@gmail.com:
2015-01-16 0:26 GMT+01:00 Thomas Morley thomasmorle...@gmail.com:
2015-01-15 15:02 GMT+01:00 tisimst tisimst.lilyp...@gmail.com:
On Wed, Jan 14, 2015 at 11:47 PM,
From: Noeck noeck.marb...@gmx.de
To: lilypond-user@gnu.org
Subject: Re: Understanding Lilypond
Date: Sat, 17 Jan 2015 00:04:34 +0100
Dear David,
as a small addition and a partly similar answer to Urs’, I think the point is:
LilyPond tries to suggest (or even enforce as a default)
for i in *.ly; do lilycrop $i; done
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Re-bottom-of-EPS-output-cut-off-size-of-PDF-files-tp170572p170591.html
Sent from the User mailing list archive at Nabble.com.
___
30 matches
Mail list logo
