ary.
>
> Urs
>
>
>
> ___________
> lilypond-user mailing list
> lilypond-u...@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Han-Wen Nienhuys - hanw...@gmail.com - http://www
I'm at commit 2728f57934651f8de7ae99064305b72d27990932
When I run input/regression/morgenlied through lilypond, I get a small
bit of staff that shouldnt be there,
--
Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
___
bug-lilypond
Hi there,
my clef glyph looks broken (see attachment).
I am on
* commit 3c6b011ceedc9f3eb7908acac19cf7fe7bf54f5c (from Aug 25)
* Fedora 19, which has MetaPost 1.802 (TeX Live 2013), on x86_64
anyone ideas where to find the cause?
--
Han-Wen Nienhuys - han...@xs4all.nl - http
.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
anyone have the same feeling? And please take look
at the atachment - this is how perfect flags should look like to me.
In your example, the top hook looks larger than the other ones,
especially in 32, 64 and 128, because it has nothing above it.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
in scm_error () from /usr/lib/libguile.so.17
#6 0xb76e1e6a in scm_wrong_type_arg () from /usr/lib/libguile.so.17
#7 0xb7714d9a in scm_sum () from /usr/lib/libguile.so.17
#8 0xb76f4190 in scm_gc_protect_object () from /usr/lib/libguile.so.17
This looks like GUILE problem.
--
Han-Wen Nienhuys - han
,
The whole report looks like a non-Tiny example, so politely reject
it and politely point the submitter at our bug reporting
guidelines.
For understanding segmentation faults, the size of the example is
usually irrelevant.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
was the case before Ian turned debugging off in
february with commit 52bea08ef73a55ee?
Guile debugging store a lot more information about the Scheme source
code, so it could easily explain increased memory usage.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman
the vertical spacing (skyline and all) is at stake
here, since in 2.12 the staves are printed further apart (and the beam
slope is totally different).
The message about viable configurations comes from the beam code
which now takes the flat symbol into account.
--
Han-Wen Nienhuys - han...@xs4all.nl
, we'd only apply patches that fix critical or high priority
problems.
The beauty of branching off is that nobody needs to hold off anything.
You just continue to put stuff in master (2.15.0), and cherry-pick
whatever needs to go to 2.14.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
the 2.14 branch so the release
candidate does not get disturbed by other one-liners with unintended
effects? If you don't branch off a stable branch, 2.14 will never get
finished.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
thereafter, SABAM got sued.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
On Fri, Feb 11, 2011 at 3:23 PM, Graham Percival
gra...@percival-music.ca wrote:
On Fri, Feb 11, 2011 at 11:34:00AM -0200, Han-Wen Nienhuys wrote:
The examples have always been part of the /doc hierarchy
By always, you mean until commit
4e92d8b035235815fc55f2fe76505ca3db0f890d
which
have been a quicker way to get started with running comparison
tests.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
On Fri, Nov 26, 2010 at 2:21 AM, Graham Percival
gra...@percival-music.ca wrote:
On Fri, Nov 26, 2010 at 02:15:22AM -0500, Han-Wen Nienhuys wrote:
The reason I did not do it originally is that it moves the comparison
farther away from lilypond itself and pixel-per-pixel changes
/lilypond-devel/2010-04/msg00467.html
We need to merge it and document the feature (and add a regtest). Then this
issue can be closed.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen
On Fri, Apr 30, 2010 at 11:22 AM, Han-Wen Nienhuys hanw...@gmail.com wrote:
On a more general note: can we stop the let's improve the syntax
discussions altogether? We've had them for over 10 years, they
generate a lot of heated bikeshedding discussions, and don't really
help anything, since
to think a bit more about this, but probably the whole font
metric api could use some overhaul. It dates from the time that we
used TeX, and all fonts had to be loaded explicitly by lilypond, while
nowadays some fonts are loaded through Fontconfig/pango.
--
Han-Wen Nienhuys - han...@xs4all.nl
profiling before going that complicated route. The
40 is just an arbitrary number, to force a garbage collect of loaded
fonts.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
On Thu, Feb 18, 2010 at 7:20 AM, Francisco Vila paconet@gmail.com wrote:
Rests are not centered with noteheads in other voices.
This is intentional; only whole-measure rests should be centered.
(Please provide scans of publications if you think otherwise)
--
Han-Wen Nienhuys - han
://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
it is a symlink to the 2.0 documentation. We dont remove it to
not break other people's links gratuitiously.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman
could add a patch to the beam-scoring algorithm
that would penalize configurations that lead to small
white triangles? Or if there's already one, increase the
penalty?
There is no code that penalizes for small white triangles on the inner stems.
--
Han-Wen Nienhuys - han...@xs4all.nl - http
, but in some cases there are small divergences with the
'prescribed' quants. We even have a regtest for it, see
input/regression/beam-quant-standard.ly
It might be possible to tune the scoring parameters to copy Ross
exactly, but probably some other configurations will fall over.
--
Han-Wen Nienhuys
that after the scoring there's a second pass to
fine-tune the result, for example, to `snap' various parts of the beam
to the staff lines where possible.
No, that would not work; the snapped position was also scored and did
not win, so in many cases there is something wrong with it.
--
Han-Wen Nienhuys
On Sun, May 10, 2009 at 6:44 PM, Mark Polesky markpole...@yahoo.com wrote:
Han-Wen Nienhuys wrote:
The rules in Ross' books are guidelines, and they certainly don't
cover all the cases.
Yes, but what about the too-short stem on the
middle-line note:
It could be that there is a bug
could reproduce it, maybe changing an
optimization option? (I use -O2)
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond
list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug
*)':
/home/foth/src/lilypond-2.11.60/lily/beam-quanting.cc:190: undefined
reference to `Align_interface::has_interface(Grob*)'
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond
()\
{ \
cl::interface_symbol_ = add_interface (#cl, b, c); \
} \
ADD_SCM_INIT_FUNC (cl ## ifaces, cl ## _init_ifaces);
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http
2.10.33
I suspect we changed the fontconfig version (which does the font
selection) since then.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo
was
going wrong.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
it, this is a font you created. I haven't been able to
find it though. The web points me to
http://projects.thedanielmay.com/khmerfonts/unicode.htm
which does not exist
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug
-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
"FF";
google_color_link = "006792";
google_color_url = "006792";
google_color_text = "000000";
//-->
Re: 2.11.58-1: Unable to find file ice-9/boot-9.scm in load path
Valentin Villenave
Re: 2.11.58-1: U
://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
)) != SCM_BOOL_F)
prevents it from returning an erroneous match in notemode so it can
return a string instead.
fix looks good. Can you write a regtest, fix and commit?
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug
faults:
Preprocessing graphical objects...Segmentation fault
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
padding) (number?)
#{
\once \override TextScript #'padding = #$padding
#})
\relative c''' {
c4^piu mosso b a b
\padText #1.8
c4^piu mosso d e f
\padText #2.6
c4^piu mosso fis a g
}
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http
several reports stating that the latest development
release is broken on PPC and Windows.
You mean: MacOS? I think linux-PPC is working correctly.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
programs are no prerequisites for a normal build (this
is, using a tarball), only for a build from the git sources.
How so? We are not shipping the fonts in the tarball, and I don't
think we should.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
, and I've demonstrated it to The bug has gone away.
As far as I can remember it was always like this. Maybe the label
name can be enhanced.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug
the grob property list
through definitions in \layout{}
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
in mathematics).
Suggest: ? perhaps ...centered on the leftmost note head
(if that correctly describes it!)
Stan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL
/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
...
Suggest: replace with many
...If not in raggedright mode, lily will pack as many bars of music as
possible...
Stan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys
/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
you file a bugreport for this?
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
/uninstalling
process: on Windows, for instance, such a thing would be practically
impossible (the installation takes ages, and the uninstall is even
worse).
did you know you can run the (un)installer in batch mode if you supply
the /S flag?
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl
setting for
side-axis, (side-axis . ,Y), yet the docs imply that the setting would
be ,X (or 1).
huh? X=0, Y=1
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
, it is
placed vertically.
Like most quantities in lily, we start counting axes at 0.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug
confused :)
Are you saying that the above quote is correct?
Because it seems to imply that #X = 1 and #Y = 0.
no, it's wrong and that's why I cc-d Graham. X = 0, Y = 1
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug
, and
prints i texts accordingly.
(To what does i refer?)
Stan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
Can you try 2.11.43-2 (uploaded today)?
2008/3/26, Tom Richard [EMAIL PROTECTED]:
Version 2.10.33 for Windows XP compiles great. I have tried re-installing
2.11.43 3 times, carefully un-installing previous version every time.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond
-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
seconds
--
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
version fails on XP but works fine on Vista,
as the above demonstrates?
There are certainly differences between these files, but they're not
vista related; the whole build procedure runs on linux, and is for
generic windows32.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl
) and install (as
admin) again?
* Can you see what happens if you deinstall (as admin) and install
(without admin rights) again?
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
seems to have no adverse effect on a couple of
simple tests, but I don't use any unusual fonts.
I'll rebuild the 34-1 and check if I see any interesting anomalies
compared to .42.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
brackets. The code works fine
when the acciaccatura is moved outside, like this:
I fixed the exception. It still doesn't work (you get a bunch of
errors and no bracket.)
I suggest to avoid this: what does it mean for a grace note to be
inside a \times ?
--
Han-Wen Nienhuys - [EMAIL
All compile slowly - 65 secs
All use .lilypond-fonts directory
Dang, this happened after a big refactoring of our build system.
Is there anything interesting (eg. by way of diff -r) of /program
files/lilypond/usr/etc/ directory between .34 and .36 ?
--
Han-Wen Nienhuys - [EMAIL PROTECTED
this entirely. AFAIK lilycall.py isn't
really used anymore, since we put all the relocation logic in the
lilypond binary itself.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
yep. please fix
2008/3/9, Stan Sanderson [EMAIL PROTECTED]:
2.11.42 regressions: grace-stem-length.ly
problem: clarity in text
current: ...even if that would lead to beam quanting program.
Should program be problems?
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl
be defined...
Users may define nonstandard markup commands
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
this trick.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
bracket.
Looks ok to me.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
() if necessary.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
of
extra warning messages. This needs to be looked in to.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
2008/1/7, Valentin Villenave [EMAIL PROTECTED]:
I'll commit some texidoc explanations... as soon as I manage to get my
rsa pubkey accepted by git.
I approved you the day before yesterday. It should work right away.
Can you post what is not working?
--
Han-Wen Nienhuys - [EMAIL PROTECTED
stuff about this.
I have made a mistake, as the file was committed without a texidoc
header, but it may test valuable behavior.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
will fix this.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
administrators
Any questions or comments should be directed to the list administrator
at:
[EMAIL PROTECTED]
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org
for the completely
general case. Is there some reason why this isn't as good as the
equivalent \lyricsto solution?
\addlyrics is implemented with \lyricsto. The problem is that
convert-ly cannot reliably handle the (possibly nesting) arguments to
\lyriccombine.
--
Han-Wen Nienhuys - [EMAIL
will look the same on other systems; PDFs created on
OSX should have
the same compatibility stuff.
I'm not sure if that is feasible when taken to its consequence. We'd
have a to include a font that has coverage in all of unicode; it will
be large, and there might be licensing problems.
--
Han-Wen
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
the output of running it from
the commandline in windows with FC_DEBUG=255 in the environment.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo
, maybe should we ship a sans-serif font too, so chord
names have uniform appearance across platforms. Any suggestions which
would be the best font?
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
, but it would take a lot of space, for rare occasions.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
to be a problem with the
ghostscript that's included in the binary package.
In the original report, it didn't crash in GS but in lily.
It looks as if someone needs to build a macos binary without
stripping.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
that idea
encapsulated in a property by itself. One extreme idea could be to
calculate up and down extents separately, perhaps with a
Y-extent - (up-extent , down-extent)
dependency, which we would have just for Stem for now.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl
unlikely.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
in seeing examples with stems in the wrong order.
Joe
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
(re)building process going on
somewhere. But if not, could someone put the docs back online?
Trevor.
--
Trevor Bača
[EMAIL PROTECTED]
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Han-Wen
Zapf a long time ago. In the standard
chord, the 3 and 11 combine very badly, so ususally the 11 is dropped.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org
() is called before line
breaking.
In general all before/after-line-breaking callbacks are not
data-driven, so they should disappear.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
strings, ie.
the cmd \\tweak
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Joe, can you have a look at this?
2007/7/3, Toine Schreurs [EMAIL PROTECTED]:
segfault,
programming error bad number of pages
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug
in inkscape, and I don't know enough of SVG to
effectively add or test these changes.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug
engravings. In the case you show, arguable the 1st
beam should rather be slightly slanted
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug
a
choir piece on two staves, with four stanzas of lyrics.
I'll try cooking up a minimal example. The following example is
I have fixed this bug (I think), and am rolling a .25 to amend
this brown-paper-bag bug
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
Joe Neeman escreveu:
Is this the old page breaker (optimal-page-breaks) or the new one
(ly:optimal-breaking)? There will be some dramatic speed increases in the new
breaker in 2.11.24.
what's your plan for this? I want to release .24 end of this weekend.
--
Han-Wen Nienhuys - [EMAIL
it to .pdf fails. The weird thing is that typing manually the command
mentioned in the error message, the conversion works fine.
I use debian etch. I think that I have all the fonts installed because I can see
the ps perfectly.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
) introduced increased memory use.
Unfortunately, I lack the time to investigate this deeply now, and I
would be grateful if someone did a bit of legwork for me.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond
1 - 100 of 908 matches
Mail list logo
