From: Antoine Junod <toto@tots-ns.net>
To: ntg-context@ntg.nl
Subject: typescript
Date: Sat, 19 Apr 2008 13:06:48 +0200 [thread overview]
Message-ID: <87lk3axfw7.fsf@zapata.tots-ns.net> (raw)
Hello, List!
Follownig your recommendations while playing with fonts, I've started
to write one. It's actually very basic but I already have a few
questions. Here is the basic, working stuff I did until now:
\starttypescript[serif][garamondpp]
\definefontsynonym [GaramondPP-Roman] [GaramondPremrPro]
\definefontsynonym [GaramondPP-Bold] [GaramondPremrPro-Bd]
\definefontsynonym [GaramondPP-Italic] [GaramondPremrPro-It]
\definefontsynonym [GaramondPP-Bold-Italic][GaramondPremrPro-BdIt]
\stoptypescript
If I've understood what I did in that part, I've simply defined alias
for the font file names. What I do not catch is the \starttypescript
line. Is it right to say that the second parameter is the name of the
'class' to which the definitions that follow are linked? Second
question on that part: Is the first argument (serif) a reserved
keyword or not? What's the point of that argument? Third and last
question for that part, in the case, as in here, where the font file
names are easy to remember, is it still needed to create that synonyms
for any reason?
Then, I wrote the [name] part of the typescript, as the following:
\starttypescript[serif][garamondpp][name]
\definefontsynonym [Serif] [GaramondPP-Roman]
\definefontsynonym [SerifBold] [GaramondPP-Bold]
\definefontsynonym [SerifItalic] [GaramondPP-Italic]
\definefontsynonym [SerifSlanted] [SerifItalic]
\definefontsynonym [SerifBoldItalic] [GaramondPP-Bold-Italic]
\stoptypescript
If I caught the point of the last argument, it is here to indicate
that what follows links font files to the pre-defined font concept
that are Serif, SerifBold, SerifItalic and so on and so on). Here are
my questions: I've seen in the sources that there were 7 predefined
types in the Serif family: Serif, SerifBold, SerifItalic,
SerifSlanted, SerifBoldItalic and SerifBoldSlanted. What if I have a
font that not only have a Bold face but also a Medium face and a
SemiBold face? Second question: my font do not have a slanted face and
I do not want to have pieces of computer modern in the text because,
by mistake, I typed an \sl switch or something related. To avoid that,
you can see I declared SerifSlanted to be a synonym for
SerifItalic. Is it the way to do that or is it better to directly
define SerifSlanted as a synonym to GaramondPP-Italic (in my case)?
And for the last part of my little type script:
\starttypescript [GaramondPP]
\definetypeface [GaramondPP][rm][serif][garamondpp][default]
\stoptypescript
That part is for me a beautiful piece of ununderstanding :) First
question: the first argument is the name we will use with the
\usetypescript command. Right? Second question: the first argument of
the \definetypescript is the name that will be used with the
\setupbodyfont call. Is it right? Isn't there any conflict with the
GaramondPP of the \starttypescript and the one of the \definetypeface?
Or do they need to be the same? Other question: how are related the
three following parameters (rm, serif and garamondpp)? And finally,
what's the point of the 'default' argument?
I'm aware that's a huge load of questions. Nothing is urgent but every
replies are welcome, and that will allow me to help others. More
questions will certainly occurs later (certainly related to sizes) but
at first I'll try to better understand all what is above.
Thanks a lot for everything!
A+
-AJ
___________________________________________________________________________________
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 reply other threads:[~2008-04-19 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 11:06 Antoine Junod [this message]
2008-04-19 13:13 ` typescript Hans Hagen
2008-04-19 16:39 ` typescript Aditya Mahajan
2008-04-19 17:12 ` typescript Henning Hraban Ramm
2010-03-15 21:32 typescript Michael Saunders
2010-03-15 21:35 ` typescript Aditya Mahajan
2010-03-15 21:42 ` typescript Hans Hagen
2010-03-15 21:46 ` typescript Philipp Gesang
2010-03-15 21:55 ` typescript Hans Hagen
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=87lk3axfw7.fsf@zapata.tots-ns.net \
--to=toto@tots-ns.net \
--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).