ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: proposed convention for variation switching	[wasRE:inheriting ...
Date: Fri, 22 Apr 2005 10:45:54 +0200	[thread overview]
Message-ID: <4268B9C2.1010505@seznam.cz> (raw)
In-Reply-To: <4278A2EE@webmail.colostate.edu>

Idris Samawi Hamid wrote:
 >
> Let's keep \sc. After all, ConTeXt already contains many redundancies (and 
> that's a good thing imho->)

Yes.

> (I think that \Var[up] (for upright figures) is more intuituve that \Var[ns]), 
> at least in English:-)))

I agree, both Adams's \Var[lf] and Idris's \Var[up] is better then my 
ns. I prefer 'lf', since a) it is related to figures, b) 'up' can be mix 
up with upshape/slanted.

> % lowercase
> light \lf 
> medium \tf
> semibold \sb
> bold \bf
> lightitalic \lt
> italic \it
> semibold italic \st
> bold italic \bi

What about:
light \lf
medium \mf
semibold \sf
bold \bf
lightitalic \li
italic \it
semibold italic \si
bold italic \bi
It is more intuitive, is't it?

I checked if they have not been occupied yet and at least in en 
interface it is OK.

vit

  parent reply	other threads:[~2005-04-22  8:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 23:53 Idris Samawi Hamid
2005-04-22  1:11 ` fontsite 500 CD Ciro Soto
2005-04-22  8:45 ` Vit Zyka [this message]
2005-04-22  9:03   ` proposed convention for variation switching [wasRE:inheriting Taco Hoekwater
  -- strict thread matches above, loose matches on Subject: below --
2005-04-21 18:36 Idris Samawi Hamid
2005-04-21 19:56 ` Adam Lindsay
2005-04-21 22:43   ` Vit Zyka
2005-04-21 23:00     ` Adam Lindsay
2005-04-22  8:16   ` Hans Hagen
2005-04-22  9:38     ` Vit Zyka
2005-04-22 14:36     ` Idris Samawi Hamid
2005-04-22 14:55       ` Adam Lindsay
2005-04-22 17:13         ` Idris Samawi Hamid
2005-04-21 19:59 ` Adam Lindsay

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=4268B9C2.1010505@seznam.cz \
    --to=vit.zyka@seznam.cz \
    --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).