From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: dejavu fonts
Date: Sun, 14 Aug 2011 16:39:44 +0200 [thread overview]
Message-ID: <4E47DE30.60108@wxs.nl> (raw)
In-Reply-To: <CALBOmsZq1HMNjo76A5GYRTEGns9iK-NKZE2VQqE3v2TaqY8QDw@mail.gmail.com>
On 14-8-2011 2:30, Mojca Miklavec wrote:
> On Sun, Aug 14, 2011 at 09:59, Wolfgang Schuster wrote:
>>
>> For MkIV you can put the definition in “type-<font>.mkiv” and when
>> put “\setupbodyfont[<font>]” in your document ConTeXt loads the file
>> without the need for \usetypescriptfile.
>
> Thank you. That is very useful to know.
>
>> When you want to support XeTeX and pdfTeX at the same time you have
>> to use \beginNEWTEX and \beginOLDTEX when you want both of them in
>> the same file but you can also put both in separate files where is
>> loaded from type-<font>.mkii
>>
>> \ifnum\texengine\pdftexengine
>> \usetypescriptfile[type-<font>-pdftex]
>> \else
>> \usetypescriptfile[type-<font>-xetex]
>> \fi
>
> Thank you. So no general guidelines about the desired approach exist?
> (I'm thinking about type-one-<font>.mkii& type-otf-<font>.mkii.)
Speaking for mkiv, some run time loading modules new get names like
*-imp-*.mkiv in order to avoid clashes with core (code) modules. At some
point I will probably rename some of the type-*.mkiv files (after all
imp is already supported there). Also, some font definitions might move
to lfg files (and some already are).
btw, dejavu is already defined in mkiv
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-08-14 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 18:07 Mojca Miklavec
2011-08-14 7:59 ` Wolfgang Schuster
2011-08-14 12:30 ` Mojca Miklavec
2011-08-14 14:39 ` Hans Hagen [this message]
2011-08-14 15:17 ` Mojca Miklavec
2011-08-14 15:54 ` Hans Hagen
2011-08-14 17:50 ` Hans Hagen
2011-08-14 19:41 ` Mojca Miklavec
2011-08-14 22:07 ` Andreas Harder
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=4E47DE30.60108@wxs.nl \
--to=pragma@wxs.nl \
--cc=mojca.miklavec.lists@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).