Re: [NTG-context] problems with XML export

On 11/12/2017 05:06 PM, Alan Braslau wrote: > [...]> Whereas I might want to export systematically, Hans suggests that one > should export in a separate run using modes for example. This is not a > bad idea, but I would NOT want to have to then make a third run to fix > the "broken" PDF. This

Re: [NTG-context] problems with XML export

Hans made some changes a while ago. Enabling export, floats are handled differently, notably side floats become location=here. Hans tells me that this derives from how the xml export is constructed, and this makes handling certain bugs with the export possible. I have urged Hans to consider, if

Re: [NTG-context] problems with XML export

On 11/12/2017 09:33 AM, Henning Hraban Ramm wrote: > Am 2017-11-11 um 19:46 schrieb Pablo Rodriguez: >> \definehighlight[read][color=red, style=\sc] >> [...] >> I guess you have to use this instead of \color[]{}. > > Yes, I guess too. I remembered highlight suits color after sending, > but that

Re: [NTG-context] problems with XML export

Am 2017-11-11 um 19:46 schrieb Pablo Rodriguez : > On 11/11/2017 06:30 PM, Henning Hraban Ramm wrote: >> Here are a few problems that I encountered in my current ePub projects: >> >> * \color[]{} leaves no trace in export. > > Hi Hraban, > > this works with PDF, it should work

Re: [NTG-context] problems with XML export

On 11/11/2017 06:30 PM, Henning Hraban Ramm wrote: > Here are a few problems that I encountered in my current ePub projects: > > * \color[]{} leaves no trace in export. Hi Hraban, this works with PDF, it should work with ePub: \definehighlight[read][color=red, style=\sc] \starttext

[NTG-context] problems with XML export

Here are a few problems that I encountered in my current ePub projects: * \color[]{} leaves no trace in export. * As soon as I activate export, my PDFs get two pages more, i.e. page breaking changes somehow, I didn’t yet track how. * For quotability, I’d like to set markers in my HTML, where