From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: E-books and XML.
Date: Fri, 29 Aug 2014 17:46:19 +0600 [thread overview]
Message-ID: <F15453B5-692A-4D8F-962F-E13CF57AE433@fiee.net> (raw)
In-Reply-To: <54005331.4060603@wxs.nl>
Am 2014-08-29 um 16:17 schrieb Hans Hagen <pragma@wxs.nl>:
>> Thank you for caring, the tag hierarchy is good now, but why did you leave out the locations now?
>> I need some connection between register entry and the origin to be able to create a link.
>> I can’t use the page numbers, since they don’t exist in the XML (and of course they make no sense there).
>
> There is probably some more cleanup to do with respect to referencing (like with lists) but it takes time (till now I never really needed the export which started as a quick and dirty experiment and normally I need usage in projects to spend real time on such things.)
>
> Anyway. I've added some more register stuff, but not yet in the default css where the register is simply ignored (no time for that now).
Thank you, I’ll see what I can make out of it. (I’ll try to trace every reference back to the chapter level, where I split output HTML files.)
> Maybe we should make a todo list for the export. It's not that complex but just takes time.
Is there already a solution for \em (or \emph) and other switches? They don’t show up in export.xml.
Greetlings, Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2014-08-29 11:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 15:07 john Culleton
2014-08-26 15:10 ` Wolfgang Schuster
2014-08-26 17:08 ` Henning Hraban Ramm
2014-08-26 17:29 ` Hans Hagen
2014-08-27 7:02 ` Henning Hraban Ramm
2014-08-27 9:05 ` Hans Hagen
2014-08-27 9:25 ` Henning Hraban Ramm
2014-08-27 9:37 ` Hans Hagen
2014-08-27 9:46 ` Henning Hraban Ramm
2014-08-27 10:06 ` Hans Hagen
2014-08-28 8:10 ` Henning Hraban Ramm
2014-08-28 8:22 ` Hans Hagen
2014-08-28 10:54 ` Henning Hraban Ramm
2014-08-28 13:34 ` Hans Hagen
2014-08-28 13:35 ` Hans Hagen
2014-08-28 17:39 ` Hans Hagen
2014-08-29 6:33 ` Henning Hraban Ramm
2014-08-29 10:17 ` Hans Hagen
2014-08-29 11:46 ` Henning Hraban Ramm [this message]
2014-08-29 12:46 ` Hans Hagen
2014-08-30 7:56 ` Henning Hraban Ramm
[not found] ` <540AEA44.2080106@wxs.nl>
[not found] ` <540C26D3.1020101@wxs.nl>
2014-09-13 7:29 ` Henning Hraban Ramm
2014-08-27 9:03 ` Henning Hraban Ramm
2014-08-26 18:04 ` Hans Hagen
2014-08-26 18:12 ` Thomas A. Schmitz
2014-08-27 14:03 ` XML as source (was: E-books and XML) Procházka Lukáš Ing. - Pontex s. r. o.
2014-08-27 18:40 ` Jan Tosovsky
2014-08-28 17:02 ` Mica Semrick
2014-08-27 14:38 ` E-books and XML john Culleton
2014-08-27 16:15 ` Schmitz Thomas A.
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=F15453B5-692A-4D8F-962F-E13CF57AE433@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).