From: Taco Hoekwater <bittext@quicknet.nl>
Cc: Hans Hagen <pragma@wxs.nl>, ntg-context@ntg.nl
Subject: Re: fonts / proposal
Date: Sat, 04 Aug 2001 13:45:15 +0200 [thread overview]
Message-ID: <3B6BE04B.AF5A2C06@quicknet.nl> (raw)
In-Reply-To: <161016672.20010803220612@bigfoot.com>
Giuseppe Bilotta wrote:
>
> I think the TeX Directory Standard puts fonts under
>
> \texmf\fonts\<type>\<class>\<vendor>\<name>
I strongly believe that was a mistake. Because that way, the different
parts
that make up a font are split over two or three separate directories.
But that is not important now...
> I think the (only) problem with this is that it fails on pure DOS
> system (8.3 naming constrictions). Since the font naming is X
> Windows-like, why don't you just use the X Windows scheme?
The X system has rather a lot of keys that dont make sense in TeX.
Here is the list and an example:
Foundry Adobe
Family Helvetica
Weight bold
Slant oblique
Set Width expanded
Additional Style
Pixel Size 12
Point Size 120
Resolution X 75
Resolution Y 75
Spacing proportional
Average Width 69
Charset iso8859-1
Slant and Spacing are actually one letter in the X font name, so this
font's name is:
-adobe-helvetica-bold-o-normal--12-120-75-75-p-69-iso8859-1
Slant is normally one of (o,r,i) for oblique,roman,italic
Spacing is normally one of (c,p,m) for cell,proportional,monospaced
(cell is roughly the same as monospaced)
AddStyle is normally not used.
Point Size is in 1/720th of an inch (value 0 for scalable font).
PxlSize, resX and resY are never really applicable to a type 1 font.
(values 0)
AvgW is a bit of a weird thing that is sometimes handy when trying to
replace the font for a block of text, but it is usually generated
on-the-fly and not saved in the name (value==0).
Therefore, the example font is actually specified in the font directory
as:
-adobe-helvetica-bold-o-normal--0-0-0-0-p-0-iso8859-1
Whatever Hans comes up with, at should be documented straight away. And
by that I mean a precise specification of what the font installer can
generate in the fields.
Just some background info.
Greetings, Taco
next prev parent reply other threads:[~2001-08-04 11:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 15:32 Hans Hagen
2001-08-03 20:06 ` Giuseppe Bilotta
2001-08-04 11:45 ` Taco Hoekwater [this message]
2001-08-06 8:29 ` Hans Hagen
2001-08-07 17:59 ` Re[2]: " Giuseppe Bilotta
2001-08-08 8:32 ` Hans Hagen
2001-08-04 12:30 ` siepo
2001-08-06 8:38 ` Hans Hagen
2001-08-06 9:22 ` siep
2001-08-06 12:13 ` Hans Hagen
2001-08-06 13:14 ` siep
2001-08-07 8:40 ` Taco Hoekwater
2001-08-08 9:13 ` Hans Hagen
2001-08-08 9:34 ` siep
2001-08-08 12:13 ` 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=3B6BE04B.AF5A2C06@quicknet.nl \
--to=bittext@quicknet.nl \
--cc=ntg-context@ntg.nl \
--cc=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).