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 =
Hi David et All,
2018-07-06 10:27 GMT+02:00 Orm Finnendahl
>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.
Same here
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'
Copying the postscript code into a text file, saving it as a .csv file,
loading it into OpenOffice spreadsheet, cutting and pasting things
around to get things in the right columns, and performing calculations
was a fairly easy and painless way for me to manipulate the data.
David
_
I put the postscript code into a spreadsheet and calculated the x
positions to move over -200 units, and put the 'moveto, lineto, curveto,
closepath' commands first. In the code below I am able to control
spacing nicely with "\override Staff.Clef.space-alist" except for the
note clashing with t
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.
David
___
David and Pierre,
Thank you for the suggestions. I appreciate you making a code example
for me. I saw this method earlier in the LSR, but could not make sense
of it at the time. Pierre, your example helps me to see the difference
between the "\path" way of doing things and the "\markup \postsc
Hi DFro,
How about :
%CODE START
% Valentin Villanave's macro for the French-style C clef %%%
\version "2.19.82" %% "2.18.2"
altoClef =
#(ly:make-stencil
`(path 0.001
`(moveto 2.48 -3.06
lineto 2.48 -4.92
curveto 2.48 -4.96 2.45 -5.00 2.40 -5.00
lineto 2.18 -5
dfro writes:
> In the code snippet below, the custom glyph sometimes collides with
> the notes before it, and sometimes does not. Also, I cannot control
> the distance from notes immediately after the custom glyph, as I can
> with the standard "alto" glyph.
>
> I have tried to experiment and to u
Hello,
I am interested in using custom clef symbols. I am practicing with a
snippet from the library that replaces the internal "alto" clef glyph
with a user defined postscript glyph. However, the behavior of the new
glyph is not the same as the standard "alto" glyph.
In the code snippet bel
10 matches
Mail list logo
