Re: bug in magnetic snapping lyrics engraver

Hi all, On 4/6/22 20:17, Jean Abou Samra wrote: > Le 06/04/2022 à 14:33, Werner LEMBERG a écrit : >> Is someone taking care of bugs in the magnetic snapping lyrics >> engraver?  Here is an example where it fails to position lyrics >> correctly (see last system in the image). >> >> >> Werner

Re: More regular horizontal spacing

Hi Urs, I tried to reproduce, but couldn't easily. Do you have a MWE? What I tried to test is from http://lilypond.org/doc/v2.19/Documentation/notation/proportional-notation In particular, strict-note-spacing; but I'm not sure what will happen if you try to combine strict-note-spacing = ##t

Re: How to set a fixed distance between upper page edge and top line of first staff?

Hi Urs, hi Kim, On 29.07.19 11:10, Urs Liska wrote: > Hi Kim (?), > > 28. Juli 2019 22:59, "kimfierens" schrieb: > >> Hi everyone, I'm new to LilyPond, and I have a layout question for you. The >> title says it all basically: how do I get LilyPond to put a fixed distance >> between the upper

Re: Removing lyric hyphens

Hi Benjamin, the closest we have available to eliminate spurious space between syllables is described in the thread culminating in https://lists.gnu.org/archive/html/lilypond-user/2019-05/msg00389.html (I'm not the author of the snippet, just the bearer of the full include file in this

Re: bug in lyric syllable magnetic snap

On May 28, 2019 8:51:04 PM GMT+02:00, Karlin High wrote: >On 5/28/2019 8:43 AM, Alexander Kobel wrote: >> diffpdf is my friend here. > >That sounds like an interesting piece of software. A web search brought > >up quite a list of diffpdf and pdfdiff things; which is "the

Re: bug in lyric syllable magnetic snap

Hi, On 28.05.19 18:12, Thomas Morley wrote: Am Di., 28. Mai 2019 um 15:48 Uhr schrieb Thomas Morley : I then switched to brute-force, i.e. always throw away all line-starting LyricHyphens Seems to work, see attached revised file. G, it does not. Please try to replace

Re: bug in lyric syllable magnetic snap

Hi, On 27.05.19 22:34, Thomas Morley wrote: Am Mo., 27. Mai 2019 um 10:40 Uhr schrieb Alexander Kobel : unless I additionally engage http://lsr.di.unimi.it/LSR/Item?id=1090 to replace Lily's built-in hyphens by the "proper" Lyric's font hyphens; then it breaks again. I di

Re: bug in lyric syllable magnetic snap

Hi Harm, On 22.05.19 23:08, Thomas Morley wrote: Am Mi., 22. Mai 2019 um 08:17 Uhr schrieb Alexander Kobel : Hi Harm, hi all, On 22.05.19 01:20, Thomas Morley wrote: Am Do., 16. Mai 2019 um 13:25 Uhr schrieb Alexander Kobel : Hi David, hi Mike, hi all, I sometimes (still use Lilypond

Re: bug in lyric syllable magnetic snap

Hi Harm, hi all, On 22.05.19 01:20, Thomas Morley wrote: Am Do., 16. Mai 2019 um 13:25 Uhr schrieb Alexander Kobel : Hi David, hi Mike, hi all, I sometimes (still use Lilypond, and when I do, I typically use) your wonderful snippet for snapping "close" syllables into a si

Re: Barcheck with full measure rests

e removed). As I said I probably am overlooking something since Alexander Kobel made the very same suggestion off list. Ugh, sorry, I didn't intend to take this off-list. Feel free to repost here. http://lilypond.org/doc/v2.19/Documentation/learning/music-expressions-explained#simultaneous-mu

Re: Barcheck with full measure rests

Hi Michael, what about \new Voice { << R1 { s2. s4^"some markup" } >> } ? The \new Voice should not even be necessary in a typical score, with blocks like \score { << \new Staff << % clef, time, etc. \new Voice \thisIsWhereMyMusicComesFrom >> >> } (It's only because

Re: Barcheck with full measure rests

Moreover, if you're working on you favorite Pi tribute choral in 3/14 time (granted, unusual), you'd be out of luck without fractions: { \time 3/14 R1*15/14 } ;-) On 21.05.19 13:16, Malte Meyn wrote: Am 21.05.19 um 13:08 schrieb J Martin Rushton: The notation reference for 2.18.2 doesn't

