Michael Green wrote:
> In ver: 2007.01.12, a typescript like this works fine:
>
> \starttypescript[serif][minion][uc]
> \definefontsynonym [MinionRegular] ['Minion Pro:mapping=tex-text;
> +onum;'] [encoding=uc]
> \stoptypescript
>
> We get Minion Pro, mapping TeX markup to unicode characters and old-
> style numbers.
> This seems not to work in ver: 2007.07.24: the font can't be found
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
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : [email protected] / 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
___________________________________________________________________________________
