Re: New LilyPond website

> Ok, so what are the major things you would like from a new web > redesign (not including the docs)? > > I know of: > > Not reliant on JavaScript > Can be translated > Can be updated with each new build If possible, try an incremental approach! I'm quite sure that you can achieve almost

Re: Which Linux distro for Lilypond

>> OK, thanks for working on this. However, it would be still >> valuable to know why module loading fails with a static version of >> guile. This might be either a bug or missing information in the >> documentation. > > It's a known problem ... there already is a related thread in >

Re: Which Linux distro for Lilypond

> After a loser look at the sources and the build system I think it's > better (= much easier) to stay with shared libraries. OK, thanks for working on this. However, it would be still valuable to know why module loading fails with a static version of guile. This might be either a bug or

Re: Which Linux distro for Lilypond

Hello Knut! > Using a guile 1.8.8 built with --disable-shared building of lilypond > fails early: Ouch. > Ok, let's look at srfi-1.scm line 221..223: > >;; Load the compiled primitives from the shared library. >;; >(load-extension "libguile-srfi-srfi-1-v-3" "scm_init_srfi_1") > >

Re: Which Linux distro for Lilypond

> I can't speak for other distros, but at least as far as Debian is > concerned, if the upstream (i.e., lilypond) source tarball contains > a copy of the guile-1.8 sources, and the build script is tweaked > such that it installs a copy of guile 1.8 in paths private to > lilypond, e.g.,

Re: Which Linux distro for Lilypond

