Re: Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil

[Han-Wen Nienhuys]

2008/5/30 Mats Bengtsson <[EMAIL PROTECTED]>:

>
> It cannot be that simple, since there are no font related settings on
> TimeSignature in
> scm/define-grobs.scm and the font related settings are done within
> ly:time-signature::print
> which ins't used here.

There 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

Re: appoggiatura at beginning fouls clef

[Mats Bengtsson]

Quoting David Bobroff <[EMAIL PROTECTED]>:


> I'm not top posting.

I tried a search to see if this has been reported and did not find a 
report about this.


The following example shows the problem.  When the clef is given in 
the score block as simultaneous with the predefined music the 
appoggiatura causes the default clef (treble) to print before the 
indicated clef (in this case, "F").  It is possible to work around 
this by putting the clef in the music definition but this limits the 
flexibility of using the music in different transpositions/clefs 
without resorting to re-editing the music definition for each 
transposition/clef.



Not at all! In your example, just do \context Staff {
   \clef "F"
   \music
   }
instead of \context Staff <<
   \clef "F"
   \music
   >>


   /Mats



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 541 in lilypond: Hebrew lyrics diacritic not well aligned

[codesite-noreply]

Issue 541: Hebrew lyrics diacritic not well aligned
http://code.google.com/p/lilypond/issues/detail?id=541

Comment #7 by yotam.medini:
In a chat I had with Han-Wen, I said I will explain in more details
the 8 PDFs result I submitted on April 15.

Attached is an image as xpdf renders the 8 pdfs (inside nik2han2.tgz):
 [EMAIL PROTECTED]:541:84> stat -c "%s %x %n" *.pdf
 14375 2008-05-31 21:31:24.0 +0300 nikud-aharoni-neg.pdf
 14373 2008-05-31 21:31:26.0 +0300 nikud-aharoni-orig.pdf
 66506 2008-05-31 21:31:30.0 +0300 nikud-century-neg.pdf
 66503 2008-05-31 21:31:29.0 +0300 nikud-century-orig.pdf
 66507 2008-05-31 21:31:30.0 +0300 nikud-default-neg.pdf
 66503 2008-05-31 21:31:30.0 +0300 nikud-default-orig.pdf
 66506 2008-05-31 21:31:32.0 +0300 nikud-frank-neg.pdf
 66503 2008-05-31 21:31:31.0 +0300 nikud-frank-orig.pdf

The '-neg' variants fixes the diacritic mark positions
in the {'default','century','frank'} cases, but not in the 'aharoni' case.

In all cases we have 6 lines of one Hebrew syllable in each.

1. Letter 'Kaf' with the 'Patah' mark below it is like a lower-underline.
  It should be positioned in the middle below the character.
  Badly shifted to the right in {'default-orig', 'century-orig', 'frank-orig'},
  Badly shifted to the left in {'aharoni-orig', 'aharoni-neg'},
  Well positioned in {'default-neg','century-neg','frank-neg'}.

2. 2-letters (Bet+Vav), with 'Shuruq' (=~? 'Dagesh') mark (small dot)
  attached to 'Vav'.
  It should be positioned slightly left of the 'Vav' (vertical line),
  with a tiny space.
  {'default-orig','default-neg'} has the dot too close.
  {'default-orig','default-neg','aharoni-orig'} has the dot too close.
  {'aharoni-neg} has the dot too far.
  {'century-orig','century-neg','frank-orig','frank-neg'}' has it OK.

3. Letter 'He' with 'Patah'  mark below it is like a lower-underline.
  It should be positioned in the middle below the character.
  Badly shifted to the left in {'aharoni-orig', 'aharoni-neg'}
  It is well positioned in the other 6 cases.

4  2-letters (Aleph+Vav) with 'Holam' mark (upper dot).
  It should be position above the Vav, makes it look like lower-case 'i'.
  I believe it is also OK to have it slightly to the left.
  So it may be acceptable in all cases.

5. 3-letters, I did not put any diacritic mark there.

6. Letter Vav with Patah mark. Again, it is like a lower-underline.
  It should be positioned in the middle below the character.
  Similar results as with the 1st line, namely:
  Badly shifted to the right in {'default-orig', 'century-orig', 'frank-orig'},
  Badly shifted to the left in {'aharoni-orig', 'aharoni-neg'},
  Well positioned in {'default-neg','century-neg','frank-neg'}.

One significant point Han-Wen said was:
 hanwenn: We should probably use the higher level library to do this
  positioning, but I haven't got time to look into that unfortunately.

-- yotam


Attachments:
x8pdf.jpeg  49.3 KB
nik2han2.tgz  340 KB



--
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