From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Preliminary support for the Luxi typeface
Date: Fri, 8 Jul 2005 18:04:31 +0200 [thread overview]
Message-ID: <1603001901.20050708180431@iol.it> (raw)
I couldn't find the appropriate typescript definition in
ConTeXt, so here's the initial stuff:
\starttypescript[mono][luxi][\defaultencoding]
\definefontsynonym[Luxi] [\defaultencoding-ul9r8a] [encoding=\defaultencoding]
\definefontsynonym[LuxiBold] [\defaultencoding-ul9b8a] [encoding=\defaultencoding]
\definefontsynonym[LuxiOblique] [\defaultencoding-ul9ro8a][encoding=\defaultencoding]
\definefontsynonym[LuxiBoldOblique] [\defaultencoding-ul9bo8a][encoding=\defaultencoding]
\stoptypescript
% Maybe should map Slanted, not Italic
\starttypescript[mono][luxi][name]
\definefontsynonym[Mono][Luxi]
\definefontsynonym[MonoBold][LuxiBold]
\definefontsynonym[MonoItalic][LuxiOblique]
\definefontsynonym[MonoBoldItalic][LuxiBoldOblique]
\stoptypescript
Of course there's the usual Berry name mapping needed if you only
have the LaTeX metrics, which go to the regular expression
ul9[rb]o?8[artc]
as usual.
--
Giuseppe "Oblomov" Bilotta
reply other threads:[~2005-07-08 16:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1603001901.20050708180431@iol.it \
--to=gip.bilotta@iol.it \
--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).