Re: 48 and 72 ET

On 10/02/2017 04:47, Thomas Richter wrote: > I wrote an extension for 72ET "Ekmelily": > http://www.ekmelic-music.org/en/extra/ekmelily.htm > It uses by default ins own font (Ekmelos) but it should work with e.g. > Bravura, too. > Thanks, Thomas. It looks like excellent work. It should be

Re: Multiple markings

On Tue, 2017-02-07 at 23:01 +0100, Thomas Morley wrote: > Meanwhile why not use some of the workarounds? > > (1) > \mark \markup <\[center-]column> > (already mentioned) > > (2) > http://lsr.di.unimi.it/LSR/Item?id=976 > or > http://lsr.di.unimi.it/LSR/Item?id=977 > > (3) >

Double time signature when there are grace notes

Dear all, I need help with the following situation: \version "2.19.54" << { c'1 \break \time 15/16 \grace a'16 b'2... } { R1 \break \time 15/16 c'2... } >> This results in the attached output. Is that a bug or is this supposed to be encoded differently? There are dirty

chord names

I'm trying to figure out how to make chord modifiers like "sus4" not be superscript. It seems like there should be a simple way to do that, but I don't see it in the "Customizing Chord Names" section

Re: Double time signature when there are grace notes

Hello Thomas, Not a bug, but a feature : you have to add graces in all voices : \version "2.19.44" << { c'1 \break \time 15/16 \grace a'16 b'2... } { R1 \break \time 15/16 \grace s16 c'2... } >> JM > Le 10 févr. 2017 à 23:23, Thomas Weber

Re: tuplet slurs

