From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MKIV, fonts, confusion
Date: Thu, 14 May 2009 11:48:20 +0200 [thread overview]
Message-ID: <fe8d59da0905140248v15510cddvd2f773bddd2fea60@mail.gmail.com> (raw)
In-Reply-To: <4A0BE5AC.3040208@elvenkind.com>
[-- Attachment #1.1: Type: text/plain, Size: 1108 bytes --]
On Thu, May 14, 2009 at 11:34 AM, Taco Hoekwater <taco@elvenkind.com> wrote:
>
>
> luigi scarso wrote:
> > > So I don't understand how OO "transform" this opentype in a Type1 ,
> >
> > I guess that that is not hard when a document uses no more than 256
> > glyphs from the font.
> >
> >
> > yes, a sort of creation of font encodings at fly for more than 256
> > glyphs -- but why ?
>
> Maybe to get around that bug^H^H^Hfeature in AR8 and AR9
it's a bug of AR8 and AR9 , IMHO .
AR7 shows it ok;
AR5 says it's a broken pdf .
> > Also, does it fix em size, given that this appears to be the root of the
> > problem ?
>
> No, it fixes nothing. It just works around the issue. The cause of
> the problem is that AR8 and AR9 *require* Type0 fonts to have 1000
> units/em, otherwise the glyph drawing routine outputs an incorrectly
> scaled object. There is no such limitation for Type1C fonts, and
> that is why it works ok there (at least for now, who knows what AR10
> will bring ...)
>
And aren't we able to do the same trick -- even with a lots of unreadable
macros -- in luatex ?
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1778 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-05-14 9:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 13:18 afsmith
2009-05-13 13:29 ` luigi scarso
2009-05-13 14:36 ` Wolfgang Schuster
2009-05-13 14:48 ` luigi scarso
2009-05-13 15:36 ` Wolfgang Schuster
2009-05-13 15:51 ` luigi scarso
2009-05-13 16:27 ` Wolfgang Schuster
2009-05-14 7:34 ` luigi scarso
2009-05-14 9:11 ` Taco Hoekwater
2009-05-14 9:26 ` luigi scarso
2009-05-14 9:34 ` Taco Hoekwater
2009-05-14 9:48 ` luigi scarso [this message]
2009-05-14 9:56 ` Taco Hoekwater
2009-05-14 10:12 ` luigi scarso
2009-05-14 10:39 ` Wolfgang Schuster
2009-05-14 11:21 ` Arthur Reutenauer
2009-05-14 11:38 ` Taco Hoekwater
2009-05-14 11:50 ` Arthur Reutenauer
2009-05-14 23:48 ` luigi scarso
2009-05-15 6:18 ` Wolfgang Schuster
2009-05-14 11:08 ` Arthur Reutenauer
2009-05-14 12:27 ` luigi scarso
2009-05-14 9:03 ` luigi scarso
2009-05-14 11:49 ` Khaled Hosny
2009-05-14 12:10 ` Arthur Reutenauer
2009-05-13 13:32 ` Hans Hagen
2009-05-13 16:31 ` afsmith
2009-05-13 16:47 ` Hans Hagen
2009-05-13 17:23 ` Wolfgang Schuster
2009-05-13 20:23 ` Aditya Mahajan
2009-05-13 20:31 ` Wolfgang Schuster
2009-05-13 22:12 ` Mohamed Bana
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe8d59da0905140248v15510cddvd2f773bddd2fea60@mail.gmail.com \
--to=luigi.scarso@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).