From: Hans Hagen <pragma@wxs.nl>
Subject: palatino / input needed
Date: Wed, 15 Mar 2000 15:35:23 +0100 [thread overview]
Message-ID: <3.0.6.32.20000315153523.007ff410@pop.wxs.nl> (raw)
Hi all,
I'm in the process of making a file font-ppl.tex, being a definition file
for the palatino. For the moment the content is:
\definefontsynonym [Palatino-Roman] [uplr8r] [encoding=ec]
\definefontsynonym [Palatino-Italic] [uplri8r] [encoding=ec]
\definefontsynonym [Palatino-Slanted] [uplro8r] [encoding=ec]
\definefontsynonym [Palatino-Bold] [uplb8r] [encoding=ec]
\definefontsynonym [Palatino-BoldItalic] [uplbi8r] [encoding=ec]
\definefontsynonym [Palatino-BoldSlanted] [uplbo8r] [encoding=ec]
\definefontsynonym [Serif] [Palatino-Roman]
\definefontsynonym [SerifBold] [Palatino-Bold]
\definefontsynonym [SerifItalic] [Palatino-Italic]
\definefontsynonym [SerifSlanted] [Palatino-Slanted]
\definefontsynonym [SerifBoldItalic] [Palatino-BoldItalic]
\definefontsynonym [SerifBoldSlanted] [Palatino-BoldSlanted]
\definefontsynonym [SerifCaps] [Palatino-Roman]
\definebodyfont
[14.4pt,12pt,11pt,10pt,9pt,8pt,7pt,6pt,5pt]
[rm]
[default]
\endinput
When testing this file with:
\setuplayout
[topspace=1cm,backspace=2cm,
header=0pt,footer=0pt,height=middle,
width=middle]
\starttext
\setupbodyfont[cmr,9pt] \showencoding
\setupbodyfont[ppl,9pt] \showencoding
\stoptext
One gets an overview of the glyphs, which in itself can be worth a try,
since it demonstrates one of the tracing options. Somehow, these fonts
don't match the ec encoding as perfect as they are supposed to. Does
someone has better experiences? (accented chars etc come out ok.)
My pdftex map file has the following entries:
uplr8r <uplr8a.pfb <8r.enc
uplri8r <uplri8a.pfb <8r.enc
uplb8r <uplb8a.pfb <8r.enc
uplbi8r <uplbi8a.pfb <8r.enc
uplro8r ".167 SlantFont" <uplr8a.pfb <8r.enc
uplbo8r ".167 SlantFont" <uplb8a.pfb <8r.enc
pplb8r Palatino-Bold <pplb8a.pfb 8r.enc
pplbi8r Palatino-BoldItalic <pplbi8a.pfb 8r.enc
pplbo8r Palatino-Bold ".167 SlantFont" <pplb8a.pfb 8r.enc
pplbu8r Palatino-BoldItalic "-.1763 SlantFont" <pplb8a.pfb 8r.enc
pplr8r Palatino-Roman <pplr8a.pfb 8r.enc
pplri8r Palatino-Italic <pplri8a.pfb 8r.enc
pplro8r Palatino-Roman ".167 SlantFont" <pplr8a.pfb 8r.enc
pplru8r Palatino-Italic " -.1763 SlantFont" <pplr8a.pfb 8r.enc
Since I want to add the font definition file to distribution, I need to be
sure that the original as well as berry names and encodings are ok. So, any
input is welcome.
While testing this a \SS (german s) showed up, which I repaired. (I had to
move a def to the enco-ini file instead of the font-ini file.). This
probably also solves some bugs reported with this s.
The next few months, I will also implement pdftex hz support. In the
process I want to do some tests (also with other optimizations). If people
don't mind, I'll ask for input and comments on this list.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
next reply other threads:[~2000-03-15 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 14:35 Hans Hagen [this message]
2000-03-16 8:27 ` Taco Hoekwater
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=3.0.6.32.20000315153523.007ff410@pop.wxs.nl \
--to=pragma@wxs.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).