I'm creating a custom bookTitleMarkup for a project I'm working on and
have some lines which are setup like `meter` and `arranger` in the
default template (two blocks of text, one flushed left the other right,
on the same line).
However, on one of those lines the header properties to be used
I would like to add the basic solfege note names to the english language
module so that I can enter music (mostly chant) using solfege and then
use `\transpose` to adjust its sounding pitch to create a midi file
which can be used for practice. So far, I've done this by editing
On 3/27/18 4:48 AM, Thomas Morley wrote:
Though, examples to define and use an own language can be found in
makam.ly and bagpipe.ly
>
Leads to below, note: only the method is demonstrated, `myNames' needs
to be extended, ofcourse
Does the new language have to be defined from scratch? Is
On 3/27/18 2:42 PM, Torsten Hämmerle wrote:
Br. Samuel Springuel wrote
Is there a way to import into the new language the note names from an
existing language?
Yes.
All the note name definitions are contained in the associated list
language-pitch-names
When applying (assoc-get 'english
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
On 2018-11-03 2:10 PM, David Baptista wrote:
c'
For Lilypond the tab is 8 spaces, thus the c' is on columns 9 and 10
(one column for each character). Lilypond is not aware of your editor
settings (which change that result) and thus cannot account for that.
The "\t" = "" convention
On 10/3/18 7:09 PM, Kevin Barry wrote:
lualatex lyluatest.ly --shell-escape
That's the wrong order. Options come before the file name.
--
✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
St. Anselm’s Abbey
4501 South Dakota Ave, NE
Washington, DC, 20017
202-269-2300
(c)
On 9/19/18 6:23 PM, Urs Liska wrote:
Do you have any concerns about the limitations with regard to the use of
the Score Wizard for the Score Wizard's use case too?
The limitations I was worried about were related to the lack of variety
of the glyphs involved in the preview. When it comes to
As my general use case is hymns for congregational singing, if I were to
find the time to create a sample, it would probably have the following
characteristics:
Notes of all durations from 1/16 to whole.
Some of the 1/8 and 1/16 notes would be beamed while others unbeamed.
Some slurs and ties.
On 9/21/18 12:31 PM, Urs Liska wrote:
Slurs and ties are not part of the music font and therefore look the
same, regardless of the font.
Good to know. I guess then they ought to be left out of the preview.
I think the fact that it'd be vocal music would be different enough.
Especially the
The one problem that jumps out at me about Karlin's proposal is that the
information about the font type (OTF, SVG, WOFF) and whether or not that
type has a defined brace would be lost. That sort of information can be
important depending on your target file format. If you can find a way
to
I was in the process of noting the limitations of the Score Wizard
preview and how they made it less useful for a font preview when your
preliminary demo came through. Since I think the preliminary demo is
great and addresses my concerns, I'm scrapping that post just to say I
like where the
On 2018-12-17 12:08 PM, David Kastrup wrote:
Uh, anything wrong with the obvious
custom = \markup { PRAELUDIUM I \italic { italicized text } Back to
normal }
?
It works in the MWE I posted, but not in my original use case (the
contents of the field disappear entirely. After some
Thanks Harm. The code may not be fully tested, but it does seem to do
the job for me. There was one issue I ran into. I have a
`\wordwrapright-field` and `\wordwrapcenter-field` which I make use of
in this project and I had to load your code before I defined those
commands (if done in
What is the best way to suppress the default scoreTitleMarkup? I've
been using `scoreTitleMarkup = \markup \null` but this is creating an
extra space above the score (which, with lilypond-book-preamble.ly,
comes out as an empty "system"). I'm defining a custom titling format
in which I want
I'm making use of a custom header (with custom fields) and have come
across a situation in which I need to apply custom formatting (italics)
to a piece of the field (just a handful of words in the middle). Given
that the header fields are normally simple strings, is there a way to
format part
On 2018-12-18 2:22 PM, Kieren MacMillan wrote:
scoreTitleMarkup = ##f
That did it. Thanks.
--
✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
St. Anselm’s Abbey
4501 South Dakota Ave, NE
Washington, DC, 20017
202-269-2300
(c) 202-853-7036
PAX ☧ ΧΡΙΣΤΟΣ
On 2019-04-02 11:05 AM, Kieren MacMillan wrote:
The auto-beamer should beam according to the settings that it would apply if
there were no rests.
I don't think it's quite that simple as rests that begin or end beam
groups wouldn't have beams over them, only ones in the middle.
It might be
101 - 118 of 118 matches
Mail list logo
