From: Idris Samawi Hamid <ishamid@colostate.edu>
Subject: Open Type trickery [was Re: Encoding and mapping glyphs from an expert font
Date: Sat, 09 Apr 2005 19:27:21 -0600 [thread overview]
Message-ID: <opsozszvyhu9mfh0@lamar.colostate.edu> (raw)
In-Reply-To: <20050410002231.31504@mail.comp.lancs.ac.uk>
On Sun, 10 Apr 2005 00:22:31 +0100, Adam Lindsay <atl@comp.lancs.ac.uk>
wrote:
> But wait, where are you coming from? Are your source fonts really Minion
> .pfbs, or are they from OpenType? With OpenType, you can use some nice
> TeXFont stuff to select the features (OSF, SC, alternates) without having
> to draw from two arbitrary encodings.
I am very interested in the Open Type trickery. I have been wrestling for
quite some time about the problem of multiple accents over ligatures in
Arabic. I can do it in Aleph but the present procedure (due originally to
Yannis) is much too slow and cumbersome, especially when dealing with huge
fonts (my present virtual ovf has about 10,000 characters!). I finally
found a solution that OpenType might help with--multiple glyphs for one
character. I can implement this without OpenType, but OpenType opens the
possiblity for word searches in Acrobat of Arabic text, something that is
well-nigh impossible with the usual pfb approach.
While we will still need huge fonts, the processing of complicated accents
should be much faster with the approach I have in mind (smaller otp's and
ovf's). Do you think TeXFont can be tweaked to generate ovf's and ofm's as
well?
Take care
Idris
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next prev parent reply other threads:[~2005-04-10 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-09 22:30 Idris Samawi Hamid
2005-04-09 23:22 ` Adam Lindsay
2005-04-10 1:17 ` Idris Samawi Hamid
2005-04-10 1:27 ` Idris Samawi Hamid [this message]
2005-04-10 15:29 ` Open Type trickery [was " Adam Lindsay
2005-04-10 17:31 Idris Samawi Hamid
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=opsozszvyhu9mfh0@lamar.colostate.edu \
--to=ishamid@colostate.edu \
--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).