On 2009-08-14, Neil Puttock wrote:
Two issues have caught my eye (one minor, the other more serious):
1. After a break, I think there's too little space between key
signature alterations and a continuation (though this also applies to
ties, so it's probably a more general issue): at low
Andrew Hawryluk ahawry...@gmail.com writes:
On Thu, Aug 13, 2009 at 7:33 AM, David Kastrupd...@gnu.org wrote:
Sure do. So what driver with what setting converts your PDF to the
respective printer language?
Good question.
At home: Samsung ML-2010, SpliX V. 2.0.0 on Ubuntu 9.04 (evince or
2009/8/14 Joseph Wakeling joseph.wakel...@webdrake.net:
I'd prefer not to do that for semantic reasons. In my conception of
arrow-notated quarter-tones, C-quarter-sharp is enharmonically, but not
semantically, the same as C-sharp-quarter-flat (just as D# is
enharmonically but not
Op donderdag 13-08-2009 om 16:46 uur [tijdzone -0700], schreef Graham
Percival:
1) Jan, please merge automated-engraving into essay/.
Done. I've kept the actual files in the separate automated-engraving
directory. Also, I added a hack to web-texi2html.init.
3) Jan, please move
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 14. August 2009 06:54:45 schrieb David Kastrup:
Werner LEMBERG w...@gnu.org writes:
FWIW, I used to think that this would be a very important feature;
now I'm not so sure. There are certainly a few cases (eg. slurs,
hairpins, treble
2009/8/11 Mark Polesky markpole...@yahoo.com:
Then I propose the following Dutch-English changes:
Added as
http://code.google.com/p/lilypond/issues/detail?id=830
(just in case we can't do it in a near future)
Regards,
Valentin
___
lilypond-devel
Mark Polesky schrieb:
* there are single and double angle-brackets here. Recently I've
noticed some e-mail clients and/or mailing list archives do
weird things with them (like removing them). Just in case you
think I accidentally left something out!
Yes, the closing angled bracket is
On Thu, Aug 13, 2009 at 8:03 PM, Patrick McCarty pnor...@gmail.com wrote:
Hello,
I've decided to dive into deep waters (the slur code) and try to fix
the popular ugly slur bugs, #379 and #427.
See the attached patch for the progress I've made. Also attached is
an image of Mark Polesky's
Op donderdag 13-08-2009 om 16:46 uur [tijdzone -0700], schreef Graham
Percival:
On Thu, Aug 13, 2009 at 05:25:57PM +0200, John Mandereau wrote:
Le jeudi 13 août 2009 à 01:31 +0200, Jan Nieuwenhuizen a écrit :
All right. Here's my proposal to get the docs stabilized with a
minimum of effort:
Le vendredi 14 août 2009 à 16:01 +0200, Jan Nieuwenhuizen a écrit :
We have a problem using the --split=node --node-names that we use
for the current web [general]: translated files get different
names, ie for Introduction (nl: Inleiding)
Probably because cloning an output-def does not copy the parent_ pointer
(so recursive lookups are broken by ly:paper-params-normalize).
Joe
Thanks, Joe, for pointing this out. Now, after thinking a lot about it,
I will try a different approach and control/modify the paper values
On Thu, Aug 13, 2009 at 10:49 PM, David Kastrupd...@gnu.org wrote:
Andrew Hawryluk ahawry...@gmail.com writes:
On Thu, Aug 13, 2009 at 7:33 AM, David Kastrupd...@gnu.org wrote:
Sure do. So what driver with what setting converts your PDF to the
respective printer language?
Good question.
I'm trying to get a better understanding of LilyPond the
programming language. Can someone look this over? Am I on the
right track? As an example of some of the confusion I'm having,
it seems to me that there are 3 categories of datatypes. That
seems wrong, but I don't know how to resolve it. Can
Hmm...there's a new problem I don't understand.
If I set a breakpoint in lily-parser.cc:225 (get_paper) and call
normalize() from there, it seems that all default variables which are
set in paper-defaults-init.ly aren't accessible.
What's the reason for this? Are the *.ly-initfiles parsed
Am Freitag, 14. August 2009 18:33:16 schrieb Andrew Hawryluk:
www.musicbyandrew.ca/essayCMYKblack.pdf - original
[...]
On every combination of OS, PDF viewer, and BW laser printer that I
have tried, the original text is rendered just a shade lighter than
true black, both on-screen and in
Some time ago we had this discussion that \overrides are not quoted from the
original music when you use \cueDuring or \quoteDuring.
Unfortunately, this also means that accacciaturas will be quoted wrong, since
the slash through the note will not be quoted (so singers will usually read
the
Graham Percival wrote:
PS what about this? Of course, we'd need to go through and delete
all @funindex \ lines... then again, that wouldn't be very hard.
diff --git a/Documentation/common-macros.itexi
b/Documentation/common-macros.it
index a852227..eb1b5a1 100644
---
However, we need a mechanism to improve the more critical cases.
Maybe attaching some ghost characters without actual content to
the glyphs might be possible, where the total outline is determined
by overlaying all the bounding boxes?
This is a very nice idea! For example, the
|
That patch changed the grob type from TextScript (?) to
MultiMeasureText, so
The grob type hasn't changed: if you add a markup to a multi-bar
rest, the function `script-to-mmrest-text' converts the ScriptEvent
to a MultiMeasureTextEvent.
yes, it changed the priority, from what I can see.
Mark,
I was looking at your excellent work in organizing the Emmentaler font
appendix, A.6.
With no sub-headings, it's not clear what the organization of each of the
sections of this appendix is. The notehead glyphs are all grouped together,
and the ancient notation glyphs are all grouped
On Fri, Aug 14, 2009 at 7:50 AM, Jan
Nieuwenhuizenjanneke-l...@xs4all.nl wrote:
Op vrijdag 14-08-2009 om 16:31 uur [tijdzone +0200], schreef John
Mandereau:
Le vendredi 14 août 2009 à 16:01 +0200, Jan Nieuwenhuizen a écrit :
Texi2MHTML customization interface (if it ever deserves the name of
Op vrijdag 14-08-2009 om 12:02 uur [tijdzone -0700], schreef Patrick
McCarty:
On Fri, Aug 14, 2009 at 7:50 AM, Jan
Nieuwenhuizenjanneke-l...@xs4all.nl wrote:
This is the part I commented out related to Opera, right?
Yes, I think so.
I think this is really a problem with texi2html; I don't
Werner LEMBERG w...@gnu.org writes:
However, we need a mechanism to improve the more critical cases.
Maybe attaching some ghost characters without actual content to
the glyphs might be possible, where the total outline is determined
by overlaying all the bounding boxes?
This is a very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Apparently Nicolas' commit da383997e929d8301424e9d320e3f5ada7cf6a58 two years
ago (yeah, a long time ago, but I hadn't use that functionality until today,
when I had to create dozens of examples for my girlfriend's thesis) removed
the possibility
2009/8/14 Werner LEMBERG w...@gnu.org:
Any idea how to fix my issue?
Change MultiMeasureRestText #'outside-staff-priority so it's lower
than TextScript #'outside-staff-priority.
Shall this be added to the bug tracker
as a regression?
I don't think so; we just need to agree on a more
On 8/12/09 5:54 PM, Graham Percival gra...@percival-music.ca wrote:
On Wed, Aug 12, 2009 at 05:43:39PM -0600, Carl Sorensen wrote:
Also, we need to recognize that the first commit after running convert-ly on
the docs and the snippets will result in changes to every version statement.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 15. August 2009 01:54:17 schrieb Carl Sorensen:
A related problem is that when I run convert-ly as
find input/regression *.ly | xargs convert-ly -e --from 2.13.3
it does a convert-ly on all the files in input/regression/out/* and
On Fri, Aug 14, 2009 at 05:54:17PM -0600, Carl Sorensen wrote:
On 8/12/09 5:54 PM, Graham Percival gra...@percival-music.ca wrote:
Yes. Now, we could just *hope* that there's only one convert-ly
update for each version, but that would be silly. What about
adding:
convert-ly
On Fri, Aug 14, 2009 at 11:01:11AM -0700, Mark Polesky wrote:
Graham Percival wrote:
diff --git a/Documentation/common-macros.itexi
b/Documentation/common-macros.it
index a852227..eb1b5a1 100644
Graham, what does the above code do?
It automatically adds a \ to every @funindex item.
On Fri, 2009-08-14 at 17:09 +0200, Reinhold Kainhofer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 11. August 2009 02:57:08 schrieb Joe Neeman:
I do intend to write some docs (once I've finished dealing with my TODO
list), but in the absence of docs, here's a list of
On 8/14/09 6:14 PM, Reinhold Kainhofer reinh...@kainhofer.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 15. August 2009 01:54:17 schrieb Carl Sorensen:
A related problem is that when I run convert-ly as
find input/regression *.ly | xargs convert-ly -e --from
31 matches
Mail list logo