Re: Barcheck with full measure rests

Hi Michael, TL;DR: It's intended. As the name implies, "FULL measure rests" are supposed to span full measures. In particular, they are always rendered as if they do, so your input should be virtually indistinguishable from R1. And it's also indistinguishable from R1. in 3/2 time, or R1*2 in

bug in lyric syllable magnetic snap

Hi David, hi Mike, hi all, I sometimes (still use Lilypond, and when I do, I typically use) your wonderful snippet for snapping "close" syllables into a single token. (For those who don't know this contribution: it's meant to get rid of unpleasant thin-space gaps between syllables in cramped

Re: Markup beyond the final barline

Hi Urs, hi all, sorry, I accidentally deleted the thread just before some hint came to my mind, so this is not a "proper" reply. \with-dimensions came to my mind as well, but it's not without drawbacks. Somewhat more cumbersome to use, but also *somewhat* more robust is to use a

Re: Character encoding / poor man's letterspacing

Hi, On 12.03.19 10:43, Urs Liska wrote: Am 12.03.19 um 01:14 schrieb Aaron Hill: On 2019-03-11 3:40 pm, David Kastrup wrote: Urs Liska writes: [...] Also, I should have been clear before.  David's code should work for most cases.  I was just being pedantic that /./ would not work if the

Re: [lyric sheet stylesheet] fixing lyric spacing

Hi, On 07.12.18 19:27, Kieren MacMillan wrote: Hi Alex, David's and Mike's "magnetic snapping lyrics"? https://lists.gnu.org/archive/html/lilypond-user/2014-03/msg00489.html Yes — I have an old copy in my "Workarounds" include folder. But I ran into a lot of problems with it (maybe

Re: [lyric sheet stylesheet] fixing lyric spacing

Hi Kieren, without even looking at your example, to be honest, but a shot in the dark: Fo you still remember David's and Mike's "magnetic snapping lyrics"? https://lists.gnu.org/archive/html/lilypond-user/2014-03/msg00489.html This snippet eventually went into OpenLilyLib, and was apparently

Re: UTF-8-aware backwards string searching in Guile, or: fixing centered lyrics ignoring punctuation

Alex On 31/10/2018 05.23, Aaron Hill wrote: On 2018-10-30 4:56 pm, Aaron Hill wrote: On 2018-10-30 10:01 am, Alexander Kobel wrote: Does anyone have a hint how to approach this one? (Or is the answer just: be patient and hope for Guile v2?) The only hint here is to replace the built-in funct

UTF-8-aware backwards string searching in Guile, or: fixing centered lyrics ignoring punctuation

Dear all, I'm happily using center-lyrics-ignoring-punctuation.ily in the version from https://lists.gnu.org/archive/html/lilypond-user/2016-12/msg00382.html for a while now. (It's attached as well.) Now I stumbled across the following unexpected warning: \version "2.19.82" \include

Re: fonts not working as expected

On 30/10/2018 14.08, Andrew Bernard wrote: I have written to huertatipografica to ask where the definitive and most current state of Alegreya is to be found, from their website or from github. It's not clear what the relationship is between the two. Hehe, indeed that's a funny coincidence.

Alegreya [was: fonts not working as expected [SOLVED, at least for OP]]

