From: Han The Thanh <thanh@informatics.muni.cz>
Cc: ntg-context@ntg.nl
Subject: Re: fonts fonts and fonts
Date: Tue, 13 Mar 2001 11:12:20 +0100 [thread overview]
Message-ID: <20010313111220.A19790@anxur.fi.muni.cz> (raw)
In-Reply-To: <3AADE975.BC3CAF07@wkap.nl>; from taco.hoekwater@wkap.nl on Tue, Mar 13, 2001 at 10:33:41AM +0100
> > Are you using fontinst for this? This should imho be the best way to do
> > it, because you can also use the font for tex/latex.
>
> fontinst is a confusing affair. While it is fairly easy to install
> a simple text font with it, it is very hard to do something complicated.
> People keep telling me that it's possible, but it doesnt make a lot
> of sense to me.
>
> Also, I don't understand why it was coded in TeX (don't tell me it is
> for ease of use ... it's not easy to use ... and it's not helpful for
> portability ... fontinst doesn't even do any of the non-portable stuff).
completely agree!
> In short: I don't like fontinst, nor will I ever. But it does make
> sense to create an 8t/7t encoded tfm along with the texnansi one for
> context.
I do use fontinst, because I don't have anything more reasonable to deal
with things like composed glyphs, letterspacing, kerning and the likes.
Don't tell me that afm2tfm can do that job.
Thanh
next prev parent reply other threads:[~2001-03-13 10:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-25 18:14 Broken catcodes Giuseppe Bilotta
2002-05-25 20:17 ` Hans Hagen
2002-05-25 21:46 ` Re[2]: " Giuseppe Bilotta
2002-05-26 17:39 ` Hans Hagen
2002-05-26 20:38 ` Re[3]: " Giuseppe Bilotta
[not found] ` <pragma@wxs.nl>
2001-03-12 16:50 ` fonts fonts and fonts Hans Hagen
2001-03-12 17:07 ` Frans Goddijn
2001-03-12 23:11 ` Christoph Dreyer
2001-03-13 9:33 ` S2P development
2001-03-13 10:12 ` Han The Thanh [this message]
2001-03-13 10:35 ` Hans Hagen
2001-03-14 21:32 ` H. Ramm
2001-03-13 7:12 ` Steve Lumos
2001-03-13 9:13 ` Hans Hagen
2001-03-14 0:29 ` Uwe Koloska
2001-03-13 14:35 ` Ed L Cashin
2001-03-14 0:18 ` Uwe Koloska
2001-03-15 21:55 ` H. Ramm
2002-05-27 15:27 ` Re[2]: Broken catcodes Daniel Flipo
2002-05-27 15:32 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2001-05-30 11:40 Environments, Projects, Products, Components Giuseppe Bilotta
2001-05-30 15:14 ` Taco Hoekwater
2001-05-30 18:01 ` Re[2]: " Giuseppe Bilotta
2001-05-31 7:51 ` Taco Hoekwater
2001-05-31 9:34 ` Hans Hagen
2001-08-30 17:54 ` Steve Lumos
2001-08-31 7:19 ` Hans Hagen
2001-05-31 8:11 ` Re[2]: " Hans Hagen
[not found] <C21706811338D411A0130090273D20B291AD48@msgmarbio02.bio.dfo .ca>
2001-03-13 14:54 ` fonts fonts and fonts Hans Hagen
2001-03-13 13:38 White, George
2001-03-13 9:05 siep.kroonenberg
2001-03-12 23:11 Christoph Dreyer
2001-03-13 9:25 ` Hans Hagen
2001-02-22 7:24 Horizontal centering \startlines...\stoplines Steve Lumos
2001-02-22 8:47 ` Horizontal centering \startlines...\stoplines / poems Hans Hagen
2001-03-03 9:22 ` Steve Lumos
2001-03-04 21:09 ` Hans Hagen
2001-03-07 4:08 ` Steve Lumos
2001-03-07 8:14 ` Hans Hagen
2000-08-19 12:21 Setting up footnotes Joop Susan
2000-08-21 11:00 ` Hans Hagen
2000-08-21 18:19 ` Joop Susan
2000-08-22 6:59 ` 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=20010313111220.A19790@anxur.fi.muni.cz \
--to=thanh@informatics.muni.cz \
--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).