ChordNames

2006-11-29 Thread Philip Chinery
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 have posted to the user list but got no respone on that - is it possible
at all at the moment?

I have discovered these properties in the documentation:
 - chordRootNamer
 - chordNoteNamer

The documentations says: The chordNoteNamer property can be set to a
specialized function to change this behavior. For example, the base can be
printed in lower case.

Now the only problem for me is to know how to write and set such a function,
then I would probably be able to make moll chords lowercase :)

Is this documented somewhere?

Regards,
Philip



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


Re: patch for properly scaled fractions

2006-11-29 Thread Han-Wen Nienhuys
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 large since it isn't
 scaled.  I consider this as, well, a bad feature, and I suggest to
 change it too.
 
 After some thinking I wonder whether *all* commands which move objects
 should obey the font size.  For example, consider a small \score
 within a \markup -- in such cases it would be natural to use the
 small score's size values.

If you want to create a smaller score, you should tone the staff size 
down from the \layout block. This will scale down everything, including markups.
(at least, so it should)

-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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


Re: patch for properly scaled fractions

2006-11-29 Thread Han-Wen Nienhuys
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
 the documentation.

Please apply.


 However, it's still not perfect yet: For smaller sizes, the whitespace
 surrounding the plus sign is too large since it isn't scaled.  I
 consider this as, well, a bad feature, and I suggest to change it too.

Yes, the word-space in line and justified paragraph composition should be 
scaled by the font-size.


-- 

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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


Re: ChordNames

2006-11-29 Thread Johannes Schindelin
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 A remains A and Am will become a.

Have you tried \germanChords?

 Is this documented somewhere?

I looked at

http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Printing-chord-names.html

Hth,
Dscho



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


AW: ChordNames

2006-11-29 Thread Philip Chinery
 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/mailman/listinfo/lilypond-devel


Re: \concat markup command

2006-11-29 Thread Werner LEMBERG

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


Re: patch for properly scaled fractions

2006-11-29 Thread Werner LEMBERG

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

 Please apply.

Done.


Werner


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


regression: tuplet brackets missing in cues

2006-11-29 Thread Werner LEMBERG


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.org/mailman/listinfo/lilypond-devel


Re: AW: ChordNames

2006-11-29 Thread Johannes Schindelin
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 passed a single pitch (not enough information).

Attached is my attempt at it. It is dirt simple, in that it only displays 
alower case letter for minor chords, and an upper case letter for all 
others. No triangles, numbers or symbols. But it's a start...

Ciao,
Dscho


\version 2.10.0
\header {

texidoc = Demonstrate German chord names

}

chs =  \transpose c' c' 
{
c e g1
c es g% m = minor triad
c e gis
c es ges \break
\transpose c' d' {
c e g bes
c es g bes
c e g b   % triangle = maj
c es ges beses 
}
c es ges b \break
\transpose c' es' {
c e gis bes
c es g b
}
c e gis b 
c es ges bes\break
c e g a   % 6 = major triad with added sixth
c es g a  % m6 = minor triad with added sixth
c e g bes d' 
c es g bes d' \break
c es g bes d' f' a' 
c es g bes d' f' 
c es ges bes d'  
c e g bes des'  \break
c e g bes dis'
c e g bes d' f'
c e g bes d' fis'
c e g bes d' f' a'\break
c e g bes d' fis' as'
c e gis bes dis'
c e g bes dis' fis'
c e g bes d' f' as'\break
c e g bes des' f' as'
c e g bes d' fis'
c e g b d'
c e g bes d' f' as'\break
c e g bes des' f' as'
c e g bes des' f' a'
c e g b d'
c e g b d' f' a'\break
c e g b d' fis'
c e g bes des' f ' a'
c f g
c f g bes\break
c f g bes d'
c e g d'  % add9
c es g f'
}

#(define (simple-german-chord-name pitches bass inversion context)
  Return simple chord markup for PITCH, using german note names.
Use lower case for minor, otherwise upper case. Does not do any fancy
sub or superscripts.

  (let* ((pitch (car pitches))
 (pitch2 (cadr pitches))
 (diff (if (null? pitch2) (ly:make-pitch 0 0 0)
(ly:pitch-diff pitch2 pitch)))
 (minor? (and (= (ly:pitch-notename diff) 2)
  (= (ly:pitch-alteration diff) -2)))
 (name (ly:pitch-notename pitch))
 (short-alt? (or (= name 2) (= name 5)))
 (alt (ly:pitch-alteration pitch))
 (n-a (if (member (cons name alt) `((6 . ,FLAT) (6 . ,DOUBLE-FLAT)))
 (cons 7 (+ SEMI-TONE alt))
 (cons name alt
   (markup #:line
((string-append
  (vector-ref
   (if minor?
#(c d e f g a h b)
#(C D E F G A H B))
   (car n-a))
  (list-ref
   (if short-alt?
'(ses s  is isis)
'(eses es  is isis))
   (+ 2 (/ alt 2

germanChordProperties = \sequential { 
\set chordNameFunction = #simple-german-chord-name
}

\score{

\new ChordNames {
\set instrumentName = #Ignatzek (default)
\set shortInstrumentName = #Def
\chs
}

\new ChordNames {
\germanChordProperties
\set instrumentName = #Deutsch
\set shortInstrumentName = #dt
\chs
}

\new Staff  \transpose c c' { \chs }

\layout {
indent = 3.\cm
\context { 
\ChordNames
\consists Instrument_name_engraver
}
}
}

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


Re: \concat markup command

2006-11-29 Thread Han-Wen Nienhuys
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] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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


AW: AW: ChordNames

2006-11-29 Thread Philip Chinery
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:[EMAIL PROTECTED] 
 Gesendet: Mittwoch, 29. November 2006 21:32
 An: Philip Chinery
 Cc: lilypond-devel@gnu.org
 Betreff: Re: AW: ChordNames
 
 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 passed a single pitch (not enough information).
 
 Attached is my attempt at it. It is dirt simple, in that it 
 only displays alower case letter for minor chords, and an 
 upper case letter for all others. No triangles, numbers or 
 symbols. But it's a start...
 
 Ciao,
 Dscho
 
 
 



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


Re: urgent: layout of first page

2006-11-29 Thread Werner LEMBERG

  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/layout-page-layout.scm

 ;; not tested
 (define (first-line-position line layout)
   Position of the first line on page
   (max (+ (if (ly:prob-property? line 'is-title)
   0.0 ; do not use page-top-space when the 1st line is a title
   (ly:output-def-lookup layout 'page-top-space))
 (interval-end (paper-system-staff-extents line)))
(interval-end (paper-system-extent line Y

Han-Wen, shall I apply this to the git repository?

Regarding head-separation I wonder whether the current approach of
lilypond to handle headers and footers is the right one.  Wouldn't it
be better to define a zone of a given height within the header (or
footer) is rendered, instead of defining a distance from the header to
the score?

  current with header:current without header:

header line  ^
 ^   |
 |   | head-separation
 | head-separation   |
 |   v
 v score
   score

  suggested with header:  suggested without header:

 ^  header line  ^
 |   |
 |   |
 |   |
 |   |
 v   v
  scorescore


Currently, if a header line is missing, the whole text jumps up.


Werner


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


copyright symbol?

2006-11-29 Thread Ian Stirling
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't translated by convert-ly.

Ian
--


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


Re: copyright symbol?

2006-11-29 Thread Mats Bengtsson

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
Character Map program to find it) and then save the file in UTF-8 encoding.

  /Mats


Ian Stirling wrote:

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't translated by convert-ly.

Ian
--


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


--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
   Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=



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