|
Orm and Pierre,
Thank you, for your comments. I also like the postscript way of
creating custom clef symbols, and I have found that the scale and
translate commands make positioning glyphs easy. I am glad to find
that the commands:
\override Staff.Clef.space-alist =
#'((time-signature minimum-space . 1.5)
(first-note minimum-fixed-space . 1.5))
work well on the glyphs positioned at the beginning of a staff.
My original reason for posting questions about this is that I am
having no luck using space-alist to reliably adjust spacing for
change clef glypsh using the postscript method, though; and, many
of the space-alist commands seem to have no effect.
My experiments trying to convert the postscript way of doing
things to the \path-like way of doing things have produced strange
results.
For custom change clefs, I may try an ugly solution of using
\cadenzaOn, hidden notes, and \cadenzaOff to get some spacing
around the glyph. I think this may work for now until I understand
things better.
Irregardless of these problems, I am thrilled with how beautiful
my manuscript projects are turning out!
Thanks for the help.
Peace,
David
On 7/6/18 4:27 AM, Orm Finnendahl wrote:
Hi David,
good you figured it out. As I'm doing this stuff frequently,
here are
some remarks, maybe it's useful for you:
Am Freitag, den 06. Juli 2018 um 01:49:09 Uhr (-0400) schrieb
dfro:
I figured out why
copying and pasting the postscript code did not
work. The 'lineto, moveto, curveto' commands must come before
the
numbers in the \path-like version, whereas in the postscript
version
the 'lineto, moveto, curveto' commands come after the numbers.
If I'm not mistaken, the name "Postsript" is actually related to
the
fact, that it is a postfix programming language There are lots of
tutorials on Postscript in the net and I'd recommend reading some
of
them and learning the basics. Postscript is turing complete and
therefore a very powerful programming language.
If you insert "<x> <y> scale" or "<x> <y>
translate" somewhere into
your postscript code, all drawing afterwards will be scaled or
translated accordingly. That might save you some number editing
using
spreadsheets. In Postscript you can also create macro-like
definitions, build dictionaries and such. If you use emacs as a
text
editor, you can explore postscript in a very similar fashion as
lilypond out of the box: Type the code in a text window and
evaluate
it to see the graphics shown in another window.
When I design custom clefs or symbols for lilypond, I normally
start
by using inkscape (https://www.inkscape.org)
for importing, drawing
and exporting to ps or eps format and then open it in emacs and
adjust/reduce the code.
HTH,
Orm
|