From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug in export with \definehighlight
Date: Tue, 11 Oct 2011 23:26:08 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1110112323550.12928@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <alpine.LNX.2.02.1110112242510.12928@ybpnyubfg.ybpnyqbznva>
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-10-12 3:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 3:40 Aditya Mahajan
2011-10-12 2:43 ` Aditya Mahajan
2011-10-12 3:26 ` Aditya Mahajan [this message]
2011-10-12 8:15 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.02.1110112323550.12928@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).