]
# \definemeasure
# \defineoutput[name][specials]
\defineoverlay[names][command]
# \definepagebreak
\definepalet[name][name]
\definepapersize[name][dimenstions]
\defineparagraphs[name][options and settings]
\defineprofile[names][names]
\defineprogram[name][text][text]
# \definepushbutton
# \definepushsymbol
running into problems:
\resetspecials
\defineoutput [xetex] [xtx]
\setupoutput[xetex]
\usetypescriptfile [type-xtx]
\definetypeface[Hoe][rm][serif][hoefler] [default][encoding=unicode]
\setupbodyfont [Hoe,rm]%
\setupcolor[state=start]
\starttext
{\red test}
\stoptext
! Undefined control sequence
, a temporary workaround is
replacing the following:
\resetspecials
\defineoutput [xetex] [xtx]
\setupoutput[xetex]
...with:
\setupoutput[dvipdfmx]
It's not entirely accurate, but XeTeX now supports 85% of the important
dvipdfmx specials, so the next spec-xtx will inherit from dvipdfmx.
best,
adam
even gets set, there. A
minimal-but-complete test file (that would work with pdfetex, say) could
be really helpful in terms of getting the feature going on my end...
Cheers,
adam
\resetspecials
\defineoutput [xetex] [xtx]
\setupoutput[xetex]
...with:
\setupoutput[dvipdfmx]
It's
