Freeman Gilmore wrote
> That is interesting, it is in the Private Use Area of Unicode, same area
> as
> Bravura.
Yup. In Emmentaler, there is one big exception I forgot to mention (but this
has nothing to do with accidentals):
The dynamic characters (f, m, p, etc.) are part of Emmentaler's text
Hi Ming
Le mer. 26 févr. 2020 à 22:30, MING TSANG a écrit :
> Pierre:
> Thank you for the \scale option, but the text part did not scale. refer
> to below:
>
Yes it does... Have you ckek the last line?
> On Wednesday, February 26, 2020, 03:43:02 p.m. EST, Pierre Perol-Schneider
> wrote:
>
Hello,
given two voices, for example:
\new Staff <<
\new Voice = "first"
{ \voiceOne c'8[ c'^> c' c']}
\new Voice= "second"
{ \voiceTwo \stemUp c''8[ c'' c'' c''] }
>>
... is it possible to make the script " ^>" avoid collisions on the other
voice too?
Thanks!
On Wed, Feb 26, 2020 at 6:09 PM Torsten Hämmerle
wrote:
> As far as I know, some special implementations are using SMuFL fonts, most
> notably Dorico's Bravura. These implementations will definitely use
> explicit code points.
>
> But LilyPond's makam.ly is making use of Emmentaler (Feta)
Hans,
Thank you for providing this. It works great, except for one bug I found. It
seems that when it’s installed it expects the file system to be using ISO Latin
1 rather than UTF-8. When I ran it on file names with non-ASCII characters in
UTF-8, it returned fatal errors like this:
Warnung:
On Wed, Feb 26, 2020 at 6:09 PM Torsten Hämmerle
wrote:
> As far as I know, some special implementations are using SMuFL fonts, most
> notably Dorico's Bravura. These implementations will definitely use
> explicit code points.
>
LilyPond converts the names to Unicode, the file can be found in
On Wed, Feb 26, 2020 at 1:46 PM David Kastrup wrote:
> Freeman Gilmore writes:
>
> > What is the name of the file that converts the glyph accidental names
> used
> > in the makam.ly to Unicode code points?
>
> I don't think we are working with Unicode code points in our output and
> fonts. At
As far as I know, some special implementations are using SMuFL fonts, most
notably Dorico's Bravura. These implementations will definitely use
explicit code points.
But LilyPond's makam.ly is making use of Emmentaler (Feta) glyphs, and, as
David pointed out, may change their code points each
Pierre:Thank you for the \scale option, but the text part did not scale.
refer to below:
The note is now outside the fish.
Thank you,Ming
On Wednesday, February 26, 2020, 03:43:02 p.m. EST, Pierre Perol-Schneider
wrote:
Hi Ming,How about \scale?e.g.:\version "2.19.84"
ymt = \markup
Hi Ming,
How about \scale?
e.g.:
\version "2.19.84"
ymt = \markup {
\note #"16" #1
" yMt"
\scale #'(.5 . .5)
\postscript #"0.075 setlinewidth 0 -2.5 moveto -13.75 10 -10 -7 2.5 5
rcurveto stroke"
}
\markup\ymt
\markup\scale #'(1 . 5)\ymt
Cheers,
Pierre
Le mer. 26 févr. 2020 à
dear lilyponders,
I have the following postscript code. How can I make it smaller or larger?
ymt = \markup { \note #"16" #1 " yMt" \postscript #"0.075 setlinewidth 0
-2.5 moveto -13.75 10 -10 -7 2.5 5 rcurveto stroke"}
image after lilypond compilation:
Thank you for the help.Ming
Freeman Gilmore writes:
> What is the name of the file that converts the glyph accidental names used
> in the makam.ly to Unicode code points?
I don't think we are working with Unicode code points in our output and
fonts. At some point of time it might be interesting to employ the code
points
What is the name of the file that converts the glyph accidental names used
in the makam.ly to Unicode code points?
Thank you, ƒg
How can I specify a font directly via a path?
For example, I want something like this to work:
\override LyricText.font-name = "./fonts/MyFont.otf"
Thanks!
While not what I was expecting, it works well for me. (I was expecting them to
have been merged into a single grob, not to be printed on top of eachother). If
anyone was curious about it, my rather more aggressive hack was:
%
\version "2.19.84"
{ <\tweak Accidental.alteration
15 matches
Mail list logo
