headers
Heikki Johannes Junes | 2 Aug 2003 10:26
Picon
Picon

Post-fix syntax

Shouldn't \cresc, \decresc, and all similar have a post-fix syntax, too?

  Heikki Junes
Permalink | Reply | 0 comments |
headers
Han-Wen Nienhuys | 2 Aug 2003 11:40
Picon

Re: AFM font handling corrected?

rz <at> daimi.au.dk writes:
> Mats Bengtsson wrote:
> 
> > As far as I can understand, this means that the values should be
> > multiplied by 10/1000 for cmr10, right? Note that the definition
> > of point here is different from what TeX uses 1 inch = 72.27pt,
> > but that should only make a minor difference.
> 
> Yep, I would think that too. The problem is that the result comes out wrong.
> 
> I have attached a blow up of the example from yesterday - processed with 
> and without the afm. As you see, something is clearly wrong.

This could have to do something with kerning and buildup of rounding
errors, though. 

--

-- 

Han-Wen Nienhuys   |   hanwen <at> cs.uu.nl   |   http://www.xs4all.nl/~hanwen
Permalink | Reply | 0 comments |
headers
Han-Wen Nienhuys | 2 Aug 2003 12:12
Picon

Re: AFM font handling corrected?

mats.bengtsson <at> s3.kth.se writes:
> OK, I checked the Adobe Font Metrics File Format Specification
> document (available at http://www.wotsit.org, for example) and
> found the following statement:
> 
> ====================================================================
> 3.2 Units of Measurement
> 
> All measurements in AFM, AMFM, and ACF M fi les are given in terms
> of units equal to 1/1000 of the scale factor (point size) of the font
> being used. To compute actual sizes in a document (in points; with
> 72 points = 1 inch), these amounts should be multiplied by
> ( scale factor of font ) / 1000.
> ==========================================================================
> 
> As far as I can understand, this means that the values should be
> multiplied by 10/1000 for cmr10, right? Note that the definition
> of point here is different from what TeX uses 1 inch = 72.27pt,
> but that should only make a minor difference.
> 
> cmr10.afm and other AFM files can be found at CTAN in /fonts/cm/afm/.
> 
> I tried to quickly browse through the source code of afm2tfm that's
> included in teTeX, but couldn't find the relevant parts.

A proper fix is involved: the design size for every font should be
known (how do you do that, cmr14 is not 14 pt but 14.4) to lily, and
some internal APIs must be reworked to transport all that information.

The complete handling of font-sizes should be redone anyway. I'll wait
(Continue reading)

Permalink | Reply | 0 comments |
headers
Han-Wen Nienhuys | 3 Aug 2003 03:01
Picon

markups in scheme

nicolas.sceaux <at> free.fr writes:
> Hello,
> 
> Having upgraded from 1.6 to 1.7.something, I had a look to the new
> markups, as many messages in this list reported that it was a big
> improvement. (They were not lying.)
> 
> I looked for a scheme user interface, so that I could build markups in
> scheme functions. In a comment, it is said that is left as an exercise
> to the reader. But maybe I missed something?

Dunno. I suppose it as an excercise for the more advanced reader ;-)

The comment refers to writing new XXX-markup functions that are
recognized as \XXX by the parser.

The idea is that you do

	#(define-public (XXX-markup grob props . rest)
	  (interpret-markup  grob
	   (cons (cons font-shape italic) props)
	   (car rest)))
	#(set-object-property! XXX-markup 'markup-signature '(markup))
	#(set-object-property! xXX-markup 'markup-keyword 'markup0)

The problem is that (lookup-markup-command) only looks for XXX in the
new-markup.scm module. It should take optional arguments to lookup XXX
in different modules (such as the one for the currently translated .ly
file). Of course, if you write them as Scheme, you do not have to
worry about any macros.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Han-Wen Nienhuys | 3 Aug 2003 13:37
Picon

\grace at start of repeat block bug

richard.shann <at> virgin.net writes:
> If you have a grace note at the start of a repeat, it is placed before 
> the repeat, it should of course come after.
> Here is an example (the \partial is used to force the presence of the 
> begin-repeat bar).

>I have lilypond 2.6.5.

Ah! You're from the future! Can you tell me the winning lottery for
next week? :-)

Try upgrading to 1.8  when it's available (or try 1.7.30)

> http://mail.gnu.org/mailman/listinfo/lilypond-devel

--

-- 

Han-Wen Nienhuys   |   hanwen <at> cs.uu.nl   |   http://www.xs4all.nl/~hanwen
Permalink | Reply | 0 comments |
headers
Richard Shann | 3 Aug 2003 12:29
Favicon

\grace at start of repeat block bug

