From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: storm font
Date: Wed, 20 Apr 2005 17:59:37 +0200 [thread overview]
Message-ID: <42667C69.4080804@seznam.cz> (raw)
In-Reply-To: <425C0916.9060706@wxs.nl>
Hi fonTeXters,
I have incorporated your suggestions to storm-font-support:
A) ---------------
Adam Lindsay wrote:
> Okay, I noticed a second thing, in the [serif][cond][size] and other
> [size] typescripts: you define things like \tfc with the intention of
> "typeface-condensed". This will interfere with people who rely on the
and Hans Hagen wrote:
> when i have to deal with that i just define another typeface:
>
> \definetypeface[blabla-normal] ...
> \definetypeface[blabla-condensed] ...
I split Lido font to
1) Lido
2) Lido-Condensed
B) ----------------
Adam Lindsay wrote:
> A general suggestion--you might experiment with the [special]
> typescripts in type-spe as a way of loading the mathcollections.
Incorporated, so \input t-math-sto.tex \usemathcollection[storm]
is no more needed; just e.g.
\useencoding[st1]
\useencoding[st3]
\usetypescriptfile[t-type-slido]
\usetypescript[Lido][st2]
\setupbodyfont[Lido,10pt,rm]
C) --------------------
Hans Hagen wrote:
> Taco Hoekwater wrote:
>>
>> Patrick, my vote is against a separate interface for this. Perhaps
>> split the stuff at modules.cg.net into modules/fonts/docs/packages
>> subtrees, but I really like the 'central repository' idea.
>
> the only thing about user typescripts and modules is that we need to
> make sure that names don't clash; so for instance, a user typescript
> can be something
>
> t-type-xxx.txx
OK, I changed all typescripts in this way. But still there are some
files that do not fit this concept:
a) redistributed files (storm.map, slido.map, stormex.enc)
b) enco-*.tex files since \useencodings has not enabled loading
t-enco-*.tex yet (something like \useencoding[t][st1]).
D) -----------------------
Adam Lindsay wrote:
> it could be a way of supporting an encoding like TS1, if people really
> still cared about that.
TS1 is texnansi??? Why ec (=st1) is not sufficient? You can setup
regime... If you persuade me I will prepare some enco-st4.tex(??) =
texnansi for storm fonts.
Patrick Gundlach wrote:
> If you think of a clever way, please tell me where/how to put your
> typescripts + .. on garden. I could even add a new section:
> fonts.contextgarden.net if this sounds appropriate for collecting
> stuff like yours.
I think it is a good idea. So please... After that I will write some
words or two about the package and upload you the files. Is it OK?
G) -------------------------
Examples of mathbold (where bold font is available) were added to the
catalog.
F) -------------------------
Some bug fixes namely in t-type-slido.tex and t-type-sbiblon.tex.
Upgraded version is available from
http://typokvitek.com/stormcontext/index.html
Vit
next prev parent reply other threads:[~2005-04-20 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 21:17 Vit Zyka
2005-04-11 7:38 ` Patrick Gundlach
2005-04-11 11:13 ` Adam Lindsay
2005-04-12 11:43 ` Adam Lindsay
2005-04-12 12:27 ` Vit Zyka
2005-04-12 14:37 ` Adam Lindsay
2005-04-12 17:44 ` Hans Hagen
2005-04-20 15:59 ` Vit Zyka [this message]
2005-04-20 16:13 ` 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=42667C69.4080804@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).