Originally created by: *anonymous
Originally created by: RalphBug...@gmail.com
LyricHyphen does not use the glyph of the LyricText font, but instead a custom line markup. Alexander Kobel: "Once I also tried to exchange the LyricHyphen stencil to mimic LyricText, but to no avail - AFAICS, the alignment of the hyphens is more or less hard-coded in the C++ part."
lily/lyric-hyphen.cc: (line 555-556)
"TODO: should extract hyphen dimensions or hyphen glyph from the font."
--
Allow a markup to replace the default LyricHyphen
Solves issue #1255.
Signed-off-by: Knut Petersen knut_petersen@t-online.de
Originally posted by: brownian.box@gmail.com
Some discussion here:
http://lists.gnu.org/archive/html/lilypond-user/2010-09/msg00063.html
Originally posted by: perpeduu...@gmail.com
Before they get lost on my webspace: here are the digicam photos of some scores I checked out and referenced in <http://lists.gnu.org/archive/html/lilypond-user/2010-09/msg00128.html>.
Originally posted by: percival.music.ca@gmail.com
(No comment was entered for this change.)
Labels: -Type-Other Type-Enhancement Priority-Low
Diff:
The current behaviour also has its pros. I think we should allow for both by providing different stencil procedures, like
ly:lyric-hyphen::print-flexibleandly:lyric-hyphen::print-from-font(names to be discussed). In the latter case,text-interfaceproperties would be read.The attached patch solves the problem.
Allow a markup to replace the default LyricHyphen
Solves issue #1255.
Signed-off-by: Knut Petersen knut_petersen@t-online.de
http://codereview.appspot.com/325470043
Version 2 of issue #1255 patch
http://codereview.appspot.com/325470043
Test file changed to support the V2 syntax.
Diff:
Passes make, make check and a full make doc.
Patch on countdown for September 19th
It is more important to work on the ghostscript issue right now.
I cannot see that getting resolved any time 'soon' so do you want to push this or not?
Setting back to needs work.
Issue 5210 has been opened. The proposed patch does not entirely solve this issue, so it is better to keep this open and use a new issue.