From: Andreas Harder <aharder@uni-koblenz.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Header spoils X(HT)ML export
Date: Tue, 6 Dec 2011 23:19:15 +0100 [thread overview]
Message-ID: <C64E2B17-9B5D-48F6-8D48-80239619D8BC@uni-koblenz.de> (raw)
Hi Hans,
please consider the following example.
\setupbackend[export=yes,xhtml=yes,css=yes]
\setupheadertexts[{\startelement[header] test \stopelement}]
\starttext
\startbuffer
\startparagraph
\input tufte
\stopparagraph
\startparagraph
\input ward
\stopparagraph
\stopbuffer
\startsection[title=first head]
\getbuffer
\stopsection
\startsection[title=second head]
\getbuffer
\stopsection
%% try to comment this section
\startsection[title=third head]
\getbuffer
\stopsection
\stoptext
The section-title order is now 3, 1, 2 (in the XHTML output). This problem appears only if there is a page break. After commenting the last section the XHTML output looks like expected.
Best wishes
Andreas
PS. I’ve encountered another export problem. Perhaps it is because of an not intending using of \settaggedmetadata … Here is an example.
\setupbackend[export=yes,xhtml=yes,css=yes]
\startsetups document:start
\settaggedmetadata[title=\documentvariable{title}]
\stopsetups
\startdocument
[title=This document title is wrapped in section-tags]
\startsection[title=test]
\startparagraph
\input tufte
\stopparagraph
\stopsection
\stopdocument
___________________________________________________________________________________
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 reply other threads:[~2011-12-06 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 22:19 Andreas Harder [this message]
2011-12-09 17:28 ` 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=C64E2B17-9B5D-48F6-8D48-80239619D8BC@uni-koblenz.de \
--to=aharder@uni-koblenz.de \
--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).