From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: New typescript mechanism for weights/opticals?
Date: Wed, 22 Sep 2010 17:28:25 +0200 [thread overview]
Message-ID: <20100922172825.6756f2ed@vorbis> (raw)
In-Reply-To: <4C99F01D.6090902@wxs.nl>
On 2010-09-22 Hans Hagen <pragma@wxs.nl> wrote:
> On 22-9-2010 1:35, Marco wrote:
> > Hi,
> >
> > I like Mojcas idea for new typescripts:
> >
> > %%%%%%%%%%%
> > \startsomenewfonttypescriptcommand [kepler]
> > [width={condensed,semicondensed,*regular,extended}]
> > [size={caption,*regular,subhead,display},switch={10pt,12pt,17pt}]
> > [weight={light,*regular,medium,semibold,*bold,black}]
> > ...
> > %%%%%%%%%%%
> > \switchtofontdimension[width=semicondensed,weight={light,medium}]
> > %%%%%%%%%%%
>
> sure. looks nice, but the outcome is quite unpredictable unless you know
> the font and that in turn demands some investiation on the users end
I think some user investiation will always be necessary since the vendors
dont't follow the same schema and every font collection is different.
>
> > That would make different weight/opticals font handling much less
> > cumbersome. At the moment its no fun dealing with weights/opticals.
>
> it will never be fun ... (in most cases one will use suggested
> combinations and then for odd cases like a section title something special)
Don't be that pessimistic ;-) Selecting the proper font *is* fun.
> > I really would appreciate that (or any other easy usable) solution that
> > provides a standardized way to handle weights/opticals with not too much
> > overhead.
>
> given the huge differences in font collections there will never be an
> easy way with fonts that come in many weights/widths/sizes .. at least I
> cannot remember a project that I did where any system was present
That's a true point. But I think there is room for improvements. ConTeXt
supports a standardized interface for Bold/Sans/Italic/Slanted... font
variants and it lacks an interface for (more) weights/widths.
Of course the person setting up the (whatever variant of) typescript(s) has to
do some investiation about the font. But after that the user should be
provided with standardized commands for the weights/widths.
Regards
Marco
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-09-22 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 11:35 Marco
2010-09-22 12:01 ` Hans Hagen
2010-09-22 15:28 ` Marco [this message]
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=20100922172825.6756f2ed@vorbis \
--to=netuse@lavabit.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).