From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: problems with XML export
Date: Sun, 12 Nov 2017 09:33:00 +0100 [thread overview]
Message-ID: <D6D390C9-13E4-4042-A253-BF393D2D11ED@fiee.net> (raw)
In-Reply-To: <547259de-ba6d-497b-54ad-bf6d15806cda@gmx.es>
Am 2017-11-11 um 19:46 schrieb Pablo Rodriguez <oinos@gmx.es>:
> 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[]{}.
Yes, I guess too. I remembered highlight suits color after sending, but that means I need to define a new highlight for every color - as semantic as that may be, it’s a PITA.
>> * 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.
Of course. I still didn’t check what changes at all.
>> * 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.
At the state where it exports XML, ConTeXt already knows about page breaks, doesn’t it?
>> * 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.
No, that was my question in the thread "insert tags in export xml".
\definehighlight only supports style and color, but not command.
I tried to understand its definition and found \dostarttagged, but I guess I used it the wrong way, since it breaks the tabulation.
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2017-11-12 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 17:30 Henning Hraban Ramm
2017-11-11 18:46 ` Pablo Rodriguez
2017-11-12 8:33 ` Henning Hraban Ramm [this message]
2017-11-12 10:29 ` Pablo Rodriguez
2017-11-12 16:06 ` Alan Braslau
2017-11-12 16:49 ` Pablo Rodriguez
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=D6D390C9-13E4-4042-A253-BF393D2D11ED@fiee.net \
--to=texml@fiee.net \
--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).