Issue 222: measure "numbers" in XML aren't actually numbers
http://code.google.com/p/lilypond/issues/detail?id=222
Comment #7 by lemzwerg:
The next crash. This time, I've used the reference MusicXML file
`ActorPreludeSample.xml' from
http://www.recordare.com/xml/samples/xmlsamples.zip
Given t
Issue 52: collision suggested accidental and beam
http://code.google.com/p/lilypond/issues/detail?id=52
Comment #1 by gpermus:
Fixed at some point before 2.11.10, probably with the vertical skyline.
Issue attribute updates:
Status: Verified
--
You received this message because you are
> > You could use:
> >
> > \override Score.BarLine #'hair-thickness = #1.2
> [...]
>
> Yes, I could. However, Lilypond's stated goals include the
> generation of top-quality notation with minimal tweaking.
My conclusion of this discussion is that lilypond should reduce the
bar line thickness
Lilypond 2.11.10, Windows XP
I didn't see this issue listed on the bug tracker site, so I thought I'd
mention it here, in case no one else has seen it yet. With 2.11,
accidentals (other than naturals) aren't being displayed. 2.10 displays
them correctly.
\version "2.11.10"
\paper { ragged-
Marnen Laibow-Koser escreveu:
> Mats Bengtsson wrote:
>> Yes, but this is one of the aspects of typesetting layout where
>> there are no fixed rules, but rather a matter of taste.
> [...]
>
> That's true, of course. But if the sample of scores that I have
> examined is at all representative, then
Mats Bengtsson wrote:
Yes, but this is one of the aspects of typesetting layout where
there are no fixed rules, but rather a matter of taste.
[...]
That's true, of course. But if the sample of scores that I have
examined is at all representative, then Lilypond's output is in this
regard so f
Han-Wen Nienhuys wrote:
Thanks for your input.
You're welcome!
I'll keep it in mind when I'm fiddling with fonts
and blackness the next time. It might be a good idea to tune the bar size
down a bit (say: to 1.75), but I'll have to have a good look at the output
first.
Is that 175% of th
Marnen Laibow-Koser escreveu:
> Marnen Laibow-Koser wrote:
>> Han-Wen Nienhuys wrote:
>>
I am giving approximate dimensions of barlines, stems, and staff lines
in pixels. All scans are 300 dpi, so 1 px = 1/300". Editions are
>>>
>>>
>>>
>>> You need 1200 dpi to get a good impression of
Marnen Laibow-Koser wrote:
Karl Hammar wrote:
[EMAIL PROTECTED]:
However, I think that Lilypond's barlines are so far off the chart
that the higher resolution will not change anything.
You could use:
\override Score.BarLine #'hair-thickness = #1.2
[...]
Yes, I could. However, Lilyp
Karl Hammar wrote:
[EMAIL PROTECTED]:
However, I think that Lilypond's barlines are so far off the chart that
the higher resolution will not change anything.
You could use:
\override Score.BarLine #'hair-thickness = #1.2
[...]
Yes, I could. However, Lilypond's stated goals include the g
Marnen Laibow-Koser wrote:
Han-Wen Nienhuys wrote:
I am giving approximate dimensions of barlines, stems, and staff lines
in pixels. All scans are 300 dpi, so 1 px = 1/300". Editions are
You need 1200 dpi to get a good impression of the actual thickness.
If file size is a problem, you can
Ed Rush wrote:
I've searched for the word "classic" in the LilyPond
documentation, to no avail. Nor can I find what
"lilypond-book specific settings" are. I've tried deleting
various parts of the code. So what do I have to do
to make one of your simple examples work for me?
Try only copying
The initial example works on my Mac OS 10.4.8 computer,
but none of the examples in the documentation
work for me. For each one I've tried to compile (command-r),
I get this message:
The PostScript backend does not support the 'classic'
framework. Use the EPS backend instead,
lilypond -b ep
Issue 114: svg backend still has font problems in 2.9.22-mingw
http://code.google.com/p/lilypond/issues/detail?id=114
Comment #2 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the ow
Tomas Sauer wrote:
... that's what I found out too. Nevertheless abc2ly could be a bit improved.
I can try if you're interested. At least I have some motiviation since I like
to get more stuff from Simon Wascher's Trad archive. As long as noone else
works on it at the same time - I just cannot
Issue 225: dot position for rests is wrong
http://code.google.com/p/lilypond/issues/detail?id=225
Comment #3 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC fields of
Issue 221: associatedVoice fails when context is instantiated in same timestep
http://code.google.com/p/lilypond/issues/detail?id=221
Comment #1 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are
Issue 228: tuplet bracket doesn't end properly when quoting
http://code.google.com/p/lilypond/issues/detail?id=228
Comment #1 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
Issue 227: ChoirStaff with Instrument_name_engraver (instrument name aligns
with lyrics)
http://code.google.com/p/lilypond/issues/detail?id=227
Comment #2 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message beca
Issue 226: Dot in `\note #"1." #1' touches note head
http://code.google.com/p/lilypond/issues/detail?id=226
Comment #2 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC
Issue 223: glissandi should not be broken.
http://code.google.com/p/lilypond/issues/detail?id=223
Comment #1 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC fields of
Issue 219: collision simultaneous tuplets
http://code.google.com/p/lilypond/issues/detail?id=219
Comment #2 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC fields of t
Issue 162: define-markup-command in .ly leaks memory
http://code.google.com/p/lilypond/issues/detail?id=162
Comment #5 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC
Issue 86: midi cresc messes up dynamics
http://code.google.com/p/lilypond/issues/detail?id=86
Comment #2 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC fields of this
I don't have a Windows box in front of me right now, but
you could try
convert-ly -e file\ one
or
convert-ly -e "file\ one"
Of course, an alternative is to rename the file.
/Mats
Luc wrote:
Under Windows XP, running [convert-ly "file One"] (with a blank in the file
name) I get the followin
Karl Hammar wrote:
Maybe we should have a "my style" section in the doc.
Like section 4.3 Style sheets ?
Cheers,
- Graham
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
[EMAIL PROTECTED]:
> However, I think that Lilypond's barlines are so far off the chart that
> the higher resolution will not change anything.
You could use:
\override Score.BarLine #'hair-thickness = #1.2
instead of 1.9. Or better make an include file with your style and share
it. Here are e
Alard de Boer escreveu:
> On 08/01/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>> http://code.google.com/p/lilypond/issues/detail?id=228
>
> Thanks for the quick fix!
>
> BTW, why are you allowed to "top post" to the list? :)
See
http://mail.gnu.org/mailman/listinfo/bug-lilypond
->
su
On 08/01/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
http://code.google.com/p/lilypond/issues/detail?id=228
Thanks for the quick fix!
BTW, why are you allowed to "top post" to the list? :)
Alard de Boer.
Alard de Boer escreveu:
>> Not top posting.
>
> In the following case, when quotin
Under Windows XP, running [convert-ly "file One"] (with a blank in the file
name) I get the following errors:
convert-ly.py (GNU LilyPond) 2.11.9
convert-ly.py: error: cannot open file: `file'
convert-ly.py: error: cannot open file: `One'
Similarly, [midi2ly "file One"] produces errors:
Trace
Issue 222: measure "numbers" in XML aren't actually numbers
http://code.google.com/p/lilypond/issues/detail?id=222
Comment #6 by hanwenn:
also fixed , probably won't make .10 - but don't expect the output to be
anything
useful.
--
You received this message because you are listed in the owner
http://code.google.com/p/lilypond/issues/detail?id=228
Alard de Boer escreveu:
>> Not top posting.
>
> In the following case, when quoting another voice, the tuplet
> bracket doesn't end where it should:
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software
Issue 228: tuplet bracket doesn't end properly when quoting
http://code.google.com/p/lilypond/issues/detail?id=228
New issue report by hanwenn:
%% tuplet bracket doesn't end properly when quoting
\version "2.10.9" % on Ubuntu Linux 6.10
\paper { ragged-right = ##t }
\addquote x {
\times 2/3
> "Han-Wen" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
Han-Wen> Laura is the only one using abc2ly on a regular basis. The ABC
"standard"
Han-Wen> is so convoluted that it's hard to work out what's valid and
invalid ABC.
Correction: Laura is the only regular contributor to thi
Issue 7: \partcombine prints multiple tuplet brackets
http://code.google.com/p/lilypond/issues/detail?id=7
Comment #4 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -fixed_2_10_11 -fixed_2_11_11 fixed_2_10_10 fixed_2_11_10
--
You received this me
Issue 7: \partcombine prints multiple tuplet brackets
http://code.google.com/p/lilypond/issues/detail?id=7
Comment #3 by hanwenn:
note the solution will still get things wrong when you quote nested tuplets.
So, Don't Do That.
--
You received this message because you are listed in the owner
or
Issue 7: \partcombine prints multiple tuplet brackets
http://code.google.com/p/lilypond/issues/detail?id=7
Comment #2 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_10_11 fixed_2_11_11
--
You received this message be
Issue 224: loading DejaVuLGCSansMono.ttf replaces spaces by !
http://code.google.com/p/lilypond/issues/detail?id=224
Comment #6 by hanwenn:
Filed with GS bugzilla,
http://bugs.ghostscript.com/show_bug.cgi?id=689038
--
You received this message because you are listed in the owner
or CC fie
Bertalan Fodor escreveu:
> Just a question, I'm curious. Does barline thickness depends on staff
> size? I mean the quotient between staff line thickness and barline
> thickness.
Staff line thickness increases with diminishing staff sizes, see eg.
Eulenburg pocket scores. I'd guess that bar line
Just a question, I'm curious. Does barline thickness depends on staff
size? I mean the quotient between staff line thickness and barline
thickness.
Bert
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-li
> However, I think that Lilypond's barlines are so far off the chart
> that the higher resolution will not change anything.
Higher resolutions gives better comparison values -- some of the
scanned images show too much ragged lines.
Werner
___
bug
Han-Wen Nienhuys wrote:
I am giving approximate dimensions of barlines, stems, and staff lines
in pixels. All scans are 300 dpi, so 1 px = 1/300". Editions are
You need 1200 dpi to get a good impression of the actual thickness.
If file size is a problem, you can small areas of the page.
Y
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> We try to mimick German style engraving. Perhaps we should mention that
> somewhere
Yes, probably; and a quite black style. We have not yet seen an
attempt at tweaking all default settings to produce a different style
of typesetting, with LilyPond.
A simple solution is to use
\override TextScript #'staff-padding = #3.0
(adjust the value so that the distance to the staff looks good).
As long as no note head comes too close, the text will then keep this
fixed distance to the staff.
/Mats
Jesse F. Engle wrote:
I'm not top posting.
Marnen Laibow-Koser escreveu:
> Here we go...some scanned images of barlines. They were too big to
> attach, but you can download them at
> http://doko.ebon-askavi.homedns.org:8080/scans.zip . Image file names
> contain edition name and page number; more bibliographic info about each
> book I sca
Marnen Laibow-Koser escreveu:
> Thomas Scharkowski wrote:
> [...]
>> I have looked into some other editions (Bärenreiter, Peters, Breitkopf
>> & Härtel, Schott) - the barlines are always thicker than the stafflines.
>
> Yes, but by how much?
>
> Maybe these extremely thick barlines are a German p
Issue 227: ChoirStaff with Instrument_name_engraver (instrument name aligns
with lyrics)
http://code.google.com/p/lilypond/issues/detail?id=227
Comment #1 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_10 fixed_2
47 matches
Mail list logo
