From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: typescripts
Date: Wed, 17 Mar 2010 10:11:44 +0100 [thread overview]
Message-ID: <4BA09CD0.1030904@googlemail.com> (raw)
In-Reply-To: <6faad9f01003170204m503f80c5i96fcad90c72b6645@mail.gmail.com>
Am 17.03.10 10:04, schrieb Mojca Miklavec:
> Maybe I'm wrong, but shouldn't it be possible (I didn't test) to
> modify font-unk.mkiv and add a few extra definitions to the following?
> (Maybe not modify font-unk itself, but just adding a couple of more
> definitons to the typescript.)
>
> \definebodyfont [default] [rm]
> [tf=Serif sa 1,
> bf=SerifBold sa 1,
> it=SerifItalic sa 1,
> sl=SerifSlanted sa 1,
> bi=SerifBoldItalic sa 1,
> bs=SerifBoldSlanted sa 1,
> sc=SerifCaps sa 1]
>
> You could add your
> in=SerifYourFontVariantName sa 1,
> bd=SerifYourOtherFontVariantName sa 1,
>
The last time i did this you needed for MkIV also
\definefontalternative[in]
\definefontalternative[bd]
but be carefull with the shortcuts, \in is already used (references).
> And then
> \definefontsynonym[SerifYourFontVariantName][YourFontName]
>
> It's true that most people don't do that, but I see no reason for not
> extending the model for your particular needs.
>
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-03-17 9:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 1:26 typescripts Michael Saunders
2010-03-17 8:20 ` typescripts Wolfgang Schuster
2010-03-17 9:04 ` typescripts Mojca Miklavec
2010-03-17 9:11 ` Wolfgang Schuster [this message]
2010-03-17 11:33 ` typescripts Mojca Miklavec
2010-03-17 12:12 ` typescripts Wolfgang Schuster
-- strict thread matches above, loose matches on Subject: below --
2010-11-12 14:32 typescripts Herbert Voss
2010-11-12 16:29 ` typescripts Herbert Voss
2010-11-12 16:54 ` typescripts Hans Hagen
2010-11-12 16:57 ` typescripts Hans Hagen
2010-11-12 17:41 ` typescripts Herbert Voss
2010-11-12 17:46 ` typescripts Hans Hagen
[not found] ` <4CDD80A7.7040803@FU-Berlin.DE>
[not found] ` <4CDD8246.2020206@wxs.nl>
2010-11-12 20:39 ` typescripts Herbert Voss
2010-11-10 18:57 typescripts Herbert Voss
2010-11-10 20:28 ` typescripts Mojca Miklavec
2010-11-10 21:14 ` typescripts Herbert Voss
2010-11-11 5:20 ` typescripts Wolfgang Schuster
2010-11-11 11:03 ` typescripts Mojca Miklavec
2010-11-11 11:27 ` typescripts Hans Hagen
2010-11-11 14:15 ` typescripts Mojca Miklavec
2010-03-18 20:42 typescripts Michael Saunders
2010-03-18 1:32 typescripts Michael Saunders
2010-03-18 9:53 ` typescripts Wolfgang Schuster
2010-03-18 10:04 ` typescripts Wolfgang Schuster
2010-03-17 12:16 typescripts Michael Saunders
2010-03-17 12:34 ` typescripts Wolfgang Schuster
2010-03-18 0:04 ` typescripts Wolfgang Schuster
2003-08-16 20:05 typescripts Henning Hraban Ramm
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=4BA09CD0.1030904@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).