On Tue, 2005-01-04 at 23:29 +0100, Werner LEMBERG wrote:
> > > Owen, can you answer this, please? Since there are two mechanisms
> > > for kerning (the `kern' table and the `kern' feature in the GPOS
> > > table) I wonder how Pango is handling this.
> >
> > I won't say that I actually have plans
> > Owen, can you answer this, please? Since there are two mechanisms
> > for kerning (the `kern' table and the `kern' feature in the GPOS
> > table) I wonder how Pango is handling this.
>
> I won't say that I actually have plans for handling AFM files. I
> basically know how it would work: [...]
On Mon, 2005-01-03 at 19:28 +0100, Werner LEMBERG wrote:
> > > > * How do we deal with kerning in Pango? AFAIK, Pango does not
> > > > read AFM/TFM files, so how can it compute kernings?
> > >
> > > IIRC Owen has mentioned that he plans to support reading of AFM
> > > files for Type 1 fonts to
[EMAIL PROTECTED] writes:
>
> > > We need a new command to select the backend -- I propose
> > > \TeXformat and \PSformat so that the `-f ps' and `-f tex' switches
> > > become obsolete.
> >
> > And SVG/Gnome/whatever-we-come-up-with-next? I disagree with this
> > idea.
>
> See my other mail to
> > We need a new command to select the backend -- I propose
> > \TeXformat and \PSformat so that the `-f ps' and `-f tex' switches
> > become obsolete.
>
> And SVG/Gnome/whatever-we-come-up-with-next? I disagree with this
> idea.
See my other mail too. We must make a distinction between backe
> > > * How do we deal with kerning in Pango? AFAIK, Pango does not
> > > read AFM/TFM files, so how can it compute kernings?
> >
> > IIRC Owen has mentioned that he plans to support reading of AFM
> > files for Type 1 fonts to get kerning. Kerning from OpenType
> > should be supported alread
Jan Nieuwenhuizen writes:
> Hadden we niet al over gehad?
[sorry, please ignore]
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
lilypond-devel mailing
Han-Wen Nienhuys writes:
> * To provide backend routines for Pango_font::text_stencil, which is
> suitable for the SVG and GNOME backends.
>
> My current idea is to wrap PangoFontDescription as SCM and dump that
> into the backend. I hope for some input by Jan on this, since I
> guess th
Han-Wen Nienhuys writes:
>> We need a new command to select the backend -- I propose \TeXformat
>> and \PSformat so that the `-f ps' and `-f tex' switches become
>> obsolete.
>
> And SVG/Gnome/whatever-we-come-up-with-next? I disagree with this
> idea.
In fact, I would like to remove as much non-
[EMAIL PROTECTED] writes:
> > * Remove all support code for encoding within LilyPond. [...]
> > Encoding is either handled by (La)TeX, or by Pango. This means
> > that
> >
> > \encoding
> >
> > will disappear, as will the inputencoding field in \layout{}
>
> We need a new command to se
> * Remove all support code for encoding within LilyPond. [...]
> Encoding is either handled by (La)TeX, or by Pango. This means
> that
>
> \encoding
>
> will disappear, as will the inputencoding field in \layout{}
We need a new command to select the backend -- I propose \TeXformat
and
Hi there,
followers of the CVS commit list might have noticed that
Pango/FontConfig integration is proceeding. The last status is that
--format=ps now produces credible results in the PS output, and that
the dimensions of bounding boxes are computed correctly. The current
TODO list for the pango
12 matches
Mail list logo
