27;s temporary.
>
> 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.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
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-lil
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
tarting
point into the hash table, and then serialize the hash table.
--
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
curate. **Does 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...
m /usr/lib/libguile.so.17
> #4 0xb76e1ac4 in scm_error_scm () from /usr/lib/libguile.so.17
> #5 0xb76e1b61 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 0
H" looks,
>
> 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 -
ow is, what 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 - h
; \voiceOne
> r1 r1
> }
> \new Voice {
> \voiceThree
> c'2 e' g' b'
> }
> \new Voice {
> \voiceTwo
> r1 r1
> }
>
>
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> http://lists
cent.
>
> Indeed. I suspect 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
2.14.0), we can still
> sit on it for a week or two before building it with GUB. During this
> incubation phase, 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 ma
ine change
by Mike. Can I ask that you branch off 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
towel dispenser) and "Kenwood"
(kitchen appliances).
Shortly 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
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
> 4e92d8b035235815fc55f2fe76505ca3d
ing 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
http://lists.gnu.org/mailman/listinfo/bug-lilypond
On Fri, Nov 26, 2010 at 2:21 AM, Graham Percival
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 are not
>> ca
core. It
might 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
0abfec92296095b369a5497
Also, when doing diffs, it's probably more direct to read the file and
apply a difflib function on ti.
--
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
nts. (this assumes
atomic writes, which is reasonable given the size of a snippet)
>> File "/usr/local/bin/lilypond-book", line 1768, in filter_pipe
>> error (_ ("`%s' failed (%d)") % (cmd, exit_status))
>> TypeError: 'str' object is not c
On Fri, Apr 30, 2010 at 11:22 AM, Han-Wen Nienhuys 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 real
__
> bug-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
http://lists.gnu.org/mailman/listinfo/bug-lilypond
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 - http://www.
bably done 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@g
On Thu, Feb 18, 2010 at 7:20 AM, Francisco Vila 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...@xs4a
__
> bug-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
http://lists.gnu.org/mailman/listinfo/bug-lilypond
IIRC 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:
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...@
On Sun, May 10, 2009 at 6:44 PM, Mark Polesky 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 cou
ably some other configurations will fall over.
>
> I can imagine 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 s
different
rules, 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 configuration
Does someone have an idea how I 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
gt; }
>
> \relative {
>
> << {
>gis'! gis! gis! gis!
> } \\ {
>
> } >>
> }
>
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
>
>
--
Han-We
_
> 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 mai
\
} \
void cl ## _init_ifaces ()\
{ \
cl::interface_symbol_ = add_interface (#cl, b, c); \
}
/out/beam-quanting.o: In function `Beam::quanting(scm_unused_struct*,
> scm_unused_struct*)':
> /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.xs4a
> Bye,
>
>Zoltan
>
>
> ___________
> 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@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
but failed, as it was very difficult for me to understand what 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
th the period still worked as intended in Lilypond 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-lily
ze #3
> { "Bøw meRBI" } }
> }}
As I understand 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
correct yet.
The rendering is actually done by pango. Can you verify whether the
rendering looks correct in (for example) the Gedit of your system
(which also uses pango)?
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lil
oc/v2.11/examples
>
>
> Cheers,
> Robin
>
>
>
>
>
> ___
> 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
__
issue.
> You may adjust your issue notification preferences at:
> http://code.google.com/hosting/settings
>
>
> ___
> 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@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
lor_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: Unable to find file "ice-9/boot-9.scm" in load path
Han-Wen Nienhuys
Re: 2.11.58-1: Unable to find file "ice-9/bo
_
> 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@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
&& (handle = scm_hashq_get_handle (chordmodifier_tab_,
> sym)) != 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 Nienhu
on a Linux
> machine. It seg 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
ation 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
; I'm receiving 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
_
configure file.
>
> Yes. But those 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 PRO
and fontforge implicitly, because
they were dependencies for mftrace. Now that mftrace is no longer a
requirement, we should have checks for those in the configure file.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-
#x27;t we see it on
> http://lilypond.org/test/v2.11.49-1/compare-v2.11.48-1/ ???
>
> I'm puzzled.
The output distance is based on Grob extents, which does not change
for these 2 images.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
__
ed when the bug is no longer occuring.
>
> This is almost a complete reversal of the meaning of "Verified", from "It
> really is a bug, and I've demonstrated it" to "The bug has gone away".
>
As far as I can reme
ts and a
> largish example to test? We seem to be fairly close to releasing a
> stable version and I don't particularly want to break stuff.
>
This is awesome! The beaming problems have irked me for a long time,
thanks for fixing this!
--
Han-Wen Nienhuys - [EMAIL P
ere are default font settings which enter 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
nd 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@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 mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
gest: omit "Music functions are..."
>>
>>
>> Stan
>>
>>
>>
>>
>> ___
>> bug-lilypond mailing list
>> bug-lilypond@gnu.org
>> http://lists.gnu.org/mailman/listinfo/bug-lilypond
>
&g
_
>> 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
lypond 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@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
t; 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).
did you know you can run the (un)installer in batch mode if you supply
th
extent of the bracket.
> Adding an outside staff object nearby forces visibility.
>
that would be a bug. Could 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
ke most quantities in lily, we start counting axes at 0.
>
> Now I'm really 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 Graha
lly next to the other object. If the value is #Y or 0, 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
-grobs.scm, TextScript has the the following 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-lilypon
ruary
> 24).
can you check the gub binary anyway? You can do the sign change with
the following change: in the definition of glyph-spec inside
glyph-string in output-ps.scm, change
(+ w x)
to
(- w x)
You can find the .scm file inside the gub binary, in
lilypond/usr/share/lilypond/cur
the python in your path.
I wouldn't mind shipping this, but IIRC, some systems actually put env
into /bin/
>
> This is still a problem for normal OSX users (ie people who
> haven't installed macports or fink), though. :(
>
> Cheers,
>
> - Graham
>
--
ner detects a2, solo1 and solo2, and
> prints i texts accordingly."
> (To what does "i" refer?)
>
> Stan
>
>
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> http://lists.gnu.org
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 PROTE
t again, and then
> tell us if the problem is still happening?
>
> Cheers,
> Valentin
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
>
--
Han-Wen Nienh
fc_font_lock_face:
> assertion `PANGO_IS_FC_FONT (font)' failed
> Processing time: 6 seconds
>
> --
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> http://lists.
1633, sorry.
is this py 2.3 or 2.4 ?
--
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
nd 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@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
ded for Vista, since the
> later 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
t happens if you deinstall (as admin) 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-lily
h also bypasses the timing problem. This also
> 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 Ni
lyph U+ ... Century-Schl-Roma.otf
> Uses .fontconfig directory
>
> 2.11.36-1, 37-1, 41-1, 42-1
> 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 di
gt; be placed within \times 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 ?
'] = prefix + '/share/lilypond/current'
The proper fix is to remove 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
_
>
> Cheers,
>
> Valentin
>
>
>
> ___________
> 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@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
ithin a staff group should cause the piano
> brace to be drawn to the left of the staff angle 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
mentation makes
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
kup commands may be defined..."
> (or) "Special markup commands may 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
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&q
to apply?
looks good to me.
We should really do an audit of all extent() calls and replace with
robust_relative_extent() 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
ination (attach))
> returns "nan"). If I use g2\< instead of s2\<, a value of 17,... is returned.
I suppose this should robust_relative_extent() rather than extent()
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
n with actual tests
> breaking on the current version.
no, this is on purpose. the .39 -> .40 transitions generated lots of
extra warning messages. This needs to be looked in to.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
eering
> Royal Institute of Technology (KTH)
> SE-100 44 STOCKHOLM
> Sweden
> Phone: (+46) 8 790 8463
> Fax: (+46) 8 790 7260
> Email: [EMAIL PROTECTED]
> WWW: http://www.s3.kth.se/~mabe
> =
>
>
>
> __
th postscript names at all...
Hi,
IIRC when this was written, cairo was not really up to the task of
generating print output (and not pulling in all of the X11 related
deps). I'm not up for the task of ripping out the current backend and
replacing it with cairo, but I'm certainly willi
I prefer to close this issue instead noone actually indicated they
desparately needed it.
2008/2/8, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> Issue 370: slur #'positions silently does not place slur at actual position
> http://code.google.com/p/lilypond/issues/detail?id=37
st striking example is
> probably
> the "style" property, where the current documentation is extremely
> uninformative
> for this reason.
You have a point there. However, the 'style setting does not have a
reasonable default (like "measured in linethickness&quo
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-W
uplicate.
Please contact the author of the festival 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
__
ns
shortly, which 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
LilyPond mailing list 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
scripted for the
> real-world case, although maybe not by convert-ly 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 h
be large, and there might be licensing problems.
--
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
m Files\Lilypond\usr\var\cache\fontconfig
>
> and that is empty.
that is strange: they should be called .fontconfig , not fontconfig
(note leading period).
Fontconfig actually looks at the environment variable
$USERPROFILE
--
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
:\bla directory, of course?
--
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
cond call.
It would be nice if someone could post 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-lilypo
u should work with all types of mac dfonts.
In any event, 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
_
1 - 100 of 1280 matches
Mail list logo
