From: Thomas A.Schmitz <thomas.schmitz@uni-bonn.de>
Subject: Re: Greek font
Date: Wed, 10 Sep 2003 18:26:26 +0200 [thread overview]
Message-ID: <86B0CFBA-E3AB-11D7-92F8-00039318D414@uni-bonn.de> (raw)
In-Reply-To: <20030910155103.GA7609@tullamore.elvenkind.com>
Thanks again for helping. I'm happy to say that I'm almost home free.
The trick was to go via .vpl-files and edit them. The missing glyphs
were somewhere in the table, I could simply copy and paste them in the
right position; I then added ligatures for all the accents/breathings
etc and finally kerning information. I then used vptovf to produce a
matching tfm, and everything worked as expected; even the "space" has
micraculously reappeared. Strangely, when I put the resulting .vf-file
into my "fonts/vf"-folder, TeX would go haywire; this means that I
couldn't use any remapping in the fonts. I had to cut a few corners, it
is just a "quick-and-dirty" fix, but it works!!! I've learnt more about
fonts than I ever wanted, but I now have (almost) real control; I even
managed to replace one character I didn't like with its counterpart
from another font (and then edit this new character to perfection in
pfaedit, a really amazing tool). One last (little) problem; maybe one
of you has an idea: since I couldn't remap, I have trouble producing a
single breathing in front of a capital letter. I helped myself by
defining \define\<{\getglyph{greeoxon}{96}}, so I could at least use
\<A to obtain capital alpha with rough breathing. The problem is that
after these commands, I can't get any kerning to work. Any ideas?
Maybe one day I'll know enough about TeX to do all of this the proper
way. Maybe one day I'll be able to use Omega (btw, how can the new
e-Omega/Aleph be obtained? And where can I dload Omega 1.15?). But for
the time being, I'm a happy camper again. Should any of you be
interested, I'd be glad to share my stuff.
Best
Thomas
next prev parent reply other threads:[~2003-09-10 16:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 8:06 Thomas A.Schmitz
2003-09-06 15:49 ` Willi Egger
2003-09-06 16:13 ` Thomas A.Schmitz
2003-09-08 12:13 ` Jens-Uwe Morawski
2003-09-06 18:03 ` Henning Hraban Ramm
2003-09-06 21:10 ` Thomas A.Schmitz
2003-09-06 21:35 ` Thomas A.Schmitz
2003-09-07 22:07 ` Thomas A.Schmitz
2003-09-08 13:52 ` Willi Egger
2003-09-08 14:40 ` Thomas A.Schmitz
2003-09-10 13:08 ` Re[2]: " Giuseppe Bilotta
2003-09-10 15:51 ` Siep Kroonenberg
2003-09-10 16:26 ` Thomas A.Schmitz [this message]
2003-09-10 23:01 ` 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=86B0CFBA-E3AB-11D7-92F8-00039318D414@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).