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 14:27:58 +0200 [thread overview]
Message-ID: <fe8d59da0905140527j14db254esce3e7b53f6806dc0@mail.gmail.com> (raw)
In-Reply-To: <20090514110805.GA9176@phare.normalesup.org>
[-- Attachment #1.1: Type: text/plain, Size: 1134 bytes --]
On Thu, May 14, 2009 at 1:08 PM, Arthur Reutenauer <
arthur.reutenauer@normalesup.org> wrote:
> > arthur told me that can arise rounding errors.
>
> You have to remember I used to be a mathematician. I say things that
> are meant to be true, not meant to be helpful :-)
>
> If you want to be sure that LuaTeX's output looks right in the most
> recent versions of Adobe Reader, editing the font is the way to go
> (although there might be license issues with commercial fonts). Of
> course conversion is not perfect, but you can't have it both way!
> Besides, the metrics won't change if you only modify upm; only the
> outlines do.
>
> > I should try to convert to Type1 instead
>
> That should indeed work if you don't need more than 256 glyphs in the
> font (are you *sure* you don't?).
>
> Arthur
>
what I mean is:
chose an encoding
convert otf to type1 as is,
make a pdf with mkiv
check if it's ok.
It's only for experiment , of course:
Fell type come with a native ttf edition which is OK (or better, really OK),
and one should chose this one to avoid any problems
(so eventually I can compare pdfs ).
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1608 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 12:27 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
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 [this message]
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=fe8d59da0905140527j14db254esce3e7b53f6806dc0@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).