ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Issues of Export
Date: Sat, 15 Aug 2015 17:20:57 +0600	[thread overview]
Message-ID: <66003438-9473-4F6D-A7F4-0108ABDC470E@fiee.net> (raw)
In-Reply-To: <55C8DD9F.90202@wxs.nl>

Hi, finally coming back...

Am 2015-08-10 um 23:21 schrieb Hans Hagen <pragma@wxs.nl>:

> On 8/10/2015 10:30 AM, Henning Hraban Ramm wrote:
>> As listed on http://wiki.contextgarden.net/Export
>> 
>> Open Export issues as of 2014-01-20, still valid 2015-08-08
>> 	• Structure bug: Metadata ends up within the first section instead of in front of everything
> 
> ok, fixed for document level ... keep in mind that setting metadata always relates to the next element

Thanks, for me it’s good now.

>> 	• Names of metavariables are missing in div.xhtml
> ok, i've added something

Works. Not that important anyway.

>> 	• Notes (footnotes): Only visual formatting, no semantical markup and no reference/ID
> boring, so todo

Hey, I thought TeX would be about semantical markup? At the moment the markup for footnotes is purely graphical - a marker in the text, and the footnote somewhere later (where it appears on the printed page). E.g.

Bla bla<descriptionsymbol detail="footnote"><sup>1</sup></descriptionsymbol> bla bla ba <break/>...<description detail="footnote" chain="footnote"><descriptiontag><sup>1</sup> </descriptiontag><descriptioncontent>This is the footnote text</descriptioncontent></description>

That makes no sense and is very hard to process, even using xsl.
I would suggest to stay with the source flow instead of the output, if possible. E.g. markup like

Bla bla<description detail="footnote" id="1" tag="1">Footnote text</description>

The id would be some internal id (I guess there is one?), the tag the footnote marker (as of \setupnotes).
Is that not possible and even simpler than the current version?

>> 	• Delimited: Quotations have tagging *and* quotation marks, even in raw.xml
> i added symbol and content element

Less would be enough, but works this way.

>> 	• Firstpage/Lastpage is ignored in project structure
> fuzzy, so todo

The keywords are defined in setup, I don’t understand where they get forgotten.

>> 	• Minimal example doesn’t create a cover at all
> no beta yet

? Is this intentional, or what triggers the creation of cover.xhtml?

Greetlings, Hraban
---
http://www.fiee.net
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
___________________________________________________________________________________

  reply	other threads:[~2015-08-15 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10  8:30 Henning Hraban Ramm
2015-08-10 17:21 ` Hans Hagen
2015-08-15 11:20   ` Henning Hraban Ramm [this message]
2015-08-21 17:30     ` Hans Hagen
2015-08-27  9:33       ` Henning Hraban Ramm
2015-08-27 19:04         ` Hans Hagen

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=66003438-9473-4F6D-A7F4-0108ABDC470E@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).