Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap
Comment #19 on issue 2146 by philehol...@gmail.com: Error: Illegal entry in bfrange block in ToUnicode CMap http://code.google.com/p/lilypond/issues/detail?id=2146 I think a further action that's needed is to include working NCSB font files with the LilyPond Ubuntu distro. AFAICS neither of the Ubuntu machines I use has an NCSB font file that correctly renders Cyrillic characters. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2218 in lilypond: Web: Added Concert to Introduction.itexi
Updates: Status: Verified Comment #3 on issue 2218 by philehol...@gmail.com: Web: Added Concert to Introduction.itexi http://code.google.com/p/lilypond/issues/detail?id=2218 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2215 in lilypond: lost commits jan 7
Updates: Status: Verified Comment #8 on issue 2215 by philehol...@gmail.com: lost commits jan 7 http://code.google.com/p/lilypond/issues/detail?id=2215 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2213 in lilypond: Update documentation for \footnotes in Notation Reference
Updates: Status: Verified Comment #8 on issue 2213 by philehol...@gmail.com: Update documentation for \footnotes in Notation Reference http://code.google.com/p/lilypond/issues/detail?id=2213 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2205 in lilypond: Breathing sign is positioned incorrectly after changing Staff or TabStaff size
Updates: Status: Verified Comment #6 on issue 2205 by philehol...@gmail.com: Breathing sign is positioned incorrectly after changing Staff or TabStaff size http://code.google.com/p/lilypond/issues/detail?id=2205 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2204 in lilypond: Patch: Gets rid of PostScript in bar-chords-notation-for-guitar--with-text-spanner.ly
Updates: Status: Verified Comment #5 on issue 2204 by philehol...@gmail.com: Patch: Gets rid of PostScript in bar-chords-notation-for-guitar--with-text-spanner.ly http://code.google.com/p/lilypond/issues/detail?id=2204 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2193 in lilypond: collision between beams and flags
Updates: Status: Verified Comment #21 on issue 2193 by philehol...@gmail.com: collision between beams and flags http://code.google.com/p/lilypond/issues/detail?id=2193 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Strange spacing
The example below produces a quite strange spacing in measure 2, the
second note should be placed nearer to the first note.
When I remove bar on the spacing is o.k.
Thomas
\version 2.15.26
upper = \relative c'' {
\voiceOne
\repeat unfold 8 {c32 c c c} |
c4 c2 c4
}
lower = \relative c'' {
\voiceTwo
s1
a2 a
}
\score
{
\upper
\\
\lower
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
Thomas,
On 23 January 2012 09:54, Thomas Scharkowski t.scharkow...@t-online.de wrote:
The example below produces a quite strange spacing in measure 2, the second
note should be placed nearer to the first note.
When I remove bar on the spacing is o.k.
Thomas
\version 2.15.26
upper = \relative c'' {
\voiceOne
\repeat unfold 8 {c32 c c c} |
c4 c2 c4
}
lower = \relative c'' {
\voiceTwo
s1
a2 a
}
\score
{
\upper
\\
\lower
}
You're going to have to provide a screenshot.
I am using 2.14.2 and I get the following spacing in the 'second' bar
regardless if I have the first bar or not.
--
--
James
attachment: Capture.JPG___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
2012/1/23 Thomas Scharkowski t.scharkow...@t-online.de:
The example below produces a quite strange spacing in measure 2, the second
note should be placed nearer to the first note.
When I remove bar on the spacing is o.k.
This example shows that the voice thinks she is alone.
sOne = { b4 b2 b4 }
sTwo = { b4 b b b }
\score
{
\new Staff { \sOne }
}
\score
{ \new Staff { \sOne }
\new Staff { \sTwo }
}
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
attachment: document.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap
Comment #20 on issue 2146 by lemzw...@gmail.com: Error: Illegal entry in bfrange block in ToUnicode CMap http://code.google.com/p/lilypond/issues/detail?id=2146 This sounds reasonable. Since the URW fonts are GPLed, I don't see a problem here. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
You're going to have to provide a screenshot. Yes, here it is. Thomas attachment: strange_spacing.png___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
On 23 January 2012 12:06, James pkx1...@gmail.com wrote:
Yes that is what I have but the first bar seems to have nothing to do
with anything - at least as far as I can see.
It looks like the first bar's shortest-duration-space carries over
into the first beat of the second, messing up the spacing. This looks
better in my opinion:
\version 2.15.26
upper = \relative c'' {
\voiceOne
\repeat unfold 8 {c32 c c c} |
\newSpacingSection
c4 c2 c4
}
lower = \relative c'' {
\voiceTwo
s1
a2 a
}
\score
{
\upper
\\
\lower
}
Cheers,
Neil
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
Hello,
On 23 January 2012 12:10, Neil Puttock n.putt...@gmail.com wrote:
On 23 January 2012 12:06, James pkx1...@gmail.com wrote:
Yes that is what I have but the first bar seems to have nothing to do
with anything - at least as far as I can see.
It looks like the first bar's shortest-duration-space carries over
into the first beat of the second, messing up the spacing. This looks
better in my opinion:
\version 2.15.26
upper = \relative c'' {
\voiceOne
\repeat unfold 8 {c32 c c c} |
\newSpacingSection
c4 c2 c4
}
lower = \relative c'' {
\voiceTwo
s1
a2 a
}
\score
{
\upper
\\
\lower
}
Blimey, that's subtle (see attached)
Bottom image is with Neil's suggestion of
\newSpacingSection
Sorry Thomas, I take it back.
--
--
James
attachment: Capture1.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
Yes that is what I have but the first bar seems to have nothing to do with anything - at least as far as I can see. Also, you seem to imply that this output is different in earlier versions or are you not implying that at all? I have did not imply this - did not test it with previous versions. I cannot see what the issue is here, the notes in both voices are correctly aligned according to their length in the measure. No. I have a attached a png without bar one - correct spacing. Compare it to the the first png I sent. Thomas attachment: strange_spacing.png___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
Hello,
On 23 January 2012 12:10, Neil Puttockn.putt...@gmail.com wrote:
On 23 January 2012 12:06, Jamespkx1...@gmail.com wrote:
Yes that is what I have but the first bar seems to have nothing to do
with anything - at least as far as I can see.
It looks like the first bar's shortest-duration-space carries over
into the first beat of the second, messing up the spacing. This looks
better in my opinion:
\version 2.15.26
upper = \relative c'' {
\voiceOne
\repeat unfold 8 {c32 c c c} |
\newSpacingSection
c4 c2 c4
}
lower = \relative c'' {
\voiceTwo
s1
a2 a
}
\score
{
\upper
\\
\lower
}
Blimey, that's subtle (see attached)
Bottom image is with Neil's suggestion of
\newSpacingSection
Sorry Thomas, I take it back.
Thank you.
Neil's workaround should not be necessary - this is a bug, isn't it?
Thomas
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
Thomas Scharkowski t.scharkow...@t-online.de writes: Thank you. Neil's workaround should not be necessary - this is a bug, isn't it? Personally, I consider glaringly dissimilar spacing in adjacent bars more of a bug than the other way round. If there were a line break in between, this might be different, but stepping on the brakes for your eye movement like that does not seem healthy to me. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
Thomas Scharkowskit.scharkow...@t-online.de writes: Thank you. Neil's workaround should not be necessary - this is a bug, isn't it? Personally, I consider glaringly dissimilar spacing in adjacent bars more of a bug than the other way round. If there were a line break in between, this might be different, but stepping on the brakes for your eye movement like that does not seem healthy to me. I understand your point and agree, but I still think the distance 1st note - 2nd note should be smaller than the distance 2nd to 3rd note (in my first example). This simply looks wrong to me. I do attach an excerpt of my real world example, without \newSpacingSection. Thomas attachment: K356-strange_spacing.png___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
I do attach an excerpt of my real world example, without \newSpacingSection. This is *definitely* a bug. Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
Thomas Scharkowski t.scharkow...@t-online.de writes: Thomas Scharkowskit.scharkow...@t-online.de writes: Thank you. Neil's workaround should not be necessary - this is a bug, isn't it? Personally, I consider glaringly dissimilar spacing in adjacent bars more of a bug than the other way round. If there were a line break in between, this might be different, but stepping on the brakes for your eye movement like that does not seem healthy to me. I understand your point and agree, but I still think the distance 1st note - 2nd note should be smaller than the distance 2nd to 3rd note (in my first example). This simply looks wrong to me. I do attach an excerpt of my real world example, without \newSpacingSection. I'd say that spacing becomes tight too fast here, not that it starts out too lose. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap
Comment #21 on issue 2146 by julien.r...@gmail.com: Error: Illegal entry in bfrange block in ToUnicode CMap http://code.google.com/p/lilypond/issues/detail?id=2146 My ubuntu install has Cyrillic in the fonts provided by the gsfonts package. Looks like it's a matter of installing or updating that package. $ grep Cyrillic /usr/share/fonts/type1/gsfonts/c059013l.pfb Binary file /usr/share/fonts/type1/gsfonts/c059013l.pfb matches $ apt-file search /usr/share/fonts/type1/gsfonts/c059013l.pfb gsfonts: /usr/share/fonts/type1/gsfonts/c059013l.pfb $ aptitude show gsfonts Package: gsfonts State: installed Automatically installed: no Version: 1:8.11+urwcyr1.0.7~pre44-4.2ubuntu1 Priority: optional Section: text Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Uncompressed Size: 4,878 k Conflicts: gs ( 5.50-5), gs-aladdin ( 6.50-4), gsfonts-x11 ( 0.13) Description: Fonts for the Ghostscript interpreter(s) These are free look-alike fonts of the Adobe PostScript fonts. Recommended for all flavors of Ghostscript (gs-gpl, gs-afpl and gs-esp). Homepage: http://www.ghostscript.com/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap
Comment #22 on issue 2146 by philehol...@gmail.com: Error: Illegal entry in bfrange block in ToUnicode CMap http://code.google.com/p/lilypond/issues/detail?id=2146 Sounds like the best option is to check the correct fonts are installed during configur? It will also mean that the GUB build machines will need updating, since the lack of Cyrillic output in the NR (see NR 2.14 page 441) shows that it doesn't have the correct fonts. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap
Comment #23 on issue 2146 by pkx1...@gmail.com: Error: Illegal entry in bfrange block in ToUnicode CMap http://code.google.com/p/lilypond/issues/detail?id=2146 ..and lilydev.. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap
Comment #24 on issue 2146 by philehol...@gmail.com: Error: Illegal entry in bfrange block in ToUnicode CMap http://code.google.com/p/lilypond/issues/detail?id=2146 See comment 19. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2239 in lilypond: google code only returns 20 or 25 comments with API
Updates: Status: Started Owner: julien.r...@gmail.com Comment #3 on issue 2239 by julien.r...@gmail.com: google code only returns 20 or 25 comments with API http://code.google.com/p/lilypond/issues/detail?id=2239 https://github.com/gperciva/lilypond-extra/pull/9 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax
Comment #30 on issue 1110 by d...@gnu.org: Wrong octave of repetition chord
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
Now since issue 2240 aka 2270 is on the countdown, it makes some sense to
think about this one again. We now have the situation that EventChord is a
satisfactorily reliable indicator of an actual chord.
I see two ways to deal with this issue now.
a) have q work in the parser (as it does now), let \relative completely
reconsider the relation between q and its preceding chord. This is
actually pretty ugly.
b) have q never record any pitches (it won't be fazed by \relative then).
Instead, the iterator for the repeated chord fills in the pitches. The
question is just where it gets them from. It can't bother the EventChord
iterator for that since in the case of { c c d e } q the
event-chord-iterator is called later than the corresponding repeated chord
iterator. Basically we need to comb through the whole expression that is
going to be iterated, and fill in the repeated chords.
\relative does its respective work on demand. How can we avoid unnecessary
work? Do it on demand as well?
\repeatChords \relative c' { c c d e } q
Then the user would be responsible not to apply \relative after
\repeatChords...
That would be a very straightforward solution without extra cost if you did
not actually use the feature. Normally it would be sufficient to put the
contents of your \score into a single \repeatChords. I doubt that this
will make people happy...
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running
Comment #6 on issue 2223 by julien.r...@gmail.com: Regtest for lilypond-book are not running http://code.google.com/p/lilypond/issues/detail?id=2223 A couple of fixes pushed directly to staging as a24772e986386801a35cc49eea9971cdabc93bc4 The rest with come in a patch soon. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2222 in lilypond: lilypond-book fails with html input
Updates: Status: Fixed Labels: -Patch-push Fixed_2_15_27 Comment #9 on issue by julien.r...@gmail.com: lilypond-book fails with html input http://code.google.com/p/lilypond/issues/detail?id= pusehd as b906f1aeb7ed444f58d082b7bc382efc0ec57fc7 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2239 in lilypond: google code only returns 20 or 25 comments with API
Updates: Status: Fixed Comment #4 on issue 2239 by julien.r...@gmail.com: google code only returns 20 or 25 comments with API http://code.google.com/p/lilypond/issues/detail?id=2239 To those using patchy, do a git pull to update your local copy. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running
Updates: Labels: Patch-new Comment #7 on issue 2223 by julien.r...@gmail.com: Regtest for lilypond-book are not running http://code.google.com/p/lilypond/issues/detail?id=2223#c7 Run regression tests for lilypond-book (issue 2223). Re-enable running the regtests in input/regression/lilypond-book. Fix various typos, clarify what each input file tests for and how the output should look, and fix the following problems: collated-files.tely: Was linking to the input files rather than the output files generated by lilypond-book. The input files were thus not tested individually as it should but as included files. Fixed in the local GNUmakefile by an explicit rule for collated-files.list which tracks the output files. suffix-texi: Failed, was not being preprocessed by lilypond-book but simply copied to the output folder. Fixed in the local GNUmakefile by adding a specific make rule for it. tex-twocolumn: Failed, image had full-page width. Fixed in the input file by moving \twocolumn to the preamble. Column width detection in the body of the tex document is not yet implemented. texinfo-language-detection: Suspicious, had a weird @lydoctitle popping up. Fixed in the input file by defining the @lydoctitle macro. http://codereview.appspot.com/5569045 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running
Updates: Labels: -Patch-new Patch-waiting Comment #8 on issue 2223 by julien.r...@gmail.com: Regtest for lilypond-book are not running http://code.google.com/p/lilypond/issues/detail?id=2223 must wait until b906f1aeb7ed444f58d082b7bc382efc0ec57fc7 is in master before testing ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running
Updates: Labels: -Patch-waiting Patch-new Comment #9 on issue 2223 by julien.r...@gmail.com: Regtest for lilypond-book are not running http://code.google.com/p/lilypond/issues/detail?id=2223 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer.
Updates: Status: Verified Labels: -Patch-push Fixed_2_15_27 Comment #22 on issue 2177 by julien.r...@gmail.com: Patch: Reverts public interface for simple spacer. http://code.google.com/p/lilypond/issues/detail?id=2177 Thanks for clarifying the patchy stuff. As to this issue, verified that it's 072d33dbc1f31fafa96c24ac579b1ba4422d2eee ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files
Updates: Status: Verified Comment #14 on issue 2158 by julien.r...@gmail.com: Patch: Sketch of not remaking html files http://code.google.com/p/lilypond/issues/detail?id=2158 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2028 in lilypond: Make doc always recreates HTML files
Updates: Status: Verified Comment #7 on issue 2028 by julien.r...@gmail.com: Make doc always recreates HTML files http://code.google.com/p/lilypond/issues/detail?id=2028 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9)
Updates: Status: Verified Comment #9 on issue 2127 by julien.r...@gmail.com: Patch: Directs output of texi2html to log files (GOP 9) http://code.google.com/p/lilypond/issues/detail?id=2127 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1815 in lilypond: lilypond-book fails on Windows
Updates: Status: Verified Owner: julien.r...@gmail.com Comment #35 on issue 1815 by julien.r...@gmail.com: lilypond-book fails on Windows http://code.google.com/p/lilypond/issues/detail?id=1815 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2243 in lilypond: Incorrect subdivision of beams
Comment #1 on issue 2243 by m...@apollinemike.com: Incorrect subdivision of beams http://code.google.com/p/lilypond/issues/detail?id=2243 Tracked this to 44155056614ee1ff6b3bf4f286bdb386147c21a2 via git bisect. Carl - lemme know if you'd like a hand w/ squashing this bug. I have some time later in the week (Thursday-ish). ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange spacing
2012/1/23 David Kastrup d...@gnu.org:
Thomas Scharkowski t.scharkow...@t-online.de writes:
Thomas Scharkowskit.scharkow...@t-online.de writes:
Thank you.
Neil's workaround should not be necessary - this is a bug, isn't it?
Personally, I consider glaringly dissimilar spacing in adjacent bars
more of a bug than the other way round. If there were a line break in
between, this might be different, but stepping on the brakes for your
eye movement like that does not seem healthy to me.
I understand your point and agree, but I still think the distance 1st
note - 2nd note should be smaller than the distance 2nd to 3rd note
(in my first example). This simply looks wrong to me.
I do attach an excerpt of my real world example, without
\newSpacingSection.
I'd say that spacing becomes tight too fast here, not that it starts out
too lose.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
FWIW: if I compile \upper only, the spacing is more convincing.
\version 2.15.24
upper =
\relative c'' {
\voiceOne
\repeat unfold 8 {c32 c c c} |
c4 c2 c4
}
lower = \relative c'' {
\voiceTwo
s1
a2 a
}
\score
{
\upper
\\
\lower
}
\upper
Cheers,
Harm
attachment: atest-08.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax
Comment #31 on issue 1110 by plros...@gmail.com: Wrong octave of repetition
chord with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
I'm not so knowledgeable in Lilypond internals but let me try to understand
the dilemma in simple terms. I want q to emit the same set of pitches as
the last chord did. That must be something closer to the output side
because we want the actual pitches, not the input.
I guess the example with two voices shows the case when the last chord
before q wasn't processed because it happens after q. I'm absolutely
fine with Lilypond showing an error in this case. It's a forward reference.
In my opinion, not supporting q in some corner cases is acceptable.
Producing wrong output silently is not. Writing out a chord is an easy
task for the fingers. Proofreading scores is a costly task for the eyes.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2245 in lilypond: wrong/inconsistent placement of lyrics under suspended notes
Comment #1 on issue 2245 by thomasmo...@gmail.com: wrong/inconsistent placement of lyrics under suspended notes http://code.google.com/p/lilypond/issues/detail?id=2245 As remarked in the threads above the same appears with DynamicText. But not with Script or TextScript. Attached an image wich shows the default and a corrected version, using the function created by David Nalesnik. Cheers, Harm Attachments: atest-09.ly 1.5 KB atest-09.png 12.1 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2245 in lilypond: wrong/inconsistent placement of lyrics and dynamics under suspended notes
Updates: Summary: wrong/inconsistent placement of lyrics and dynamics under suspended notes Comment #2 on issue 2245 by janek.li...@gmail.com: wrong/inconsistent placement of lyrics and dynamics under suspended notes http://code.google.com/p/lilypond/issues/detail?id=2245 nice example, thanks! ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Top Margin Adjustment
On 24 January 2012 00:13, Thomas Wilmot thomas-wil...@hotmail.com wrote: Hello, In any LilyPond score, I always find the top margins to look abnormally small. I have tried to set top-margin, but for some reason, it is ignored. If you replace top-margin by top-margin-default it works. But of course this issue (regression?) is totally valid! I do not understand why many paper settings have been replaced by same-name-default in ‘ly/paper-defaults-init.ly’. Is it for automatic scale depending on paper size? IIRC that does not work for several of them and it is not properly documented in the NR. Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Top Margin Adjustment
On 24 January 2012 00:25, -Eluze elu...@gmail.com wrote: it's not ignored - but after having defined top-margin = 5\cm you override this with #(set-paper-size letter) changing this order will do what you expect! I missed that point. IMHO it is worth mentioning this as a warning in NR 4.1.3 and 4.1.5 (for top-margin, bottom-margin and left-margin, right-margin, inner-margin, outer-margin, binding-offset, indent and short-indent respectively). The difference between modifying these variables and their corresponding top-margin-default, bottom-margin-default, etc. should also be explained there. Thank you in advance. Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9)
Comment #10 on issue 2127 by pkx1...@gmail.com: Patch: Directs output of texi2html to log files (GOP 9) http://code.google.com/p/lilypond/issues/detail?id=2127 not sure one is supposed to verify one's own fixes. Or was this done because its been a longtime since it was fixed? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9)
Comment #11 on issue 2127 by julien.r...@gmail.com: Patch: Directs output of texi2html to log files (GOP 9) http://code.google.com/p/lilypond/issues/detail?id=2127 I verify Phil's fix? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax
Comment #32 on issue 1110 by d...@gnu.org: Wrong octave of repetition chord
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
The dilemma basically is that last chord is not well-defined. \relative
has an order for last pitch that it follows. The parser has an order
for last default duration that it follows. Both are different but
thankfully orthogonal. last chord is not. It gets garbled when
\relative does not know which chords belong together, so it makes sense to
define last chord like \relative does. Unfortunately we don't know when
and whether at all \relative will run on the material, so a \relative-only
answer to the order is not going to fly.
However, time order (like shown with parallel music which is _not_ two
voices) is too different from what LilyPond does elsewhere to make much
sense. It would be very easy to implement.
Is
input/regression/repeat-tremolo-chord-rep.ly
a corner case? We have here
\relative c' {
c e g1
\repeat tremolo 4 q16
\repeat tremolo 4 { q16 }
\repeat tremolo 4 { c16 q16 }
}
Before 2240,we _had_to involve the parser in the last chord concept
because only the parser had the information which EventChord would even
count as a chord. Personally, I think a single run through the whole score
when iteration _starts_ is probably the most useful place. Forcing the
user to be explicit by doing last chord substitution when called with a
command is even more predictable, but inconvenient.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2040 in lilypond: Documentation for unpure-pure-containers
Updates: Labels: Patch-new Comment #2 on issue 2040 by pkx1...@gmail.com: Documentation for unpure-pure-containers http://code.google.com/p/lilypond/issues/detail?id=2040#c2 Doc: NR 5.5.5 Adv tweaks - Unpure-pure containers Tracker issue 2040 Added information about Unpure-pure containers based on information from Mike Solo http://codereview.appspot.com/5569050 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax
Comment #34 on issue 1110 by lemzw...@gmail.com: Wrong octave of repetition
chord with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
For me, the `last chord' is the last ... construct right before a `q'
happens. I don't mind at all if certain things like \transpose or even
\relative between a chord and `q' cause an error.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2040 in lilypond: Documentation for unpure-pure-containers
Comment #3 on issue 2040 by pkx1...@gmail.com: Documentation for unpure-pure-containers http://code.google.com/p/lilypond/issues/detail?id=2040#c3 Doc: NR 5.5.5 Adv tweaks - Unpure-pure containers Tracker issue 2040 Added information about Unpure-pure containers based on information from Mike Solo http://codereview.appspot.com/5569050 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
