> While Joe's latest changes to the horizontal spacing are giving good
> results, here's a special case where it fails.
>
> \relative c' {
> \tieDashed
> ces1 ~ |
> ces!8 bes ces bes ces bes ces bes |
> }
>
> \paper {
> ragged-right = ##t
> }
BTW, this very example exposes another bug i
[git 2007-08-19 13d78fe]
While Joe's latest changes to the horizontal spacing are giving good
results, here's a special case where it fails.
Werner
==
\relative c' {
\tieDashed
ces1 ~ |
ces!8 bes ces bes ces bes
> in 2.11.30 you will be able to do
> \relative
> {
>
> \arpeggioBracket
> \override Arpeggio #'positions = #'(-5 . 5)
> \arpeggio
> }
>
> and get a bracket with the desired size.
This sounds great! However, I need more than a single vertical
bracket in a chord. AFAIK, this is not (easi
2007/8/19, Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> > . What must I do to guarantee that the vertical brackets are always
> > positioned left of the accidentals?
>
> huh? I thought they were supposed to be right of them. If you want
> brackets left of the note, you could try the arpeggio brack
Reinhold Kainhofer escreveu:
> Next round of patches: After Han-Wens comments about coding style (no
> exceptions, spaces, etc.), I reworked all my patches so far. Here they are
> all again:
Thanks, I've applied them now.
Some minor comments; I would appreciate if you address them before sendi
Next round of patches: After Han-Wens comments about coding style (no
exceptions, spaces, etc.), I reworked all my patches so far. Here they are
all again:
-) 0001-Convert-articulations-like-fermata-staccato-tenuto.patch:
Convert articulations like fermata, staccato, tenuto, tremolo (only
singl
2007/8/19, Werner LEMBERG <[EMAIL PROTECTED]>:
> . What must I do to guarantee that the vertical brackets are always
> positioned left of the accidentals?
huh? I thought they were supposed to be right of them. If you want
brackets left of the note, you could try the arpeggio bracket; in tha
2007/8/19, Reinhold Kainhofer <[EMAIL PROTECTED]>:
> > > Grr, each small project has its own coding style (kdepim has spaces
> > > inside the parentheses, kdelibs has different style, lilypond another
> > > different style). That's so confusing, and I'm mainly used to the kdepim
> > > coding style,
2007/8/19, Reinhold Kainhofer <[EMAIL PROTECTED]>:
> > use {}.get (..)
>
> I was just using the style of the rest of the code...
Certainly, however, the rest of the code is not perfect either.
> BTW, what is an easy way to work with git on multiple patches at the same
> time? Currently, I'm using
Hi John, thanks for the answer,
John Mandereau wrote:
Which Texlive version do you have? I have Texlive 2007 on my box, and
it includes epsf.tex. Maybe you need to upgrade to 2007 or rerun
Texlive setup to install the package providing epsf.tex.
Indeed, I installed texlive 2007 after remo
> > See below the snippet from the texinfo manual. I haven't yet
> > checked how to handle languages other than English.
>
> Thanks for the explanation, and sorry for not reading Texinfo
> manual. This rule can also apply to French and (I suppose) to other
> European languages, although it somet
[Using git 2007-08-19 f3734e9]
[Han-Wen, I'm resending this with slightly improved code and wording
to the lilypond-devel list since it seems that you don't have enough
time to answer.]
> String numbers usually get put next to (left or right) of notes;
> check out the manual on to how to use the
Reinhold Kainhofer escreveu:
> Attached is another git patch for musicxml2ly to make it not crash, when a
> score does not have a key or a clef set in the .xml file. Rosegarden produces
> such files.
>
> Cheers,
> Reinhold
>
+children = None
should be []
+try:
+c
Attached is another git patch for musicxml2ly to make it not crash, when a
score does not have a key or a clef set in the .xml file. Rosegarden produces
such files.
Cheers,
Reinhold
--
--
Reinhold Kainhofer, Vienna University of T
Le dimanche 05 août 2007 à 07:25 +0200, Werner LEMBERG a écrit :
> > I believe this is due to the reorganization of the info files; in file
> > `/usr/local/share/info/dir' I see the following entries now:
> >
> > LilyPond
> > * abc2ly: (lilypond/lilypond-program)Invoking abc2ly. Impor
Le 14.08.2007 11:27, Graham Percival disait :
Sorry, I'm not certain I understand -- is this a suggestion about
rewriting the docs, or a question about how to use lilypond?
Both of them, if you don't mind.
I should say I often run the examples I don't really fully understand,
in order to give
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
--- Begin Message ---
Hi all,
We would like to ask you a few questions about your use of the GIT
version control system. This survey is mainly to understand who is
using GIT, how and why.
The results will be discussed on th
Hello Mats,
2007/8/16, Mats Bengtsson <[EMAIL PROTECTED]>:
> I'd like to replace the existing LSR example entitled "Feathered beams"
> with the following more extensive example.
Thank you very much Mats; I've modified the existing snippet:
http://lsr.dsi.unimi.it/LSR/Item?id=239
> I clearly rem
Le samedi 18 août 2007 à 19:11 +0200, Werner LEMBERG a écrit :
> > > @ref{...} must *always* be followed by punctuation.
> >
> > Werner, can you tell what the real rule is?
>
> See below the snippet from the texinfo manual. I haven't yet checked
> how to handle languages other than English.
Tha
Le samedi 11 août 2007 à 13:14 +0300, Till Rettig a écrit :
> Hello everybody,
>
> I just tried to compile the documentation from git master branch. First
> it gave an error about a missing epsf.tex file that collated-files.tely
> in input/manual/out-www needed. I found that my version of texliv
Le samedi 11 août 2007 à 13:21 +0300, Till Rettig a écrit :
> Hi,
>
> another problem is that check-translation script is not working for me.
> It throws following message:
>
> [EMAIL PROTECTED]:~/Documents/Lilypond/compile/Documentation$ make ISOLANG=de
> check-translation
> find de/user/ -max
21 matches
Mail list logo
