Right! convert-ly doesn't make any attempt to translate embedded TeX
commands like \copyright. The simple solution is to open the file in your
text editor, insert the character © where you want it (on my computer, I can
get the symbol by pressing Alt gr and "C", but you may have to use some
Charac
I have the following line in lilypond 2.4.2 ..
tagline="Engraved by LilyPond, 2.4.2 { } Copyright \copyright { } 2005 Ian
Stirling, { } Some Rights Reserved
With 2.4.2 the \copyright was printed as the copyright symbol.
I used convert-ly in 2.11.0 to update the file,
but that copyright symbol isn
> > Independently of this, I think it is another error that
> > `head-separation' and `page-top-space' are applied on the first page
> > if a title is present.
>
> You'd rather have to modify the function that computes the first system
> position on page: `first-line-position' in the file
> scm/la
Thank you very much :)
I will inspect the code, but it looks very good so far. We may only need to
add 6 and 7 chords for our needs, but I will have a try on that and if I
don't succeed I will come back ;-)
Regards,
Philip
> -Ursprüngliche Nachricht-
> Von: Johannes Schindelin [mailto:[
Werner LEMBERG escreveu:
>> Can you push this change after adding it to one of the markup
>> regtests?
>
> Done. Shall I prepare an entry for the NEWS file also?
I think the feature is too minor to put in the NEWS file, but if you think
otherwise
--
Han-Wen Nienhuys - [EMAIL PROTECTED]
Hi,
On Wed, 29 Nov 2006, Philip Chinery wrote:
> > Have you tried \germanChords?
>
> Yes, I have, but it only changes B to H and such things, but our Goal ist to
> display "Am" as "a" while "A" remains "A".
Correct. And you cannot just override chordRootNamer, since that function
is only passe
Erik,
I think it was you who've changed the tuplet implementation. Please
look at this regression report:
http://code.google.com/p/lilypond/issues/detail?id=159
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu
> > I suggest the patch at the end of this email to get properly
> > scaled fractions. The two images demonstrate this, using the
> > input below. Note that the correct command to position the plus
> > sign is \translate-scaled; this is something which should probably
> > be added to the documen
> Can you push this change after adding it to one of the markup
> regtests?
Done. Shall I prepare an entry for the NEWS file also?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-deve
> Have you tried \germanChords?
Yes, I have, but it only changes B to H and such things, but our Goal ist to
display "Am" as "a" while "A" remains "A".
Regards,
Philip
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailma
Hi,
On Wed, 29 Nov 2006, Philip Chinery wrote:
> We have a problem (or rather an optical preference) with the chord names
> that are deisplayed. Moll chords are displayed like "Am", but we want to
> have it another way (maybe it is a german thing...), to have moll chords
> displayed lowercase. So
Werner LEMBERG escreveu:
> I suggest the patch at the end of this email to get properly scaled
> fractions. The two images demonstrate this, using the input below.
> Note that the correct command to position the plus sign is
> \translate-scaled; this is something which should probably be added to
Werner LEMBERG escreveu:
>> Note that the correct command to position the plus sign is
>> \translate-scaled; this is something which should probably be added
>> to the documentation.
>>
>> However, it's still not perfect yet: For smaller sizes, the
>> whitespace surrounding the plus sign is too lar
Hello,
We have a problem (or rather an optical preference) with the chord names
that are deisplayed. Moll chords are displayed like "Am", but we want to
have it another way (maybe it is a german thing...), to have moll chords
displayed lowercase. So "A" remains "A" and "Am" will become "a".
I hav
14 matches
Mail list logo
