Duration dots misplaced with multiple voices
> I'm not top posting
This looks like a bug to me...
The duration dots seem to be getting misplaced with multiple voices. In the
first example it's confusing as to whether the dot belongs to the f of the
second voice or the lower e of the first. In the second example where the note
head is on a ledger line, the dot on the upper e in the second voice has moved
downward, and appears to belong to the c in the second voice.
I don't know enough to be able to work around this one. I tried separating out
the voices further but it didn't help.
Thanks for all the great work on lilypond, I'm thoroughly enjoying learning and
using it.
Regards,
Gerard
\version "2.11.60"
bug = << { 2 4 } \\ 2. >>
\relative c' \bug
{ \clef bass \bug }
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Duration dots misplaced with multiple voices
2008/9/28 Gerard Neil <[EMAIL PROTECTED]>:
> The duration dots seem to be getting misplaced with multiple voices. In the
> first example it's confusing as to whether the dot belongs to the f of the
> second voice or the lower e of the first. In the second example where the note
> head is on a ledger line, the dot on the upper e in the second voice has moved
> downward, and appears to belong to the c in the second voice.
Thanks for the report. I'm not sure what should be the correct way to
print it; would you have a scanned example of a real-world similar
situation?
> I don't know enough to be able to work around this one. I tried separating out
> the voices further but it didn't help.
Of course, the obvious workaround is to invert the voices:
bug = << { \voiceTwo 2 4 } \\ \voiceOne 2. >>
\relative c' \bug
{ \clef bass \bug }
> Thanks for all the great work on lilypond, I'm thoroughly enjoying learning
> and
> using it.
Well, happy learning and good luck with Lilypond!
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 429 in lilypond: new accidental style: teaching
Issue 429: new accidental style: teaching http://code.google.com/p/lilypond/issues/detail?id=429 Comment #2 by v.villenave: Greetings, I have proposed a patch on the -devel list. Issue attribute updates: Status: Started -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this 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
Re: markup override font selection not carried out
Han-Wen Nienhuys gmail.com> writes:
>
> On Sat, Sep 27, 2008 at 8:56 AM, Didi Kanjahn gmx.net> wrote:
> > The font in the override is not used to render the text, but a default
> > font instead.
> > This worked fine in 2.6.5
>
> > es'2^\markup { \override #'(font-name . ".Mondulkiri A") \fontsize #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
1. Sorry, the site was kept by a friend and something obviously went wrong. Yes,
I created this font. I can email the font(s) if need be.
2. The period is to ensure the fonts come at the top of font lists, making them
easy to find for people who are not used to the Latin/Roman/English alphabet and
it's order. It's a rather useful method.
3. Indeed the same font named 'Khmer Mondulkiri A' (as it should be for the rest
of the world) instead of '.Mondulkiri A' produces the desired result.
4. The font with the period still worked as intended in Lilypond 2.10.33
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: markup override font selection not carried out
Mats Bengtsson ee.kth.se> writes: > > The dot in ".Mondulkiri A" looks a bit strange. Also, you have to check > if this is a font that LilyPond finds on your system. See > http://kainhofer.com/~lilypond/Documentation/user/lilypond/Single-entry-fonts.html#Single-entry-fonts > for information on how to list all available fonts. > > Mats Yes, the font does appear in the listing of the command 'lilypond -dshow-available-fonts x' I have written a few more things in my 'followup' of Han-Wen Nienhuys' answer. What is good practice and most helpful: repeat these things or answering to all comments in the last answer? Didi ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug in Unicode rendering
Han-Wen Nienhuys gmail.com> writes: > > Hey, > > On Sat, Sep 27, 2008 at 8:12 AM, Didi Kanjahn gmx.net> wrote: > > I am creating a hymnbook in Khmer/Cambodian. > > I am currently using legacy fonts with all associated problems. > > I would like to use real unicode, but the rendering of lilypond is not > > quite 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)? > The rendering is done with Pango? I'm using Windows XP. What happens there? The rendering under Windows is fine in all other programs. The font is my own, I can mail it on request. Didi ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug in Unicode rendering
Mats Bengtsson ee.kth.se> writes: > > Quoting Didi Kanjahn gmx.net>: > > > \version "2.6.5" > > Do you really use such an old version of LilyPond. My first > recommendation is to upgrade to the latest 2.10 or 2.11 (development > but soon to be the next stable) version. > >/Mats > Sorry, I was careless in the post. I actually used version 2.10.33 under Windows XP for that ly-file. Didi ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Appoggiatura adds hyphen to lyrics
%%
%% If there is an appoggiatura at the beginning of a new line,
%% the lyrics will get an extra hyphen before the first syllable.
%%
%% (Of course it happens only if there's a centered hyphen between the
%% syllables, but normally that should not add a hyphen at the
%% beginning of a line, see measure 3 in the example below.)
%%
%% I wrote an example with two staves, in order to show that
%% the appoggiatura influences other staves, too.
%%
%% Using \acciaccatura instead of \appoggiatura produces the same bug.
%%
\version "2.11.60"
\paper{ ragged-right=##t }
<<
\context StaffGroup
<<
\new Staff{
g'2 g' | \break
\appoggiatura f'8 g'2 g'2 | \break
g'2 g' |
}
\addlyrics{ \lyricmode{ bla -- bla -- bla -- bla -- bla -- bla }}
\new Staff{
g'2 g'2 |
g'2 g'2 |
g'2 g'2 |
}
\addlyrics{ \lyricmode{ bla -- bla -- bla -- bla -- bla -- bla }}
>>
>>
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Duration dots misplaced with multiple voices
Valentin Villenave gmail.com> writes: > Thanks for the report. I'm not sure what should be the correct way to > print it; would you have a scanned example of a real-world similar > situation? Sorry, it's taken from my own work. My thinking was that the dots should appear between the notes of the separate voices, and not after all the voices... but probably there's no bug, just a lack of knowlege on my part. > Of course, the obvious workaround is to invert the voices: Good idea. I wish I'd thought of that. Thanks for your reply, Gerard ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 429 in lilypond: new accidental style: teaching
Issue 429: new accidental style: teaching http://code.google.com/p/lilypond/issues/detail?id=429 Comment #3 by v.villenave: ... Aaand applied (thanks to Neil). This should appear in the next development (and stable) version. Issue attribute updates: Status: Fixed Labels: fixed_2_11_61 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this 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
Strict grace spacing is (still) broken
Hello,
Allegedly this bug has been fixed:
http://code.google.com/p/lilypond/issues/detail?id=577
But the output still doesn't look good to me.
I don't want to offend anybody, please tell me if I am wrong.
Oh, I am using LilyPond on a Windows XP.
Zoltan
%% Lilypond code %%
\version "2.11.60"
\paper{ ragged-right=##f }
<<
\override Score.SpacingSpanner #'strict-grace-spacing = ##t
\new Staff {
c'4
\afterGrace
c'4
{ c'16[ c'8 c'16] }
c'4
}
\new Staff {
c'16[ c'16 c'16 c'16]
c'16[ c'16 c'16 c'16]
c'4
}
>>
%%%
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 429 in lilypond: new accidental style: teaching
2008/9/28 <[EMAIL PROTECTED]>: > Issue 429: new accidental style: teaching > http://code.google.com/p/lilypond/issues/detail?id=429 Greetings, One year ago you requested a new feature in LilyPond (the 'teaching accidental style, that prints cautionary accidentals accordingly to the key signature); this feature has been implemented and will be available in the next development release. Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strict grace spacing is (still) broken
2008/9/28 Zoltan Selyem <[EMAIL PROTECTED]>: > http://code.google.com/p/lilypond/issues/detail?id=577 > > But the output still doesn't look good to me. > I don't want to offend anybody, please tell me if I am wrong. What makes it look bad to you? If i remember correctly, the bug was that it caused the sixteenth notes to be irregularly spaced, and now they're not... Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 688 in lilypond: grace notes may add an hyphen at the beginning of a lyric line
Issue 688: grace notes may add an hyphen at the beginning of a lyric line
http://code.google.com/p/lilypond/issues/detail?id=688
New issue report by v.villenave:
%% If there is an appoggiatura at the beginning of a new line,
%% the lyrics will get an extra hyphen before the first syllable.
%% The appoggiatura influences other staves, too.
\version "2.11.60"
<<
\new Staff{
g'2 g' | \break
\appoggiatura f'8 g'2 g'2 | \break
g'2 g' |
}
\addlyrics{ \lyricmode{ bla -- bla -- bla -- bla -- bla -- bla }}
\new Staff{
g'2 g'2 |
g'2 g'2 |
g'2 g'2 |
}
\addlyrics{ \lyricmode{ bla -- bla -- bla -- bla -- bla -- bla }}
Attachments:
appoggiatura-lyrics.png 3.2 KB
Issue attributes:
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this 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
Re: Appoggiatura adds hyphen to lyrics
2008/9/28 Zoltan Selyem <[EMAIL PROTECTED]>: > %% If there is an appoggiatura at the beginning of a new line, > %% the lyrics will get an extra hyphen before the first syllable. Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=688 (doesn't look so bad to me, though) Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: markup override font selection not carried out
On Sun, Sep 28, 2008 at 7:51 AM, Didi Kanjahn <[EMAIL PROTECTED]> wrote: > 3. Indeed the same font named 'Khmer Mondulkiri A' (as it should be for the > rest > of the world) instead of '.Mondulkiri A' produces the desired result. > > 4. The font with 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-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug in Unicode rendering
On Sun, Sep 28, 2008 at 8:34 AM, Didi Kanjahn <[EMAIL PROTECTED]> wrote: >> 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)? >> > > > The rendering is done with Pango? I'm using Windows XP. What happens there? It should use the same mechanism on Linux. > The font is my own, I can mail it on request. Can you open a bug tracker issue and attach the font? Truth be said: I tried fixing a hebrew rendering issue some time ago, 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
Re: Bug in Unicode rendering
2008/9/28 Han-Wen Nienhuys <[EMAIL PROTECTED]>: > Can you open a bug tracker issue and attach the font? Didi: or you can send me privately the .ly sample and the font, and I'll open an issue for you. Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strict grace spacing is (still) broken
On Sun, 28 Sep 2008 16:24:21 +0200 "Valentin Villenave" <[EMAIL PROTECTED]> wrote: > 2008/9/28 Zoltan Selyem <[EMAIL PROTECTED]>: > > > http://code.google.com/p/lilypond/issues/detail?id=577 > > > > But the output still doesn't look good to me. > > I don't want to offend anybody, please tell me if I am wrong. > > What makes it look bad to you? If i remember correctly, the bug was > that it caused the sixteenth notes to be irregularly spaced, and now > they're not... There should be no "if I remember", because you added a .png showing the bug when you added the initial report. Right? Right? Always assume that the bug won't be fixed for over a year and so you won't be able to remember anything. In fact, assume that the bug won't be fixed while you're still in charge of bugs -- write the report such that it's obvious 1) what the problem is 2) if the current output matches the problem output. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strict grace spacing is (still) broken
On Sun, 28 Sep 2008, Valentin Villenave wrote: http://code.google.com/p/lilypond/issues/detail?id=577 What makes it look bad to you? In the Notation Reference (section 1.2.6.1 Grace notes) it says that "Grace notes may be forced to align with regular notes in other staves". But if ragged-right is set to false, the grace notes are not aligned with any other notes... However, in Appendix B (B.13 Layout properties) the following is written about strict-grace-spacing: "If set, grace notes are not spaced separately, but put before musical columns." I'm not sure about the meaning of a "musical column", and by now I'm a bit confused about this strict-grace-spacing thing. I would assume that "putting grace notes _on_ musical columns" means that they should be aligned with other notes. Putting them _before_ musical columns might be what the latest version does. Maybe the current output is ok, maybe this is the intended behaviour. But in that case I don't understand the sentence in 1.2.6.1: "...to align with regular notes". Bye, Zoltan ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strict grace spacing is (still) broken
On Sun, Sep 28, 2008 at 6:17 PM, Zoltan Selyem <[EMAIL PROTECTED]> wrote: > However, in Appendix B (B.13 Layout properties) the following is > written about strict-grace-spacing: > "If set, grace notes are not spaced separately, but put before > musical columns." > > I'm not sure about the meaning of a "musical column", and The description of the property is incorrect. A musical columnt is the X-position corresponding to a point in time; clefs and time signature are on 'command columns' , notes on 'musical columns'. Each point time (including separate grace notes) has its own musical and command columns. strict-grace-spacing makes the musical columns for grace notes 'floating', ie. discoupled from the non-grace notes: first the normal notes are spaced, then the (musical columns of the) graces are put left of the musical columns for the main notes. Can someone update the documentation? thanks! > by now I'm a bit confused about this strict-grace-spacing thing. > I would assume that "putting grace notes _on_ musical columns" > means that they should be aligned with other notes. Putting > them _before_ musical columns might be what the latest version > does. Maybe the current output is ok, maybe this is the intended > behaviour. But in that case I don't understand the sentence in > 1.2.6.1: "...to align with regular notes". > > > 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
