![](https://secure.gravatar.com/avatar/c5ae4f9aa0d3a9bd5376e92b322c3e50.jpg?s=120&d=mm&r=g)
Compiling the following document ~~~ \definehighlight [object] [style=mono] \setupbackend [export=yes] \starttext \object{test} \stoptext ~~~ gives backend > export > saving xml data in 'test.export backend > export > saving css image definitions in 'test-images.css backend > export > saving css style definitions in 'test-styles.css ! LuaTeX error bad argument #3 to '?' (value expected). system > tex > error on line 0 in file : LuaTeX error ... <empty file> <*> ./test \stoptext Aditya
![](https://secure.gravatar.com/avatar/c5ae4f9aa0d3a9bd5376e92b322c3e50.jpg?s=120&d=mm&r=g)
On Mon, 10 Oct 2011, Aditya Mahajan wrote:
Compiling the following document
~~~ \definehighlight [object] [style=mono]
\setupbackend [export=yes]
\starttext \object{test} \stoptext ~~~
gives
backend > export > saving xml data in 'test.export backend > export > saving css image definitions in 'test-images.css backend > export > saving css style definitions in 'test-styles.css ! LuaTeX error bad argument #3 to '?' (value expected).
system > tex > error on line 0 in file : LuaTeX error ...
<empty file>
<*> ./test \stoptext
Quick workaround: use \definestartstop instead of \definehighlight. Aditya
![](https://secure.gravatar.com/avatar/c5ae4f9aa0d3a9bd5376e92b322c3e50.jpg?s=120&d=mm&r=g)
On Tue, 11 Oct 2011, Aditya Mahajan wrote:
On Mon, 10 Oct 2011, Aditya Mahajan wrote:
Compiling the following document
~~~ \definehighlight [object] [style=mono]
\setupbackend [export=yes]
\starttext \object{test} \stoptext ~~~
gives
backend > export > saving xml data in 'test.export backend > export > saving css image definitions in 'test-images.css backend > export > saving css style definitions in 'test-styles.css ! LuaTeX error bad argument #3 to '?' (value expected).
system > tex > error on line 0 in file : LuaTeX error ...
<empty file>
<*> ./test \stoptext
Quick workaround: use \definestartstop instead of \definehighlight.
The "bug" is with xml.css.fontspecification function that does not handle style=mono (or sans and serif for that matter). The proper solution is to convert from context font specification into html font specification for all styles. Aditya
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
On 12-10-2011 05:26, Aditya Mahajan wrote:
The "bug" is with xml.css.fontspecification function that does not handle style=mono (or sans and serif for that matter). The proper solution is to convert from context font specification into html font specification for all styles.
I've added mono/type, sans/sanserif and serif parsing (in next beta). Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (2)
-
Aditya Mahajan
-
Hans Hagen