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

On 2018-10-30 9:23 pm, Aaron Hill wrote: Here's a quick-n-dirty patch to address the issue. \version "2.19.82" \include "center-lyrics-ignoring-punctuation.ily" { d'4 4 4 } \addlyrics { Å Ɓ† «Ḉ…» } Agh, I goofed. I forgot the logic is that you want to trim the "space" characters

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

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 functions with ones which understand UTF8 encoding

vibesDamper - auto position "X" glyph next to note

Hello, With more trial and error than wisdom, I've managed to create a function to attach an X to a note and tweak its position % \vibesDamper #'(0 . 0) note %. This X between notes is a dampening notation for vibraphone. I'm really happy with it, since I shall use it a lot. One improvment I can

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

Hi, > If the problem is Mac related, then it might have to do with System fonts > (located in /Library/Fonts) vs. User fonts (located in > Users//Library/Fonts). IIRC, the default installation location > when using Font Book is the User location. Good thought… but in my case, I know for sure

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

If the problem is Mac related, then it might have to do with System fonts (located in /Library/Fonts) vs. User fonts (located in Users//Library/Fonts). IIRC, the default installation location when using Font Book is the User location. I've had problems with some programs (can't remember if

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

On 2018-10-30 10:01 am, Alexander Kobel wrote: This makes me wonder whether the problem is in the backwards string-search in string-skip-right or in the substring routine used in the make-center-on-word-callback; the only reason I can imagine why this pops up is that some blind-to-Unicode

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

Hi Karlin, I am continuing to look into it. Andrew > I got the latest Alegreya font version 2.008 from GitHub, added only the > OTF font files using FontBook, and restarted the computer. So far, my Mac’s > LilyPond has not picked up on the Alegreya font. No consequence for me, I > don’t do

Re: fonts not working as expected

Hi All, Indeed, I just heard back from Juan Pablo del Peral re which source is authoritative: The latest version is on GitHub. https://github.com/huertatipografica/Alegreya/releases/tag/v2.008 This is the official repo of the project :=) A very fine font in my opinion. Worth solving this

Re: Omitting specific symbols from key signatures

Thank you Torsten, unfortunately this doesn't satisfy the criteria of #3 request, working across transpositions. If I ask for: \key c \KeySig ...it prints a ces in the key signature. Although irrelevant, the example I'm giving is much much simpler than my actual needs which involves key

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

> On Oct 29, 2018, at 7:20 PM, Karlin High wrote: > > Glad to hear it's working for you! I'm away from the Mac for 12 hours or so. > I'll see what happens when I get back to it. > -- > Karlin High > Missouri, USA I got the latest Alegreya font version 2.008 from GitHub, added only the OTF

MIDI suffixes when compiling multiple midi score blocks in one file

They default to "-1", "-2" and so on. Is it possible to control/change them? "first", "second", "the fast one" etc. Thanks, Raitis Veinbahs. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

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: Omitting specific symbols from key signatures

Hi Adam, the KeySig you've defined is nothing but \locrian. If you don't want the F# to be shown (that's the tonic in F# locrian), you just need to define a ,FLAT for step 0 (the tonic), because this will lower the tonic and thus eliminate the F# from your key signature. That way, the F# will

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.

Omitting specific symbols from key signatures

Hi everyone, I would greatly appreciate any help assistance. In the snippet below, I define a key signature that gives accidentals for a locrian mode and then show this mode as if the tonic = fis (F#). I would like three things... 1. to suppress printing of the "fis" in the key signature (yet

Re: automatic metronome mark parentheses

Thanks a lot, Ben! JM > Le 30 oct. 2018 à 13:25, Ben a écrit : > > On 10/30/2018 8:21 AM, Jacques Menu wrote: >> Hello folks, >> >> The LPNR states that: >> >> Combining a metronome mark and text will automatically place the >> metronome mark within parentheses >> >> Is there a way to

Re: fonts not working as expected

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. Andrew ___ lilypond-user mailing list

Re: automatic metronome mark parentheses

On 10/30/2018 8:21 AM, Jacques Menu wrote: Hello folks, The LPNR states that: Combining a metronome mark and text will automatically place the metronome mark within parentheses Is there a way to remove those parentheses explicitly? Thanks for your help! JM Hello, You can

automatic metronome mark parentheses

Hello folks, The LPNR states that: Combining a metronome mark and text will automatically place the metronome mark within parentheses Is there a way to remove those parentheses explicitly? Thanks for your help! JM ___ lilypond-user

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

Hi Alexander, it's definitely a Mac only issue. Windows 10 and Ubuntu 18.10 are just fine. Andrew On Tue, 30 Oct 2018 at 21:33, Alexander Kobel wrote: > > > While there's not yet an answer: from what I can tell, the OTF in both > versions 2.007 (from huertatipografica.com) and 2.008 (the

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: fonts not working as expected

Hi Kieren, I tested this carefully on WIndows 10, with lilypond 2.19.82, and Alegreya Medium from Huerta Tipografica direct. All works fine. The output PDF according to Acrobat Pro DC shows two fonts from your example, Alegreya-Medium (Embedded Subset) and TeXGyreSchola-Regular (Embedded Subset),

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

> Inspired by Karlin’s comment > >> downloading Alegreya font from GitHub > > I went directly to the source > () and > downloaded a new full set from there. (The font set I had before was > from Google Fonts.) > > Result: All fonts