From: Johannes Huesing <hannes@ruhrau.de>
Subject: Font definition clashing?
Date: Sun, 25 Feb 2001 16:37:55 +0100 [thread overview]
Message-ID: <20010225163755.A2746@ruhrau.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Hi all,
I installed a font for myself (a clone of Candida) and wrote a ConTeXt
font definition file for it. It doesn't, however seem to go well
together with the definitions in font-eul.tex. The example file shows
the x overstriked by the bar instead of "overbarred". Enclosed you'll
find the small example and my definition file.
Does anybody have any ideas?
Groetjes
Johannes
--
"Human Genome" may be a binary file. See it anyway?
[-- Attachment #2: euler-min.tex --]
[-- Type: text/x-tex, Size: 200 bytes --]
\setupoutput[pdftex]
\setupbodyfont[pos, eul]
\starttext
$$
r_{xy} = \frac{(\sum_{i}x_{i}-\bar{x})(\sum_{i}y_{i}-\bar{y})}
{\sqrt{\sum_{i}(x_{i}-\bar{x})^{2}\sum_{i}(y_{i}-\bar{y})^{2}}}
$$
\stoptext
[-- Attachment #3: font-cdi.tex --]
[-- Type: text/x-tex, Size: 706 bytes --]
%D \module
%D [ file=font-5ci,
%D version=2001.02.25,
%D title=\CONTEXT\ Font Macros,
%D subtitle=Palatino,
%D author=J. Huesing,
%D date=\currentdate,
%D copyright=J. Huesing]
%C
%D This file loads the Softmaker Candida.
\definefontsynonym [Slab-C650-Regular] [5cir8t][encoding=ec]
\definefontsynonym [Slab-C650-Bold] [5cib8t][encoding=ec]
\definefontsynonym [Slab-C650-Italic][5ciri8t][encoding=ec]
\definefontsynonym [Serif] [Slab-C650-Regular]
\definefontsynonym [SerifBold] [Slab-C650-Bold]
\definefontsynonym [SerifItalic] [Slab-C650-Italic]
\definebodyfont [14.4pt,12pt,11pt,10pt,9pt,8pt,7pt,6pt,5pt] [rm] [default]
\endinput
next reply other threads:[~2001-02-25 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 15:37 Johannes Huesing [this message]
2001-02-26 9:11 ` Hans Hagen
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=20010225163755.A2746@ruhrau.de \
--to=hannes@ruhrau.de \
--cc=johannes.huesing@ruhrau.de \
/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).