> > 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
>
[EMAIL PROTECTED] writes:
> > relying on the TeX backend. That implies minimal font encoding
> > handling.
>
> Be careful to made a distinction between font and input encoding! Use
Now that we've dived into this matter, we understand the
distinction.
> > We have not yet found the trick to let
> If we want to replace [La]TeX titling kludges (in lilypond.py), we
> must at the very least offer something that is capable of printing
> our own examples (Les N'er'eides, S"angers Morgenlied) without
> relying on the TeX backend. That implies minimal font encoding
> handling.
Be careful to ma
Werner LEMBERG writes:
> I see a lot of changes related to fonts, font encoding, input
> encoding, etc., in the CVS. What is the near-time goal of your
> changes?
The long-time goal (somewhere this Easter :-) is to have LilyPond do
proper page layout. For page layout, it is necessary for LilyPo
[EMAIL PROTECTED] writes:
> > \override Lyrics #'X-extent-callback = #(lambda (grob)
> > (lookup-latex-dimension the-dimension-table (ly:get-property grob 'text)))
>
> I don't fully understand what I shall do. Can you give a real
> example, please? Assume that the words `foo', `bar', and
[EMAIL PROTECTED] writes:
>
> Han-Wen, Janneke,
>
>
> I see a lot of changes related to fonts, font encoding, input
> encoding, etc., in the CVS. What is the near-time goal of your
> changes?
Getting proper support for latin and latin-like languages. We don't
know how to handle unicode/Japanes
Han-Wen, Janneke,
I see a lot of changes related to fonts, font encoding, input
encoding, etc., in the CVS. What is the near-time goal of your
changes?
Reason for asking is support for Japanese -- I've written some Haiku,
and I would like to use lilypond for typesetting them.
There is still t
