2008/12/10 Carl D. Sorensen <[EMAIL PROTECTED]>:
> On 12/9/08 6:12 PM, "Francisco Vila" <[EMAIL PROTECTED]> wrote:
>> Yes, because the problem is that explicitly created staves have to be
>> given English names 'up' and 'down' if they are to be used for the
>> autochange feature. This is illustrate
On 10 Dec 2008, at 07:40, Graham Breed wrote:
Not using key signatures will not solve that problem.
I didn't say anything about not using them -- although, as it happens,
they are trouble in microtonal music. What I said is that they lead
to confusion. The main point is that learning contra
On 10 Dec 2008, at 07:55, Graham Breed wrote:
I attach an example file.
I don't see any transpositions.
From what I recall, if one uncomments the key signature, lilypond
complains that it cannot handle the rational numbers. So one does not
get as far as doing transpositions. Otherwise, o
On 12/10/08 1:37 AM, "Francisco Vila" <[EMAIL PROTECTED]> wrote:
> 2008/12/10 Carl D. Sorensen <[EMAIL PROTECTED]>:
>> On 12/9/08 6:12 PM, "Francisco Vila" <[EMAIL PROTECTED]> wrote:
>>> Yes, because the problem is that explicitly created staves have to be
>>> given English names 'up' and 'down
On 12/9/08 9:51 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> On Tue, Dec 9, 2008, "Carl D. Sorensen" <[EMAIL PROTECTED]> said:
>> On 12/9/08 4:37 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>
>> You're confusing users with developers. Code and data structures are
>> developer-only ite
2008/12/10 Hans Aberg <[EMAIL PROTECTED]>:
>
> On 10 Dec 2008, at 07:40, Graham Breed wrote:
>> Transpositions aren't "computed against" any equal temperament. If
>> you transpose by a comma, then a comma will be added or subtracted
>> from the previous alterations. The resulting alterations wil
On Tue, Dec 09, 2008 at 07:35:41PM +, Neil Puttock wrote:
> I've tweaked the examples for `Clef' in the Glossary, and they seem to
> be the only examples which use [quote]. Shouldn't this apply to all
> the snippets?
Ideally yes, but the glossary is very low priority and we haven't
been too p
2008/12/10 Werner LEMBERG <[EMAIL PROTECTED]>:
>> > Since you put 'scheme' in single quotes, I suspect you don't know
>> > about Scheme programming. Scheme is a Lisp-like programming
>> > language.
>>
>> ()()((()))()()(((
>>
>> I hope not, that kinda stuff leaves me with a headache, th
On 10 Dec 2008, at 12:47, Graham Breed wrote:
I did it for E53 - it did not work. I attach a file.
No you didn't. You did something else in E53 and that didn't work.
There are still no transpositions. There are some attempts to get the
MIDI output to work. Did it? It looks like you're on t
2008/12/10 Hans Aberg <[EMAIL PROTECTED]>:
> On 10 Dec 2008, at 07:55, Graham Breed wrote:
>
>>> I attach an example file.
>>
>> I don't see any transpositions.
>
> From what I recall, if one uncomments the key signature, lilypond complains
> that it cannot handle the rational numbers. So one does
On 10 Dec 2008, at 12:47, Graham Breed wrote:
Perhaps you mean the between a sharp and a flattened M, like
between F# and
Gb, which may be positive or negative. Since I do not impose any such
relations, those are not confused.
Yes, that's the one. If you only record pitches with M and m the
On 10 Dec 2008, at 13:01, Graham Breed wrote:
doing transpositions. Otherwise, one could have written
\key b \bayati
Say what? You're talking about key signatures again, not
transpositions.
I just assume the system for transposing key signatures is synced
with that.
You can uncomment
On Sat, Dec 6, 2008 at 8:24 PM, Till Rettig <[EMAIL PROTECTED]> wrote:
> Thanks I know. Actually I just discovered that Century Schoolbook is to
> blame: indeed it doesn't include small caps. Didn't check how pango/lilypond
> handles a font that includes them.
>
It will try to substitute small c
On Wed, Dec 10, 2008 at 08:01:08PM +0800, Graham Breed wrote:
> I've checked the documentation for key signatures and see no
> indication that \key b \bayati could possible work though.
Say what?
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Arabic-music#Arabic-key-signatures
Doc team
On 10 Dec 2008, at 15:04, Graham Percival wrote:
I have no clue (beyond "microtones") what you two have been
talking about, but perhaps Hans should take a serious look at what
is ALREADY WORKING in 2.11.65 before discussing new features.
The guy set it in E24, which is obviously wrong.
Hans
On 10 Dec 2008, at 15:04, Graham Percival wrote:
You'll want to pay special attention to ly/arabic.ly, and make
sure you understand everything that's happening in there.
Have you looked it into yourself? - It goes on like
bayati = #`(
(0 . 0)
(1 . ,SEMI-FLAT)
(2 . ,FLAT)
(3 .
2008/12/10 Hans Aberg <[EMAIL PROTECTED]>:
> On 10 Dec 2008, at 13:01, Graham Breed wrote:
>> You can uncomment anything you like now because the
>> rational numbers are accepted.
>
> Fine.
But if you try and do \key d \bayati you'll get that error.
>> I've checked the documentation for key
>> s
2008/12/9 Werner LEMBERG <[EMAIL PROTECTED]>:
>
>> > I've just added ly:font-config-add-directory and
>> > ly:font-config-add-font. Please test.
Hi Werner,
for some reason I can't figure out how to make it work. Would you have
an example file to send me?
I've tried
#(ly:font-config-add-font "./Do
2008/12/10 Graham Percival <[EMAIL PROTECTED]>:
> On Wed, Dec 10, 2008 at 08:01:08PM +0800, Graham Breed wrote:
>> I've checked the documentation for key signatures and see no
>> indication that \key b \bayati could possible work though.
>
> Say what?
> http://lilypond.org/doc/v2.11/Documentation/u
On 10 Dec 2008, at 16:26, Graham Breed wrote:
You can uncomment anything you like now because the
rational numbers are accepted.
Fine.
But if you try and do \key d \bayati you'll get that error.
OK. I don't remember. It works in E24, though.
I've checked the documentation for key
signatu
On 12/10/08 4:41 AM, "Richard Schoeller" <[EMAIL PROTECTED]> wrote:
> I'd like to represent the capo point as a straight barre, but then still
> indicate the unfingered strings with 'x' or 'o'. I think that you can
> do it in standard form as well, just not in terse.
>
> Better still for the
> for some reason I can't figure out how to make it work. Would you
> have an example file to send me?
> I've tried
> #(ly:font-config-add-font
> "./Documents/chemoelectric_-_Goudy_Bookletter_1.otf")
>
> or
> #(ly:font-config-add-directory "./Documents/")
>
> and then
>
> c-\markup{ \override #
2008/12/10 Werner LEMBERG <[EMAIL PROTECTED]>:
>
>> for some reason I can't figure out how to make it work. Would you
>> have an example file to send me?
>> But this doesn't work (more surprisingly, it doesn't display any
>> message during the compilation??).
>
> What message do you expect? You
On Tue, Dec 9, 2008 at 10:50 PM, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> > > Still a buglet: The stemwidth of the down arrow in the
> > > `natural.arrowboth' glyph is too thick if compared to the other
> > > arrowed natural signs. Everything else looks fine.
> >
> > Finally one with an instan
Graham Percival wrote Wednesday, December 10, 2008 2:04 PM
On Wed, Dec 10, 2008 at 08:01:08PM +0800, Graham Breed wrote:
I've checked the documentation for key signatures and see no
indication that \key b \bayati could possible work though.
Say what?
http://lilypond.org/doc/v2.11/Documentati
Le mercredi 10 décembre 2008 à 03:07 -0700, Carl D. Sorensen a écrit :
> Then I imagine the problem must be that sometimes you want "up" and "down"
> to be translated, but not in the autochange snippet. So perhaps my
> suggestion should just be to change the defined names for autochange staves
> t
> Oh, I didn't think TTF fonts would work (of course, I should have
> guessed that any file recognized by fontconfig could do the trick).
This is not correct. Lilypond can't handle bitmap fonts (which
FontConfig will also find if it is configured to do so -- we have to
implement something to rej
On 10 Dec 2008, at 20:14, Trevor Daniels wrote:
Happy to add the link, but I'm not sure non-standard
key signatures are working properly. Try this:
\relative c' {
\set Staff.keySignature = #`(((0 . 3) . ,SHARP)
((0 . 5) . ,FLAT)
((0
Le mercredi 10 décembre 2008 à 02:38 -0200, Han-Wen Nienhuys a écrit :
> LGTM
Done (with the correct sed regexp).
John
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi, I just git-pulled lily to take a look, but got side-tracked
by configure problems:
$ ./configure
...
ERROR: Please install required programs: mpost
See INSTALL.txt for more information on how to build LilyPond
but there's no INSTALL.txt ?
Since I'm at it... what I wanted to look INSTALL
2008/12/10 Graham Percival <[EMAIL PROTECTED]>:
> If the LM and NR 1-4 were finished, and we still had 6 months left
> in GDP with 10 helpers sitting on their hands, of course I'd want
> the glossary to follow the doc policies, but as it is, I suggest
> that you leave it alone.
Well, as I've alre
http://lilypond.org/web/devel/participating/localization
<<
Messages to be localised must be encapsulated in `_ (STRING)' or `_f (FORMAT,
...)'. Eg:
warning (_need music in a score);
error (_f ("cannot open file: `%s'", file_name));
>>
I guess the warning should look like this ?
Hi strk,
Le mercredi 10 décembre 2008 à 22:36 +0100, strk a écrit :
> Hi, I just git-pulled lily to take a look, but got side-tracked
> by configure problems:
>
> $ ./configure
> ...
> ERROR: Please install required programs: mpost
> See INSTALL.txt for more information on how to build LilyPo
Hi everybody,
This combination is disabled in lilypond-book, but there are several
places in the docs where it's used, resulting in no quote block.
I've just reworked a snippet in the Glossary which would benefit from
this; it's currently a bit too long for the pdf output (the final
snippet here:
2008/12/8 Maximilian Albert <[EMAIL PROTECTED]>:
> Awesome to hear and thanks for testing! What do you guys think, should
> a default value be set, and if so which one? I guess something between
> 0.5 and 0.75 would be sensible, according to Reinholds findings.
Though I much prefer the centred-on
Le mercredi 10 décembre 2008 à 23:21 +0100, strk a écrit :
> http://lilypond.org/web/devel/participating/localization
> I guess the warning should look like this ?
>
> warning ( _("need music in a score") );
Yes, the unescaped double quotes confused Firefox and possibly othe
browsers. This
German tabs origins are, like all the forms, obscured by time.
It is reputed to have been invented by Conrad Pauman, mid fifteenth
century, as a way to record music for short-necked lutes having 5 courses.
The notation was extended for lutes having 6 or more courses and more
frets, and we have l
2008/12/10 Graham Percival <[EMAIL PROTECTED]>:
> You'll want to pay special attention to ly/arabic.ly, and make
> sure you understand everything that's happening in there.
I found it! There's some stencil stuff which looks interesting, but
otherwise it doesn't do very much -- the tuning comes f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 30. November 2008 16:07:39 schrieb Graham Percival:
> Incidentally*2, I think there's enough interest in compound time
> signatures that we should add it to the main lilypond.
I have now found a nice workaround for my problems with the cen
2008/12/10 Hans Aberg <[EMAIL PROTECTED]>:
> Now, everyone agrees that in Arab music, the intermediate pitch isn't that -
> in fact the guy who write it said he was taught to lower it, which agree
> with the values Farhat uses in Persian music (using koron and sori; see
> below).
Yes, but nobody
Hi Carl,
Your recent commit with Ralph changes (DOC -- Index editorial...)
seems to be based on a *very* old version of staff.itely. I had
completely rewritten this section a few months ago, so the diff for
this file immediately stood out to me. :-)
Can you revert this commit and include only t
Patrick,
I've reverted the commit, and committed only pitches and editorial. I will
investigate what went on with staff.
I'm sorry about the mistake. Thanks for catching it.
Carl
On 12/10/08 9:49 PM, "Patrick McCarty" <[EMAIL PROTECTED]> wrote:
> Hi Carl,
>
> Your recent commit with Ralph
Hi Carl,
On Wed, Dec 10, 2008 at 10:05:26PM -0700, Carl D. Sorensen wrote:
>
> I've reverted the commit, and committed only pitches and editorial. I will
> investigate what went on with staff.
>
> I'm sorry about the mistake. Thanks for catching it.
That's no problem. Thanks for fixing this
2008/12/10 John Mandereau <[EMAIL PROTECTED]>:
>
> I've never promised to do exactly this; not gettexting a verbatim
> snippet is a different issue from keeping a snippet from being
> overwritten by snippet-update, so I added a fragment option 'nogettext'.
> Francisco, Jean-Charles, can one of you
Le jeudi 11 décembre 2008 à 07:59 +0100, Francisco Vila a écrit :
> Tested, it works, thank you!
> I have kept the KEEP LY so I can still translate the other
> translatable name, right?
If you like.
John
___
lilypond-devel mailing list
lilypond-devel
On 11 Dec 2008, at 04:47, Graham Breed wrote:
Now, everyone agrees that in Arab music, the intermediate pitch
isn't that -
in fact the guy who write it said he was taught to lower it, which
agree
with the values Farhat uses in Persian music (using koron and
sori; see
below).
Yes, but nob
46 matches
Mail list logo
