From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: XeTeX and OpenType LM
Date: Wed, 31 Jan 2007 20:12:59 +0100 [thread overview]
Message-ID: <45C0EA3B.1020703@wxs.nl> (raw)
In-Reply-To: <7E5493F1-197C-484E-92FB-7A48552BA85E@sil.org>
Jonathan Kew wrote:
>
> Font names and font filenames are quite different, in many cases, and
> it didn't seem wise to mix them up and allow the exact same form of
> the \font declaration to access either one. This could lead to
> ambiguity and confusion in the case where a filename does happen to
> be the same as a font name.
>
> As for why square brackets.... why not? :) We just needed a way to
> distinguish filenames from font names, and this seemed a reasonably
> safe choice -- unlikely to be present in a real font name, and not
> usually given special treatment in TeX.
>
hm, but square brackets can interfere with optional args where [] don't
nest well (tex does not treat them as delimiters as it does {}
using {} would probably have been safer or maybe () (round ones) since
afaik these are seldom used for delimiting args; or maybe just
file:somename
anyhow, if it's filename stuff i can probably just feed the [] deep down
in context to the xetex font command
will think of something
please forward to jonathan since his mailer an dmy mail server don;t
like each other -)
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
-----------------------------------------------------------------
next prev parent reply other threads:[~2007-01-31 19:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 4:44 Mojca Miklavec
2007-01-31 11:09 ` Hans Hagen
2007-01-31 16:58 ` Mojca Miklavec
2007-01-31 17:16 ` Jonathan Kew
2007-01-31 19:12 ` Hans Hagen [this message]
2007-02-02 8:26 ` Hans Hagen
2007-02-02 13:23 ` Mojca Miklavec
2007-02-02 13:50 ` Hans Hagen
2007-02-02 15:40 ` Mojca Miklavec
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=45C0EA3B.1020703@wxs.nl \
--to=pragma@wxs.nl \
--cc=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).