Hello,
I've uploaded a new patchset related to the SVG backend:
http://codereview.appspot.com/96083/show
The several examples I am using as test cases can be found on this page:
http://uoregon.edu/~pmccarty/svg/
They reflect the output created with the above patchset.
***
Right now, only the
On ma, 2009-07-20 at 15:38 -0700, Patrick McCarty wrote:
> On Mon, Jul 20, 2009 at 01:41:18PM -0700, Patrick McCarty wrote:
> > On Mon, Jul 20, 2009 at 03:09:19PM +0200, Jan Nieuwenhuizen wrote:
> > > On vr, 2009-07-17 at 21:50 -0700, Patrick McCarty wrote:
> > >
> > >
> > > cd /home/pnorcks/g
On ma, 2009-07-20 at 21:04 -0700, Graham Percival wrote:
> On Mon, Jul 20, 2009 at 02:38:13PM +0200, Reinhold Kainhofer wrote:
> > In our lilypond docs, we have several texinfo comments, most notably the
> > git
> > revision of the texinfo document
> better done as a macro; that way, we can reta
On ma, 2009-07-20 at 21:24 -0700, Patrick McCarty wrote:
Hi Patrick,
> The recent commit (e0ed3589241383db0b8d77c1c7738ad3432a4fd5) regarding
> the shallow cloning of non-tracking branches broke GUB on my machine.
> I'm running Git 1.6.3.3.
>
> I simply reverted the commit for now, so that I am
Carl Sorensen schrieb:
Wikipedia (in a poorly-cited article) uses the term "ghost note" for all
instruments (including the string-muted and palm-muted notes). This entry
seems to indicate that "ghost note" is a term widely used with drums.
Following up on links to "ghost note" in the guitar wor
Hi Jean-Charles,
Le lundi 20 juillet 2009 à 22:06 +0200, Jean-Charles Malahieude a
écrit :
> Hi Mr release-master and his fellow workers,
>
> Please wait a couple of days before delivering a new release, since I'm
> almost (99% plus a proof-reading) of a complete reviewing of the French
> versio
On di, 2009-07-21 at 15:47 +0200, John Mandereau wrote:
> I'm currently moving manuals in user/ one directory up for all languages
> -- what a PITA, I've only done 30% of it ,`:-o,'. The last of us that
> will push will have to resolve conflicts, i.e. moving the last updated
> file from the old t
Le mardi 21 juillet 2009 à 15:56 +0200, Jan Nieuwenhuizen a écrit :
> What is so difficult here, can't this be scripted?
If you mean solving conflicts caused by moved files, this certainly can.
John
signature.asc
Description: Ceci est une partie de message numériquement signée
_
> If this were strictly a tablature issue, I'd say keep it at "dead notes",
> since that is the guitar term.
but what of citterns, ukes, banjoes and other modern plucked instruments
who would (do) use tablature notation?
BTW, its been several decades since I was actively consulting tutors on
cl
On Tue, Jul 21, 2009 at 9:37 AM, wrote:
> > If this were strictly a tablature issue, I'd say keep it at "dead notes",
> > since that is the guitar term.
>
> but what of citterns, ukes, banjoes and other modern plucked instruments
> who would (do) use tablature notation?
>
> BTW, its been several
On Tue, 2009-07-21 at 16:43 +1000, Cameron Horsburgh wrote:
> Joe Neeman writes:
>
> > On Tue, 2009-07-21 at 10:08 +1000, Cameron Horsburgh wrote:
> >> Hi Joe,
> >>
> >> You may already be aware of this issue, but I'll report it anyway.
> >>
> >> I'm currently typesetting a piece that should co
Hi guys,
I expect comments (and even maybe votes from developers) about the
directory structure, which will very soon drive an important part of the
docs and web site reorganization (especially the makefiles and
buildscripts :-P).
I have a naive question with not so naive implications about the c
I'm getting ready to push the new autobeaming code. Are there any more
comments before I do so?
http://codereview.appspot.com/88155
Thanks,
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond
On Tue, Jul 21, 2009 at 11:03 AM, Carl Sorensen wrote:
>
>
> I'm getting ready to push the new autobeaming code. Are there any more
> comments before I do so?
>
> http://codereview.appspot.com/88155
Did you address Neil's last comment on the patchset, from 5 days ago?
-Patrick
On Tue, Jul 21, 2009 at 11:06 AM, Patrick McCarty wrote:
> On Tue, Jul 21, 2009 at 11:03 AM, Carl Sorensen wrote:
>>
>>
>> I'm getting ready to push the new autobeaming code. Are there any more
>> comments before I do so?
>>
>> http://codereview.appspot.com/88155
>
> Did you address Neil's last co
very nice!
http://codereview.appspot.com/88155/diff/3092/2039
File ly/music-functions-init.ly (right):
http://codereview.appspot.com/88155/diff/3092/2039#newcode699
Line 699: (make-music 'SequentialMusic 'void #t))
I'd feel better if this were finished. At least add FIXME so it can be
easily gr
http://codereview.appspot.com/96083/diff/1/8
File lily/pango-font.cc (right):
http://codereview.appspot.com/96083/diff/1/8#newcode351
Line 351: // options.
Could you please have a look at this? (after applying this patch, if you
prefer). The more special cases we add for different backends, the
On 7/19/09 3:07 AM, "Graham Percival" wrote:
> On Sat, Jul 18, 2009 at 09:14:40PM -0600, Carl Sorensen wrote:
>> In preparing information on regression testing for the Contributors' Guide,
>> I happened to check the downloadable regression test results at
>>
>> http://lilypond.org/download/bi
Also in a part set to a smaller fontsize
\set fontSize = #-1 {
\mark A
r8^\markup "Frage" b es8.[ b16] c g8. r4 |
}
\set fontSize = #-4 {
r8^\markup "Antwort" b b[ b] b16 c8. r4 |
}
\set fontSize = #-1 {
\bar ":|" \break
}
% (With fontsize -1 in general I want to get a „less black“ paper.)
t
I'd like a feature which allows the following
(and I think, that should be the default):
\score {
\new StaffGroup
<<
\new ChordNames
\Harmonien
\new Staff
{
\clef F
\relative c {
\Zweite
}
Werner wrote:
> \set fontSize doesn't effect beams and stems
It's not supposed to -- beams and stems are not part of any font, they
are drawn according to calculations that happen when the program is
processing your file. So changing the fontSize doesn't do anything to
them. On the other hand, no
On Tue, Jul 21, 2009 at 07:45:28PM +0200, John Mandereau wrote:
> I have a naive question with not so naive implications about the current
> shape of docs reorganization: what is the planned directory structure
> for the new web site?
>
> Do we want to make a clear distinction between the site and
22 matches
Mail list logo
