From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: problems with XML export
Date: Sun, 12 Nov 2017 11:29:22 +0100 [thread overview]
Message-ID: <356023fa-8a1b-0bae-83c9-15eeb2e648c7@gmx.es> (raw)
In-Reply-To: <D6D390C9-13E4-4042-A253-BF393D2D11ED@fiee.net>
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 means I need to define a new highlight for every color - as
> semantic as that may be, it’s a PITA.
I wonder whether Hans would accept a patch with these definitions to be
applied in the ConTeXt source.
> [...]
> At the state where it exports XML, ConTeXt already knows about page
> breaks, doesn’t it?
You are right. I have almost no experience generating ePubs with ConTeXt
(trying your sample was one of my first attempts to generate an ePub
document with ConTeXt [I use pandoc for that]).
>> [...]
>> Try the approach proposed above. I think it should work.
>
> No, that was my question in the thread "insert tags in export xml".
Sorry, I overlooked that message.
> \definehighlight only supports style and color, but not command.
I wonder whether this is the right approach.
I mean, you could only (ab)use the style option:
\setupbackend[export=yes]
\definehighlight[read][style=\word\sc]
\starttext
\starthighlight[read] ROT ROT ROT\stophighlight
\stoptext
Other approach would be to use your own CSS file:
.read { text-transform: lowercase; font-variant: small-caps; }
In any case, you need to add the small caps to the class definition in
the CSS file. ConTeXt doesn’t seem to export \sc to anything in the CSS
file.
> I tried to understand its definition and found \dostarttagged, but I
> guess I used it the wrong way, since it breaks the tabulation.
I guess custom CSS is an easier approach.
Just in case it helps,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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 10:29 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
2017-11-12 10:29 ` Pablo Rodriguez [this message]
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=356023fa-8a1b-0bae-83c9-15eeb2e648c7@gmx.es \
--to=oinos@gmx.es \
--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).