From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: luatex and typescripts/fonts
Date: Wed, 29 Aug 2007 16:07:49 +0200 [thread overview]
Message-ID: <73A9C4C0-194B-4E29-855B-5A58E91180FA@uni-bonn.de> (raw)
In-Reply-To: <46D55E06.40909@wxs.nl>
Wolfgang, Hans,
thanks a lot for your replies, that was extremely helpful.
On Aug 29, 2007, at 1:52 PM, Hans Hagen wrote:
>
> one option is to make two versions (name.mkii and name.mkiv) and
> then in
> the name.tex file say \loadmarkfile{name} which will choose the right
> variant then
>
Ah, so \loadmarkfile is the magic switch. I had the idea to use .mkii
and .mkiv but couldn't figure out how to. Now that's very useful for
all further experiments...
> depends on the way you define things ... maybe the kerning is language
> dependent? kern is a feature
>
> in base mode, we use tex's kerning and ligatures and can only have
> simple replacement, in node mode, mkiv does everything itself
>
Okay, I tried this minimal definition in my typescript:
\definefontfeature
[jens]
[mode=node,kern=yes]
\starttypescript [serif] [jenson]
\definefontsynonym [Jenson-Roman] [name:AJensonPro-
Regular] [features=jens] \stoptypescript
\starttypescript [serif] [jenson]
\definefontsynonym [Serif] [Jenson-Roman] [features=jens]
\stoptypescript
\starttypescript [Jenson]
\definetypeface [Jenson] [rm] [serif] [jenson] [default]
\stoptypescript
But still no joy: I don't get any kerning. Tried with all sorts of
settings for script= and language=, but to no avail.
Thomas
___________________________________________________________________________________
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 prev parent reply other threads:[~2007-08-29 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 11:05 Thomas A. Schmitz
2007-08-29 11:28 ` Wolfgang Schuster
2007-08-29 11:52 ` Hans Hagen
2007-08-29 14:07 ` Thomas A. Schmitz [this message]
2007-08-29 16:29 ` Hans Hagen
2007-08-29 17:21 ` Hans Hagen
2007-08-29 17:49 ` Thomas A. Schmitz
2007-08-29 18:51 ` Hans Hagen
2007-09-03 8:08 ` Wolfgang Schuster
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=73A9C4C0-194B-4E29-855B-5A58E91180FA@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).