Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo

2010-06-07 Thread Neil Puttock
On 7 June 2010 17:15, Phil Holmes wrote: > Here's another (yes - I am working my way through .bugs for likely > outstanding issues.) http://code.google.com/p/lilypond/issues/detail?id=1020 Cheers, Neil ___ lilypond-user mailing list lilypond-user@gnu.

Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo

2010-06-07 Thread Phil Holmes
Here's another (yes - I am working my way through .bugs for likely outstanding issues.) -- -- Phil Holmes "Neil Puttock" wrote in message news:7ca3d5a31002201344p6b1cf23ya0b3a3b83da7c...@mail.gmail.com... On 20 February 2010 18:40, Dmytro O. Redchuk wrote: I can not figure out how to t

Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo

2010-02-23 Thread Dmytro O. Redchuk
У сб, 2010-02-20 у 21:44 +, Neil Puttock пише: > On 20 February 2010 18:40, Dmytro O. Redchuk wrote: > > > I can not figure out how to test ("to understand" for me) this issue > > to choose one of "yes, that's what i'm doing wrong" or "yes, this is a > > bug". > > If it helps, it looks like

Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo

2010-02-20 Thread Neil Puttock
On 20 February 2010 18:40, Dmytro O. Redchuk wrote: > I can not figure out how to test ("to understand" for me) this issue > to choose one of "yes, that's what i'm doing wrong" or "yes, this is a > bug". If it helps, it looks like a bug to me. Cheers, Neil

Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo

2010-02-20 Thread Dmytro O. Redchuk
У сб, 2010-02-20 у 17:03 +, Neil Puttock пише: > On 19 February 2010 15:18, Dmytro O. Redchuk wrote: > > > Sorry. > > > > It DOES NOT. > > > > My fault. MY FAULT. > > > > Again --- i can not understand anything. > > If you use double parentheses, \override does nothing. Your first > overrid

Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo

2010-02-20 Thread Neil Puttock
On 19 February 2010 15:18, Dmytro O. Redchuk wrote: > Sorry. > > It DOES NOT. > > My fault. MY FAULT. > > Again --- i can not understand anything. If you use double parentheses, \override does nothing. Your first override appears to work since NCSB is the default font. Regards, Neil

Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo

2010-02-19 Thread Dmytro O. Redchuk
У пт, 2010-02-19 у 16:58 +0200, Dmytro O. Redchuk пише: > % works good (overrides font-name): > c'' -\markup \override #'((font-name . "New Century Schoolbook")) "good" Sorry. It DOES NOT. My fault. MY FAULT. Again --- i can not understand anything. Well, will test later, i guess. If nobod

Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo

2010-02-19 Thread Dmytro O. Redchuk
У сб, 2010-01-30 у 12:27 +0200, Dmytro O. Redchuk пише: > Hi! Hi again!-) Something to add; please take a look at this snippet: \version "2.13.13" { c'' -"sizes " % % works good (overrides font-name): c'' -\markup \override #'((font-name . "New Century Schoolbook")) "good" % % bad --

Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo

2010-01-30 Thread Dmytro O. Redchuk
Hi! Well... Have i written something wrong?-) I guess here are two options: this *is* the problem, or i have missed something heavily, there is no any problem with overriding font-name in markups. In the latter case --- please don’t mind my bothering you, and let me know what i am doing wrong. T

[2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo

2010-01-27 Thread Dmytro O. Redchuk
Hi! So, overriding font-name in markup increases font-size. To be sure that this is not a problem of different fonts, i've "made pango-font-tree" with a single font, AntiquaPSCyr, which is definitely unique in my system (i mean i have the only copy of this font, in one place, with the only defini

Re: [2.13.11] strange problem with markup in \tempo

2010-01-26 Thread Dmytro O. Redchuk
У вт, 2010-01-26 у 21:05 +0200, Dmytro O. Redchuk пише: > % this one *is* displayed, because it is very different in some way, > % no problem, but why it is larger? > \tempo \markup \setOurTempiFont "Moderato" Probably would be better to mention that this markup: \tempo \markup \override #`(

[2.13.11] strange problem with markup in \tempo

2010-01-26 Thread Dmytro O. Redchuk
Hi, masters! Please, again, i can not find what's wrong. In the snippet below (image attached) the last metronome mark is larger than others --- why? % ---8<-- \version "2.13.11" % ourTempiFont = #"Century Schoolbook L Bold" ourTempiFont = #"New Century Schoolbook Bold"

Re: Problem with \markup

2007-10-30 Thread Graham Percival
Yes, minimal example required. Hints here: http://lilypond.org/web/devel/participating/bugs Cheers, - Graham Mats Bengtsson wrote: This is a clear bug, which is a regression againts version 2.10. I forward it to bug-lilypond. Perhaps Graham finds the example too complicated, so it would be go

Re: Problem with \markup

2007-10-29 Thread Mats Bengtsson
This is a clear bug, which is a regression againts version 2.10. I forward it to bug-lilypond. Perhaps Graham finds the example too complicated, so it would be good if you can reduce it to a minimal example that illustrates the same problem. The problem may be somewhat related to http://code.googl

Problem with \markup

2007-10-29 Thread Till Rettig
Hi, what is happening here? The first bar shows the version that a want, the second then adds some markup text -- and screws the rest totally up! Greetings Till %% %EXAMPLE %% \version "2.11.33" u = { \change Staff = upper \stemDown \slurDown } m = { \change Staff = lower \ste

RE: Problem with \markup { \score } quitting after first measure

2006-09-21 Thread Rick Hansen (aka RickH)
> Trent > > > From: "Rick Hansen (aka RickH)" <[EMAIL PROTECTED]> > To: lilypond-user@gnu.org > Subject: Problem with \markup { \score } quitting after first measure > Date: Wed, 20 Sep 2006 14:36:32 -0700 (PDT) > > > v2.9.17 > > I believe I have u

RE: Problem with \markup { \score } quitting after first measure

2006-09-20 Thread Rick Hansen (aka RickH)
> Trent > > > From: "Rick Hansen (aka RickH)" <[EMAIL PROTECTED]> > To: lilypond-user@gnu.org > Subject: Problem with \markup { \score } quitting after first measure > Date: Wed, 20 Sep 2006 14:36:32 -0700 (PDT) > > > v2.9.17 > > I believe I have un

RE: Problem with \markup { \score } quitting after first measure

2006-09-20 Thread Trent J
ars of the ossia staff will display. Trent From: "Rick Hansen (aka RickH)" <[EMAIL PROTECTED]> To: lilypond-user@gnu.org Subject: Problem with \markup { \score } quitting after first measure Date: Wed, 20 Sep 2006 14:36:32 -0700 (PDT) v2.9.17 I believe I have uncovered a

Problem with \markup { \score } quitting after first measure

2006-09-20 Thread Rick Hansen (aka RickH)
v2.9.17 I believe I have uncovered a bug when using the \markup { \score { ... } } capability. In the following example I assign a markup score of 2 measures to a variable called "varFreeFormOssia". Then in the main music I apply that markup variable to a note. I would expect 2 measures of mar