On Wednesday 14 April 2004 00.19, Han-Wen Nienhuys wrote:
> Dear LilyPond afficionado,
>
> As you might have noticed, LilyPond has been improving at a breakneck
> speed for the last year, which is a good thing. This email hopes to
> continue that trend by unleashing an enormous source of developme
[EMAIL PROTECTED] writes:
>
> > The Debian maintainer disagrees, he claims lmodern is (usually
> > considered to be) better:
>
> This is correct, basically. But lmodern is `more' work in progress
> than cm-super -- it doesn't contain Cyrillic glyphs yet. Besides
> this, the quality and hinting
> The Debian maintainer disagrees, he claims lmodern is (usually
> considered to be) better:
This is correct, basically. But lmodern is `more' work in progress
than cm-super -- it doesn't contain Cyrillic glyphs yet. Besides
this, the quality and hinting is *excellent*.
> The Latin Modern
Werner LEMBERG writes:
> Uh, oh, lmodern is a different project! You should definitely use
> cm-super
The Debian maintainer disagrees, he claims lmodern is (usually
considered to be ) better:
$ apt-cache show lmodern
Package: lmodern
Priority: optional
Section: tex
Installed
> Tonight, I looked at lmodern (that's what apt-cache says when looking
> for cm-super) and tried to hook in into LilyPond, replacing the ec*
> fonts.
Uh, oh, lmodern is a different project! You should definitely use
cm-super, this is, selecting a single instance, say, sfrm1000.pfb,
sfss1000.pfb
> > A good thing would be to allow 32bit input character codes.
I mean *internally*, in case I was unclear.
> I don't see so much problems on the input side. ATM, you switch
> encodings on the fly with
>
> \encoding "latin1"
>
> (only affects \markup though) which means that latin1 is used to
>
