Yes, I regularly use this snippet to set the document fonts. I think I
learned it from Abraham Lee. IIRC, Frescobaldi also pasted it with the
menu entry
Tools > Document fonts …
What is the new and correct command? What Frescobaldi gives me?
\paper {
#(define fonts
(set-global-fonts
Hi Lukas,
once again, I am no expert on ancient notation. So I don't know whether the
length of the stems in your renaissance style are required to be exactly as long
as they are now. They roughly end in the middle of a staff space for notes on
this position and on a staff line for notes on a
http://clairnote.org / lilypond-web-demo2/
Hi Paul,
I like your changes to the website. Especially the flatter gradient in the top
menu is more modern. I would even have preferred the removal of the background
image and the small icon next to LilyPond. Others see that differently.
Two small
Am 20.01.2014 18:02, schrieb Alex Loomis:
I'm still getting a lot of warnings, but it works beautifully!
The word silence is in roman, but commenting out the line
\override-lines #'(font-name . Century Schoolbook L)
makes it italic. I assume this is because you need to specify an
Hi,
this is another thing, but how about adding a nice standard notation
example to the wikipedia entry?
(like http://lilypond.org/ly-examples/bach-bwv610.png)
This Stockhausen is very impressive if you want to know that you can
tweak most everything to your needs. And it is now really close to
For me it now looks heavily distorted (wrong aspect ratio)
Joram
Am 13.01.2014 12:26, schrieb Werner LEMBERG:
Attached are a source version, without the font change for the time
sig which crashes SVG creation, and the SVG output.
Thanks! Looks great. I've updated the Wikipedia page.
Am 13.01.2014 14:04, schrieb Werner LEMBERG:
For me it now looks heavily distorted (wrong aspect ratio)
Which browser?
Firefox 26, Chromium and Konqueror 4.8.5 - also after reload.
On the other hand, the uncropped SVG image
works for me now.
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 06.01.2014 12:17, schrieb lemzw...@googlemail.com:
I've now had some time to check the glyphs. Here my comments.
1. Please make all corners round in `clefs.varC' and `clefs.tenorG'.
2. In `clefs.tenorG', I'm not sure that the left `slanted' end of the
top horizontal bar should really
Am 24.03.2013 12:34, schrieb David Kastrup:
Werner LEMBERG w...@gnu.org writes:
The axis names are #X and #Y so I am not in favor.
What about changing axis names as well?
I'm all for it.
Not really easy. We have in C++ macros X Y LEFT RIGHT etc, and making
them lowercase would heavily
Am 20.03.2013 19:10, schrieb Werner LEMBERG:
But there are millions of TeX users who are used to \phantom. And I
believe that a lot of Lilypond users are TeX users also. This means
that those users are already acquainted with this command and can
easily deduce what it does.
I think knowing
Even while I am a bit sceptical whether the syntax for R should differ
from r, I see your point.
Rather than R14 for a 14 measure rest, I would suggest to keep the
syntax close to the one before: R*14 (This way I would almost be
convinced ;) )
Could the duration be optional this way, keeping the
Hi,
I would like to add some thoughts to that:
1.) What I use (and what is probably the most frequent case) are:
a) \repeat {} and \alternative { {} {} } % repeats
b) \bar || % new section
c) \bar |. % end of staff
The first is syntactical the others are bar lines. Syntactical elements
for
Is
http://lilypond.org/website/pictures/double-lily-modified3.png
available at higher resolution (or even as a vector graphic) anywhere?
Hi!
Wouldn't it be a good idea to invent a new/derived LilyPond logo as
vector graphic and perhaps a bit more schematic/abstract (like logos
typically
Am 13.01.2013 19:31, schrieb m...@mikesolomon.org:
… It is possible to do accidental configuration
scoring with a priority queue, very much how we do slurs. But I have
no clue how much this would slow the program down.
It is only an issue for chords with more than 2 accidentals, which
should
I summarize the open issues, concerning the German translation (point 3
is could be also concerns the English documentation).
Am 13.11.2012 21:15, schrieb Joram Berger:
Hi,
recently, I noticed some spots in the documentation, where I think that
could be wrong – at least I don't understand
Hi,
recently, I noticed some spots in the documentation, where I think that
could be wrong – at least I don't understand why it is documented like that:
1)
http://lilypond.org/doc/v2.16/Documentation/notation/writing-rhythms#scaling-durations
It is:
% Scale music by *2
Should it be?
% Scale
Am 13.11.2012 23:59, schrieb Keith OHara:
Joram Berger joram.noeck at gmx.de writes:
http://lilypond.org/doc/v2.16/Documentation/notation/writing-rhythms#scaling-
durations
It is:
% Scale music by *2
Should it be?
[ ... ] % Divide durations by 2
The notes are typed printed
Am 14.11.2012 00:15, schrieb Trevor Daniels:
Joram Berger wrote Tuesday, November 13, 2012 8:15 PM
recently, I noticed some spots in the documentation, where I think that
could be wrong – at least I don't understand why it is documented like that:
1)
http://lilypond.org/doc/v2.16
Some comments from my usage experience.
Am 12.11.2012 12:27, schrieb David Kastrup:
Francisco Vila paconet@gmail.com writes:
...
The fundamental question for an user (and he thinks it is for all new
users, too) was to realize that lilypond is a programming
language. Every syntax is
Dear developers,
how about integrating the chordmode into normal music syntax?
Reasoning: chords are music, too. And with … chords are already
possible in the music input. Many modifiers like duration, alteration,
etc. are also possible with chords. So they are similar in many ways.
A solution
Hi,
here is another (probably not so well thought) idea:
Issue: \noBeam is a quite long command if used heavily and for the
opposite feature [ and ] represent much more convenient solutions.
Possible solution: use X or ; (or any other reasonable token as a
\noBeam equivalent.
Again, this is
Am 06.11.2012 22:10, schrieb David Kastrup:
Joram Berger joram.no...@gmx.de writes:
Hi,
here is another (probably not so well thought) idea:
Issue: \noBeam is a quite long command if used heavily and for the
opposite feature [ and ] represent much more convenient solutions.
Possible
Am 07.11.2012 00:10, schrieb David Kastrup:
Joram Berger joram.no...@gmx.de writes:
Am 06.11.2012 22:10, schrieb David Kastrup:
Joram Berger joram.no...@gmx.de writes:
Hi,
here is another (probably not so well thought) idea:
Issue: \noBeam is a quite long command if used heavily
Am 04.11.2012 01:36, schrieb David Kastrup:
Eluze elu...@gmail.com writes:
do you really want to add /francais/?
It's not likely more scary to the French than espanol is to the
Spanish. Basically there are two options making sense to me: native
language name in utf-8, or English language
Am 04.11.2012 00:17, schrieb David Kastrup:
Joram Berger joram.no...@gmx.de writes:
Would it be an idea to add … français as aliases to italiano?
According to my knowledge in French, the note names are the same and
bémol/dièse also fits with the Italian abbreviations -b/-d.
I think
janek.lilyp...@gmail.com:
Ah, so \language español will do the same as \language espanol?
That's nice.
http://codereview.appspot.com/__6811060/
As far as I see, there is no language french or français.
Would it be an idea to add french, francais and français as
aliases to italiano (like
janek.lilyp...@gmail.com:
Ah, so \language español will do the same as \language espanol?
That's nice.
http://codereview.appspot.com/__6811060/
As far as I see, there is no language french or français.
Would it be an idea to add french, francais and français as
aliases to italiano (like
Hi,
could the lilypond options to specify the output file format be unified?
Currently, depending on the format, there are different options:
--pdf or --formats=pdf (and ps and png)
-dbackend=svg (eps, scm, …)
Even though things are perhaps a little bit different, I would suggest
to include svg
Am 23.10.2012 09:08, Federico Bruni:
2012/10/23 Joram Berger joram.no...@gmx.de:
Even though things are perhaps a little bit different, I would suggest
to include svg (or the whole backend-options) into formats, if possible.
Because thats essentially what the user wants: get the output
Dear developers,
is there a reason that the forced accidental must not be written before
the octavation? It took me some time to figure out which order does compile.
(a) This works: cis'!='
(b) This doesn't: cis!'='
However, I would consider (b) more logical as the exclamation mark
forces the
Am 16.10.2012 02:44, schrieb David Kastrup:
Most of the things that would count as simplifications are so because
they drop details used for distinguishing things told to the computer.
Where those distinctions are distinctions between non-sensical
directions and potentially useful directions,
Dear Lilypond developers,
I joined this list to thank you all for your amazing work!
In 2002, I was searching for a free music typesetting program. From the
first moment, when I found Lilypond I liked how Lilypond cares about
beautiful scores and how well thought the basic syntax is. Since then
Am 15.10.2012 22:14, schrieb Janek Warchoł:
dear Werner,
On Mon, Oct 15, 2012 at 9:38 PM, Werner LEMBERG w...@gnu.org wrote:
we've now had zillions of e-mails without coming to a concensus.
David has shown extreme patience in discussing all aspects, and I want
to have at least *some*
34 matches
Mail list logo