Hi Werner, On Thu, Feb 9, 2017 at 12:53 PM, Werner LEMBERG wrote: > > For voices with lyrics it is common to put triplet indications always > above the staff, using the following rules. > >. stems up or down, no beam: as usual (i.e., a number and a bracket > at the top, as

Re: tuplet slurs

On 09/02/17 18:53, Werner LEMBERG wrote: > > For voices with lyrics it is common to put triplet indications always > above the staff, using the following rules. > >. stems up or down, no beam: as usual (i.e., a number and a bracket > at the top, as if using \tupletUp) > >. stems

Re: Double time signature when there are grace notes

Am 10.02.2017 um 23:48 schrieb Jacques Menu Muzhic: > Not a bug, but a feature Well, I'd say a bug but a well known one: https://sourceforge.net/p/testlilyissues/issues/34/ Joram ___ lilypond-user mailing list lilypond-user@gnu.org

Re: chord names

Hi Ben, Benjamin Bloomfield wrote > I'm trying to figure out how to make chord modifiers like "sus4" not be > superscript. for your first issue you can modify what you've found in "Customizing chord names": % --- chExceptionMusic = {

Re: chord names

Benjamin Bloomfield wrote > I'm trying to figure out how to tweak the size of the sharp and flat > symbol that displays when the chord name has one in it. Those symbols are > slightly taller than the capitals in my font, and I'd like to get them > even. Maybe there's an easier way, but here's a

Re: Double time signature when there are grace notes

Am 10.02.2017 um 23:48 schrieb Jacques Menu Muzhic: Not a bug, but a feature : you have to add graces in all voices : I already realized that: Le 10 févr. 2017 à 23:23, Thomas Weber a écrit : * I can add a "grace space" to the bottom staff But I tried to avoid this

Re: 48 and 72 ET

> On 10 Feb 2017, at 00:35, David Kastrup wrote: > > Hans Åberg writes: > >>> On 10 Feb 2017, at 00:16, David Kastrup wrote: >>> >>> So is there any reason people don't use convert-ly when upgrading to >>> a newer version? >> >> For

Re: 48 and 72 ET

> On 10 Feb 2017, at 00:39, msk...@ansuz.sooke.bc.ca wrote: > > On Fri, 10 Feb 2017, David Kastrup wrote: >> enthused. Why wouldn't we want to have best practices pointed out and >> promoted on the user list? > > Best practices do not include attacking other list users. It is the human

Re: New LilyPond website

On Thu, 9 Feb 2017 14:32:18 -0800, "H. S. Teoh" wrote: > I don't speak for anyone else, but I'm perfectly OK with using > Javascript -- as long as it's not *required* for the website to be > usable at all. And all necessary javascript is loaded from the site itself, not

Re: 48 and 72 ET

Am 09.02.2017 um 20:18 schrieb Bernardo Barros: Hello, Quarter-tones (24ET) work very well and use the most used symbols. Is there any implementation of eighth-tone (48ET) with arrows for the 8th-tone alterations, or even better, 72ET? I know "makam.ly" could be a good start, I'm just

Re: 48 and 72 ET

> On 10 Feb 2017, at 00:55, Simon Albrecht wrote: > > On 10.02.2017 00:19, Hans Åberg wrote: >> If LilyPond knows how to run the code via convert-ly, why does it not do it? > > LilyPond itself doesn’t change the code it is reading. convert-ly is a > separate Python

Re: 48 and 72 ET

Hans Åberg writes: >> On 10 Feb 2017, at 00:39, msk...@ansuz.sooke.bc.ca wrote: >> >> On Fri, 10 Feb 2017, David Kastrup wrote: >>> enthused. Why wouldn't we want to have best practices pointed out and >>> promoted on the user list? >> >> Best practices do not include

Re: 48 and 72 ET

> On 10 Feb 2017, at 10:24, David Kastrup wrote: > > Hans Åberg writes: > >>> On 10 Feb 2017, at 00:39, msk...@ansuz.sooke.bc.ca wrote: >>> >>> On Fri, 10 Feb 2017, David Kastrup wrote: enthused. Why wouldn't we want to have best practices pointed out

Re: 48 and 72 ET

> On 10 Feb 2017, at 10:22, David Kastrup wrote: > > Hans Åberg writes: > >>> On 10 Feb 2017, at 00:35, David Kastrup wrote: >>> >>> Hans Åberg writes: >>> > On 10 Feb 2017, at 00:16, David Kastrup

Re: 48 and 72 ET

> On 10 Feb 2017, at 00:34, Urs Liska wrote: > > Am 10.02.2017 um 00:22 schrieb Hans Åberg: >>> So is there any reason people don't use convert-ly when upgrading to a >>> newer version? >>> >> For libraries, you would want to keep track of the changes, but running >>

Re: 48 and 72 ET

> On 10 Feb 2017, at 04:20, Bernardo Barros wrote: > > On 09/02/2017 17:22, Hans Åberg wrote: > >> 1. >> https://secure2.storegate.com/Shares/Home.aspx?ShareID=35e0b920-6910-4e4f-8340-7d8290115dda > thank you! Let me know if it works!

Re: 48 and 72 ET

Hans Åberg writes: >> On 10 Feb 2017, at 00:35, David Kastrup wrote: >> >> Hans Åberg writes: >> On 10 Feb 2017, at 00:16, David Kastrup wrote: So is there any reason people don't use convert-ly when

Re: New LilyPond website

> in total. After enabling scripts this problem vanishes. > > In Vivaldi I don't see the background image at the top of the page > at all. > > > I test using all major browsers including Vivaldi (my main browser) and > I am not getting any of these issues. Hmm. What is that to

Re: 48 and 72 ET

> On 10 Feb 2017, at 10:58, David Kastrup wrote: > > Hans Åberg writes: > >>> On 10 Feb 2017, at 10:24, David Kastrup wrote: >>> >>> Hans Åberg writes: >>> > On 10 Feb 2017, at 00:39, msk...@ansuz.sooke.bc.ca wrote:

Re: 48 and 72 ET

Hans Åberg writes: >> On 10 Feb 2017, at 10:24, David Kastrup wrote: >> >> Hans Åberg writes: >> On 10 Feb 2017, at 00:39, msk...@ansuz.sooke.bc.ca wrote: On Fri, 10 Feb 2017, David Kastrup wrote: > enthused. Why

Re: New LilyPond website

On Fri, 10 Feb 2017 10:51:05 +0100, Michael Gerdau wrote: > The new page is about 1.3 MB while the original one is about 170 kB > Factor of 7.x This is due to CSS/JS overhead and happens only once. -- Johan ___ lilypond-user mailing

Re: long `instrument' names in frenched scores

Hi Werner, > In vocal scores it is common that singer parts that were omitted for > some sytems are introduced again with its full name – not written in > front of the system but at the beginning of the line. > > Do we have support for this feature already? As far as I know, the answer is no.