ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco <melmothx@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Missing <break/> while exporting to xml before <highlight>
Date: Mon, 07 Nov 2011 08:53:04 +0100	[thread overview]
Message-ID: <87y5vsid27.fsf@universe.krase.net> (raw)
In-Reply-To: <4EB7178A.80304@wxs.nl> (Hans Hagen's message of "Mon, 07 Nov 2011 00:26:02 +0100")

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?

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.

Thanks again

Best wishes

-- 
Marco
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2011-11-07  7:53 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 [this message]
2011-11-07  8:13       ` Hans Hagen
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=87y5vsid27.fsf@universe.krase.net \
    --to=melmothx@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).