From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Marco <melmothx@gmail.com>
Subject: Re: Missing <break/> while exporting to xml before <highlight>
Date: Mon, 07 Nov 2011 09:13:29 +0100 [thread overview]
Message-ID: <4EB79329.7010200@wxs.nl> (raw)
In-Reply-To: <87y5vsid27.fsf@universe.krase.net>
On 7-11-2011 08:53, Marco wrote:
> Hans Hagen<pragma@wxs.nl> writes:
>
>> On 6-11-2011 21:38, Marco Pessotto wrote:
>>>
>>> Hi!
>>>
>>> The highlight seems to act strangely. In addition to the previous
>>> report, I get an unwanted<break/>:
>>>
>>> %%% start example
>>> \setupbackend[export=yes]
>>> \definehighlight[emph][style=italic]
>>>
>>> \starttext
>>>
>>> \section{test}
>>>
>>> \emph{Hello} world!
>>>
>>> \stoptext
>>> %%% stop example
>>
>> It has to do with the way grouping interferes with the start of a paragraph
>>
>> \dontleavehmode \emph ...
>>
>> I'll make highlights horizontal by default
>
> It works, thanks a bunch. The previous missing<break/> seems to be
> fixed wrapping the paragraph with \startparagraph \stopparagraph. I
> assume this is the right thing to do for a proper export, isn't it?
Indeed. On and off I'm trying to make the automatic recognition more
clever but too much guessing is bad too.
> Btw, is there a way to run context just for the xml output (as I'm doing
> conditional runs, and I discard the pdf which comes with the xml as a
> side effect). context --help doesn't seem to have an option for
> that. Well, not so important, just asking.
Currently not. It would also complicate matters as we need to flush some
information in the pdf backend that is needed in following passes.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-11-07 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 13:54 Marco Pessotto
2011-11-06 20:38 ` Marco Pessotto
2011-11-06 23:26 ` Hans Hagen
2011-11-07 7:53 ` Marco
2011-11-07 8:13 ` Hans Hagen [this message]
2011-11-07 8:35 ` highlight problems on xml export (Was: Missing <break/> while exporting to xml before <highlight>) Marco Pessotto
2011-11-07 16:48 ` highlight problems on xml export [hacky workaround included] Marco Pessotto
2011-11-05 15:13 ` Aditya Mahajan
2011-11-07 17:07 ` Marco Pessotto
2011-11-07 17:49 ` Hans Hagen
2011-11-07 18:02 ` Marco Pessotto
2011-11-08 16:04 ` highlight problems on xml export Marco Pessotto
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=4EB79329.7010200@wxs.nl \
--to=pragma@wxs.nl \
--cc=melmothx@gmail.com \
--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).