From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: showfont with xetex (syntax changed?)
Date: Thu, 06 Dec 2007 14:48:55 +0100 [thread overview]
Message-ID: <4757FDC7.5050103@wxs.nl> (raw)
In-Reply-To: <6faad9f00712060332s32be7922yf9b7e7788b4197f4@mail.gmail.com>
Mojca Miklavec wrote:
> But generally, LuaTeX is much more suitable for such previews (only
> that there might be no "newshowfont" available yet - writing one is
> doable if you know what you're interested in).
>
> My two cents: ConTeXt currenty uses
> smcp=yes,script=latn,onum=yes,liga=yes...
> while fontspec uses either
> Letters=SmallCaps
> Script=Latin
> Numbers=OldStyle
> Ligatures=Common
> or the same raw names as above. I would prefer the "human-readable"
> names as in fontspec, but ... well, the font calling mechanisms really
> need to improve in my opinion.
> What fontspec achieves in one line like (copying from XeTeX list):
> \setmainfont[Script=Devanagari]{Sanskrit 2003}
> needs dozens of lines in ConTeXt (definefontfeature, define
> typescripts in two steps, ... brrrr)
>
> So in case that some more features in XeTeX/LuaTeX change, do not be
> surprised too much ...
keep in mind that xetex and mkiv support will not be the same in all
those aspects; i more or less expect users to use one or the other
engine and then become familiar with its specific interfaces
anyhow, a next version of mkiv will support more verbose options,
script=slovenian
smallcaps=true
basically anything in the script, language and feature hashes
(lowercased and de-spaced when compared)
something numbers=oldstyle could be supported but i see no real reason
for it since then we end up in endless lists of possibilities (given all
kind of combinations)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-12-06 13:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 10:26 Steffen Wolfrum
2007-12-06 11:32 ` Mojca Miklavec
2007-12-06 13:48 ` Hans Hagen [this message]
2007-12-06 14:30 ` Steffen Wolfrum
2007-12-06 14:37 ` Wolfgang Schuster
2007-12-06 15:50 ` Steffen Wolfrum
2007-12-06 17:33 ` Wolfgang Schuster
2007-12-06 17:58 ` Hans Hagen
2007-12-07 19:09 ` Hans Hagen
2007-12-09 12:13 ` Wolfgang Schuster
2007-12-10 12:09 ` Hans Hagen
2007-12-10 12:20 ` Wolfgang Schuster
2007-12-07 19:08 ` Hans Hagen
2007-12-06 16:30 ` Mojca Miklavec
2007-12-07 9:29 ` Hans Hagen
2007-12-07 9:33 ` Hans Hagen
2007-12-06 14:23 ` Wolfgang Schuster
2007-12-07 19:07 ` Hans Hagen
2007-12-06 15:43 ` Steffen Wolfrum
2007-12-06 16:09 ` Steffen Wolfrum
2007-12-06 16:35 ` Mojca Miklavec
2007-12-06 16:59 ` Steffen Wolfrum
2007-12-06 17:36 ` Wolfgang Schuster
2007-12-06 17:45 ` Wolfgang Schuster
2007-12-06 17:55 ` Hans Hagen
2007-12-06 20:14 ` Steffen Wolfrum
2007-12-06 20:32 ` 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=4757FDC7.5050103@wxs.nl \
--to=pragma@wxs.nl \
--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).