[EMAIL PROTECTED] writes:
> On Tue, 2005-01-04 at 14:11, Han-Wen Nienhuys wrote:
> > Hmm. I'd say it should contain all info from the TFM
> >
> > * metrics (these are entirely unrelated to the extents of the
> > outlines)
> The advance widths have their natural place.
> Height/Depth informa
[EMAIL PROTECTED] writes:
>
> > How do we prevent bigcheese20.otf from ending up hundreds of times
> > in the output?
>
> It shouldn't be too difficult:
>
> . LilyPond produces EPS files which contain
>
> %%DocumentNeededResources: font bigcheese20
>
> but doesn't contain the font
[EMAIL PROTECTED] writes:
> > mailing lists. George already has started with three SFNT tables in
> > fontforge:
> >
> > ITLC italic correction
> > TCHL TeX charlist
> > TEXL TeX extension list
> Actually I didn't add tables, I added new feature tags.
> ITLC is a GPOS format 1 feat
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
On Tue, 2005-01-04 at 00:09, Werner LEMBERG wrote:
> > > Ideally, those OpenType TeX fonts should behave similar to any
> > > other OpenType font; this means the loss of italic correction
> > > (which isn't available in OpenType fonts), for example, but it
> > > assures that the fon
On Tue, 04 Jan 2005 09:09:16 +0100 (CET), Werner LEMBERG <[EMAIL PROTECTED]>
wrote:
>
> > > Ideally, those OpenType TeX fonts should behave similar to any
> > > other OpenType font; this means the loss of italic correction
> > > (which isn't available in OpenType fonts), for example,
Hello
I find myself using boxed rehersal marks all the time. Instead of
using long \markup stuff, I've created a patch for
scm/translation-functions.scm. This patch makes it easy to write \mark
\default and get nice boxed rehersal marks:
\set Score.markFormatter = #format-mark-box-letters, or
\set
> > Ideally, those OpenType TeX fonts should behave similar to any
> > other OpenType font; this means the loss of italic correction
> > (which isn't available in OpenType fonts), for example, but it
> > assures that the font interface doesn't have to cope with
> > special case
> > As perverse as it probably sounds in the very first moment, what
> > do you think of always create an EPS file, even for the TeX
> > backend, but without the text strings?
>
> Hmmm; that's an interesting idea. I agree it sounds perverse at the
> beginning, but on 2nd thought it actually makes
