Am Mi., 29. Jan. 2020 um 16:41 Uhr schrieb Dan Eble :
>
>
>
> > On Jan 29, 2020, at 10:17, Masamichi Hosoda wrote:
> >
> >> I ask because, in the german forum Arnold found a method to cure some
> >> windows-only bugs., about mis-predicted force and p
Am Mi., 29. Jan. 2020 um 16:17 Uhr schrieb Masamichi Hosoda
:
>
> > I ask because, in the german forum Arnold found a method to cure some
> > windows-only bugs., about mis-predicted force and probably several
> > assertion-failures:
> > https://lilypondforum.de/index
t; I just got news from Phil (who had been offline for a while) and he
> plans to set to it this weekend, time allowing.
>
> > I ask because, in the german forum Arnold found a method to cure some
> > windows-only bugs., about mis-predicted force and probably several
> > asserti
> On Jan 29, 2020, at 10:17, Masamichi Hosoda wrote:
>
>> I ask because, in the german forum Arnold found a method to cure some
>> windows-only bugs., about mis-predicted force and probably several
>> assertion-failures:
>> https://lilypondforum.de/index.php/
> I ask because, in the german forum Arnold found a method to cure some
> windows-only bugs., about mis-predicted force and probably several
> assertion-failures:
> https://lilypondforum.de/index.php/topic,609.msg3463.html#msg3463
The patch is very interesting.
I've tried x87man
e allowing.
> I ask because, in the german forum Arnold found a method to cure some
> windows-only bugs., about mis-predicted force and probably several
> assertion-failures:
> https://lilypondforum.de/index.php/topic,609.msg3463.html#msg3463
>
> Though, this would first need to b
Hi all,
iirc in Salzburg there was the plan to do a 2.19.84-release, soon
followed by stable 2.20
May I ask how's the state of 2.19.84?
I ask because, in the german forum Arnold found a method to cure some
windows-only bugs., about mis-predicted force and probably several
assertion-fai
On 12/10/14 12:21, erik flister wrote:
ok here you go
http://code.google.com/p/lilypond/issues/detail?id=4163
Thanks.
I have added you as a contact on the 'Rietveld' site where most of the
reviews are done. So you will see any comments mainly there. If you do
get anything you need to fix yo
ok here you go
On Sun, Oct 12, 2014 at 2:31 AM, James wrote:
> Erik,
>
> On 12/10/14 04:05, erik flister wrote:
>> hi there-
>> sorry for cross posting to all the lists, i'd rather not subscribe and
>> this post seems to apply to all three.
>>
>> attached is a recorder diagram patch, would love f
Erik,
On 12/10/14 04:05, erik flister wrote:
> hi there-
> sorry for cross posting to all the lists, i'd rather not subscribe and
> this post seems to apply to all three.
>
> attached is a recorder diagram patch, would love for feedback and for
> it to be incorporated. hopefully it's ok it's not
hi there-
sorry for cross posting to all the lists, i'd rather not subscribe and
this post seems to apply to all three.
attached is a recorder diagram patch, would love for feedback and for
it to be incorporated. hopefully it's ok it's not actually in patch
format, it just drops into display-wood
Hey Julien,
thanks a million!
Cheers,
patrick
http://codereview.appspot.com/5697059/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Patrick,
A cleaned up version of this patch has been committed (and credited to
you), so you may close this Rietveld issue. You will see the fix in
version 2.15.41, the next development release.
Cheers,
Julien
http://codereview.appspot.com/5697059/
__
LGTM
http://codereview.appspot.com/6330046/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 12-03-01 10:23 AM, ptrcklsch...@googlemail.com wrote:
Well it would certainly be easier for me if we opened a new issue for
this patch as it contains fixes for several bugs I reported lately. For
some of them no issues were opened. Here are the bugs / reports at
stake:
-) http
sufficiently different that we should open a new issue for it?
Well it would certainly be easier for me if we opened a new issue for
this patch as it contains fixes for several bugs I reported lately. For
some of them no issues were opened. Here are the bugs / reports at
stake:
-) http
On 2012/02/29 22:33:45, Julien Rioux wrote:
So please revert the changes to musicxml.py
I mean musicxml2ly.py
http://codereview.appspot.com/5697059/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypo
This patch is not associated with any issue in the bug tracker. It will
not get a proper review until it is added there, and the automatic
testing shows that it does not cause any unexpected problems. Should it
be added to issue 1983, or is it sufficiently different that we should
open a new issue
Reviewers: ,
Description:
Fix for several musicxml2ly bugs.
musicxml2ly: title, chord symbol and midi bug
Titles and headers can now contain single words followed by a
punctuation mark (.,!:). See issue 1983.
Chord symbols are now placed above staffs instead of below.
musicxml2ly now
On Wed, Oct 5, 2011 at 5:17 AM, Alex Austin wrote:
> On Tue, Oct 4, 2011 at 3:22 PM, wrote:
>>
>> ... There are no hard links that I am aware of.
>
> http://msdn.microsoft.com/en-us/library/windows/desktop/aa365006(v=vs.85).aspx
It is not a restriction of NTFS but of the windows C api and thus
i
On Tue, Oct 4, 2011 at 3:22 PM, wrote:
>
> ... There are no hard links that I am aware of.
>
>
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365006(v=vs.85).aspx
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/ma
? i.e. you don't need
my-cmd "\\\$\"\`"
?
The " might give trouble, but it cannot appear in a filename. Same goes
for \, which is the path separator. It's definitely wrong to use \ as
the escape character anyway. The other characters are plain characters.
Description:
http://codereview.appspot.com/5183042/diff/1/python/book_snippets.py
File python/book_snippets.py (right):
http://codereview.appspot.com/5183042/diff/1/python/book_snippets.py#newcode643
python/book_snippets.py:643: os.rename (src, dst)
Doesn't this REMOVE the src?
os.link creates a link at dst,
>> ToUnicode entries are generated by texinfo.tex. Assuming that your
>> texinfo.tex (in the lilypond/tex) isn't garbled, it seems that your
>> pdftex can't digest them properly.
>
> You have to be looking, otherwise it's a bit like a needle in a
> haystack. I think it may also be Ubuntu specifi
- Original Message -
From: "Werner LEMBERG"
To:
Cc:
Sent: Monday, June 13, 2011 3:54 PM
Subject: Re: Further build bugs
Error: Illegal entry in bfrange block in ToUnicode CMap
and the Error message repeated about 500 times. The block of these
error messages is repeat
> Error: Illegal entry in bfrange block in ToUnicode CMap
>
> and the Error message repeated about 500 times. The block of these
> error messages is repeated through the output. This is using
> lily-ubuntu (ubuntu 10.04). It appears from the web that it's a bug
> in Ubuntu, but just wondering
I've now reduced the output from make doc from over 500,000 lines to just
over 100,000 so there are some error messages I see that were not obvious
before. In the output I see:
cd ./out-www; texi2pdf -I /home/phil/lilypond-git/Documentation -I
/home/phil/lilypond-git/input/regression --quiet
On Fri, Dec 25, 2009 at 12:25 AM, James Bailey
wrote:
>
> On 24.12.2009, at 23:57, Joe Neeman wrote:
>>
>>> profile-property-access.ly errors and fails when I try to compile it.
>>> Additionally, the properties shown in the output are all 0
>>
>> You need to configure with --disable-optimising in
On 24.12.2009, at 23:57, Joe Neeman wrote:
profile-property-access.ly errors and fails when I try to compile it.
Additionally, the properties shown in the output are all 0
You need to configure with --disable-optimising in order for property
access profiling to work.
Okay, since I can't com
On Thu, 2009-12-24 at 23:24 +, Graham Percival wrote:
> On Thu, Dec 24, 2009 at 02:57:07PM -0800, Joe Neeman wrote:
> > On Sun, 2009-12-20 at 18:42 +0100, James Bailey wrote:
> > > profile-property-access.ly errors and fails when I try to compile it.
> > > Additionally, the properties shown i
On Thu, Dec 24, 2009 at 02:57:07PM -0800, Joe Neeman wrote:
> On Sun, 2009-12-20 at 18:42 +0100, James Bailey wrote:
> > profile-property-access.ly errors and fails when I try to compile it.
> > Additionally, the properties shown in the output are all 0
> You need to configure with --disable-opti
On Sun, 2009-12-20 at 18:42 +0100, James Bailey wrote:
> In checking the regressions, I've come across some issues. And, sorry
> for posting these all in one go, but I've just been saving them up
> until one day I could post a massive email and have the bug tracker
> explode with new regressi
Am Sonntag, 20. Dezember 2009 18:42:47 schrieb James Bailey:
> quote-during.ly and quote.ly appear to be fundamentally identical.
> Additionally, quote-during references cueDuring in the explanatory
> text, although cueDuring isn't used in the example.
On the other hand. quote.ly speaks of "\quote
ed. Consequently, I couldn't compile any of these examples.
On 12.12.2009, at 06:43, Graham Percival wrote:
With the release of 2.13.9, we now believe that all bugs are
either fixed, or have been added to the issue tracker. If you
have reported a bug and it is not in the tracker, please chec
With the release of 2.13.9, we now believe that all bugs are
either fixed, or have been added to the issue tracker. If you
have reported a bug and it is not in the tracker, please check the
bug reporting guidelines and re-submit it.
http://lilypond.org/doc/v2.13/Documentation/web/bug-reports
On Fri, Nov 27, 2009 at 09:54:49PM -0800, Patrick McCarty wrote:
> On Fri, Nov 27, 2009 at 9:27 PM, Graham Percival
> wrote:
> > If it doesn't exist already, is it worth writing something for the
> > CG about using git bisect to find the exact commit where a
> > regression was introduced?
>
> The
On Fri, Nov 27, 2009 at 9:27 PM, Graham Percival
wrote:
> If it doesn't exist already, is it worth writing something for the
> CG about using git bisect to find the exact commit where a
> regression was introduced?
There doesn't appear to be anything in the CG about `git bisect'. The
man page fo
If it doesn't exist already, is it worth writing something for the
CG about using git bisect to find the exact commit where a
regression was introduced?
If it does exist, would it be worth trying to convince a frog or
two to spend time doing this? I heartily admit that it's not
glamorous work, bu
On 2009-08-14, Han-Wen Nienhuys wrote:
> On Thu, Aug 13, 2009 at 8:03 PM, Patrick McCarty wrote:
> >
> > See the attached patch for the progress I've made. Also attached is
> > an image of Mark Polesky's example from the bug tracker:
> >
> > http://code.google.com/p/lilypond/issues/detail?id=379#
On Thu, Aug 13, 2009 at 8:03 PM, Patrick McCarty wrote:
>
> Hello,
>
> I've decided to dive into deep waters (the slur code) and try to fix
> the popular "ugly slur" bugs, #379 and #427.
>
> See the attached patch for the progress I've made. Also attache
On 2009-08-14, Neil Puttock wrote:
>
> Two issues have caught my eye (one minor, the other more serious):
>
> 1. After a break, I think there's too little space between key
> signature alterations and a continuation (though this also applies to
> ties, so it's probably a more general issue): at l
Patrick McCarty wrote:
> I've decided to dive into deep waters (the slur code) and try to fix
> the popular "ugly slur" bugs, #379 and #427.
>
> See the attached patch for the progress I've made. Also attached is
> an image of Mark Polesky's
2009/8/14 Neil Puttock :
> Will report back once I've given the patch a whirl.
This is already very impressive, as far as I can tell.
I've just run `make check' and there are no important changes visible,
but I imagine that's due to the fact we haven't got any tests which
really exercise this is
2009/8/14 Patrick McCarty :
> I've decided to dive into deep waters (the slur code) and try to fix
> the popular "ugly slur" bugs, #379 and #427.
Hurrah! :)
You've already made more progress than I have tackling this; I spent
far too much time fiddling a
Hello,
I've decided to dive into deep waters (the slur code) and try to fix
the popular "ugly slur" bugs, #379 and #427.
See the attached patch for the progress I've made. Also attached is
an image of Mark Polesky's example from the bug tracker:
http://code.google.com
On Thu, 2008-09-11 at 22:26 +0200, Werner LEMBERG wrote:
> > Perhaps we could add a default for minimum-X-extent in
> > define-grobs.scm. [...]
>
> Sounds like a good idea. Joe seems to be on vacation, though...
I just moved to a different continent to start a Ph.D, so I've been a
bit preoccupi
> Perhaps we could add a default for minimum-X-extent in
> define-grobs.scm. [...]
Sounds like a good idea. Joe seems to be on vacation, though...
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listi
2008/9/4 Werner LEMBERG <[EMAIL PROTECTED]>:
>
>> > 1. I'm replacing hara-kiri with axis-group; however, whatever I
>> >do, there is no (empty) lyrics line in the first system.
>>
>> This appears to be the same issue affecting the piano centred
>> dynamics template when there's a system with no
Werner LEMBERG wrote:
The defaults are `not-set', which is equivalent to #f since both
properties are read using to_boolean ().
No, remove-empty is set to true by default in a number of contexts,
including Lyrics.
But those defaults aren't hard-coded but explicitly set in
engrave
> > The defaults are `not-set', which is equivalent to #f since both
> > properties are read using to_boolean ().
>
> No, remove-empty is set to true by default in a number of contexts,
> including Lyrics.
But those defaults aren't hard-coded but explicitly set in
engraver-init.ly -- Neil has ans
Neil Puttock wrote:
3. The default values of the `remove-empty' and `remove-first' flags
are not documented in lilypond-internals.
The defaults are `not-set', which is equivalent to #f since both
properties are read using to_boolean ().
No, remove-empty is set to true by defaul
> > 1. I'm replacing hara-kiri with axis-group; however, whatever I
> >do, there is no (empty) lyrics line in the first system.
>
> This appears to be the same issue affecting the piano centred
> dynamics template when there's a system with no dynamics.
Ok. Is this classified as a bug or as
Hi Werner,
2008/9/2 Werner LEMBERG <[EMAIL PROTECTED]>:
> 1. I'm replacing hara-kiri with axis-group; however, whatever I do,
> there is no (empty) lyrics line in the first system.
This appears to be the same issue affecting the piano centred dynamics
template when there's a system with no
> Here the bugs:
>
> 1. I'm replacing hara-kiri with axis-group; however, whatever I
> do, there is no (empty) lyrics line in the first system.
>
> 2. I have to set the `remove-empty' flag explicitly to #f, which I
> consider wrong behaviour. If
aver"
\override VerticalAxisGroup #'minimum-Y-extent = #'(-10 . 10)
\override VerticalAxisGroup #'remove-empty = ##f
} \lyricsto "foo" \lyricmode {
bla
}
\context Voice = "bar" {
R1 * 33 |
}
>>
Here the bugs:
1.
2008/1/28, Robert Memering <[EMAIL PROTECTED]>:
> Am Sonntag, 27. Januar 2008 23:19 schrieb Han-Wen Nienhuys:
> > For issue 297, I can change the formatting to end exactly on the last
> > note; would that solve the problem? Juergen?
>
> I would be very happy if only this could be solved!
Hi,
hav
On Tue, 29 Jan 2008, Han-Wen Nienhuys wrote:
2008/1/27, Juergen Reuter <[EMAIL PROTECTED]>:
The ligature events are implemented as 'command-event', like \bar and
\time, which fall in between the notes.This is inconsistent with
start/stop commands like [ ] , but I can't really judge if tha
2008/1/27, Juergen Reuter <[EMAIL PROTECTED]>:
> > The ligature events are implemented as 'command-event', like \bar and
> > \time, which fall in between the notes.This is inconsistent with
> > start/stop commands like [ ] , but I can't really judge if that is the
> > best way to do it.
>
> Hmm
Am Sonntag, 27. Januar 2008 23:19 schrieb Han-Wen Nienhuys:
> For issue 297, I can change the formatting to end exactly on the last
> note; would that solve the problem? Juergen?
I would be very happy if only this could be solved!
However, there is one additional problem with ligature
brackets:
On Sun, 27 Jan 2008, Han-Wen Nienhuys wrote:
Juergen (CC-d) is the person who wrote the ligature code, including
the one for the brackets.
Yepp, ages ago (around early 2002)...
I'm looking at the issues now, but there is something I don't
understand.
The ligature events are implemented
Juergen (CC-d) is the person who wrote the ligature code, including
the one for the brackets.
I'm looking at the issues now, but there is something I don't understand.
The ligature events are implemented as 'command-event', like \bar and
\time, which fall in between the notes.This is inconsis
Dear Lilypond developers,
I am preparing some sophisticated scores of
renaissance vocal music and I am severely affected
by the problems with ligature brackets described
in issue #83 and #297 of the bug tracker. (I can
send examples much uglier than in the bug tracker if
anyone is interested.)
I
There are three bugs that are particularly annoying from a documentation
maintenance perspective:
http://code.google.com/p/lilypond/issues/detail?id=268
http://code.google.com/p/lilypond/issues/detail?id=483
http://code.google.com/p/lilypond/issues/detail?id=485
These aren't urgent b
Anybody object to this change? I'm looking at Micro tones right now:
Bugs
There are no generally accepted standards for denoting three-quarter
flats, so LilyPond's symbol does not conform to any standard.
IMO this isn't really a _bug_, so I propose using the mo
Folks,
I would be *really* glad if you run `make web' before checking in your
changes! It took me almost the whole afternoon to fix the bugs in the
translations.
Note, however, that there's a nasty bug in texinfo 4.8: It's not
possible to say @q{\} (@q is a macro -- a built-i
Ruud van Silfhout wrote:
Graham Percival wrote:
http://lilypond.org/web/devel/participating/bugs
http://lilypond.org/web/devel/participating/documentation-adding
I think there is a small typo in the documentation-adding page.
In the sentence "Ask on the lilypond-devel mailist if such a re
Graham Percival wrote:
Could one or two people proofread the new pages on bug reports and doc
suggestions?
http://lilypond.org/web/devel/participating/bugs
http://lilypond.org/web/devel/participating/documentation-adding
I think there is a small typo in the documentation-adding page.
In the
Cameron Horsburgh wrote:
On Thu, Dec 28, 2006 at 07:15:07PM -0800, Graham Percival wrote:
http://lilypond.org/web/devel/participating/bugs
http://lilypond.org/web/devel/participating/documentation-adding
There's one small error on the doc adding page, where you seem to have
cut
On Thu, Dec 28, 2006 at 07:15:07PM -0800, Graham Percival wrote:
> Could one or two people proofread the new pages on bug reports and doc
> suggestions?
>
> http://lilypond.org/web/devel/participating/bugs
> http://lilypond.org/web/devel/participating/documentation-adding
>
I've finally finished catching up on all the bug reports and doc
submissions. Please check the bug tracker for your favorite bugs; if
they're not there, and if the bugs are still in 2.11.6 (when that comes
out), then send another bug report to the bugs mailist. Likewise, if
there&#
Cameron Horsburgh wrote:
%% the octovation command doesn't do anything.
'octavation' is misspelled.
Thanks.
I wonder if it would be worthwhile advising new bughunters to ask
-devel or -user if they're not sure it is a bug they have found.
Sometimes bugs are just lack of
On Thu, Dec 28, 2006 at 07:15:07PM -0800, Graham Percival wrote:
> Could one or two people proofread the new pages on bug reports and doc
> suggestions?
>
> http://lilypond.org/web/devel/participating/bugs
> http://lilypond.org/web/devel/participating/documentation-adding
>
Could one or two people proofread the new pages on bug reports and doc
suggestions?
http://lilypond.org/web/devel/participating/bugs
http://lilypond.org/web/devel/participating/documentation-adding
Cheers,
- Graham
___
lilypond-devel mailing list
Joe Neeman schreef:
My page-breaking patch is getting big and unwieldy again, so I've split
off some bits that aren't really related. Among other things, this patch
fixes the bug that Kieren MacMillan found a month ago (subject line
"modifying items-worth-living").
It also makes annotate-spacing
My page-breaking patch is getting big and unwieldy again, so I've split
off some bits that aren't really related. Among other things, this patch
fixes the bug that Kieren MacMillan found a month ago (subject line
"modifying items-worth-living").
It also makes annotate-spacing more robust. Before t
Erik Sandberg schreef:
I also fixed some other problems in your code, but ignored the TEX stuff
because I don't understand it. Attached is a patch which works well as far as
I have tested. Han-Wen, may I apply?
looks good.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/
\
> if (YY_START==lyric)\ // start_lyric_quote() was called
> Just yy_push_state (lyric_quote); \ // in status
> else\
> yy_push_state (quote); \
> yylval.string = new string
Why can't we just use separate defines for start_lyric_quote a
[sorry...forgot to CC list]-- Forwarded message --From: Erlend Aasland <[EMAIL PROTECTED]>
Date: Apr 26, 2006 1:59 PMSubject: Re: reporting bugs in 2.9 (dotted line infects staff lines)To: Graham Percival <[EMAIL PROTECTED]>
On 4/26/06, Graham Percival <[EMAIL PR
I'm starting to look at doing Bug Meister stuff. How do we deal with
bugs in 2.9? I think this bug has a simple fix; I don't think it's
worth entering it into cvs. Can I just send the report here?
In this specific case, any dotted line (like a "cresc." or
&q
Sorry again, the patch should add a "8 2 roll" (not -2).
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Sorry, forgot to attach the patch...On 4/18/06, Erlend Aasland <[EMAIL PROTECTED]> wrote:
Hello again David,Dashed slurs are completely misdrawn in LilyPond 2.9.2. I suspect that this one-liner will fix the problem. Shall I apply or have you got another fix?Regards,
Erlend
dash.patch
Descript
Hello again David,Dashed slurs are completely misdrawn in LilyPond 2.9.2. I suspect that this one-liner will fix the problem. Shall I apply or have you got another fix?Regards, Erlend
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gn
Erik Sandberg wrote:
-%Thomas Scharkowski
+%fixed: not a bug; the 8 has no dimension to make lyrics come closer to
the staff. see define-grobs.scm (hwn) +%Thomas Scharkowsk
This _is_ still a bug: If lily's architecture isn't currently powerful enough
to avoid all collisions between clefs whi
On Sunday 05 February 2006 01.45, Han-Wen Nienhuys wrote:
> CVSROOT: /cvsroot/lilypond
> Module name: lily-bugs
> Branch:
> Changes by: Han-Wen Nienhuys <[EMAIL PROTECTED]>06/02/05 00:45:52
> --- lily-bugs/bugs/c-clef-clef.ly:1.3 Mon Oct 3 08:48:00 2005
> +
On 15-Jan-06, at 4:55 PM, Erlend Aasland wrote:
Recent changes in the documentation introduced some small bugs. Please
see attached patches and apply. Patches are against latest CVS.
Thanks, applied.
- Graham
___
lilypond-devel mailing list
Hi Graham & Han-WenRecent changes in the documentation introduced some small bugs. Please see attached patches and apply. Patches are against latest CVS.ChangeLog entry:2006-01-16 Erlend Aasland <
[EMAIL PROTECTED]> * Documentation/user/global.itely: fix typos; @bugs -> @ref
hi,
I've gone through the bugs directory in CVS, and fixed some problems.
Please update fixed issues.
The latest status is at
lilypond.org/bugs/v2.7/
Thanks!
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~h
Use the mailing list bug-lilypond@gnu.org, as described at
http://lilypond.org/web/about/
/Mats
Raphael Manfredi wrote:
Hello,
I've not found any link to a bug tracking system on the website of
Lilypond. I've made a few very simple .ly files and .png showing
formatting bugs.
Hello,
I've not found any link to a bug tracking system on the website of
Lilypond. I've made a few very simple .ly files and .png showing
formatting bugs.
Could you please let me know the procedure for reporting those?
Thanks,
Raphael
__
Hi,
The following fragment shows some bugs on tremolo's (version 2.7.0):
- The eight note has too many beams (should be just one).
- The beams are also placed too close to the notehead (there should be
at least two staff-spaces between the notehead and the beam).
- The beam shouldn't
On 5-Aug-05, at 12:18 AM, Werner LEMBERG wrote:
instrument-notation.ly is tagged as being latin-1 encoded but contains
data in utf8. The last change thus changed correct UTF8 strings into
Sorry; I updated the document encoding in 2.7 but not 2.6. Fixed in
CVS.
Cheers,
- Graham
_
instrument-notation.ly is tagged as being latin-1 encoded but contains
data in utf8. The last change thus changed correct UTF8 strings into
incorrect ones, caused by opening the file in latin-1 but saving it as
utf-8. See, for example, the quotation marks around the lyrics in
line 797 -- `let my
Hi,
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=280352
Debian developer Jonas Smedegaard is looking for the bugs Lilypond 2.6
and other programs expose in Ghostscript. If I understand correctly, he
needs these as arguments for a non-maintainer upload of a newer gs-gpl
package to the
t;" in the header.
Ok.
Would it be useful to document some of these bugs in the manual? We've
got a @refbugs command, where we note bugs that aren't likely to be
fixed
soon. In this case, we could have a note at the bottom of the page
break
section with the workaround --
[EMAIL PROTECTED] writes:
> It seems to me this system could work very well for Lilypond, perhaps
> better in many ways than the mailing lists/CVS. For what it's worth, Trac
> integrates with Subversion, which though it'd be a change from CVS, has
> some neat features from what I hear. Trac also in
Hi,
I wonder if Trac (http://www.edgewall.com/trac/) might be a useful system
with which to submit and track bugs, enhancements, feature requests, and
changes to Lilypond, and/or to the Lilypond documentation. I don't know
enough about the current CVS system to know how well that works, but
[EMAIL PROTECTED] writes:
> I'm seeing two bugs in the chord symbols generated by 2.5.11 and
> earlier 2.5 releases (back to when the default backend was switched to
> ps):
>
> - the :maj7 symbol does not get printed with the ps backend and is
> vastly oversized with
[EMAIL PROTECTED] writes:
> I'm seeing two bugs in the chord symbols generated by 2.5.11 and
> earlier 2.5 releases (back to when the default backend was switched to
> ps):
>
> - the :maj7 symbol does not get printed with the ps backend and is
> vastly oversized w
> IIRC, the problem is that mftrace reads system installed AFMs,
> (eg. from a 2.4 release in /usr) using kpsewhich, extracting foundry
> and font name from there. I believe I fixed that bug some time ago.
> What version of mftrace do you run?
I use version 1.1.1 -- anyway, the problem is gone n
[EMAIL PROTECTED] writes:
>
> Currently, we have the funny situation that the DVI output of a
> LilyPond document created with `-b tex' can be viewed with xdvi (using PS
> fonts) but the result of dvips doesn't work at all, inspite of
> correctly loading all fonts.
>
> Reason is that lilypond.map
1 - 100 of 178 matches
Mail list logo
