ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Michael Saunders <odradek5@gmail.com>
To: ntg-context@ntg.nl
Subject: typescripts
Date: Wed, 17 Mar 2010 07:16:26 -0500	[thread overview]
Message-ID: <54d7f5601003170516q76f5d740w1c789c31c2903b4@mail.gmail.com> (raw)

Wolfgang Schuster:


> You can apply only *one* feature to \definefontfeatures.

I've seen examples like this:
\definefontfeature
 [fea]
 [mode=node,language=dflt,script=arab,
  init=yes,medi=yes,fina=yes,isol=yes,
  liga=yes,dlig=yes,rlig=yes,tlig=yes,
  calt=yes,trep=yes,mark=yes,mkmk=yes,
  kern=yes,curs=yes]
so I think you mean to say that I can apply only one feature to
\definefontsynonym or to \definetypeface.  I tried this and it
checks out.  Thanks---it's nice to see hz working.  Protrusion is
only on the right margin?

> > 2. As far as I can tell from trying to decode examples, there is some
> > hidden connection between the first arguments of the second typescript
> > block and the font switches.  So, for example, a secret connection
> > between SerifBoldItalic and \bi seems to connect Junicode-BoldItalic
> > to \bi.  Fine, but, in all the examples I've seen, there are no more
> > than two weights and no widths.  In some cases, I have five weights
> > (light, book, medium, semi-bold, bold).  How do I set up the
> > typescript for this and the switches in the text?  Must I learn more
> > pairs like (SerifBoldItalic, \bi)?

You need more typefaces. One for light, another one for condensed etc.



------------------------------

Mojca Miklavec:

>> Must I learn more pairs like (SerifBoldItalic, \bi)?

> Yes, but there are not many (tf, it, sl, bf, bi, bs, sc) and I assume
> that they are extensible. See also below.

> > You need more typefaces. One for light, another one for condensed etc.

> Maybe I'm wrong, but shouldn't it be possible (I didn't test) to
> modify font-unk.mkiv and add a few extra definitions to the following?
> (Maybe not modify font-unk itself, but just adding a couple of more
> definitons to the typescript.)
>
> \definebodyfont [default] [rm]
>  [tf=Serif sa 1,
>   bf=SerifBold sa 1,
>   it=SerifItalic sa 1,
>   sl=SerifSlanted sa 1,
>   bi=SerifBoldItalic sa 1,
>   bs=SerifBoldSlanted sa 1,
>   sc=SerifCaps sa 1]
>
> You could add your
>  in=SerifYourFontVariantName sa 1,
>  bd=SerifYourOtherFontVariantName sa 1,
>
> And then
>   \definefontsynonym[SerifYourFontVariantName][YourFontName]

> It's true that most people don't do that, but I see no reason for not
> extending the model for your particular needs.

Mojca


------------------------------

Wolfgang Schuster:

> The last time i did this you needed for MkIV also
>
> \definefontalternative[in]
> \definefontalternative[bd]
>
> but be carefull with the shortcuts, \in is already used (references).



Thank you both.  I want to begin experimenting with this, but there's
one thing that still confuses me.  If I have a font with say, forty different
combinations of weight/width/shape (5x4x2), I will need to come up with
forty different pairs like:
myNewFontSwitch=SerifMyFontVariantName sa 1,
a strain on the poetic imagination, but possible.
It would be nicer though, if I could change weight/width/shape independently
of each other (then I need have only 5+4+2 switches).  For example, when
I see something like:
\rm\tf roman \it italic \bf bold
resulting in:
<book roman> <book italic> <bold roman>,
it's surprising to see that \bf has turned off the italic---you don't
expect a switch
of the weight to have a hidden switch of the shape in it.  Could the typescript
be set up with fewer switches, so that:
\rm\tf roman \it italic \bf bold
would result in:
<book roman> <book italic> <bold italic>,
or, e.g.,
\rm\tf (regular book roman) \cd (condensed) \it (italic) \bf (bold)
would result in:
<regular book roman> <condensed book roman> <condensed book italic>
<condensed bold italic>?



(Also, I'm hoping that having a dozen different sets of font features won't
require twelve times as many switches and feature names as this.  I think
there is some easier method for switching---Hans mentioned \addff{}, but
I can't find anything in the docs.  If that works, that would make two kinds
of switches, one for some kinds of features and another for other kinds.)
___________________________________________________________________________________
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
___________________________________________________________________________________


             reply	other threads:[~2010-03-17 12:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 12:16 Michael Saunders [this message]
2010-03-17 12:34 ` typescripts Wolfgang Schuster
2010-03-18  0:04 ` typescripts Wolfgang Schuster
  -- strict thread matches above, loose matches on Subject: below --
2010-11-12 14:32 typescripts Herbert Voss
2010-11-12 16:29 ` typescripts Herbert Voss
2010-11-12 16:54   ` typescripts Hans Hagen
2010-11-12 16:57 ` typescripts Hans Hagen
2010-11-12 17:41   ` typescripts Herbert Voss
2010-11-12 17:46     ` typescripts Hans Hagen
     [not found]       ` <4CDD80A7.7040803@FU-Berlin.DE>
     [not found]         ` <4CDD8246.2020206@wxs.nl>
2010-11-12 20:39           ` typescripts Herbert Voss
2010-11-10 18:57 typescripts Herbert Voss
2010-11-10 20:28 ` typescripts Mojca Miklavec
2010-11-10 21:14   ` typescripts Herbert Voss
2010-11-11  5:20   ` typescripts Wolfgang Schuster
2010-11-11 11:03     ` typescripts Mojca Miklavec
2010-11-11 11:27       ` typescripts Hans Hagen
2010-11-11 14:15         ` typescripts Mojca Miklavec
2010-03-18 20:42 typescripts Michael Saunders
2010-03-18  1:32 typescripts Michael Saunders
2010-03-18  9:53 ` typescripts Wolfgang Schuster
2010-03-18 10:04 ` typescripts Wolfgang Schuster
2010-03-17  1:26 typescripts Michael Saunders
2010-03-17  8:20 ` typescripts Wolfgang Schuster
2010-03-17  9:04   ` typescripts Mojca Miklavec
2010-03-17  9:11     ` typescripts Wolfgang Schuster
2010-03-17 11:33       ` typescripts Mojca Miklavec
2010-03-17 12:12         ` typescripts Wolfgang Schuster
2003-08-16 20:05 typescripts Henning Hraban Ramm

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=54d7f5601003170516q76f5d740w1c789c31c2903b4@mail.gmail.com \
    --to=odradek5@gmail.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).