ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: showfont with xetex (syntax changed?)
Date: Fri, 07 Dec 2007 20:07:18 +0100	[thread overview]
Message-ID: <475999E6.2010007@wxs.nl> (raw)
In-Reply-To: <115224fb0712060623x55694bdbgedabbcbf9d5925e0@mail.gmail.com>

Wolfgang Schuster wrote:

> And even worse both engines have their own default values for fonts.

add to that

-- they may implement feature support differently
-- fonts have bugs in lookup rules (obscured by processing engines)
-- we may want to control aspects of features
-- we may invent our own features (fea files)

ater all, open type has hardly any good reference documentation, bugs 
and unclear specs may dictate wrong behaviour in persistent manners (as 
with html and browsers),font designers have to think like programmers 
which may not be their stringest point, ...

although font installation becomes way easier in tex, it does mean that 
all our problems are solved

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2007-12-07 19:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 10:26 Steffen Wolfrum
2007-12-06 11:32 ` Mojca Miklavec
2007-12-06 13:48   ` Hans Hagen
2007-12-06 14:30     ` Steffen Wolfrum
2007-12-06 14:37       ` Wolfgang Schuster
2007-12-06 15:50         ` Steffen Wolfrum
2007-12-06 17:33           ` Wolfgang Schuster
2007-12-06 17:58             ` Hans Hagen
2007-12-07 19:09         ` Hans Hagen
2007-12-09 12:13           ` Wolfgang Schuster
2007-12-10 12:09             ` Hans Hagen
2007-12-10 12:20               ` Wolfgang Schuster
2007-12-07 19:08       ` Hans Hagen
2007-12-06 16:30     ` Mojca Miklavec
2007-12-07  9:29       ` Hans Hagen
2007-12-07  9:33       ` Hans Hagen
2007-12-06 14:23   ` Wolfgang Schuster
2007-12-07 19:07     ` Hans Hagen [this message]
2007-12-06 15:43   ` Steffen Wolfrum
2007-12-06 16:09   ` Steffen Wolfrum
2007-12-06 16:35     ` Mojca Miklavec
2007-12-06 16:59       ` Steffen Wolfrum
2007-12-06 17:36         ` Wolfgang Schuster
2007-12-06 17:45       ` Wolfgang Schuster
2007-12-06 17:55         ` Hans Hagen
2007-12-06 20:14           ` Steffen Wolfrum
2007-12-06 20:32             ` Hans Hagen

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=475999E6.2010007@wxs.nl \
    --to=pragma@wxs.nl \
    --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).