From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ePub issues: XML structure
Date: Fri, 6 Mar 2020 09:33:33 +0100 [thread overview]
Message-ID: <D5EA603F-AAA6-457A-9C4A-8473FE5B5A42@fiee.net> (raw)
In-Reply-To: <55F998CD-9570-4B52-8C01-C03A9F9DD9FC@fiee.net>
> Am 2020-03-04 um 07:55 schrieb Henning Hraban Ramm <hraban@fiee.net>:
>
> While the first book in a series of four is now ready with a lot of manual corrections, in the second one the XML structure is messed up: the chapter title structure comes only after the chapter content, and index entry tags are empty with the actual entry behind like this:
>
> <paragraph>Ein sentimentales Rührstück ist <highlight detail="emph">Rico, Oskar und die Tieferschatten</highlight> dennoch nicht. Die beiden Hauptdarsteller <registerlocation detail="index" internal="396"></registerlocation>Anton Petzold (Rico) und <registerlocation detail="index" internal="397"></registerlocation>Juri Winkler (Oskar) füllen ihre Rollen ganz wunderbar aus...</paragraph>
>
> In ConTeXt code I marked the actors with
> \def\NPers#1#2{\index{#2, #1}#1 #2}
> as \NPers{Anton}{Petzold}.
>
> But since that just uses \index, the XML tag should catch the contents, don’t you think?
Coming back to this. I recognized that of course the name behind </registerlocation> is completely correct and according to my definition of \NPers.
But the content of \index (here: "Petzold, Anton") is still missing, while the command creates this <registerlocation> structure.
Since you (Hans) say the export only looks at the output, then it makes sense that is empty, since there’s nothing to see.
Actually my XSLT already looks for the <registerentry>:
<registerentry>
<registercontent>Petzold, Anton</registercontent>
<registerpages><registerpage><link destination="internal(396)" location="396" prefix="c_anhang">76</link></registerpage><registerseparator>,</registerseparator><registerpage><link destination="internal(406)" location="406" prefix="c_anhang">77</link></registerpage></registerpages>
</registerentry>
And the lookup actually works, so I don’t know why I’m complaining. Didn’t understand my own workflow any more.
Now to solve the title structure mystery…
Best, Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-03-06 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 6:55 Henning Hraban Ramm
2020-03-04 8:58 ` Hans Hagen
2020-03-11 19:59 ` Henning Hraban Ramm
2020-03-11 21:42 ` Axel Kielhorn
2020-03-12 7:09 ` Henning Hraban Ramm
2020-03-12 11:58 ` Axel Kielhorn
2020-03-06 8:33 ` Henning Hraban Ramm [this message]
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=D5EA603F-AAA6-457A-9C4A-8473FE5B5A42@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).