>>> Where would I find suitable documentation or tutorials to do so >>> (doesn't have to be explicitly about Guile 1.8 vs. 2 of course)? >> >> It's rather simple. [...] > > To build lilypond we require guile-xx-dev (don't remember if we > require guile-xx-libs as well). Will the method described

Re: Which Linux distro for Lilypond

> You probably know about > http://lists.gnu.org/archive/html/guile-user/2016-11/msg00031.html > http://lists.gnu.org/archive/html/guile-devel/2016-12/msg00041.html > http://lists.gnu.org/archive/html/guile-devel/2017-01/msg3.html > > Regarding all the bugreports I listed there (probably with

Re: Which Linux distro for Lilypond

> ./configure --disable-error-on-warning --prefix=`pwd`/../gnu-packages Ah, using `pwd' here is a bad idea, sorry. You should rather use ./configure --disable-error-on-warning --prefix=$HOME/gnu-packages So here are the complete instructions again. cd $HOME mkdir gnu-packages wget

Re: Which Linux distro for Lilypond

> If you get a failure, simply restart the `configure' script (with > all options) until it succeeds. Of course you have to fix the problem first that makes `configure' fail :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Which Linux distro for Lilypond

>> Mhmm, compiling and installing guile 1.8 is not rocket science... > > Probably not, but ... > >> Have you tried that already? > > ... i am not familiar enough with all this packaging stuff to be > confident about installing alternative versions to system installed > packages ... You would

Re: Which Linux distro for Lilypond

> Unfortunately I ran into this very issue, changing from Debian > stable (in the Linux Mint Debian Edition incarnation) to vanilla > Debian testing. I did this because the PyQt5 packages in stable are > too old to run current Frescobaldi from its Git repository. Now > that I managed to get

Re: Which Linux distro for Lilypond

>> OpenSuSE, I'd recommend to use the Tumbleweed variant. It's a good >> distribution, and a nice feature for developers is that it allows >> easy parallel installation of guile 1 and 2. > > Unfortunately, as always, there are trade-offs. I'm a SuSE guy > myself (back from SuSE 5.4 days iirc the

Re: New LilyPond website

>> I just don't think I am the best person for the job. > > Roper has finally posted something I agree with. Why this unwarranted hostility? His final design was sound, and I think we should adapt some key elements. And even if you think it was not, you shouldn't word it like that.

Re: How to build LilyPond.app on macOS?

> Note I'm not saying it can't be done. OK, we agree :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to build LilyPond.app on macOS?

>> Can someone please provide me a hint about how to build >> LilyPond.app on macOS (natively, without any cross-compiling, >> ideally without compiling any dependencies like ghostscript etc.)? > > It is not meant to be compiled natively. This is not true. However, we rely heavily on the GNU

Re: New LilyPond website

> Regarding the font: While I find it acceptable for most of the text, > I’d prefer something different for titles, esp. the main title. You have to be more specific. I like the current font look of http://jmroper.com/lilypond because it is very uniform, not distracting from the contents.

Re: New LilyPond website

> I updated the font (again) and I think it works for everyone's > requests. I like it, thanks! Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: New LilyPond website

>>> I don't understand. Where is the point in recreating somthing >>> close to the old look? I thought the whole idea was to create >>> something new? He provides fine-tuning, e.g., responsive design suitable to different screen widths. I consider this quite valuable! > I updated the font

Re: New LilyPond website

> I added a small shadow to the boxes, and I fixed some coloring of > links. You may have to force-refresh the page to see the changes > (CTRL + F5) Ah, I wasn't aware of that command, thanks! Werner ___ lilypond-user mailing list

Re: New LilyPond website

>> > You make the argument of readability, and I counter it with this: >> > https://www.google.com/amp/www.webdesignerdepot.com/2013/03/serif-vs-sans-the-final-battle/amp/?client=ms-android-google >> >> Perhaps a misunderstanding: The readability concern is the grey >> colour in combination with

Re: New LilyPond website

> You make the argument of readability, and I counter it with this: > https://www.google.com/amp/www.webdesignerdepot.com/2013/03/serif-vs-sans-the-final-battle/amp/?client=ms-android-google Perhaps a misunderstanding: The readability concern is the grey colour in combination with too thin

Re: New LilyPond website

>>> One of the major things on the site that make it look antiquated >>> is the LilyPond intro using the text that looks like it came from >>> a server error message. >> >> LOL > > Concise, readable, informative: must be an error. Hehe. It's very annoying to me that so many sites use extremely

Re: New LilyPond website

> jmroper.com/lilypond Nice! Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: New LilyPond website

>> As David K. pointed out, it must be viewable and navigatable by >> blind people. > > As I wrote, there are some aspects that need to be solved. I just > do not reject a potential valuable approach beforehand. Nobody does that. You are inferring this. >> Additionally, it must be possible

Re: New LilyPond website

>> Additionally there has been *very strict* opposition to anything >> other than statically served sites for lilypond.org in the past. >> Not all of the reasons are bullet-proof but most are, and you will >> not get consent for anything else. > > If the web site must be cast in stone, then

Re: Solution to 7 over sqr(71) time against integer polyrhythms

> Nice try, but so obvious I already tried it long ago -- remove the > timing translator and default barline engraver from the Score > portion of the layout and insert it in the Staff portion. Nope. > Doesn't work with my score. As usual, please show us a minimum working example that exhibits

Re: Can't get page breaks for 7 over square root of 71 meter

> A meter of 7/sqr(71) [...] > The problem comes from Lilypond's bizarre assumption that at some > point all the barlines in the score will line up. [...] > > That's a) insane, Mhmm. > b) stupid, Mhmm, mhmm. > c) unmusical, You are joking, aren't you? Show me *any* piece that uses this –

Re: Changing voice order...

> So > \voiceOne \voiceTwo \voiceThree \voiceFour > becomes > \voiceUp \voiceDown \voiceUpTwo \voiceDownTwo I would make \voiceUp and \voiceDown be the same as \voiceUpOne and \voiceUpTwo, respectively, so that we can write \voiceUpOne \voiceDownOne \voiceUpTwo \voiceDownTwo Werner

Re: Changing voice order...

> I was thrilled and excited by your proposal. Having had some > leisure time this afternoon (although without net-access) I played > around with it. I've taken it as a local command, though. > > The result is a wrapper around simultaneous music, with and without > "\\". You can input

Re: Changing voice order...

