From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: proposed convention for variation switching [wasRE:inheriting ...
Date: Fri, 22 Apr 2005 00:43:06 +0200 [thread overview]
Message-ID: <42682C7A.3070606@seznam.cz> (raw)
In-Reply-To: <20050421205604.33@mail.comp.lancs.ac.uk>
Adam Lindsay wrote:
>
> It's not that I'm trying to rain on your parade, it's just that I've lost
> a bit of enthusiasm for standardisation.
I generally agree with Adam, fonts are very varios. But the next Idris
idea is nice. More intuitive then \sc, \bc, \ic, and \bic. I would vote
for it, but ... at least \sc needs some backward compatibility :-(
>>%% small caps
>>% medium \TF
>>% bold \BF
>>% italic \IT
>>% bold italic \BI
Another discussion proposal: I will get the rest font families from
Storm to make the support complete. So I will have to solve many similar
problems with naming conventions. So I am interesting about some
recommendations. What way to solve via
A) variants via \Var[...]
B) \tf, \bf, ... switches,
C) different font family.
For now I am using:
A) for extended glyph definitions and old style digits {Var[os]} (if
they are not default in the font - in that case there might be reverse
normal style digit variant \Var[ns?]).
B) standard 4 + small caps + symbols/ornaments designed to the font {\sy}
C) condensed, extended, medium, ...
Some comments?
Cheers,
vit
next prev parent reply other threads:[~2005-04-21 22:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 18:36 Idris Samawi Hamid
2005-04-21 19:56 ` Adam Lindsay
2005-04-21 22:43 ` Vit Zyka [this message]
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
2005-04-21 23:53 Idris Samawi Hamid
2005-04-22 8:45 ` Vit Zyka
2005-04-22 9:03 ` Taco Hoekwater
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=42682C7A.3070606@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).