On 30/10/2018 07.55, Werner LEMBERG wrote: Conclusion: Not all "Alegreya" fonts are the same! Oh yes. Comparing `Alegreya-Medium.ttf': The font available from Google Fonts is version 2.003 (from October 2017, according to the `modified' field in the font's `head' table, even if the file stamp

Re: Re-sizing score on the fly

On 08/07/2018 11:37 AM, Johan Vromans wrote: On Tue, 7 Aug 2018 18:25:53 +1000, Don Gingrich wrote: Then the multiplier would reside in the included files, the variable would be in the score file, and by including the correct file I could have either type of score. Why not set the staff

Re: Understanding the eps bounding box (rounding)

Hi again, On 03/02/2018 03:10 PM, Urs Liska wrote: [...] First I thought this is the solution. Then the confusion came. But now I think again that it's the solution :-) I assume the difference between the BoundingBox and the HiResBoundingBox is exactly what I'm after. Unfortunately the box is

Re: Understanding the eps bounding box (rounding)

Hi Urs, some educated guessing (and hopefully another suggestion): On 03/01/2018 11:11 PM, Urs Liska wrote: Hi all, can anyone tell me *exactly* how the bounding box values are generated and especially rounded in LilyPond? What are they exactly referring to, the content *with* or *without*

Re: Force top-system-spacing to be absolute

Hi Urs, On 01/29/2018 02:27 PM, Urs Liska wrote: [...] I want to have a score start with a defined position of the first staff symbol to match the type area of a surrounding text document. [...]   #'((basic-distance . 16) (minimum-distance . 0) (padding . 0)

Re: Fwd: Re: Is the lyric-syllable-magnetic-snap snippet obsolete?

Hi, have to be very brief right now: have a look at https://github.com/akobel/openlilylib/commit/bbba147196bb8527ed09d8db6b97246c579995fb Not sure why I didn't seem to make that a PR... I thought I did? (I filed the first PR without the version predicate, which was rightfully declined for

Re: Differing header position depending on tallest letter

Hi Peter, On 2017-03-09 17:32, Peter Crighton wrote: > Hello all, > > I noticed that the title (and other header types) doesn’t get vertically > positioned according to its baseline (which would make sense to me), but to > its cap height or ascender height. According to NR 4.1.4

Re: Melisma with manual syllable durations

On 2017-02-22 17:21, David Sumbler wrote: > [...] > So I experimented. I find that, not only does it not matter which > voice or stave I name as "associatedVoice", but it does not even matter > whether such a voice exists! [...] Wrong. Compare the extenders in: \version "2.18.2" \paper {

Re: Start new score without line break

On 2017-02-22 14:28, Alexander Kobel wrote: > On 2017-02-22 14:02, Andrew Bernard wrote: >> There's currently a thread here which refers in passing to the >> difficulty of starting a new score on a page without a line break or >> a page break. > [...] > I just want

Re: Start new score without line break

Andrew, On 2017-02-22 14:02, Andrew Bernard wrote: > There's currently a thread here which refers in passing to the > difficulty of starting a new score on a page without a line break or > a page break. I assume you refer to the thread that I hijacked to ask Pierre for his MuseScore-made D.C.,

Re: Reduce LilyPond installation disk size

Hi Trevor, On 2017-02-22 11:31, Trevor wrote: > To run LilyPond on AWS Lambda for LilyBin, I need to upload a zip > file containing the LilyPond executable and assets, and it must be no > larger than 50 MB. Recent versions of LilyPond unstable are about 52 > MB zipped (zip -r9). Are there any

Re: Different spacings indifferent staves

c.) manually on the output... Cheers, Alexander > Le 22/02/2017 à 00:17, Alexander Kobel a écrit : >> Hi Pierre, >> >> sorry to hear - I hoped that this might give you the desired >> result. I'm out of other ideas for that problem, unfortunately. >> >

Re: Different spacings indifferent staves

direction I want. I tried your solution, it doesn't work either. I may have placed the commands in the wrong place, but I don't think so. Thanks! Pierre Le 13/02/2017 à 16:53, Alexander Kobel a écrit : Hi Pierre, On 2017-02-13 10:57, Les Éditions Valmajour - pg wrote: Hello co-lister

extenders over bar lines in 2.19.55 [was: Automatic Lyric Extenders]

[Bug report summary:] Extenders are not drawn anymore for melismata that include notes that are not bar-aligned, starting somewhere between 2.19.50 and 2.19.55. M(N)WE attached - the first and second score should have extenders until the last note. Hi Michael, On 2017-02-18 18:59, Michael

Re: Different spacings indifferent staves

Hi Pierre, On 2017-02-13 10:57, Les Éditions Valmajour - pg wrote: > Hello co-listers, > > does anyone know if there a way to apply different horizontal spacings to > different staves, whithin the same bar? > > In the attached example, the stemless notes are 16ths. I would like the > stemless

Re: Back in the Pond

On 2017-01-20 10:46, David Kastrup wrote: > Knut Petersen writes: > >> Hi everybody! >> +1. A personal wish: I think that \lyricsto ChoirStaff = "ctx" { ... } has the potential to be a killer feature w.r.t. usability for choir literature (especially

Re: Back in the Pond

Hi David, On 2017-01-19 12:59, Trevor Daniels wrote: David, you wrote Thursday, January 19, 2017 10:18 AM it would appear that my excursion into a regular workplace ended up somewhat shortlived. Really sorry to hear that, but it's great to have you back! Ditto. I wish that you would have

Re: Forcing some horizontal space between two notes

On 2017-01-03 17:25, Urs Liska wrote: > Am 03.01.2017 um 17:01 schrieb Alexander Kobel: >> On 2017-01-03 16:27, Urs Liska wrote: >>> Just for reference, attached you'll find my preliminary result with a >>> compound slur that is somewhat more "mainstream" t

Re: Forcing some horizontal space between two notes

On 2017-01-03 16:27, Urs Liska wrote: > Just for reference, attached you'll find my preliminary result with a > compound slur that is somewhat more "mainstream" than the original Sorabji > example :-) Geez! Apparently there's not just a need for irrational tuplets, but also Bézier curves of

Re: Forcing some horizontal space between two notes

On 2017-01-03 13:56, Pierre Perol-Schneider wrote: > How about the new spacing section? > http://lilypond.org/doc/v2.19/Documentation/notation/new-spacing-section Sounds like the most proper solution, perhaps with adjustments of shortest-duration-space. For dirty one-shot tweaks though,

Re: Rests in polyphonic and simple music in the same staff in LilyPond version 2.18.2.

Hi Jay, On 2016-12-24 08:24, Jay Anderson wrote: On Fri, Dec 23, 2016 at 2:30 PM, Alexander Kobel <a-ko...@a-kobel.de> wrote: it seems that there is some interest in integrating your scheme engraver for merged rests into Lilypond core. Do you mind this idea? If not, are you inte

Re: Rests in polyphonic and simple music in the same staff in LilyPond version 2.18.2.

On 2016-12-22 18:47, David Nalesnik wrote: On Thu, Dec 22, 2016 at 9:01 AM, Alexander Kobel <a-ko...@a-kobel.de> wrote: On 2016-12-22 15:28, Kieren MacMillan wrote: Hi Alexander (et al.), http://lsr.di.unimi.it/LSR/Item?id=336 Is this useful function part of the regular

Re: Vertical spacing titles and highest staff in LilyPond version 2.18.2.

Hi Miroslaw, may I ask you to use the reply function of your mail interface to answer mails? Similar to how you organize your Lilypond input in several folders, I file my mails in several places; if you do not use the reply function, no In-Reply-To header is inserted in your mails. So no mail

Re: Rests in polyphonic and simple music in the same staff in LilyPond version 2.18.2.

On 2016-12-22 15:28, Kieren MacMillan wrote: Hi Alexander (et al.), http://lsr.di.unimi.it/LSR/Item?id=336 Is this useful function part of the regular distro? Not that I'm aware of. If not, is there a technical reason why not None that I'm aware of. Unless you count the known

Re: Vertical spacing titles and highest staff in LilyPond version 2.18.2.

Hi Miroslaw, moving this from bug- to -user. On 2016-12-20 20:40, Mirosław Doroszewski wrote: 1. Only setting "title" in \header block is OK: when is set alone (without any other titles), necessary additional space between "title" and highest staff is automatically calculated. 2. But when

Re: Rests in polyphonic and simple music in the same staff in LilyPond version 2.18.2.

On 2016-12-21 18:50, Mirosław Doroszewski wrote: Rests in polyphonic and simple music in the same staff in LilyPond version 2.18.2. http://lsr.di.unimi.it/LSR/Item?id=336 HTH, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Scaling global staff size without scaling Lyrics in LilyPond version 2.18.2.

Hi Miroslaw. On 2016-12-20 21:11, Mirosław Doroszewski wrote: \version "2.18.2" \include "deutsch.ly" %{ Scaling global staff size without scaling Lyrics in LilyPond version 2.18.2. 1. It can be happen: when font size is set for lyrics, that titles are smaller then lyrics. a) I do not know

Re: Automatic Lyric Extenders

On 2016-12-20 02:44, Br. Samuel Springuel wrote: On 2016-12-19 6:27 PM, Simon Albrecht wrote: I actually meant using an include file like the attached and not having to add the music function locally at all. Beautiful - didn't know that this was possible at all. #(set!

Re: Automatic Lyric Extenders

Hi again Samuel, great that you find it useful. Yes, the minimum-length is well-tweakable; the default will likely be different in the "final" version. This version for killing extenders is my old and home-grown solution for my use cases and by no means optimized. It's not been long since

Re: Automatic Lyric Extenders

On 2016-12-19 21:09, Br. Samuel Springuel wrote: Is there a way to get lyric extenders to appear automatically when lyrics have been applied to a voice using `\lyricsto`? I know how to manually get them to appear (with `__`), but I'm wondering if there is a simple setting that can be changed in

Re: Automatic lyric extenders

On 2016-12-14 11:03, Urs Liska wrote: Am 14.12.2016 um 10:45 schrieb Alexander Kobel: On 2016-12-14 07:50, Knut Petersen wrote: Hi Alexander! add-lyric-extenders = #(define-music-function (parser location lyrics) (ly:music?) You don't need "parser location". Hi Knut, I

Re: Automatic lyric extenders

On 2016-12-14 07:12, Knut Petersen wrote: Am 13.12.2016 um 22:43 schrieb Alexander Kobel: On 2016-12-12 13:48, Knut Petersen wrote: Hi everybody! Please test and comment, patch and examples attached. Hi Knut, works beautifully, as far as your code is concerned. But I found a bug in my

Re: Automatic lyric extenders

On 2016-12-14 07:50, Knut Petersen wrote: Hi Alexander! add-lyric-extenders = #(define-music-function (parser location lyrics) (ly:music?) You don't need "parser location". Hi Knut, I think I do - see the post on lily-devel. AFAIK, the type check (here: ly:music?) is applied to the third

Re: Fixing LSR 888: center-on-words ignoring punctuation

Dear all, On 2016-12-10 00:12, Alexander Kobel wrote: [...] AFAICS, everything works beautifully as expected, with one strange exception: in a chord with two equal notes, the default algorithm chooses the right one as reference, your method chooses the reference point depending on the stem

Re: exchange LyricHyphen with a "proper" hyphen

Hi. On 2016-12-10 20:23, Knut Petersen wrote: Am 07.12.2016 um 23:59 schrieb Thomas Morley: So here a very first shot. Thanks for your work. I think the attached code shows a problem of your code ... Back on the topic for this thread. I also noticed that behavior, and I thought I have a

Re: Automatic lyric extenders

On 2016-12-12 13:48, Knut Petersen wrote: Hi everybody! Please test and comment, patch and examples attached. Hi Knut, works beautifully, as far as your code is concerned. But I found a bug in my function (add-lyric-extenders): Unintuitively, adding an extender after _ makes extenders

Re: Ties across voices

On 2016-12-12 13:42, Urs Liska wrote: [...] BTW: Has this warning been disabled somewhere in the unstable versions? From 2.19.49, I get no complaint even for << { \stemDown b' } \\ a' >> which clearly collides... I think in this example there actually is no colliding-note-column clash

Re: Ties across voices

Hi, On 2016-12-12 13:27, Andrew Bernard wrote: On 12 December 2016 at 23:24, Alexander Kobel <a-ko...@a-kobel.de <mailto:a-ko...@a-kobel.de>> wrote: BTW: Has this warning been disabled somewhere in the unstable versions? From 2.19.49, I get no complaint even for <

Re: Ties across voices

Hi, On 2016-12-12 12:24, Peter Toye wrote: Andrew, Urs, Thanks both for the ideas. It's interesting. Andrew's method works but gives a warning about clashing note columns but the layout is fine. you can add a \once \override NoteColumn.ignore-collision = ##t before \stemDown; this will

Re: exchange LyricHyphen with a "proper" hyphen

Hi Knut, hi all. On 2016-12-12 00:52, Knut Petersen wrote: Hi Alexander IIUC (I didn't compile it in), your patch inhibits extenders on a single note, correct? Yes. Is that really what we want unconditionally, Currently we get a short extender ... that is imho of no use and should be

Re: exchange LyricHyphen with a "proper" hyphen

On 2016-12-11 17:24, Knut Petersen wrote: Am 11.12.2016 um 09:05 schrieb Simon Albrecht: Sorry to ask so bluntly, but can it really be that simple? I thought a solution must consider the x-extent of the syllable vs. the melisma as well… I think this is sufficiently easy to handle with the

Re: exchange LyricHyphen with a "proper" hyphen

On 2016-12-10 23:33, Alexander Kobel wrote: On 2016-12-10 20:20, Noeck wrote: [...] Would it be possible to have automatic extender lines? For every melisma there is an extender line if it would be longer than the minimum-length? Hm. Iterate over lyrics and add Extender events for each

Re: exchange LyricHyphen with a "proper" hyphen

On 2016-12-11 11:04, Alexander Kobel wrote: Hi Joram. On 2016-12-11 09:28, Noeck wrote: Hi Alexander, Am 11.12.2016 um 01:17 schrieb Alexander Kobel: Ah, no, here's the problem, as can be readily seen in the "Brich an, o schönes Morgenlicht", first full measure I don't think s

Re: exchange LyricHyphen with a "proper" hyphen

Hi Joram. On 2016-12-11 09:28, Noeck wrote: Hi Alexander, Am 11.12.2016 um 01:17 schrieb Alexander Kobel: Ah, no, here's the problem, as can be readily seen in the "Brich an, o schönes Morgenlicht", first full measure I don't think so. Because for notes like the second one in t

Re: exchange LyricHyphen with a "proper" hyphen

Hi again, On 2016-12-10 23:33, Alexander Kobel wrote: On 2016-12-10 20:20, Noeck wrote: Hi Alexander, where is this from: conditional-kill-lyric-extender-callback? [...] It is a perfect solution for a problem I had for quite some time: In chorales (4 voices, mostly homophone), I often have

Re: exchange LyricHyphen with a "proper" hyphen

On 2016-12-10 20:20, Noeck wrote: Hi Alexander, where is this from: conditional-kill-lyric-extender-callback? Does it have any drawback? Hi Joram, glad it helped. It seems that I wrote it, probably modeled after a suggestion by Kieren:

Re: exchange LyricHyphen with a "proper" hyphen

On 2016-12-10 09:40, Knut Petersen wrote: Am 10.12.2016 um 00:36 schrieb Alexander Kobel: [...] And with this, all of this week's issues of mine are worked around, and I can proudly present a beautiful little setting of a beautiful little piece by Reger... :-) Those old settings by Max Reger

Re: exchange LyricHyphen with a "proper" hyphen

On 2016-12-10 11:50, Michael Gerdau wrote: And with this, all of this week's issues of mine are worked around, and I can proudly present a beautiful little setting of a beautiful little piece by Reger... :-) Nice one (Others already mentioned the two hyphen in bar 30) Would you share the

Re: exchange LyricHyphen with a "proper" hyphen

Hi all, On 2016-12-10 08:33, Noeck wrote: Dear Alexander, a very nice score! thanks Joram and Knut. I don't like to spoil it but in the last line (measure 30) I see an extra hyphen. I like that you spoil, that's why I posted it - always better to hame some more pairs of eyes look at it

Re: exchange LyricHyphen with a "proper" hyphen

On 2016-12-07 23:59, Thomas Morley wrote: 2016-12-07 22:03 GMT+01:00 Simon Albrecht <simon.albre...@mail.de>: On 07.12.2016 11:45, Alexander Kobel wrote: I'm not sure whether Harm's proof of concept also involved pre-compile-time modifications. It certainly didn’t; Harm is a S

Re: Fixing LSR 888: center-on-words ignoring punctuation

supported in my Frescobaldi installation) plus dagger and double dagger that might be used as footnote marks. Cheers, Alexander On 2016-12-09 00:50, Thomas Morley wrote: 2016-12-07 1:07 GMT+01:00 Alexander Kobel <a-ko...@a-kobel.de>: Hi all, yet another semi-feature request whe

Re: Emmentaler font issues with the infinality bundle [was: on Arch Linux builds]

On 2016-12-09 23:36, Michael Gerdau wrote: Hi Alexander, Confirmed by a two-minute test without recompiling anything (I use bohoomils repo for infinality, not the aur package). Could you do me a favor and double-check whether the skylines change if you replace {cairo,fontconfig,freetype2} by

Re: Emmentaler font issues with the infinality bundle [was: on Arch Linux builds]

Hi Michael, On 2016-12-09 07:17, Michael Gerdau wrote: Hi Alexander, I'm on ArchLinux 64bit myself and use a self compiled devel (curretly 2.19.52) myself. My skyline seems identical to your 2.19.50 version. thanks a lot, that helped tremendeously to get me on the right track. My fontforge

Re: Fixing LSR 888: center-on-words ignoring punctuation

Hi Harm, On 2016-12-09 00:50, Thomas Morley wrote: [...] Hi, how about below? You need a devel-version, though. Please test thoroughly. I'm too tired to do more than the included examples. \version "2.19.52" %% sic !! [...] The devel version is no problem, but sleep is. Same here. Plus my

Re: Emmentaler font issues on Arch Linux builds

Following up on my own question: On 2016-12-09 00:54, Alexander Kobel wrote: [...] So, two-and-a-half questions: What goes wrong, who has a clue or hint? And how can I double-check whether the FontForge compilation flag was properly acknowledged? Ouch! It wasn't: % fgrep enable-double

[Solved] Re: \accidentalStyle for common choir notation

On 2016-12-06 22:45, Alexander Kobel wrote: Dear all, I'd like to lift the thread "\accidentalStyle for common choir notation" from June-July out of the grave. Unfortunately, I don't have it in my inbox anymore, so I need to refer to the horribly url'ed archive http://lilypond.

Re: exchange LyricHyphen with a "proper" hyphen

On 2016-12-07 23:59, Thomas Morley wrote: [...] So here a very first shot. For now I let display the new _and_ the colored default LyricHyphen. You'll see a drawback already: In tight situations the default gets shortened until it vanishs. This is not possible or at least not desirable for

Re: Chords in choral music(Re: Fixing LSR 888: center-on-words ignoring punctuation)

On 2016-12-07 22:05, Simon Albrecht wrote: On 07.12.2016 01:07, Alexander Kobel wrote: chords with two adjacent notes (shifting one note). I know that this should be a forbidden situation for vocal music Why should it? I hardly think anybody should feel inclined to sing it /non divisi

Re: exchange LyricHyphen with a "proper" hyphen

Hi Knut, thanks for looking into that. IIUC (and without looking into your code - is it on Github or otherwise publicly avaiable?), it seems that you essentially add a text-interface to LyricHyphen. That's what would have been my idea as well, if I were up to it. Rebuilding is not a problem

Re: exchange LyricHyphen with a "proper" hyphen

On 2016-12-07 00:10, Thomas Morley wrote: 2016-12-06 23:41 GMT+01:00 Alexander Kobel <a-ko...@a-kobel.de>: On 2016-12-06 23:28, Simon Albrecht wrote: On 06.12.2016 23:00, Alexander Kobel wrote: replace the LyricHyphen "elementary stencil" by a properly printed hyphen from th

Fixing LSR 888: center-on-words ignoring punctuation

Hi all, yet another semi-feature request where I'm running out of knowledge... I happily used LSR 888 (center lyrics without taking punctuation into account) for years and only now found out that the alignment is off under certain circumstances: The default algorithm seems to align lyrics on

Re: exchange LyricHyphen with a "proper" hyphen

On 2016-12-06 23:28, Simon Albrecht wrote: On 06.12.2016 23:00, Alexander Kobel wrote: replace the LyricHyphen "elementary stencil" by a properly printed hyphen from the LyricText font A very good request :-) <https://sourceforge.net/p/testlilyissues/issues/1255/> Oh, rig

Re: exchange LyricHyphen with a "proper" hyphen

Hi Abraham, On 2016-12-06 23:14, tisimst wrote: Alexander, [...] I failed with \override LyricHyphen.text = #"-" \override LyricHyphen.stencil = #lyric-text::print trying to replace the LyricHyphen "elementary stencil" by a properly printed hyphen from the LyricText

exchange LyricHyphen with a "proper" hyphen

Dear all, every now and then, I use a font for lyrics where the hyphen is quite different from Lilypond's LyricHyphen (in particular, sometimes it's slightly slanted). That combined with lyrics where a hyphen has to appear looks, well, ugly. (Recent example: a repetition of part of a word

[Resurrection] \accidentalStyle for common choir notation

Dear all, I'd like to lift the thread "\accidentalStyle for common choir notation" from June-July out of the grave. Unfortunately, I don't have it in my inbox anymore, so I need to refer to the horribly url'ed archive

Re: Development manuals. Was: Re; New LilyPond website

(Bcc'ing bug-lilypond now. What a useful feature! ;-)) On 2016-11-29 16:18, Phil Holmes wrote: [...] In fact, I tend to be confused about the different layout and sectioning of the manual pages for stable and unstable. Now suddenly I wonder whether in the long run it would be a good idea to

Re; New LilyPond website

Cheers, (Cross-posting from bug-lilypond to avoid flooding of the bug list with discussion about general website design; especially the last paragraph might or not might not be interesting for the current discussion.) On 2016-11-29 15:29, Erik Ronström wrote: [...] While the old site may

Performance advice: Tied quavers in British (sacred) music

Dear all, especially the King's Singers et al. among you... ;-) A few weeks ago, a conductor (whom I appreciate a lot) gave a lesson about how to execute tied quavers in British choral music. My whole life before, another conductor (whom I appreciate a lot) taught me the exactly opposite

Re: Getting a new computer

Hi, mid-2014 laptop: Lily 2.19.49 on a Dell Latitude E5440, Arch Linux chroot running on Debian Jessie: 49 sec, 1.25 GB peak memory usage. Wouldn't recommend this particular laptop, though, but just included it so that you have a ballpark figure. % inxi -Fxz System:Host: lap-11-52

Re: segno/coda in lyrics

On 2016-11-15 12:28, Henning Hraban Ramm wrote: Ahoi! I’ve some variations in a song, so that one verse uses a different ending melody. I’d like to mark that with segno/coda signs, like this: textIII = \lyricmode { \repeat unfold 7 { " " } blah blah blah % \override

Re: Curious thing about ties

On 2016-11-15 09:21, David Kastrup wrote: Andrew Bernard writes: Hi Robert, I for one don't think lilypond should be making decisions for you about tie direction based on an idea of sequenced phrases. I know lilypond strives to do as much good layout as it can

Re: Problem with Fonts too big

Hi, FWIW, I just tested your example on a perfectly up-to-date Arch Linux setup (still my first Arch installation, regularly "pacman -Syu"-updated since appx. 4 years), with Lily 2.19.50. No problems at all - find the output attached. On your last update, did you realize the news at

Re: Alignment of instrument names

On 2016-11-10 16:34, Simon Albrecht wrote: On 10.11.2016 15:28, Francesco Napoleoni wrote: (how) can I get instrument names at the start of staves automatically aligned to the internal page margin? Unfortunately you can’t. There already is a request for that feature in our issue tracker, but

Re: Stepping down and moving on

Dear David, my sincere thanks for your past and ongoing work and dedication for Lilypond (and other FOSS, by the way). We are well aware that our donations could not sustain you in the long run. As always in such situations, it's a pity for the community to hear that an important member of

[Why you don't really want] irrational tuplets [nor CF approximations]

On 2016-11-08 18:15, Hans Åberg wrote: I gave an example of a true irrational time signature [1]. The code is actually written in 12/8, with a MIDI approximation in 19/8. Such meter approximations can be obtained using continued fractions convergents [2]. For the rendering, it suffices with an

Re: crop marks in PDF for printing

On 2016-11-07 08:16, Henning Hraban Ramm wrote: Am 2016-11-06 um 22:56 schrieb Alexander Kobel <a-ko...@a-kobel.de>: In many brochure-bound volumes of more than two or three sheets (say, 60+ pages), the paper is cut to align flush when the brochure is closed. So the inner

Re: e in the time of phi and square root of pi tuplet hijinks

On 2016-11-08 08:45, mclaren wrote: Technically speaking, we're also dealing with transcendental tuplets rather than irrationals here, since the square root of pi is a transcendental number (I think. Pi is known to be transcendental, but is the square of pi proven to be transcendental?).

Re: Skyfonts

On 2016-11-07 14:42, Andrew Bernard wrote: Just found out this is not exactly true. Fonts I have purchased are there. Subscription fonts are not. I found where they are, and they are hidden, and obfuscated and in folders you cannot read, such as:

Re: Skyfonts

On 2016-11-07 13:21, Andrew Bernard wrote: Hi All, A lot of very useful input and food for thought here. I confess I am not an expert on the legal issues, [...] I had assumed that pulling the fonts out of a PDF in the case of SkyFonts amounted to reverse engineering and was therefore barred.

  1   2   3   4   5   >