c'4
}
Trevor Daniels
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
From: Trevor Daniels [mailto:[EMAIL PROTECTED]
Sent: 08 October 2007 11:45
There is an example in the User Manual, section
1.1.3, Displaying Pitches, subsection Clef which
shows a bug. The example is the one which shows
the effect of changing the three properties,
clefGlyph, clefPosition
give correct beaming
}
Maybe I missed something in auto-beam.scm, but I can see
nothing there which affects the beaming of 1/16th notes in
12/16 time. Same fault in other time signatures too - I
tried 11/16 and 13/16 with same results.
Trevor Daniels
Two close accidentals in an ambitus collide.
\new Voice \with {
\consists Ambitus_engraver
}
\relative c'' {
aes4 cis
}
Also, I can find no override which separates them.
Trevor D
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Paul Scott wrote on 09 December 2007 06:25
Trevor Daniels wrote:
This is the difference, taken from the new GDP
NR manual:
In addition, you can specify ||:, which is
equivalent to
|: except at line breaks, where it gives a
double bar line
at the end of the line and a start
The outside-staff-priority of BarNumber is set by default to
100, the lowest of all outside-staff objects, yet it appears
in 2.1.34 to be placed further from the staff than
DynamicText (250), DynamicLineSpanner (250), and
OttavaBracket(400). Here is an illustration of an extreme
situation,
-lilypond
Subject: Re: BarNumber outside-staff-priority not honoured?
On 12/19/07, Trevor Daniels [EMAIL PROTECTED] wrote:
The outside-staff-priority of BarNumber is set by default to
100, the lowest of all outside-staff objects, yet it appears
in 2.1.34 to be placed further from
A bug in the ambitus engraver seems to have crept in between
2.11.34 and 2.11.36. The example in section 3.3.5 of the
Learning Manual at
http://kainhofer.com/~lilypond/Documentation/user/lilypond-l
earning/Adding-and-removing-engravers.html#Adding-and-removi
ng-engravers which was compiled with
Hi Valentin
Here's your first bug:
\version 2.11.34
% These two notes are different and should not be merged
{aes'8} \\ {a'}
{aes'8} \\ {a'?}
Trevor D
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Date: Sat, 26 Jan 2008 12:13:38 + (UTC)
From: Matti Aaltonen [EMAIL PROTECTED]
Subject: set associatedVoice and disappearing lyrics
To: bug-lilypond@gnu.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
I'm not top posting.
Hello.
This is my second
Stefan Thomas wrote on 28 January 2008 23:22
Dear Lilypond-users,
in the below quoted snippet I'm not happy with
the vertical priority of
the pedal-symbols and theDynamic.
I would like to have the pp , the crescendo
hairpin etc. above the
pedal-signs. But I dont know ho to do.
\once
-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED]
Sent: 05 February 2008 11:31
To: [EMAIL PROTECTED]; Lilypond bug
Cc: [EMAIL PROTECTED]
Subject: Re: Hairpin and Textscript
Trevor Daniels wrote:
...
http://kainhofer.com/~lilypond/Documentation/user/
lilypond-learning
[mailto:[EMAIL PROTECTED]
Sent: 11 March 2008 10:29
To: Valentin Villenave
Cc: [EMAIL PROTECTED]; Bug-Lilypond
Subject: Re: Slow compile on Windows XP - font
caching problem?
Valentin Villenave wrote:
2008/3/10, Trevor Daniels [EMAIL PROTECTED]:
Under 2.11.42 the fonts are cached
seeing this?
2008/3/11, Valentin Villenave [EMAIL PROTECTED]:
2008/3/11, Trevor Daniels [EMAIL PROTECTED]:
Yes, definitely a regression. I've gone
back to using
2.11.34 which does not suffer this bug, as
most of my
documentation work is fiddling with tiny
snippets, and a 1
this:
http://lilypond.org/download/binaries/
Cheers,
- Graham
On Thu, 13 Mar 2008 08:04:06 -
Trevor Daniels [EMAIL PROTECTED] wrote:
Problem seen in 2.11.41 and 42, not in 2.11.34.
I didn't install or
download any intervening development releases.
I'd be happy to try
them, but how
Han-Wen, you wrote 17 March 2008 15:18
2008/3/13, Trevor Daniels [EMAIL PROTECTED]:
OK - here are the results:
2.11.34-1
Compiles in 15 secs
Uses .fontconfig directory
2.11.35-1
Fails with libguile2-17.dll not found
Copied this in, then
Fails with error
Han-Wen Nienhuys wrote 18 March 2008 18:13
2008/3/18, Trevor Daniels [EMAIL PROTECTED]:
Not really. A couple of minor changes in
fonts/fonts.conf but nothing that seems
significant.
can you post the diff anyway?
OK. Here's a diff -q first:
Common subdirectories: LilyPond
-Original Message-
From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
Sent: 17 March 2008 15:10
To: [EMAIL PROTECTED]
Cc: Graham Percival; [EMAIL PROTECTED];
bug-lilypond@gnu.org
Subject: Re: Tuplet brackets appear when I've
asked them not to
2008/3/10, Trevor Daniels [EMAIL
I've now got my new laptop up and running, so at last I can check how LilyPond
works under Vista. It works pretty well! :) Release 2.11.42-1 installed
without problems and (apart from the very first run of around 50 secs) runs a
trivial file in around 3 secs flat, including the conversion to
Han-Wen Nienhuys, 21 March 2008 19:26
2008/3/21, Trevor Daniels [EMAIL PROTECTED]:
Some facts that might have a bearing:
This was a clean install of Vista, not an upgrade.
This was the very first LilyPond installation
on this system.
I had admin priviledges during the install
Date: Fri, 28 Mar 2008 01:20:41 -0300
From: Han-Wen Nienhuys [EMAIL PROTECTED]
Subject: Re: no compile on version 2.11.43 for Windows XP
To: Tom Richard [EMAIL PROTECTED]
Cc: bug-lilypond@gnu.org
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=UTF-8
Can you try 2.11.43-2
There seems to be a bug in \set whichBar. Rather than setting the type of
barline to print at the end of the bars it prints a barline after every
following note. Surely this isn't correct? Here's a short example:
\version 2.11.44
\relative c' {
d d d d
\set Staff.whichBar = ||
e8 e e e
Of course! Timing (and bar lines) are handled in the Score context by
default. Setting Score.whichBar works fine. Thanks, Neil.
Trevor
- Original Message -
From: Neil Puttock [EMAIL PROTECTED]
To: Trevor Daniels [EMAIL PROTECTED]
Cc: Bug-Lilypond bug-lilypond@gnu.org
Sent
Valentin Villenave wrote
Actually, I was mainly referring to the installing/uninstalling
process: on Windows, for instance, such a thing would be practically
impossible (the installation takes ages, and the uninstall is even
worse).
I have been trying to use symlinks to have several
- Original Message -
Date: Mon, 14 Jul 2008 15:45:32 + (UTC)
From: Roman Stawski [EMAIL PROTECTED]
Subject: \tag can't follow \lyricsto
To: bug-lilypond@gnu.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
I'm not top posting.
The \tag command
Roman Stawski wrote
The \tag command provokes a syntax error if it immediately follows a
\lyricsto
command. A work-around is to insert an empty expression {} between the
two.
\version 2.11.49
\paper{ ragged-right=##t }
\new Voice = dirge { c''1 }
\lyricsto dirge \new Lyrics {
In fact what you call first voice and second voice
are both in the same Voice context. The tie
override affects both ties because they occur at the
same musical moment (assuming the tie in your second
voice is intended to be between the two notes
immediately following the override) and are in
Message: 6
Date: Sat, 26 Jul 2008 19:03:24 -0700
From: [EMAIL PROTECTED]
Subject: Issue 653 in lilypond: \override inconsistency with ties in a
polyphonic situation
To: bug-lilypond@gnu.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; Format=Flowed
Issue 653:
Han-Wen, you wrote:
Doing overrides on individual ties is not supported like this, exactly
because there
is no way to select them. Try \tweak,
\new Voice
{ c''-\tweak #'direction #-1 -~ c'' }
{ e'-\tweak #'direction #1 -~ e' }
This works fine with #'control-points too. Thanks.
Graham Percival wrote Wednesday, July 30, 2008 5:09 AM
LM 5 hasn't been touched as part of GDP, and AFAIK nobody has any
spare time to look at it. The only possibility is that Trevor
might spend a few hours on it after he's done the first update for
NR 6.
Actually it's NR 5 I'm just
Message: 4
Date: Mon, 28 Jul 2008 08:18:12 -0700
From: [EMAIL PROTECTED]
Subject: Issue 653 in lilypond: \override inconsistency with ties in a
polyphonic situation
To: bug-lilypond@gnu.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; Format=Flowed
Issue 653:
Carl
This isn't a problem specific to chordmode. If you use
an identifier c you get a similar error about unexpected
notename_pitch whatever the input mode. The problem is
the identifier m.
Because m is a valid chord modifier and the parser/lexer
is scanning for chordmodifiers or pitchnames
Carl
You may be right, but the details of the parser/lexer logic
have so far defeated me. As it's late and as I'm away most of
Saturday I shall withdraw, beaten, from this discussion :(
Trevor
- Original Message -
From: Carl D. Sorensen [EMAIL PROTECTED]
To: Trevor Daniels [EMAIL
Andrew Hawryluk wrote Thursday, August 21, 2008 2:10 AM
On Tue, Aug 19, 2008 at 4:03 AM, Valentin Villenave
[EMAIL PROTECTED] wrote:
2008/8/12 Martin Klejch [EMAIL PROTECTED]:
%% the Lyrics independent of notes example (chapter 7.3.7.5 of the
manual)
%% gives errors: warning: Lyric
Trevor Daniels wrote Thursday, August 21, 2008 9:46 PM
Andrew Hawryluk wrote Thursday, August 21, 2008 2:10 AM
On Tue, Aug 19, 2008 at 4:03 AM, Valentin Villenave
[EMAIL PROTECTED] wrote:
2008/8/12 Martin Klejch [EMAIL PROTECTED]:
%% the Lyrics independent of notes example (chapter
Right
}
\new Staff \new Voice = v {c' d' e' f'}
\new Staff \new Voice {c'2 d'4 e'8 f'8}
\new Lyrics \lyricsto v \mylyrics
\new Lyrics \mylyrics
/Mats
Mats Bengtsson wrote:
Trevor Daniels wrote:
The warnings are not exactly errors. Another thread with the words
durations needed in which Mats
The GUB release 2.11.57 for Windows seems to have a problem on Vista SP1.
When started from the command line it returns immediately, even when given
no arguments - 2.11.56 is fine - it gives brief help information when given
no arguments. When started from another application like
- Original Message -
From: Valentin Villenave [EMAIL PROTECTED]
To: Trevor Daniels [EMAIL PROTECTED]
Cc: lilypond-devel [EMAIL PROTECTED]; Bug-Lilypond
bug-lilypond@gnu.org
Sent: Sunday, September 07, 2008 8:40 PM
Subject: Re: 2.11.57 fails from Vista command line
2008/9/5 Trevor
Graham Percival wrote:
On Thu, 11 Sep 2008 16:02:50 + (UTC)
Albert Bickford [EMAIL PROTECTED] wrote:
convert-ly -e myfile.ly
However, convert-ly is a python program, not an .exe, so what I had
to do was
python convert-ly.py -e myfile.ly
I don't know how it works on windows with a
Date: Thu, 09 Oct 2008 18:51:14 +0200
From: Martial [EMAIL PROTECTED]
Subject: Lilypond documentation Custos
To: bug-lilypond@gnu.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=UTF-8; format=flowed
Hello
doc error ?
I think that it is
\override Custos #'style =
Graham Percival wrote Mon, 13 Oct 2008 00:02:37 -0700
[EMAIL PROTECTED] wrote:
This is good news: it means LilyPond is ready for microtonal musics,
spectral music,
non-equal temperaments etc.; we'd just need to have more
ready-to-use macros, and
document it better. I'll look into it.
We
Graham Percival wrote Tuesday, October 14, 2008 10:39 PM
On Tue, 14 Oct 2008 21:52:11 +0100
Trevor Daniels [EMAIL PROTECTED] wrote:
Graham Percival wrote Mon, 13 Oct 2008 00:02:37 -0700
We used to include makam.ly in pitches.itely. I don't know what
happened to it.
There is a snippet
I've just noticed that there are many entries in the index to the Notation
Reference which lead you to the @seealso sections. It seems that the @r..{}
macros generate index entries automatically. But these entries are pretty
useless as they take to the place where the reference is made,
I get the same result on Vista. Here's a minimal
example which shows the problem:
\score {
\override Score.LyricText #'font-name = #Times New Roman
\relative c'' { g }
\addlyrics { nN }
}
Trevor
- Original Message -
From: sdfgsdhdshd [EMAIL PROTECTED]
To: [EMAIL
Valentin Villenave wrote Friday, October 24, 2008 12:02 PM
2008/10/24 Trevor Daniels [EMAIL PROTECTED]:
I get the same result on Vista. Here's a minimal
example which shows the problem:
Hi Trevor,
may i ask you to send a png?
(since you're about the only one who can reproduce
This accidental/fingering collision appears to be a bug, so I'm copying to
the bug list. I can't find a similar bug in the bug DB.
The collision occurs only when the chord is the first chord/note in the bar,
and the fingered note precedes the sharpened note in that chord. Here's a
short
I've added a snippet based on the example supplied by Mark
to the repository in a form which is suitable for inclusion
in the selected snippets section of NR 1.7 Editorial annotations.
It will appear in the docs in due course.
See Avoiding collisions of chord fingering with beams
Thanks Mark
Ah, I'm sorry, Eluze, and thank you! I replied from the bug digest and I
must have looked at the wrong message headers when I looked to see who wrote
it.
Trevor
- Original Message -
From: Mark Polesky [EMAIL PROTECTED]
To: Trevor Daniels [EMAIL PROTECTED]; bug-lilypond@gnu.org
Sent
Reinhold Kainhofer wrote Monday, November 24, 2008 6:14 PM
PS: Note that the comment in the documentation about the setting applying
only
to the second next syllable (fas in this case), is actually no longer
true
in LilyPond 2.11.x. The setting now applies to the very next lyrics
syllable
John Sellers wrote
In reading through the Learning manual, all concepts seeming to be well
introduced before using them in examples. The clarity of these sections
could
not be better.
However in section 2.5.1, Organizing pieces with variables
it seems that several concepts are used in
If a non-standard key signature is defined using the format which limits the
alterations to a single octave, the alterations defined in the key signature
persist only up to the end of the first bar which contains a pitch to be
altered.
They should persist indefinitely.
In this example the F#
Graham Breed wrote Thursday, December 11, 2008 1:01 AM
I can demonstrate the bug with that file though. Here's an example:
\version 2.11.65
\include arabic.ly
melody = \relative {
\key re \bayati
do re mi fa sol la si do
}
\score {
\new Staff \melody
\layout { }
\midi { }
}
It fails
Neil Puttock wrote Thursday, December 11, 2008 5:23 PM
2008/12/11 Trevor Daniels t.dani...@treda.co.uk:
In this example the F# and Ab are notated correctly only in bar 1. A Bb
does not
appear until bar 3, when it is notated correctly, but is incorrect in bar
4.
\relative c' {
\set
Using \midi without \layout in 2.11.64-1 causes an exception in Windows
Vista:
\score {
\new Staff {
\new Voice { a }
}
% \layout { }
\midi { }
}
Exception Code: c005
Exception Offset: 001bfa19
OS Version: 6.0.6001.2.1.0.768.3
Trevor
Trevor Daniels wrote Tuesday, December 16, 2008 10:09 AM
Using \midi without \layout in 2.11.64-1 causes an exception in Windows
Vista:
Sorry, this should read 2.11.65-1
\score {
\new Staff {
\new Voice { a }
}
% \layout { }
\midi { }
}
Exception Code: c005
Exception Offset
Herbert Liechti wrote Tuesday, December 23, 2008 6:40 AM
Neil Puttock schrieb:
2008/12/22 Trevor Daniels t.dani...@treda.co.uk:
Reinhold Kainhofer wrote Monday, December 22, 2008 4:22 PM
He sent me the whole file and the culprit is a PianoStaff, which seems
to
somehow override
Carl D. Sorensen wrote Thursday, December 25, 2008 12:21 AM
On 12/24/08 3:31 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
Herbert Liechti wrote Tuesday, December 23, 2008 6:40 AM
Neil Puttock schrieb:
2008/12/22 Trevor Daniels t.dani...@treda.co.uk:
Reinhold Kainhofer wrote Monday
James E. Bailey wrote Sunday, December 28, 2008 8:35 AM
Am 18.12.2008 um 09:57 schrieb Mark Polesky:
Trevor Daniels wrote:
Using \midi without \layout in 2.11.65-1
causes an exception in Windows Vista:
in XP also.
- Mark
In OSX 10.4 Intel also.
This is fixed in 2.12.
Trevor
It's because the \sustainOn and \sustainOff are written
to occur at the same musical moment. You'll need to
introduce a small time separation between them, perhaps by
adjusting the spacer rests.
Trevor
- Original Message -
From: Michael Pozhidaev m...@altlinux.org
To:
Valentin Villenave wrote Sunday, January 11, 2009 2:56 PM
2008/12/11 Trevor Daniels t.dani...@treda.co.uk:
Graham Breed wrote Thursday, December 11, 2008 1:01 AM
I can demonstrate the bug with that file though. Here's an example:
\version 2.11.65
\include arabic.ly
melody = \relative
Mats
This was changed by committish
3d90d1d4096a6fae5826445cd66e95d25de2110a by
Joe Neeman on 29 Jun 2007. The commit message
says:
use PaperColumns instead of SeparationItems.
It was part of a massive set of changes to the
spacing engine by Joe.
As you say, it looks like a doc change is
don't see the latter in the list of all
graphical objects. If this is the case then I'll make a patch to fix the
typo and send it to Carl.
I'm sure you're right. Please fix this now, although much
of NR 6 is yet to be rewritten.
Trevor
Jon
On Thu, Jan 29, 2009 at 05:28:04PM -, Trevor
Valentin Villenave wrote Sunday, January 11, 2009 2:44 PM
2008/12/7 Mark Polesky markpole...@yahoo.com:
NR 1.7.1 Editorial annotations: Inside the staff
(strangely) contains the info on stems directions.
It makes sense to me (strangely).
How are stem directions related to editorial
This looks like a bug. An attempt to add the
Instrument_name_engraver to a StaffGroup context *and* produce MIDI
output causes a Crash under Vista. Doing either separately is fine.
Here's a minimal example:
\version 2.12.2
\score {
\new StaffGroup \with { \consists Instrument_name_engraver
Jonathan Kulp wrote Wednesday, February 18, 2009 12:16 AM
Trevor Daniels wrote:
This looks like a bug. An attempt to add the
Instrument_name_engraver to a StaffGroup context *and* produce
MIDI output causes a Crash under Vista. Doing either separately
is fine. Here's a minimal example
Jonathan Kulp wrote Wednesday, February 18, 2009 12:16 PM
Trevor Daniels wrote:
Jonathan Kulp wrote Wednesday, February 18, 2009 12:16 AM
Trevor Daniels wrote:
This looks like a bug. An attempt to add the
Instrument_name_engraver to a StaffGroup context *and* produce
MIDI output causes
Mats Bengtsson wrote Sunday, March 01, 2009 8:17 AM
Quoting Patrick McCarty pnor...@gmail.com:
On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave
v.villen...@gmail.com wrote:
2009/2/2 Joe Neeman joenee...@gmail.com:
On Fri, 2009-01-30 at 12:21 -0600, Jonathan Kulp wrote:
Ok Graham. I've
Thanks Jon. Pushed to git.
Trevor
- Original Message -
From: Jonathan Kulp jonlancek...@gmail.com
To: Graham Percival gra...@percival-music.ca
Cc: Joe Neeman joenee...@gmail.com; Lilypond bug
bug-lilypond@gnu.org; Mats Bengtsson mats.bengts...@ee.kth.se
Sent: Sunday, March 01, 2009
Joe Neeman wrote Sunday, March 01, 2009 7:27 PM
On Sun, 2009-03-01 at 15:38 +, Trevor Daniels wrote:
Mats Bengtsson wrote Sunday, March 01, 2009 8:17 AM
Quoting Patrick McCarty pnor...@gmail.com:
On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave
v.villen...@gmail.com wrote:
2009
There's a way, but it's rather messy.
Here's some code to give you a start. Essentially you draw a
coloured box
with \markup, experiment to get the right size, move it into the
right
position, and place it in layer 2 to put it above everything else,
and
then make the box white. If you add
a8 a a a16 a
beginning on either the first or third beats of the bar. The
beaming
LilyPond gives me is
a8[ a a a16 a]
when I would prefer
a[8 a] a[ a16 a]
I had a go at writing a rule to get this behaviour but there
doesn't
sem to be any way of doing it. This was confirmed by Trevor
of doing it. This was confirmed by Trevor
Daniels in
the discussion on -user.
This raises two questions: first, what should the default beaming
be
in this case? I don't see a lot of the one that LilyPond
generates,
and I find it reasonably hard to sight-read. Most scores I see
seem to
use
Patrick McCarty Monday, March 23, 2009 11:07 PM
On Mon, Mar 23, 2009 at 2:58 PM, Cameron Horsburgh
ca...@netcall.com.au wrote:
I've also just noticed another thing: the figure
a8 a16 a16 a8 a16 a6
is rendered
a8[ a16 a16] a8[ a16 a6]
which is my preferred option. In fact, I would prefer
Pekka Siponen wrote Tuesday, March 24, 2009 4:24 PM
In the notation reference: 2.7.2 Displaying chords,
is a snippet for a simple lead sheet:
\chords { c2 g:sus4 f e }
\relative c'' {
a4 e c8 e r4
b2 c4( d)
}
\addlyrics { One day this shall be free __ }
Why does the following
Robin Bannister wrote Wednesday, March 25, 2009 12:46 PM
Where NR 3.3.3 is talking about \char it says
The following example shows UTF-8 coded characters being used
which got me typing in a UTF-8 byte pair after the ##x.
But, of course, it is more like UTF-32.
In fact, referring to UTF-32
Robin Bannister Wednesday, March 25, 2009 4:17 PM
Francisco Vila. wrote:
the right googleable word is Unicode, do you agree?
Well, not fully.
When I google for unicode arabic percent
I certainly end up at a relevant place
http://www.fileformat.info/info/unicode/char/066a/index.htm
But I
Hans Aberg wrote Wednesday, March 25, 2009 11:23 PM
On 25 Mar 2009, at 23:30, Francisco Vila wrote:
From your kind explanation would be right to say that the
argument to
the LilyPond \char command is a simple natural number and not a
multibyte utf-8 sequence? This is what --I think-- still
Hans Aberg wrote Thursday, March 26, 2009 8:57 AM
On 26 Mar 2009, at 00:55, Trevor Daniels wrote:
The manual says that \char #65 produces the letter A. Here, 65
is an ordinary integer. Which position number basis? The ASCII
hexadecimal number for A is 41, in languages like C/C
Graham Percival wrote Thursday, March 26, 2009 1:13 PM
Now, I'll admit that we have very few lilypond users on OpenServer
and Unicos (WTM is Unicos, anyway?!).
A bit off topic, but Unicos is the OS on some high performance
computers from Cray Research: http://www.cray.com/home.aspx . Not
Mark
If you look up layers in the index to the Notation
Reference you'll find there that it says the layer
property should be set to an integer and most objects
are drawn by default with a value of 0 or 1. Also
the example shown uses a value of -1. Maybe we
ought to change
Piero
The file which contains this translation string (po/it.po) is
encoded (correctly) in UTF-8, in which è is written (correctly) as
è. Is it possible your console output is not correctly rendering
utf-8-encoded characters?
Trevor
- Original Message -
From: Piero Faustini
Valentin Villenave Saturday, April 11, 2009 9:10 AM
2009/4/11 Trevor Daniels t.dani...@treda.co.uk:
The file which contains this translation string (po/it.po) is
encoded
(correctly) in UTF-8, in which è is written (correctly) as è. Is
it
possible your console output is not correctly
Eluze
Seems ok here, maybe your file somehow got corrupted. There were no
significant changes to midi2ly.py between these two releases (a few
lines to do with copyright were changed, but no 'big block of lines'
was moved) so using the older version should be fine if that works
for you.
-Eluze wrote Wednesday, June 10, 2009 1:29 PM
i just had the a cross experience with this code:
\context Voice = melody { c'}
\context Lyrics \lyricsto melody \lyricmode { \set
stanza=#1. hi }
}
resulting in errors:
Fehler: Grob-Name sollte alphanumerisch sein
\context Lyrics
Valentin Villenave wrote Wednesday, January 07, 2009 12:21 AM
Greetings,
NR1.2.4 says:
Known issues and warnings
Automatically kneed cross-staff beams cannot be used together with
hidden staves.
Why?
The following piece of code works well (and if you uncomment the
last
line, an ugly #76
Valentin Villenave wrote Thursday, July 16, 2009 2:26 PM
2009/2/18 Trevor Daniels t.dani...@treda.co.uk:
This looks like a bug. An attempt to add the
Instrument_name_engraver to a
StaffGroup context *and* produce MIDI output causes a Crash under
Vista.
Doing either separately is fine
Francisco Vila Friday, August 07, 2009 10:08 AM
2009/8/7 Benjamin Kwong benjamin.kw...@mail.mcgill.ca:
The following produces weird behavior with the use of \addlyrics
over barlines.
\version 2.13.3
\relative c' { { { a4 a a a | a } \addlyrics { a a a a } d d d
| f f f f } \\
{ c,1 c c
The positioning of a single note which
occupies a bar fully is not correct if
ragged-right = ##f.
The following example illustrates the problem.
\layout { ragged-right = ##f }
\relative a' {
a1 a a
\break
a a a
\break
\time 2/4
a2 a a
\break
a
\time 1/4
a4 a
}
This is a
Neil Puttock wrote Tuesday, August 25, 2009 9:17 PM
2009/8/25 Trevor Daniels t.dani...@treda.co.uk:
This is a regression from 2.10. Both 2.13 and 2.12 show the
problem, but
2.10.33 does not.
Are you sure? I think it's covered by this news entry for 2.12:
`Notes or rests
Neil Puttock wrote Thursday, August 27, 2009 10:21 PM
2009/8/25 Trevor Daniels t.dani...@treda.co.uk:
I'd forgotten that news item, but the extra space seems to be
too large. I've checked the scores of three publishers and all
of them position a single note in a bar close to the left bar
Neil Puttock wrote Tuesday, September 08, 2009 11:28 PM
2009/9/8 Trevor Daniels t.dani...@treda.co.uk:
John Ervin wrote Tuesday, September 08, 2009 6:05 AM
Subject: cueing bug
Also, slurring doesn't seem to transfer into the cueing. This
would be
nice to
have.
Setting quotedEventTypes
Comment #1 on issue 865 by Carl.D.Sorensen: Enhancement: ancient
tablatures
support
http://code.google.com/p/lilypond/issues/detail?id=865
There was some discussion about this on the -devel website some
time ago with Dana Emery, but I'm not sure
anything useful came of it.
Frédéric Bron wrote Sunday, October 25, 2009 6:45 PM
Here is my first post:
In voice style, when switching from one voice to two voices, the
program writes too much accidentals.
This example demonstrates the problem (2.12.2 and 2.13.6): the
second
bes should not have a written flat.
Frédéric Bron wrote Monday, October 26, 2009 6:30 AM
Here it is not an accidental cancelation, it is just printing the
accidentals from the key!
I consider this as a bug because the new voices should inherit the
key
from the Staff context as it is what's the musician think. No
musician
Valentin Villenave wrote Thursday, October 29, 2009 10:32 AM
On Sat, Oct 3, 2009 at 12:41 AM, luis jure l...@internet.com.uy
wrote:
Hi Luis, sorry for the delay,
% this shows the default beaming and how it should be beamed
r16 c8. c8 c r16 c8. c8[ c] |
I'm not sure what to do. The
Valentin, you wrote Thursday, October 29, 2009 9:27 AM
On Fri, Aug 28, 2009 at 11:41 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
Greetings Trevor and Neil, sorry for bumping this so late:
The default value for 'full-measure-spacing-width appears to
be just the default value
Note this error occurs only on Windows and Macs.
I just tried the minimal example again on Windows
Vista and it still crashes:
Problem signature:
Problem Event Name: APPCRASH
Application Name: lilypond.exe
Application Version: 2.13.6.1
Application Timestamp: 4adf3175
Fault Module Name:
Graham Percival wrote Friday, November 27, 2009 11:53 PM
Interesting. I'm pretty certain that James is using OSX, so that's
not at play... but perhaps it was fixed after 2.13.6?
Is the Application Version string correct (are you using 2.13.6),
or
is there some problem with GUB (i.e. you're
Trevor Daniels wrote Saturday, November 28, 2009 12:14 AM
Graham Percival wrote Friday, November 27, 2009 11:53 PM
Interesting. I'm pretty certain that James is using OSX, so
that's
not at play... but perhaps it was fixed after 2.13.6?
Is the Application Version string correct (are you
Francisco Vila wrote Sunday, November 29, 2009 8:20 PM
I can not find something similar in open issues. It seems that
lines
filled with spacing or multimeasure rests or give a first measure
wider than the others, in each line:
\version 2.13.8
{ \time 6/8
R2.*3 \break
R2.*4 \break
1 - 100 of 421 matches
Mail list logo
