Re: lily in scheme

Well, first I'd say to not take anything I say too seriously.  I am new 
to this project and I definitely don't know everything there is to know 
about the code by any means.  In fact, I don't know much, yet.

What I'm thinking about, I guess, is that for developers the mixing of 
scheme and lily is no problem, and very powerful, but I wonder about 
the typical user, if there is such a thing.

Part of my problem is that I didn't understand what you were doing the 
first time I read it, because I wasn't paying attention, but I was 
partially reacting to this example:

%%%%%%%%%%% with-props.ly %%%%%%%%%%%%%%
#(use-modules (scm lily-in-scm)
               (srfi srfi-1))

#(define (override->revert override-expr)
   "Return a \\revert music expression for `override-expr', or
#f if it's not an override music expression."
   (if (ly:music? override-expr)
       (let* ((override (ly:music-property override-expr 'element))
              (context (ly:music-property override-expr 'context-type))
              (property (ly:music-property override 'grob-property))
              (layout (ly:music-property override 'symbol)))
         (if (and (ly:music? override) context property layout)
             #{ \revert $context . $layout #'$property #}
             #f))
       #f))

#(define (overrides->reverts music)

Translator function descriptions?

Translators are not extremely well documented currently.  Although I
think I have managed to figurou out what the purpose of each of these
is, it would be nice to get the creators' words on their usage:

initialize
start_translation_timestep
process_music
do_announces
stop_translation_timestep
finalize

--

-- 
Michael Welsh Duggan
(md5i <at> cs.cmu.edu)

Translator function descriptions?

Translators are not extremely well documented currently.  Although I
think I have managed to figurou out what the purpose of each of these
is, it would be nice to get the creators' words on their usage:

initialize
start_translation_timestep
process_music
do_announces
stop_translation_timestep
finalize

--

-- 
Michael Welsh Duggan
(md5i <at> cs.cmu.edu)

A few minor patches

A couple of minor patches I am bundling together because they are too
trivial to include one at a time:

First, getting rid of a few unused functions and variables:

This next patch should make the -m option work again.

--

-- 
Michael Welsh Duggan
(md5i <at> cs.cmu.edu)

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
http://mail.gnu.org/mailman/listinfo/lilypond-devel

Help with fontify-text

As part of my ongoing work with fret diagram markups I need to be able
to create a stencil of text that can be placed at the proper location in
the diagram.

Searching through the code, it appeared that the scheme function
fontify-text would do it.

However, when I tried to do this using ly:paper-get-font to get a font
metric, I got the following errors:

Programming error: Virtual font metric cannot be indexed by ASCII.
(Continuing: crossing fingers)
(One of the above for each character in the string to be placed in the
stencil)

Warning: lily-guile: Programming error: No such font: ()
(One of these for each call to fontify-text)

Any ideas for how to fix it?

Carl D. Sorensen
Department of Mechanical Engineering
Brigham Young University
435 CTB
Provo, UT 84602 
801-422-6397    FAX 801-422-0516

_______________________________________________

Different character codings

I have a song which lyrics use iso-8859-2 (latin2) character coding. Any 
way to make LilyPond show the right characters?

- Matevz

Re: Help with fontify-text

On Sat, 01 May 2004 20:22:53 -0600 "Carl D. Sorensen" <c_sorensen <at> byu.edu> wrote:

> As part of my ongoing work with fret diagram markups I need to be able
> to create a stencil of text that can be placed at the proper location
> in
> the diagram.
> 
> Searching through the code, it appeared that the scheme function
> fontify-text would do it.
> 
> However, when I tried to do this using ly:paper-get-font to get a font
> metric, I got the following errors:
>
> ...
>
> Any ideas for how to fix it?
>  
> Carl D. Sorensen
> Department of Mechanical Engineering
> Brigham Young University
> 435 CTB
> Provo, UT 84602 
> 801-422-6397    FAX 801-422-0516
> 

AFAIK, There are also these markup commands, take a look at
scm/define-markup-commands.scm, for example, command bigger (line 539-) to
increase font size, and command natural (line 204-) to draw a symbol. Command
bigger take the font metrics from props, and command natural seeks a defined
symbol. 

Re: A few corrections and suggestions to the manual

kroegerlistas <at> pedrokroeger.net writes:
> * Han-Wen Nienhuys (hanwen <at> xs4all.nl) wrote:
> > 
> > Hi!
> > 
> > thanks for your suggestions? Could I ask you (or anyone else, for that
> > matter), to put these suggestions into a patch, so I (or anyone with
> > CVS access) can readily integrate it?
> 
> ok, I'll do that. The reason I didn't was because they were merely
> "suggestions", in the sense that one would disagree or prefer a
> different way.

If you're unsure, add a little comment

  <at> c blah blah ..  --pk  

so we know what you changed and why.

--

-- 

 Han-Wen Nienhuys   |   hanwen <at> xs4all.nl   |   http://www.xs4all.nl/~hanwen 

Way to go.

ralph.little <at> tribaldata.co.uk writes:
i> To get around this, I was going to collect the notes for each voice in
> the Braille_note_engraver separately in BrailleVoice, then at the end of
> the measure, copy these strings to the end of a property in the
> BrailleStaff parent context, and get an engraver in BrailleStaff
> (Braille_measure_engraver) to actually put the text together for the
> measure.
> 
> This method sounds a bit mad, but I cannot think of a better way to do
> this.

That sounds like a viable method, but I would postpone handling it
when you have monophonic braille support fully going.

--
 Han-Wen Nienhuys   |   hanwen <at> xs4all.nl   |   http://www.xs4all.nl/~hanwen 

A few minor patches

md5i <at> cs.cmu.edu writes:
> A couple of minor patches I am bundling together because they are too
> trivial to include one at a time:
> 
> First, getting rid of a few unused functions and variables:

Thanks for your patches. I've but them in, but could you add ChangeLog
entries for the next patch? Thanks!

--

-- 

 Han-Wen Nienhuys   |   hanwen <at> xs4all.nl   |   http://www.xs4all.nl/~hanwen