From: Marco Patzer <lists@homerow.info>
To: ntg-context@ntg.nl
Subject: Re: Cyrillic replacement for TeX Gyre Schola?
Date: Sat, 24 Aug 2013 16:18:39 +0200 [thread overview]
Message-ID: <20130824141839.GS18239@homerow> (raw)
In-Reply-To: <707C9959-8E96-43B8-9155-E292BB67F1F0@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 647 bytes --]
On 2013–08–24 Wolfgang Schuster wrote:
> I can’t reproduce your problem with the features key.
I was surprised that your example was running here, and I noticed
that a space makes all the difference:
%% fails
\definefontsynonym [Serif] [file:texgyrescholaregular] [features=default, fallbacks=cyrillic_regular]
%% works
\definefontsynonym [Serif] [file:texgyrescholaregular] [features=default,fallbacks=cyrillic_regular]
^^^
> To set the features for the fallback font I would use \
> definefontsynonym.
Makes more sense, yes.
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-08-24 14:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 5:16 Henning Hraban Ramm
2013-08-23 12:00 ` Marco Patzer
2013-08-23 14:54 ` Henning Hraban Ramm
2013-08-23 16:33 ` Marco Patzer
2013-08-23 16:44 ` Marco Patzer
2013-08-24 5:12 ` Wolfgang Schuster
2013-08-24 11:38 ` Marco Patzer
2013-08-24 14:00 ` Wolfgang Schuster
2013-08-24 14:18 ` Marco Patzer [this message]
2013-08-24 14:24 ` Wolfgang Schuster
2013-08-24 5:10 ` 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=20130824141839.GS18239@homerow \
--to=lists@homerow.info \
--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).