[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Jianpu music notation question
From: |
Menu Jacques |
Subject: |
Re: Jianpu music notation question |
Date: |
Mon, 21 Aug 2017 08:59:43 +0200 |
Hello David,
Thanks for the information, I’ll look into the NoteNames context.
A nice day!
JM
> Le 21 août 2017 à 08:22, David Kastrup <address@hidden> a écrit :
>
> Menu Jacques <address@hidden> writes:
>
>> As someone mentioned on this list some time ago, Silas S. Brown has written
>> jianpu-ly, described at
>> http://people.ds.cam.ac.uk/ssb22/mwrhome/jianpu-ly.html, that
>> produces LilyPond code from a custom text description of the score.
>>
>> This leads to code such as:
>>
>> #(define (note-one grob grob-origin context)
>> (if (grob::has-interface grob 'note-head-interface)
>> (begin
>> (ly:grob-set-property! grob 'stencil
>> (grob-interpret-markup grob
>> (make-lower-markup 0.5 (make-bold-markup "1")))))))
>>
>> \applyOutput #'Voice #note-one
>> c''4[^. ~
>>
>> with one specific function (note-one here) per note in the scale.
>
> Surprisingly awful.
>
>> Would a note engraver producing numbers instead of glyphs be a way
>> worth going for obtaining the same while keeping the regular syntax,
>> i.e. without any function such as 'note-one’ above being needed?
>
> Sounds like the way to go. Basically to be used as a part of a Jianpu
> context akin to the NoteNames context.
>
>> A by-product of this approach might be the generation of ABC music
>> notation, see http://abcnotation.com, with LilyPond btw.
>
> I don't think this would make a lot of sense since there is no point in
> getting a printed ABC score rather than a file of ABC input. So you
> would want a completely different output definition from \layout.
>
> --
> David Kastrup
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user