At 14:40 17/10/2018 -0500, David Wright wrote:
The # wiki notes that British Telecom used the term "square" for
hash at one time.
Surely not? Rather, they presumably used the term "square" for square
- which is what was on the spare key on early designs of keyboard now
occupied by the hash
Hi Davide,
Avoid the the LilyPond \tempo command entirely: then use markup (in text
spanner bound-details) for everything. Alignment (baseline and otherwise)
can then be controlled with text spanner bound-details.
If you need an empty region of of whitespace between two elements in your
Hi Urs,
I went through this a couple of months ago, and it *seems* possible to use
markups (and paths) as legitimately new articulations (maybe -- and happily
-- in contradiction to the assumption in your original post, if I'm reading
correctly).
Here's the pattern as a MWE:
%%% BEGIN NOVEL
Hi everyone,
I’m transcribing an old choral score for LilyPond (full source at [1]),
and while I’ve been mostly successful so far, one thing I haven’t
figured out yet is the extenders. In the original score, several notes
have extenders in the lyrics, to indicate the duration of the note
relative
On 2018-10-17 11:35 am, Jacques Menu wrote:
Last questions : in a programming language a C or Python, what should
one write as character strings to obtain the code for example Example
1.8.1-1, and what font or tool should one use to get it displayed as
shown in the PDF doc?
Braille can be
On Wed 17 Oct 2018 at 20:35:22 (+0200), Jacques Menu wrote:
> Hello Hwaen and Aaron,
>
> Thanks Aaron for the very useful link at www.brailleauthority.org.
> What I meant by non confidential examples is exactly that, small scores with
> full Braille Music code and the corresponding western,
\setOption stylesheets.span.use-colors ##f
did the trick.
Thanks Urs
On Wed, 17 Oct 2018 at 15:40, Urs Liska wrote:
>
>
> Am 17.10.2018 um 03:00 schrieb Craig Dabelstein:
>
> Hi all,
>
> Is this the right code to use to turn off the colors in ScholarLy? I'm
> using the latest version, but I'm
On Wed 17 Oct 2018 at 15:43:40 (+0200), Thomas Morley wrote:
> I'd like to propose the code below. Attached as well.
>
> It stores the info in a string, which is converted to a nested list
> suitable for 'systemStartDelimiterHierarchy'. It can be nested in
> arbitrary depth.
>
> I used the
Hello Hwaen and Aaron,
Thanks Aaron for the very useful link at www.brailleauthority.org.
What I meant by non confidential examples is exactly that, small scores with
full Braille Music code and the corresponding western, graphical scores.
IIUC the original post about MusicXML export,
Am Mi., 17. Okt. 2018 um 15:43 Uhr schrieb Thomas Morley
:
> I'd like to propose the code below.
>
> It stores the info in a string, which is converted to a nested list
> suitable for 'systemStartDelimiterHierarchy'. It can be nested in
> arbitrary depth.
>
> I used the following signs:
> []
On 2018-10-16 11:38 pm, Jacques Menu wrote:
Hello folks,
I read in the recent Export to MusicXML thread about braille scores.
Sorry if this is offtrack : I didn’t find on the Internet how such
scores are structured (the details of notes and the like is there
alright) and what font(s) should be
Hi Lukas-Fabian,
I finally found the time to look deeper into it.
Am So., 14. Okt. 2018 um 15:07 Uhr schrieb Lukas-Fabian Moser :
> For me, there are the following issues with the systemStartDelimiterHierarchy
> design:
>
> 1) There's an overlap between systemStartDelimiter and
>
Urs Liska writes:
> Hi,
>
> I'm trying to write an event-function that creates both a slur and a
> markup on opposite sides. I can do that by manually specifying the
> directions:
>
> \version "2.19.82"
>
> testDirection =
> #(define-event-function ()()
>#{
> _(
> ^"Text"
>#})
Hi,
I am wondering about the execution order of the callback functions. I
would have assumed that the 'stencil callback would *always* be executed
before or after the 'after-line-breaking callback. However, when I tried
to investigate this I found that in
\version "2.19.82"
{
c'
Hi,
I'm trying to write an event-function that creates both a slur and a
markup on opposite sides. I can do that by manually specifying the
directions:
\version "2.19.82"
testDirection =
#(define-event-function ()()
#{
_(
^"Text"
#})
{
c' \testDirection d' )
}
but I have
Greetings Jacques,
Could you further clarify your questions? Are you asking how Braille
music is generally structured on the physical page? And what is meant
by a non confidential example?
Hwaen Ch'uqi
On 10/17/18, Jacques Menu wrote:
> Hello folks,
>
> I read in the recent Export to MusicXML
Hello folks,
I read in the recent Export to MusicXML thread about braille scores.
Sorry if this is offtrack : I didn’t find on the Internet how such scores are
structured (the details of notes and the like is there alright) and what
font(s) should be used to display them.
Accessing non
17 matches
Mail list logo
