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 this need be so, that the PDF file
produced when export is enabled NOT overwrite a PDF that might have
been produced in a run where export was not enabled. The easiest in my
opinion would be for this PDF to be placed in the filename-export/
sub-directory, leaving filename.pdf (if exists) untouched. Hans
answered that he would have to think about this as it would break his
present workflow where he runs context from his (Scite) editor and
relies looking at the PDF to see certain results.
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 would be a nightmare in bookkeeping and prone to
errors.
Alan
On Sat, 11 Nov 2017 19:46:21 +0100
Pablo Rodriguez <oi...@gmx.es> wrote:
> 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
> \starthighlight[read] rot\stophighlight
> \stoptext
>
> I guess you have to use this instead of \color[]{}.
>
> > * As soon as I activate export, my PDFs get two pages more, i.e.
> > page breaking changes somehow, I didn’t yet track how.
>
> Without minimal sample and invocation command, it is rather hard to
> reproduce the issue.
>
> > * For quotability, I’d like to set markers in my HTML, where the
> > print version has page breaks. But the exported XML doesn’t contain
> > anything like that. Is it possible to add?
>
> Just out of curiosity, I wonder how this could be achieved.
>
> Do you have other approach than the following?
>
> 1. Complete PDF compilation with saving of page breaks.
>
> 2. Add the markers in XML code generation.
>
> > * Errors in exported XML:
> > [...]
> > (2)
> > \def\SC#1{\dostarttagged{highlight}{scaps}{\sc\lowercase{#1}}\dostoptagged}
> > [...]
> > - <highlight> breaks <tabulatecell> (maybe my \SC definition is bad,
> > but nobody answered to my according question)
>
> Try the approach proposed above. I think it should work.
>
> I hope it helps,
>
> Pablo
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
