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