From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: Using Postscript Type 1 fonts in ConTeXt/XeTeX?
Date: Tue, 4 Mar 2008 01:16:51 +0100 [thread overview]
Message-ID: <20080304011651.007b1d1f.schuster.wolfgang@googlemail.com> (raw)
In-Reply-To: <6faad9f00803031610y21cc5cadn3a74efd151b11cf0@mail.gmail.com>
On Tue, 4 Mar 2008 01:10:06 +0100
"Mojca Miklavec" <mojca.miklavec.lists@gmail.com> wrote:
> On Mon, Mar 3, 2008 at 8:58 PM, Henning Hraban Ramm wrote:
> > Am 2008-03-03 um 17:44 schrieb Mojca Miklavec:
> >
> > > - or to patch ConTeXt to use xdv2pdf instead of xdvipdfmx + rewrite a
> > > bunch of definitions that load Latin Modern (they should not be loaded
> > > since xdv2pdf doesn't support "traditional TeX-installed fonts")
> >
> > Since there are OpenType LM fonts now, one could just install them
> > for the OS.
>
> True. But there are to mechanisms to load fonts: by font name or by
> filename. By filename only works in xdvipdfmx and by font name
> requires the font to be installed (and thus cannot be made the
> default/cannot be expected from users).
>
> If there were enough requests, xdv2pdf could be made optional by:
> - providing an extra switch for texexec
IRC this is already possible on a Mac, "texexec --xtx" use dvipdfmx
and "texexec --xetex" use xdv2pdf to convert the DVI file to PDF.
> - providing an alternative that doesn't use Latin Modern by filename
> (which means either not loading OpenType LM at all or assuming that
> it's installed)
>
> I just didn't feel that it would be necessary to support that (didn't
> know the limitations of xdvipdfmx) when I was asking Hans to write
> patches. If there are requests to do it, it could probably be done.
Wolfgang
___________________________________________________________________________________
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:[~2008-03-04 0:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 10:21 Roland
2008-01-20 12:54 ` Wolfgang Schuster
2008-01-20 16:40 ` Mojca Miklavec
2008-01-20 17:37 ` Mojca Miklavec
[not found] ` <cd7ae9e30801201252k239a94cdteac2368f3b0cc45f@mail.gmail.com>
2008-01-20 20:55 ` Roland
2008-01-20 21:11 ` Mojca Miklavec
2008-01-21 7:22 ` Roland
2008-01-21 10:49 ` Mojca Miklavec
2008-01-21 23:00 ` Roland
2008-01-21 23:39 ` Mojca Miklavec
2008-01-22 6:44 ` Roland
2008-01-22 8:37 ` Mojca Miklavec
2008-02-01 8:09 ` Roland
[not found] ` <cd7ae9e30802010011i4227188fwee641ad6da7efb61@mail.gmail.com>
2008-03-01 12:19 ` Roland
2008-03-02 14:21 ` Jérome Laurens
2008-03-02 19:37 ` Henning Hraban Ramm
2008-03-03 16:44 ` Mojca Miklavec
2008-03-03 19:58 ` Henning Hraban Ramm
2008-03-04 0:10 ` Mojca Miklavec
2008-03-04 0:16 ` Wolfgang Schuster [this message]
2008-01-20 20:48 ` Roland
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=20080304011651.007b1d1f.schuster.wolfgang@googlemail.com \
--to=schuster.wolfgang@googlemail.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).