ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: E-books and XML.
Date: Thu, 28 Aug 2014 15:34:23 +0200	[thread overview]
Message-ID: <53FF2FDF.4010900@wxs.nl> (raw)
In-Reply-To: <252EE179-5D8F-4E30-9493-B73DF04817CD@fiee.net>

On 8/28/2014 12:54 PM, Henning Hraban Ramm wrote:
> Am 2014-08-28 um 14:22 schrieb Hans Hagen <pragma@wxs.nl>:
>>> <div class="document xmlns:m-http://www.w3.org/1998/Math/MathML date-Thu Aug 28 14:00:55 2014 author-Henning Hraban Ramm, fiëé visuëlle version-0.31 title-Gestammelte Werke context-2014.08.27 11:51 file-prd_hraban language-de xmlns:xhtml-http://www.w3.org/1999/xhtml">
>>
>> that one is already fixed
>
> good
>
>>>   <div class="division detail-frontpart">
>>>    <div class="metadata">
>>>     <div class="metavariable name-author">Henning Hraban Ramm, fiëé visuëlle</div>
>>
>> those are is okay as a class can have multiple names and the attribute-name prefix can be used for further css detailing ... so we export both xthml old style (using tags, something that browsers understand) and xhtml new style (something that epub devices might be able to handle)
>
> Ok, I don’t care, will continue to use the XML.
>
> Next issue:
>
> I just recognized there’s a problem with references, esp. register:
>
> ....
>      <section detail="Titel" location="aut:2">
>       <sectiontitle>Erinnerung </sectiontitle>
> ....
>         <registerentry>Erinnerung</registerentry>
>         <registerpages>         <break/>
> <registerpage><link destination="internal(3)" location="aut:3">4</link></registerpage></registerpages>
> ....
>         <registerentry>Vor meinem inn’ren Auge schweben Namen</registerentry>
>         <registerpages>         <break/>
> <registerpage><link destination="internal(4)" location="aut:4">4</link></registerpage></registerpages>
>
> (These are title and start of lyrics of a song.)
>
> Beside the inconvenience that there is no node wrapping registerentry and registerpages, the locations don’t match.
> If there are several index entries pointing to the same point (page), as here, they’re continuously numbered, so that it’s no solution to just subtract 1, as I do at the moment to create my ToC.
>
> Maybe the internal location numbers mean something, but I need a working reference; export.xml doesn’t know anything about pages, therefore the destination makes no sense. Doesn’t ConTeXt have some unique internal reference name?

the internals are the unique ones

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2014-08-28 13:34 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 [this message]
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
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=53FF2FDF.4010900@wxs.nl \
    --to=pragma@wxs.nl \
    --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).