Re: [NTG-context] Bug in export with \definehighlight
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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bug in export with \definehighlight
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 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] Bug in export with \definehighlight
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 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Bug in export with \definehighlight
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 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___