From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: typescript repository
Date: Thu, 26 Mar 2009 10:29:14 +0100 [thread overview]
Message-ID: <F04657DC-1257-4B19-A9DA-A1ADD52798FD@gmail.com> (raw)
In-Reply-To: <20090326091347.GC8620@phare.normalesup.org>
Am 26.03.2009 um 10:13 schrieb Arthur Reutenauer:
>> anyhow, this repos / table ... can we also add info about features
>> and to
>> what extend they are supported? i.e. the quality of the feature
>> support in
>> a font an dmaybe the defaults?
>
> Oh yes, that would be great. Seeing the output of otfinfo -f, or
> anything equivalent, would be immensively helpful in the choice of a
> font.
This is what I want to do with my fontbook project, a book with samples
of free fonts (left side all style plus features, right side example
text).
Adobe provides a font with a few symbols of opentype features
The document is in a earyl state and I try to automate large parts
(save font
related information like name, feature, typescript etc. in a lua table
or xml
file) and to find a better example text (english, continued text, the
gutenberg
project offers nice texts).
[1] http://bitbucket.org/wolfs/fontbook/
[2] http://www.fontspace.com/adobe/otf-icons (can't find the original
link from Adobe)
Wolfgang
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-26 9:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 20:30 Wolfgang Schuster
2009-03-23 20:32 ` luigi scarso
2009-03-23 21:20 ` Curiouslearn
2009-03-23 21:44 ` Peter Münster
2009-03-23 21:46 ` Aditya Mahajan
2009-03-23 21:51 ` Mohamed Bana
2009-03-23 22:11 ` Wolfgang Schuster
2009-03-24 15:27 ` Bruce D'Arcus
2009-03-24 17:39 ` Wolfgang Schuster
2009-03-25 3:08 ` Bruce D\'Arcus
2009-03-25 3:31 ` Mohamed Bana
2009-03-25 11:51 ` Wolfgang Schuster
2009-03-25 13:37 ` Mohamed Bana
2009-03-25 14:33 ` Wolfgang Schuster
2009-03-25 14:42 ` Mohamed Bana
2009-03-26 9:35 ` Henning Hraban Ramm
2009-03-26 10:00 ` Wolfgang Schuster
2009-03-24 23:14 ` Idris Samawi Hamid ادريس سماوي حامد
2009-03-25 7:24 ` Marcin Borkowski
2009-03-25 13:52 ` Bruce D\\\'Arcus
2009-03-25 14:30 ` Marcin Borkowski
2009-03-26 9:04 ` Hans Hagen
2009-03-26 9:13 ` Arthur Reutenauer
2009-03-26 9:23 ` luigi scarso
2009-03-26 9:29 ` Wolfgang Schuster [this message]
2009-03-26 9:50 ` Hans Hagen
2009-03-25 14:40 ` Wolfgang Schuster
2009-03-23 22:00 ` Diego Depaoli
2009-03-23 22:00 ` luigi scarso
2009-03-24 10:17 ` Alan Stone
2009-03-25 20:43 ` Wolfgang Schuster
2009-03-26 18:38 ` Mohamed Bana
2009-03-26 18:44 ` Aditya Mahajan
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=F04657DC-1257-4B19-A9DA-A1ADD52798FD@gmail.com \
--to=schuster.wolfgang@googlemail.com \
--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).