[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fri, 1 Feb 2002 18:59:14 +0100
> I've made a first attempt to implement the long awaited
> support for different font encodings. This means that you
> now can typeset Swedish, Danish, German, Spanish, ...
> in lyrics and text scripts including all special characters and
> Lilypond will understand and calculate the correct size of each letter
> when it determines the spacing. So far, the encodings OT1 (the default
> in TeX) and T1 (Latin1) are supported.
IIRC both OT1 and T1 are TeX specific. Are they? We really want to
move towards more modern standards. Specifically, for the long term,
usable direct PS output is on our wishlist. How does this work?
Shouldn't lilypond also read in .enc files? Secondly, how much work
would it be to add support for multibyte encodings? It would be nice
to support chinese.
> - You have to set both the grob property font-encoding and
> the paper variable fontenc if ly2dvi should handle the
> fonts correctly.
I don't understand why; how does LaTeX handle it when you mix fonts in
> Preferably, one of these should be set
> from the other. Maybe it would be best if the grob
> property was set based on the paper variable, since it's
> a bad idea to mix different font encodings in the same
> file. I haven't investigated how this could be done.
> Any suggestions?
you could import the default from the paper-block or style sheet, and
supply that if no font-encoding is set.
Han-Wen Nienhuys | address@hidden | http://www.cs.uu.nl/~hanwen/
- Font encoding,
Han-Wen Nienhuys <=