ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Patrick Gundlach <patrick@gundla.ch>
To: ntg-context@ntg.nl
Subject: Re: OpenType in ConTeXt
Date: Mon, 06 Aug 2007 20:03:49 +0200	[thread overview]
Message-ID: <m1y7goh75m.fsf@levana.de> (raw)
In-Reply-To: <1186420834.5981.23.camel@carnifex> (Pascal de Bruijn's message of "Mon, 06 Aug 2007 19:20:34 +0200")

Hello Pascal,

> I already noticed that script, however... It seems texfont already has
> support for OpenType. It has the --preproc and --lcdf parameters.

I have written otfinstall after I have played around with texfont.
texfont is much more versatile then otfinstall, but I think that
otfinstall is faster, easier to use and writes all necessary files.
But since I never felt like reading the texfont documentation, I might
be completely wrong about my assumptions on texfont.

> Why should I use otfinstall instead of texfont, besides the fact that
> texfont doesn't work? Is texfont incomplete? Or am I doing something
> wrong? What are the advantages/downsides of both?

They are just two different tools for a similar purpose. Nothing wrong
with each of them. There is not much to add to what Arthur said.

If you need any specific help on otfinstall, I'd be glad to assist you
(and update the documentation as well).

Patrick

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


  parent reply	other threads:[~2007-08-06 18:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 13:51 Pascal de Bruijn
2007-08-06  7:45 ` Patrick Gundlach
2007-08-06 17:20   ` Pascal de Bruijn
2007-08-06 17:54     ` Arthur Reutenauer
2007-08-06 20:01       ` Pascal de Bruijn
2007-08-06 20:07         ` Patrick Gundlach
2007-08-07 17:33           ` Pascal de Bruijn
2007-08-11 21:06             ` Patrick Gundlach
2007-08-06 20:10         ` Hans Hagen
2007-08-07  6:46           ` Pascal de Bruijn
2007-08-07  7:16             ` Taco Hoekwater
2007-08-07 17:02               ` Hans van der Meer
2007-08-07 17:09                 ` luigi scarso
2007-08-07 19:14                 ` Hans Hagen
2007-08-09 20:36                   ` John R. Culleton
2007-08-10 15:45                     ` Pascal de Bruijn
2007-08-09 13:09               ` Oliver Buerschaper
2007-08-09 14:26                 ` Hans Hagen
2007-08-09 16:28                 ` Hans van der Meer
2007-08-09 16:47                   ` Taco Hoekwater
2007-08-09 17:17                   ` Peter Münster
2007-08-07  9:36             ` Hans Hagen
2007-08-06 18:03     ` Patrick Gundlach [this message]
     [not found] <mailman.458.1186422999.2346.ntg-context@ntg.nl>
2007-08-06 23:24 ` Wolfgang Werners-Lucchini
2007-08-07  7:52   ` Patrick Gundlach
     [not found] <mailman.493.1186473146.2346.ntg-context@ntg.nl>
2007-08-07 20:18 ` Wolfgang Werners-Lucchini
2007-08-07 20:50   ` Arthur Reutenauer
2007-08-08  6:49   ` Taco Hoekwater
2007-08-11 14:09     ` John R. Culleton
2007-08-11 15:52       ` Hans Hagen
2007-08-07 20:18 ` Wolfgang Werners-Lucchini
2007-08-11 21:06   ` Patrick Gundlach

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=m1y7goh75m.fsf@levana.de \
    --to=patrick@gundla.ch \
    --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).