Originally created by: *anonymous
Originally created by: magillen...@gmail.com
LilyPond v2.12.2
When a long instrument name is used in a score, the name is cut off of the
page. I know that you can change the size of the indent to fix this, but I
was just wondering why that is not automatic. It seems like it would be
rather easy to increase the indent if the program detects an instrument's
name being cut off.
Originally posted by: v.villenave
Hmmm, let's see.. how about:
CCing Joe and Neil, since they've recently been looking at InstrumentName stuff.
It certainly woule be a nice feature indeed. Or at least, having a keep-inside-line
kind of a switch.
Summary: Indent should automatically adapt to instrument names' length.
Cc: n.puttock joeneeman
Status: Accepted
Last edit: Simon Albrecht 2015-09-28
Originally posted by: percival.music.ca@gmail.com
Issue 1093 has been merged into this issue.
Originally posted by: percival.music.ca@gmail.com
hmm, google code lets me delete non-initial commments (I removed mine from comment 1, which was just saying "give a minimal example"), but not the initial report. (I wanted Valentin's nice example to be the first one)
Here's an attached PDF showing the instrument name going off the left-hand side of the page. The generated png automatically shifts the entire thing to the right (like we'd like to happen for pdfs), so it doesn't show any problem.
Last edit: Simon Albrecht 2015-09-28
Originally posted by: Elu...@gmail.com
maybe not exactly what is asked for, but look at it the other way round:
given a certain indentation the instrument name should automatically adapt to it (this of course works only when corresponding functions are used: \fill-line, \word-wrap...)
Nicolas Sceaux has written a function to do this - with this you don't have to calculate the line-width yourself! (see the discussion on http://old.nabble.com/instrument-name-or-%5Cmarkup-question-td33030134.html )
Cc: -n.putt...@gmail.com -joenee...@gmail.com nicolas....@gmail.com
Here’s another link to the discussion Eluze referred to:
https://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00571.html
(Nicolas’ code still works nicely with no changes required, more than seven years on.)
Originally posted by: PhilEHol...@googlemail.com
(No comment was entered for this change.)
Blocking: lilypond:1015
Originally posted by: simon.al...@mail.de
It’s weird that this issue is marked as "Blocking: lilypond:1015", which latter one is fixed as of 2.15.somewhere.
Which is obsolete after the export from Google.