>> \voiceOrder { 1, 3, 5, 7, 6, 4, 2 } >> << c'''2 \\ g'' \\ e'' \\ c'' \\ g' \\ e' \\ c' >> > > More like \voices 1,3,5,7,6,4,2 << ... >> if we want to keep in > current syntax. This is assuming a one-shot command taking the << > >> construct as its last argument. Hmm, my original idea was

Re: Augmentation dots regtests

> Looking at these, I suspect dot-columns on voices should be the > default. Perhaps that would increase the motivation to fix its > issues ;) Hehe, good argument :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Augmentation dots regtests

> Does moving the dot-column-engraver to voice sort out the confusing > horizontal spacing in these situations? First time I've seen that > and it does interesting things to the positioning of dots. Alas, it doesn't work reliably in many cases (because it works locally only) and it sometimes

Re: Changing voice order...

> To make it more visible I coded a small snippet annotating some info > to NoteHeads in > << .. \\ .. \\ ... ... ... >>-constructs. > > Output attached. Thanks! What about a two-step process: You first set up the order of the voices, then you input from top to bottom. Example: % current

Re: Augmentation dots regtests

> 1) The kievan dot for a notehead on a line moved to a space, when it >should have stayed on a line. > > 2) When notes are displayed without a staff, the dot should stay on >the same level as the notehead, but it shifts up a half space. > > I'd welcome a critical review of the regtests

Re: Augmentation dots reg test

>>What happens with your new code with overlapping, rather than >>stacked notes? E.g. << 4. // 2. >> (untested). >> >>I think from previous test cases it may become difficult to >>understand which dots behind to which notes. IIRC there's an >>outstanding bug about horizontal positioning in this

Re: Augmentation dots reg test

> I would like your opinion on whether the attached regression test, > which is different from the current development regression tests, is > correct. I think it is, but I'd like your opinions. Thanks, it looks fine. However, I second Chris's concerns regarding more complicated cases where you

Re: Augmentation dot positioning

> Fortunately, it was much easier than I feared it might be. > > Here's a revised version. Now all examples look fine. Halleluja :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Augmentation dot positioning

[Note that currently the descriptions are sometimes incorrect in the tests.] > Anyway, I've run through all the tests, and I think that the default > algorithm works exactly according to the Powell algorithm, as I > understand it. Mhmm, 22b, and 24b are not correct IMHO: The lowest dot should

Re: Changing voice order...

> Werner, that does not even make sense. [...] Ok, I completely misunderstood you, sorry. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Changing voice order...

>>This concerns << ... \\ ... \\ ... ... >> >> >>If we have more than one voice, voices are assigned in order: >> >>1/2, 1/2/3, 1/2/3/4, 1/2/3/4/5, 1/2/3/4/5/6 ... >> >>while the documentation is quite explicit that, ordered from top to >>bottom, assignments should be more like >> >>1/2, 3/1/2,

Re: Augmentation dot positioning

Thanks, Carl! > At a quick glance, the only two situations that need dots-limit =2 > are #11 and #23. Seconded. I also think that #13 also looks better with value 2 – the nearer the number of dots to the number of noteheads, the better. What about #24/2? Why is the lowest dot below the a's

Re: Dynamic text font

Some more comments. > When using customised fonts for dynamics, the following works just > fine: > > \override DynamicText.font-name = "Noto Serif Bold Italic" But the font name is *not* `Noto Serif Bold Italic'! The font name is `Noto Serif', and the style is `Bold Italic'. That `Noto Serif

Re: Dynamic text font

> It’s commercially licenced. I can’t, therefore. OK. First, I would like to see the fontconfig entry. Say fc-list -v > fc-list.log on the command line, search the entry for your font in the created log file and post it here. Then please get `ttx' from

Re: Dynamic text font

> But I have a new commercial Open Type font on the Linux system, > correctly installed as proven by being able to use it in other > applications: > > \override DynamicText.font-name = "Core Slab M 27 Cn ExtraLight Italic" > > but lilypond does not use it, despite reporting its existence using

Re: v2.19.47 on Mac x86 (Jacques Menu Muzhic)

>> https://bugs.freedesktop.org/show_bug.cgi?id=97546 >> >> The proposed fix hasn't been applied yet to the fontconfig git >> repository – maybe we should downgrade GUB's fontconfig version to >> 2.12.0 until this is fixed. > > I think that there is another possible solution. To use the >

Re: v2.19.47 on Mac x86 (Jacques Menu Muzhic)

> Most likely cause of the issue will be the 2.12.1 change that > improved cache validation logic (and for yet unknown reasons always > invalidates the cache of the Mac OS System fonts) > > https://www.freedesktop.org/software/fontconfig/release/ChangeLog-2.12.1 Aah, this rings a bell.

Re: Building Lilypond on Ubuntu 16.04

> What I did was: > > $ sudo ln -s /usr/include/freetype2/freetype/config > /usr/include/freetype2/config > $ sudo sed -i 's|/freetype2$|/freetype2/freetype|' > /usr/lib/x86_64-linux-gnu/pkgconfig/freetype2.pc > $ ./configure > $ make > > Which gives me a working lilypond 2.19.49. What I

Re: Building Lilypond on Ubuntu 16.04

> When I try to "make" Lilypond on Ubuntu 16.04, the freetype headers > are expected to be located in /usr/include/freetype2/. That's also > where Ubuntu's package libfreetype6-dev used to put them, at least > in Ubuntu versions 14.04 to 15.10, but in 16.04 (also 12.04, > interestingly), it's in

Re: Augmentation dot positioning

> OK, I have rewritten the code for augmentation dot positioning. Great, and thanks a lot! > Personally, I like the results of this code better than the Gould > recommendations. I would use this code, and make the default value > of chord-dots-limit be 1. I agree. > I'm attaching a copy of

Re: Augmentation dot positioning

> Attached with some extra cases I'd forgotten about (the inverted > versions of the final 6. Looks good, thanks. Please post this to the bug list so that a bugmeister can create an issue – since the old issue was tagged as fixed, a new one will be created. Werner

Re: Augmentation dot positioning

>>> Did you intentionally mark those examples with unnecessary dots as >>> "OK", rather than "FAIL"? Yes. >>> In my opinion, they should probably be failure cases. I don't think so. IMHO, the default should be value 0; if you increase the value, more dots do appear, so it's not a failure if

Re: Augmentation dot positioning

>> However, you have found a bug I think, since it doesn't seem to >> work correctly for your case, eliminating dots on the wrong side of >> the chord. > > Also, it’s clearly wrong to have dots in two ‘columns’. They look > like double-dotted notes. Please have a closer look! The lower chords

Re: Augmentation dot positioning

>> > The issue occurs when writing closely spaced chords with an >> > augmentation dot in the rhythm. Dots are placed only on spaces >> > (which we should expect), but in certain very easy to reproduce >> > conditions, the dot appears in an unexpected place. >> >> Cf. `regression/chord-dots.ly';

Re: Augmentation dot positioning

> The issue occurs when writing closely spaced chords with an > augmentation dot in the rhythm. Dots are placed only on spaces > (which we should expect), but in certain very easy to reproduce > conditions, the dot appears in an unexpected place. Cf. `regression/chord-dots.ly'; this is

Re: that acciaccatura issue

>> What hinders you *in trying* to create a minimum example? > > [...] > > I understand the intention of the requests (although not demands) > for minimal examples. But, as someone who has spent a lifetime > developing and debugging code, I can assure you that these demands > are strictly

Re: that acciaccatura issue

> Some comments amaze me: > "pretending to be a novice" > "you should already know" > "sounds like a lame excuse" > "it isn't rocket science" > > Even my parents were not so patronizing! Well, English is not my mother tongue, and I can't reply with such elegant and

Re: that acciaccatura issue

> I am amazed/surprised/confounded on the amount of time and effort > that has been expended on a justification of the "minimal" > requirement what could have been spent on just viewing (via > Frescobaldi not a PDF) the "errors" in my code. (Wow that was a run > on!). Mark, we try to

Re: Potential improvements to the homepage?

>> Because the Web site looks like it has been left to decay since the >> time when that design style was current, viewers are inclined to >> think the software may be in a similar condition. > > +1 > > That’s definitely one reason — maybe the main one — but there are > many others, of course. >

Re: \hideNotes and MIDI

>> shouldn't \hideNotes also suppress music output to the MIDI file? > > Why? \hide\ff is nice for inserting MIDI-only instructions. Mhmm. Given that it actually makes the corresponding object only transparent, thus influencing the typesetting process, I wouldn't call that `MIDI-only'. >

\hideNotes and MIDI

Folks, shouldn't \hideNotes also suppress music output to the MIDI file? Right now, it doesn't... Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: LilyPond logo?

>> Looks promising! Can you adjust the `packman' to have a softer gap? > > “softer”? shorter? narrower? Sorry, I don’t know what you mean ... Something similar to the waterlily logo at https://www.iconfinder.com/icons/566750/ecology_flower_flowers_green_lily_nature_water-lily_icon#size=512

Re: LilyPond logo?

> But maybe less is more and two flower layers are enough; so here is > a combination of logo3 and logo4 (only two flower layers -> less > detail, only one pad but with gap -> more typical). Looks promising! Can you adjust the `packman' to have a softer gap? Werner

Re: LilyPond logo?

From: Henning Hraban Ramm Subject: Re: LilyPond logo? Date: Fri, 5 Aug 2016 21:40:23 +0200 > > Am 2016-08-05 um 19:29 schrieb Noeck : > >>> https://www.iconfinder.com/icons/566749/flora_flower_flowers_green_lily_plant_water-lily_icon >> >> This one

Re: LilyPond logo?

> Here are some experiments of mine. Very nice! > logo1.svg is the one I used in the score, logo_outline.svg is the > outline version, logo2/3/4.svg are some attempts to make it simpler. I like logo3 most. Werner ___ lilypond-user mailing list

Re: Position fingerings for diatonic accordion that include button name (not just finger)

>> Nice to see you here! > > Yes, we miss you a lot too at the Polish bonfires :) Obviously, it's always the same folks lurking arond at the same places... Werner ___ lilypond-user mailing list lilypond-user@gnu.org

Re: how to get short broken ties

>> Note that this is not a theoretical issue. Especially in French >> impressionistic piano music like the works of Debussy and Ravel >> I've seen such a notation, and having a `\shortTie' command would >> be handy. > > See . Ah, ok,

Re: how to get short broken ties

>> Is there a snippet somewhere that explains how to do this? I tried a >> quick search without success. > > Maybe use \laissezVibrer? Nope. I wan't a generalized solution that works with MIDI also. Using callbacks for broken ties, I sort-of know how to implement the whole thing in Scheme.

how to get short broken ties

Folks, I want to change broken ties like this ___ o/ \ | _ ___ / \o/ \ | _ ___ / \o/ \ | into short ones. _ o/

Re: Cannot install lilypond on a shared Hostmonster server

> Update: I have tried to build the latest tar on my system, but I got the > following errors - interestingly all to do with symlinks: > > 70: extrac07.at:27 extracting symlinks to a read-only dir > extract extract07 read-only symlink > 76: extrac13.at:26 extract over symlinks >

Re: Cannot install lilypond on a shared Hostmonster server

>> > [~]# bash lilypond_install/lilypond-2.18.2-1.linux-64.sh --prefix lilypond >> >> I can't understand this. It looks like root's prompt, not a user's. > > It's just my user's prompt. It shows that I'm in my home dir. Are you sure? The `#' sign usually indicates a super-user shell,

Re: OT: high-precision tuner app

> I think you might have misunderstood what I was saying. [...] OK, I misunderstood :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: OT: high-precision tuner app

> "Perfect pitch" is a sham. [...] It seems that you don't know the facts very well. Absolute pitch is *not* related to being a `better' musician. In fact, it's not even related to music. Have a look at the Wikipedia article; it gives a nice overview. In general, I consider having an

Re: OT: high-precision tuner app

>> Absolutely fascinating stuff but bizarre all the considerations >> that affect pitch over time. > > Off topic, I know, but how do those gifted with perfect pitch cope > with all this? They simply dispair. I speak from experience :-) To a certain extent (say, plus-minus a whole note) I can

Re: Troubleshooting installing dev version of lilypond on ubuntu

>> I don't exactly know *why* you have this specific behaviour but I'm >> nearly sure that it is related to the fact that this calls your >> system version of Ghostscript instead of the one included in >> LilyPond, and that doesn't match. > > Maybe reconsider native PDF generation for LilyPond?

Re: Whitespace in LilyPond source files

> [... about other whitespace characters ...] > > Then the thought occurred to me, why? LP is not like python: it > might be whitespace-separated, but any indentation is semantically > meaningless. It's happy to take TABs as well as SPACEs, and even > end-of-lines, so why not other varieties of

Re: Single-note tremolos

> In reviewing Gould (p. 222), I found several defaults in LilyPond > that go against Gould's recommendations. > > 1) The tremolo lines are too wide (they should be only as wide as a >crotchet note head). This is a matter of taste, it seems. I have seen scores where the width of tremolos

Re: Replying to posts

> My Titanium Internet Security blocks this site as a "Dangerous Page." Hmm. Google doesn't do any warning... Looking into the .msi file to download, everything looks right (but I'm not the right person to investigate such issues). Werner ___

Re: Replying to posts

>> . Use the `reply-to-all' button so that the discussion stays on the >> list. It is not helpful if answers are suddenly sent to >> individuals only. Additionally, it helps to properly build up >> e-mail threads. > > Remove all non-list addresses from the reply list. No. Sometimes,

Re: Replying to posts

From: Werner LEMBERG <w...@gnu.org> Subject: Re: Replying to posts Date: Fri, 29 Apr 2016 07:19:48 +0200 (CEST) > >>> What about this? >>> >>> http://home.in.tum.de/~jain/software/outlook-quotefix/ >>> >>> I'm not an outlook user, but this

Re: Replying to posts

>> What about this? >> >> http://home.in.tum.de/~jain/software/outlook-quotefix/ >> >> I'm not an outlook user, but this looks quite promising (and is >> actively maintained)! > > Really? Runs on NT4 up to XP. Support up to Outlook 2003. That's > moribund by any standard, surely? Oops! I've

Re: Replying to posts

>> . Stay polite and avoid ad-hominem attacks. > > Is that a real rule, or only what we wish were a rule? Actively managing a mailing list is work. AFAIK, no-one is taking care of that, see my other mail. So yes, currently it is a wish. > I've seldom seen more ad hominem on any list than I

Re: Replying to posts

[David, please have a look to this e-mail.] > > Of course there is a list owner. > > Who, may one ask? Why are they taking no interest in this extensive > discussion? Ah, bad wording of mine. `List owner' is too big a word; the list was automatically created for the lilypond team by the

Re: Replying to posts

> Reading your admonition to "don't use top-posting," I tried to > locate the command in Outlook 2013 that sets this option as default. What about this? http://home.in.tum.de/~jain/software/outlook-quotefix/ I'm not an outlook user, but this looks quite promising (and is actively

Re: Replying to posts

> As far as I know this particular list does not have a list owner, > and there are no published rules. Of course there is a list owner. However, up to now there wasn't a single person who stomped our nuts too hard, so to say, forcing us to banning him or her from the list. In general, the

Re: Replying to posts

> For that, you want Visual Studio... Pfft. You are probably not aware that it is not possible to compile lilypond under Windows currently... It would be great if you could improve that. Werner ___ lilypond-user mailing list

Re: Replying to posts

> Would you suggest Frescobaldi is *not* a big improvement in the User > Interface for Lilypond development? No, it isn't. It is a big improvement for *using* lilypond (well, for all those guys and ladies who like IDEs), but for lilypond *development* you certainly don't need it. Werner

Re: Replying to posts

> Now I'm going to start an argument about your deplorable > capitulation to the masses by abandoning the venerable "ß". Well, the `ß' character is not abandonded at all in Germany and Austria! Only the rules have changed when to use it. Werner

Re: Replying to posts

From: Chris Yate Subject: Re: Replying to posts Date: Wed, 27 Apr 2016 13:01:41 +0100 > On 27 Apr 2016 12:40 pm, "N. Andrew Walsh" wrote: >>> >>> In german we have a saying: >>> "Leute fresst Scheisse. Millionen Fliegen können nicht irren." >> >>

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

> So far we only have an offer for a hard and incompatible transition > to Python3-only Actually, I dislike this. Similar to you, I don't see a convincing reason to not write python code that is compatible with both version 2 and version 3. Werner

Re: Tuplet number direction

>> Nice! One minor thing: If space allows, I would move the `3' a bit >> nearer to the center to reduce the curvature of the slur. > > You mean move the `3' nearer to the staff, right? Yep. Werner ___ lilypond-user mailing list

Re: Tuplet number direction

> Meanwhile I recoded it (using make-bow-stencil which is not > available in 2.18.2) making things way easier. Nice! One minor thing: If space allows, I would move the `3' a bit nearer to the center to reduce the curvature of the slur. Would that be possible? Werner

Re: Tuplet number direction

>>> is there a way to say typeset the tuplet bracket like a slur, with >>> the tuplet number inside? >> >> I once made the attached code. > > Very nice! LSR? Actually, I would even like to see this directly in lilypond! Such triplet slurs are used very often in the engraving epoch lilypond

Re: Set beam subdivision to #t by default

> So, before integrating that into my code I would collect opinions. > Are there any strong (and reasoned) objections against changing the > default here? Your suggestions looks sensible. Werner ___ lilypond-user mailing list

Re: Put text spanner below the staff?

> Yes, that's about par for the course. You fix a bug and get three > lines of condescension for it and half a line of "thank you", and > I'm sure that you consider this completely appropriate. Uh, oh, that's unwarranted IMHO, but... > I am not going to waste all my time second-guessing people

Re: Super and sub

>> I compared the Lilypond result of \super and \sub to the >> equivalents in LaTeX (because who would doubt that LaTeX is wrong >> in such a question) Please have a look at other, non-CM fonts also, since CM is sometimes a bit peculiar :-) >> - raise the superscript by 0.8 instead of 1.0 >> -

Re: Handling of subdivisions with shortened beams

>> b) Always do the second version (i.e. shorten to indicate the >>shortened length of the beam) I prefer this, and it seems to me that this would be a good default. Werner ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Behavior of non-flag side with strictBeatBeaming

> Am I right that you want a solution that prints exactly one beam less > than the neighboring stem with the least beams. Yes, since this looks quite natural to me (well, as far as something in your constructed example can look natural at all). Werner

Re: Behavior of non-flag side with strictBeatBeaming

> I have pulled together a complicated example, which is engraved with > a number of option combinations. For ease of discussion I have > numbered the stems. Thanks. My comments below are of general nature, not specific to subdivisions. > B) and C) are with just subdivideBeams on, but with

Re: Behavior of non-flag side with strictBeatBeaming

> given the following input > > \relative a' { > \time 6/8 > \set strictBeatBeaming = ##t > a8.. a32 a16 a > } > > which of the attached engravings do you prefer, LilyPond's current or > the modified? [Both images are called `document.png', which is not optimal :-)] I prefer the second

Re: Beaming over a rest before a subdivision

>> No beams over the rest. > > But if the user manually enters the beam enclosing the rest there > should be *something*. Ah, ok, I missed this. > And I think a single beam is better here than a number of steamlets. I agree. Werner ___

<    4   5   6   7   8   9   10   11   12   13   >