[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: i18n

From: Mats Bengtsson
Subject: Re: i18n
Date: Fri, 05 Dec 2003 15:37:31 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

There's no need to hack fonts.scm. The font selection can easily
be overridden by

\property Lyrics . LyricText  \override #'font-name = #"csr10"

The problem is bigger if you use a font where the character coding
in the input file is different from the character coding in the
font file. The problem is that LilyPond uses low-level font selection
commands in the generated TeX files, not the NFSS scheme normally
used in LaTeX.

You could take a look at
to see some tricks to apply any LaTeX function to each syllable
in a lyrics line. This might help in certain situations.
One practical problem is that the latexpackages header parameter
to include extra latex packages in ly2dvi/lilypond is a bit too
primitive if you have to supply specific options to a specific
package. For example, there's no way to do specify the equivalence


Kopecek Tomas wrote:
I have similar problem. The CM fonts are not satisying in many cases. For
example in czech texts I have to use CS fonts (modification of CM with
proper accents for ISO-8859-2 distributed e.g. with TeTeX). It means I
need to rewrite scm/fonts.scm and substitute all cm* with cs*

There could be something like `font selection'. If is this system
(changing  fonts.scm) enough, there should be done some doco. Otherwise...
who know?


                        Tomas Kopecek
                        e-mail: kopecek at
                        ICQ: 114483784

Lilypond-devel mailing list

        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Phone: (+46) 8 790 8463                         
        Fax:   (+46) 8 790 7260
        Email: address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]