ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XeTeX typescripts in ver: 2007.07.24
Date: Thu, 2 Aug 2007 15:47:29 +0200	[thread overview]
Message-ID: <4728FEE0-87F4-400A-9523-C8707FB3BB81@uni-bonn.de> (raw)
In-Reply-To: <46B19570.8020909@elvenkind.com>


On Aug 2, 2007, at 10:27 AM, Taco Hoekwater wrote:

> The main problem is the explicit ":" in the definition above. The  
> latest
> context parses the string for the appearance of "name:" and  
> "file:", and
> for that it checks for explicit colons.  This change was introduced
> when ConTeXT started supporting the new XeTeX way of specifying a
> (non-installed) OpenType font by its filename.
>
> Either this:
>
>     [name:Minion Pro\xetexcolon mapping=tex-text;+onum;]
>
> or this:
>
>     ['Minion Pro\xetexcolon mapping=tex-text;+onum;']
>
> should work (I defined \xetexcolon in type-xtx.tex).
>
> Yes, this is a backward incompatible change. But: the syntax with
> inlined feature specifications will be removed in the near future
> anyway (to be replaced by separately defined "font features"), so
> IMO there is not much point in spending time now on fixing the
> current behaviour.
>
> All the best,
> Taco

Hi Taco,

just so I'm sure I understand (I play with XeTeX from time to time,  
but usually give up after 20 minutes because I find it more trouble  
than it seems worth):

1. The syntax [name:Minion Pro\xetexcolon mapping=tex-text;+onum;]  
will only work for installed fonts, not for opentype fonts that are  
in the texmf-tree, but not system fonts. My experiments suggest that  
these can be found via the [file:<filename>] mechanism, but I can't  
append any "mapping" or other specials.

2. This syntax will go away soon, so it's no use spending time on  
experiments.

Thanks

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
___________________________________________________________________________________


  reply	other threads:[~2007-08-02 13:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01 22:03 Michael Green
2007-08-02  8:27 ` Taco Hoekwater
2007-08-02 13:47   ` Thomas A. Schmitz [this message]
2007-08-02 14:24     ` Taco Hoekwater
2007-08-02 15:03       ` Thomas A. Schmitz

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=4728FEE0-87F4-400A-9523-C8707FB3BB81@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).