Nicolas Sceaux <[EMAIL PROTECTED]> writes:
> "Valentin Villenave" <[EMAIL PROTECTED]> writes:
>
>> %{
>> Greetings,
>>
>> The \smallCaps command, as described in the Manual (12.3.4),
>> uses a fixed \translate argument. Generally it's fine, but in some
>> cases it produces an ugly result.
On 29 Sep 2007, at 23:48, Graham Percival wrote:
Thanks, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=486
Thank you. Looks fine to me.
Hans Åberg
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.
Thanks, this has been added as
http://code.google.com/p/lilypond/issues/detail?id=486
Cheers,
- Graham
Hans Aberg wrote:
This bug depends on a problem with the font Verdana. If, in the example
below, one replaces the line starting with "\new ChordNames" with say
\new ChordNames \with { \over
Issue 486: chord fonts in OSX
http://code.google.com/p/lilypond/issues/detail?id=486
Comment #1 by gpermus:
Another comment from Hans:
This bug depends on a problem with the font Verdana. If, in the example below,
one
replaces the line starting with "\new ChordNames" with say
\new ChordNames \w
Issue 486: chord fonts in OSX
http://code.google.com/p/lilypond/issues/detail?id=486
New issue report by gpermus:
Hans Aberg writes:
When I run the following example, from the LilyPond 2.11.33 User Manual,
sec. 7.2.1, p. 117 (PDF p. 126):
twoWays = \transpose c c' {
\chordmode {
c1 f:sus4 bes/f
}
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 by any means
Issue 485: please make #(ly:export(lilypond-version) safe
http://code.google.com/p/lilypond/issues/detail?id=485
New issue report by gpermus:
It would be nice if there was a "safe" (ie lilypond -dsafe) command that
did #(ly:export(lilypond-version). This would reduce the number of false
positives
2007/9/29, Valentin Villenave <[EMAIL PROTECTED]>:
> I've sent a related e-mail on -user, so if you have a few minutes
> you'll see what I need this feature for.
Nicolas: Oops, I've just realised I forgot to Cc you my mail on -user,
so here's the link:
http://lists.gnu.org/archive/html/lilypond-us
Nicolas Sceaux wrote:
"Valentin Villenave" <[EMAIL PROTECTED]> writes:
%{
Greetings,
The \smallCaps command, as described in the Manual (12.3.4),
uses a fixed \translate argument. Generally it's fine, but in some
cases it produces an ugly result.
%}
\markup \fill-line { \concat { "Foo
2007/9/29, Nicolas Sceaux <[EMAIL PROTECTED]>:
> I'm taking this one.
Great! Thank you very much.
I've sent a related e-mail on -user, so if you have a few minutes
you'll see what I need this feature for.
Regards,
Valentin
___
bug-lilypond mailing l
"Valentin Villenave" <[EMAIL PROTECTED]> writes:
> %{
> Greetings,
>
> The \smallCaps command, as described in the Manual (12.3.4),
> uses a fixed \translate argument. Generally it's fine, but in some
> cases it produces an ugly result.
> %}
>
> \markup \fill-line { \concat { "Foo Foo" "ba
On 29 Sep 2007, at 04:25, Brett Duncan wrote:
[Please cc the mailing list, so that others may help.]
This bug depends on a problem with the font Verdana. If, in the
example below, one replaces the line starting with "\new
ChordNames" with say
\new ChordNames \with { \override ChordName #'f
%{
Greetings,
The \smallCaps command, as described in the Manual (12.3.4),
uses a fixed \translate argument. Generally it's fine, but in some
cases it produces an ugly result.
%}
\markup \fill-line { \concat { "Foo Foo" "bar" }}
\markup \fill-line { \concat { \smallCaps "Foo Foo" "bar" }}
13 matches
Mail list logo
