From: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: setups within typescripts: can it be done?
Date: Tue, 12 Mar 2013 19:37:31 -0600 [thread overview]
Message-ID: <op.wtu2stxdpw6hmh@ishamid-pc> (raw)
In-Reply-To: <513FCFEA.1070708@wxs.nl>
Hi Hans,
Thanks for the reply:
On Tue, 12 Mar 2013 19:01:30 -0600, Hans Hagen <pragma@wxs.nl> wrote:
> On 3/11/2013 5:51 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
>> Dear gang,
>>
>> Here is the situation: For an upcoming book project I may use a set of
>> proprietary fonts whose license that does not allow modification even
>> for personal, private use. Some characters I need are absent, but the
>
> I'd choose another font.
LOL.
If you're referring to the private-use restriction: Adobe allows
private/personal modifications for most fonts, so I could get away with
making small fallbacks, etc. In the end, I may very well go with a company
like Adobe for just this reason.
(On the other hand, all of their optical sized book fonts are made by the
same designer and have the same feel ... I'd like to try something
different if I can find it).
If you're referring to finding a font that has all the requisite
characters: Hardly any HQ commercial text font for books has the requisite
characters (mostly but not all in the Latin Extended Additional block).
TeX-Gyre has the chars (I lobbied for them some years ago) but for the
current project T-G is not really an option.
>> components I need are there (macrons, dots, etc). So I can conceivably
>> use \defineactivecharacter to map each needed unicode char to a \def
>> made of glyph components in the font.
>
> there is a 'compose' feature that does some virtual magic ...
Yes, I tried that a long time ago; will try again, though more precision
will be needed, especially for italic etc..
> it's also possible to specify things in a lfg file .. here is a copy
> from an upcoming manual:
<snip>
Yaay, I look forward to reading that! I was thinking that the goodies file
would be the ideal place to put the specs.
> Of course this assumes some knowledge of the font metrics (in base
> points) and
> \UNICODE\ slots, but it might be worth the trouble. After all, one only
> needs to
> figure it out once. But keep in mind that it will always be a kludge.
>
> A slightly different way to define such compositions is the following:
<snip>
Ok, I'll study that as well
> Of course no one really needs this because \OPENTYPE\ Lucida fonts
> have replaced the \TYPEONE\ versions.
Indeed. OTOH, I just found this wonderful (+very-expensive) Dutch typeface
that is still(!) only available in Type1/ttf format.
Thanks again and
Best wishes
Idris
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-03-13 1:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 16:51 Idris Samawi Hamid ادريس سماوي حامد
2013-03-13 1:01 ` Hans Hagen
2013-03-13 1:37 ` Idris Samawi Hamid ادريس سماوي حامد [this message]
2013-03-13 9:09 ` 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=op.wtu2stxdpw6hmh@ishamid-pc \
--to=ishamid@colostate.edu \
--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).