Alignment and style of bar numbers
Hi all,
LilyPond currently aligns all bar numbers on their right side, like in
this example (output attached):
\layout {
\context {
\Score
\override BarNumber.break-visibility = #all-visible
}
}
\repeat unfold 10 { c'1 }
I have found this to be confusing for musicians during rehearsal, because
each number overhangs the preceding measure. Therefore, I would like to
start
a discussion about how the default alignment should be. I uploaded
https://gitlab.com/lilypond/lilypond/-/merge_requests/447 as a proof of
concept
(it centers them, since that was my original idea). Note that we are
only talking
about mid-staff bar numbers − those at the beginning of a system are a
different case and need padding to avoid system start delimiters (wether
we could
add the padding only when the delimiter requires it is an interesting, but
separate, technical question).
I wanted to let you all know that this stuff is under discussion. Note that
I do *not* want the debate to move here (since the MR is easier to find and
link afterwards, and it already started there).
Furthermore, the general style of bar numbers is under question. For
example,
should we print them in italics (which Gould recommends)?
At any rate, changes in this area shall be weighed with care, because they
will certainly have (more or less) large impact on existing scores and
affect
the overall look of LilyPond output. At some point, we may want to ask users
for feedback.
Comments are very welcome on the MR.
Regards,
Jean
Re: paconet....@gmail.com
Le 08/10/2020 à 17:34, Federico Bruni a écrit : Hi Jean lilynet.net is maintained by Valentin (now in Cc). Did you want to ask feedback for this MR? https://gitlab.com/lilypond/lilypond/-/merge_requests/418 Yes, especially this comment: https://gitlab.com/lilypond/lilypond/-/merge_requests/418#note_419155708 Thanks! Jean PS: Not sure how I managed to mess up with the subject line…
Re: lilypond.pot broken (SCM missing)
Am Donnerstag, den 08.10.2020, 13:58 +0200 schrieb Michael Käppler: > Am 08.10.2020 um 13:35 schrieb Jonas Hahnfeld: > > Am Mittwoch, den 07.10.2020, 22:49 +0200 schrieb Michael Käppler: > > > Hi all, > > > while adding gettext calls to all warning and error messages I noticed > > > that the strings from all SCM files are missing in lilypond.pot. > > > > > > Bisecting yielded that > > > > > > commit 5e092ee0d9b84d1948dc90e95488e8c9b58576d1 > > > Author: Han-Wen Nienhuys > > > Date: Sat Mar 21 23:46:14 2020 +0100 > > > > > > Inline scm stepmake templates > > > > > > caused the regression. > > > > > > It seems that the definition of $(SCM_FILES) in scm/GNUmakefile does not > > > reach stepmake/stepmake/po-targets.make, > > > where it would be needed to run xgettext on it. > > > > > > I do not know how to fix this correctly, any advice or MR appreciated. > > > > https://gitlab.com/lilypond/lilypond/-/merge_requests/446 should fix > > this and has some explanations what's going on. > > On the bad side, this means we've lost the translations for French, > > Italian, and Japanese in commit ea3ead41. The ones in Catalan, Dutch, > > Esperanto, Spanish, and Swedish are still there, prefixed by #~. > > > > I'm not very familiar how the translation of the po files happens, > > adding Jean-Charles who "fetches" and commits the files. What do we > > need to resurrect them? If that requires another release, I'm all for > > doing 2.21.7 from master before creating a stable branch. > > > > Jonas > > Hi Jonas, > thank you very much! > > I will upload a MR today that fixes all warnings and errors that > were not i18ned yet. I think it would be reasonable to merge that > one, too, before sending the POT file to the Translation project. Posted here: https://gitlab.com/lilypond/lilypond/-/merge_requests/448 So as discussed on GitLab, we should indeed do a new unstable release to add back the erroneously removed messages and give the translators a chance to localize the other warnings and errors. Shall we short-track the fix and the above MR? Phil, would you be available to release 2.21.7 once merged? Regards Jonas signature.asc Description: This is a digitally signed message part
Re: paconet....@gmail.com
Hi Jean lilynet.net is maintained by Valentin (now in Cc). Did you want to ask feedback for this MR? https://gitlab.com/lilypond/lilypond/-/merge_requests/418 Il giorno mer 7 ott 2020 alle 23:34, Jean Abou Samra ha scritto: Hi all, Last week I sent a message to translati...@lilynet.net to get feedback on my CG edits. Since the message does still not appear at http://lilypond-translations.3384276.n2.nabble.com/, I figured I had to subscribe to the list. The problem is, the page linked at http://lilypond-translations.3384276.n2.nabble.com/mailing_list/MailingListOptions.jtp?forum=3384276 is not reachable, and lilynet.net is not available either. Any ideas? CCing the few translators I know… Thanks, Jean
Re: lilypond.pot broken (SCM missing)
Am 08.10.2020 um 13:35 schrieb Jonas Hahnfeld: Am Mittwoch, den 07.10.2020, 22:49 +0200 schrieb Michael Käppler: Hi all, while adding gettext calls to all warning and error messages I noticed that the strings from all SCM files are missing in lilypond.pot. Bisecting yielded that commit 5e092ee0d9b84d1948dc90e95488e8c9b58576d1 Author: Han-Wen Nienhuys Date: Sat Mar 21 23:46:14 2020 +0100 Inline scm stepmake templates caused the regression. It seems that the definition of $(SCM_FILES) in scm/GNUmakefile does not reach stepmake/stepmake/po-targets.make, where it would be needed to run xgettext on it. I do not know how to fix this correctly, any advice or MR appreciated. https://gitlab.com/lilypond/lilypond/-/merge_requests/446 should fix this and has some explanations what's going on. On the bad side, this means we've lost the translations for French, Italian, and Japanese in commit ea3ead41. The ones in Catalan, Dutch, Esperanto, Spanish, and Swedish are still there, prefixed by #~. I'm not very familiar how the translation of the po files happens, adding Jean-Charles who "fetches" and commits the files. What do we need to resurrect them? If that requires another release, I'm all for doing 2.21.7 from master before creating a stable branch. Jonas Hi Jonas, thank you very much! I will upload a MR today that fixes all warnings and errors that were not i18ned yet. I think it would be reasonable to merge that one, too, before sending the POT file to the Translation project. Cheers, Michael
Re: lilypond.pot broken (SCM missing)
Am Mittwoch, den 07.10.2020, 22:49 +0200 schrieb Michael Käppler: > Hi all, > while adding gettext calls to all warning and error messages I noticed > that the strings from all SCM files are missing in lilypond.pot. > > Bisecting yielded that > > commit 5e092ee0d9b84d1948dc90e95488e8c9b58576d1 > Author: Han-Wen Nienhuys > Date: Sat Mar 21 23:46:14 2020 +0100 > > Inline scm stepmake templates > > caused the regression. > > It seems that the definition of $(SCM_FILES) in scm/GNUmakefile does not > reach stepmake/stepmake/po-targets.make, > where it would be needed to run xgettext on it. > > I do not know how to fix this correctly, any advice or MR appreciated. https://gitlab.com/lilypond/lilypond/-/merge_requests/446 should fix this and has some explanations what's going on. On the bad side, this means we've lost the translations for French, Italian, and Japanese in commit ea3ead41. The ones in Catalan, Dutch, Esperanto, Spanish, and Swedish are still there, prefixed by #~. I'm not very familiar how the translation of the po files happens, adding Jean-Charles who "fetches" and commits the files. What do we need to resurrect them? If that requires another release, I'm all for doing 2.21.7 from master before creating a stable branch. Jonas signature.asc Description: This is a digitally signed message part
Empty markup lines behavior change (maybe regression) in dev (2.21.7) than stable (2.20.0)
Try engrave this ly code:
\version "2.20.0"
>
>/\header {/
>/title = \markup \column {/
>/\line { "Minuet" }/
>/\line { "" }/
>/\line { "" }/
>/}/
>/subtitle = "A study in accent and in the correct timing of half beats"/
>/}/
>
{s}
By lilypond v2.20.0:
[image: image.png]
By lilypond v2.21.7:
[image: image.png]
Sometimes a ly code converted from music sheet software (like Finale), and
their composers prone to typeset casually like this. It's better to
keep accordance with the original appearance.
Hello,
I cannot reproduce the original behavior where empty strings took space with
a 2.20 install on Ubuntu. What is your operating system?
Regards,
Jean Abou-Samra
