XeTeX typescripts in ver: 2007.07.24
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 (I'll put a bit of the log file at the end). However, everything is fine when the typescript is changed to read like this. \starttypescript[serif][minion][uc] \definefontsynonym [MinionRegular] ['Minion Pro'] [encoding=uc] \stoptypescript Here's what looks to me to be the relevant part of the log. systems : begin file article at line 1 (/Users/michaelgreen/Library/texmf/tex/context/article.tex (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-exa.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-syn.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-enc.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-siz.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-map.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-spe.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-akb.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-xtx.tex) (/Users/michaelgreen/Library/texmf/tex/context/myfonts.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-exa.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-syn.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-enc.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-siz.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-map.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-spe.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-akb.tex) (/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-xtx.tex) (/Users/michaelgreen/Library/texmf/tex/context/myfonts.tex) ! Font \*minion12ptrmtfrm*:='"mapping=tex-text;+onum; at 12.0pt"' not loadable: installed font not found. ("myfonts.tex" is a file of typescripts for system fonts, made to match the those in the "creating your own typescripts section of the wiki page: http://wiki.contextgarden.net/Fonts_in_XeTeX). Perhaps the old functionality being replaced with something different. Thanks. Michael Green
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
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
Thomas A. Schmitz wrote:
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,
correct
My experiments suggest that these can be found via the [file:<filename>] mechanism, but I can't append any "mapping" or other specials.
almost certainly correct. While nearly everything (except the engine-options) is supported by XeTeX's low-level interface, I expect that context would interpret such a specification as if you were asking for the file "minionpro:mapping=tex-test.otf", and it would therefore generate the wrong low-level syntax.
2. This syntax will go away soon, so it's no use spending time on experiments.
definately correct. Best wishes, Taco
participants (3)
-
Michael Green -
Taco Hoekwater -
Thomas A. Schmitz