If you have a grace note at the start of a repeat, it is placed before 
the repeat, it should of course come after.
Here is an example (the \partial is used to force the presence of the 
begin-repeat bar). I have lilypond 2.6.5.

\score {
\context Staff \context Voice \notes  {
    \partial 8 e''8
    \repeat volta 2 {
    \grace b''8 ( ) a''4
    gis''4
    a''4
    c''8
    }  
}
\paper {}
}
Permalink | Reply | 2 comments |
headers
Aaron | 3 Aug 2003 14:07

Re: \grace at start of repeat block bug

HI,
It happens to me as well..
Richard could you please share your denemo stuff with this list, I think
it would be of benefit.

Thanks
Aaron
On Sun, 2003-08-03 at 13:29, Richard Shann wrote:
> If you have a grace note at the start of a repeat, it is placed before 
> the repeat, it should of course come after.
> Here is an example (the \partial is used to force the presence of the 
> begin-repeat bar). I have lilypond 2.6.5.
> 
> \score {
> \context Staff \context Voice \notes  {
>     \partial 8 e''8
>     \repeat volta 2 {
>     \grace b''8 ( ) a''4
>     gis''4
>     a''4
>     c''8
>     }  
> }
> \paper {}
> }
> 
> 
> 
> 
> _______________________________________________
(Continue reading)

Permalink | Reply | 0 comments |
headers
Laura Conrad | 3 Aug 2003 17:36
X-Face

Re: LilyPond 1.7.30 available

Now debuild -B gives me:

mftrace --encoding feta-nummer4.enc -I ./out/ --pfa --simplify --keep-trying feta-nummer4
mftrace 1.0.17
Font `feta-nummer4'...
Using encoding file: `./out/feta-nummer4.enc'
Running Metafont...warning: mf: command exited with value 256 (ignored) 
Traceback (most recent call last):
  File "/usr/bin/mftrace", line 1034, in ?
    base = gen_pixel_font (basename, metric, magnification)
  File "/usr/bin/mftrace", line 788, in gen_pixel_font
    log = open ('%s.log' % filename).read ()
IOError: [Errno 2] No such file or directory: 'feta-nummer4.log'
make[2]: *** [out/feta-nummer4.pfa] Error 1
make[2]: Leaving directory `/home/lconrad/src/lilypond/cvs-1.7/lilypond/mf'

--

-- 
Laura (mailto:lconrad <at> laymusic.org , http://www.laymusic.org/ )
(617) 661-8097	fax: (801) 365-6574 
233 Broadway, Cambridge, MA 02139
Permalink | Reply | 0 comments |
headers
Chris Sawer | 3 Aug 2003 18:37

Re: LilyPond 1.7.30 available

In message <16172.24636.201020.933898 <at> localhost.localdomain>
          Han-Wen Nienhuys <hanwen <at> cs.uu.nl> wrote:

> LilyPond 1.7.30 is available!  I expect that this is the last 1.8
> prerelease.

I'd like to take this opportunity to say thanks to everyone who's worked on
LilyPond 1.7, I've just installed 1.7.30 on my machine, and everything seems
to work perfectly. The output is even more beautiful than ever.

Thanks especially for providing the workaround for glibc 2.2.2. I tried to
upgrade my system, via RPMs, but the new glibc RPM needed a new gcc RPM,
which needed a new binutils RPM, which needed... a new glibc RPM! At this
point, I saw the announcement that a workaround had been written, much to my
relief!

I have a couple of small 'issues' with 1.7.30 that may not have been brought
to people's attention before.

Firstly, my system had a problem with fi.po, using msgfmt (GNU gettext)
version 0.10.35:

 fi.po:2215: illegal control sequence
 fi.po:2227: illegal control sequence

If a newer version of gettext is required, perhaps it should be added to the
'INSTALL' file (unless it's there already and I've overlooked it!).

[Deleting fi.po, as I don't need Finnish support, allowed me to continue the
compilation successfully]
(Continue reading)

Permalink | Reply | 0 comments |
headers
Juergen Reuter | 4 Aug 2003 01:25
Picon
Favicon

all-font-metrics, span bars

Actually, I am currently on vacation and can not really work on lily, but
I accidentally noticed that 1.7.30 breaks the ancient font, so I put a
tiny fix in cvs.

I also noticed that input/test/bar-lines-lyric-only.ly is still (or once
again?) broken:

* Bars should be removed from the staff:

    \translator {
      \StaffContext
      \remove "Bar_engraver"
    }

* The span bar spans only across the lyrics context but not the remaining
  inter-staff place (e.g. where the notes on ledger lines are).

* Main application for this notation style is probably mensural vocal
  music, hence you may want to choose ChoirStaff rather than StaffGroup
  for the example.

Greetings,
Juergen
Permalink | Reply | 0 comments |

Gmane