ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MKIV, fonts, confusion
Date: Thu, 14 May 2009 13:21:46 +0200	[thread overview]
Message-ID: <20090514112146.GB9176@phare.normalesup.org> (raw)
In-Reply-To: <C19E0D37-DD0C-4ECF-8066-91721BA68794@gmail.com>

> when i convert the to TT format i get a correct output

  If Luigi is concerned with rounding errors, he shouldn't do that:
while the coordinates of the points on the curve wouldn't change, all
the control points would need to be recalculated due to the conversion
from cubic to quadratic splines.  On the other hand, if you keep CFF
outlines and reset the units per em size from 2048 to 1000, you're of
course exposed to rounding errors, but all the original points are
retained, both points on the curve and control points -- thus it's much
less error-prone, in my opinion.

	Arthur
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2009-05-14 11:21 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 [this message]
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=20090514112146.GB9176@phare.normalesup.org \
    --to=arthur.reutenauer@normalesup.org \
    --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).