From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: latest release(s) and XeTeX
Date: Sun, 20 Jan 2008 17:45:07 +0100 [thread overview]
Message-ID: <6faad9f00801200845l6c8d9cd3w6f05235bfd4bfe1f@mail.gmail.com> (raw)
In-Reply-To: <AC599AFE-0266-4C48-9DDA-EADD3984A7B4@uni-bonn.de>
On Jan 20, 2008 7:57 AM, Thomas A. Schmitz wrote:
>
> Thanks Mojca, that worked! Now that I have your attention, may I ask
> another question: a couple of months ago, I was wondering about using
> fonts that are NOT installed on the system but are in one of the texmf-
> trees. In typescripts, we have the "name:" and "file:" syntax; the
> latter works with these fonts but seems to have some limitations (I
> attach a reply Taco wrote). Has anything new developed on this
> question?
Yes. See type-otf.tex:
\definefontsynonym
[LMRoman10-Regular]
[file:lmroman10-regular]
[features=default]
features=default is defined in font-ini.tex:
\definefontfeature
[default]
[liga=yes,kern=yes,tlig=yes,trep=yes] % texligatures=yes,texquotes=yes
tlig=yes is than mapped to
\remapfontfeature tlig yes mapping=tlig
Note that "mapping=tlig" replaces "mapping=tex-text" (maybe it might
make sense to call it "mapping=tex-ligatures", I don't know which one
sounds better), which replaces -- with endash, --- with emdash and '
with the proper apostrophe. The rest of sligtly weird "ligatures" from
tex-text is not there.
Mojca
(I somehow still miss a sligtly more simple syntax for the whole
typescript, but I have no idea what that could be.)
___________________________________________________________________________________
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:[~2008-01-20 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 17:05 Thomas A. Schmitz
2008-01-19 18:15 ` Aditya Mahajan
2008-01-19 22:54 ` Otared Kavian
2008-01-19 23:40 ` Mojca Miklavec
2008-01-20 6:57 ` Thomas A. Schmitz
2008-01-20 16:45 ` Mojca Miklavec [this message]
2008-01-20 22:04 ` Thomas A. Schmitz
2008-01-20 22:43 ` Hans Hagen
2008-02-13 3:41 ` Jeff Smith
2008-02-13 8:21 ` Taco Hoekwater
2008-02-13 12:10 ` Mojca Miklavec
2008-02-15 2:24 ` Jeff Smith
2008-02-15 11:59 ` Mojca Miklavec
2008-02-15 16:05 ` Jeff Smith
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=6faad9f00801200845l6c8d9cd3w6f05235bfd4bfe1f@mail.gmail.com \
--to=mojca.miklavec.lists@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).