From: "Christoph Hintermüller via ntg-context" <ntg-context@ntg.nl>
To: mastermind_ x via ntg-context <ntg-context@ntg.nl>
Cc: "Christoph Hintermüller" <christoph@out-world.com>
Subject: Few quick questions
Date: Tue, 08 Mar 2022 20:45:17 +0100 [thread overview]
Message-ID: <47b198f885e97699b0e71b5e72e6705211d320de.camel@out-world.com> (raw)
Hi
I'm still stuck with also providing my lecture notes as epub in addtion
to its PDF version.
The last year, when I tried figure what is wrong, Hans indicated a
tool, a program, which allows to verify that that all start* stop* tag
pairs are symmetric and placed in correct order. I just cant remember
how it is called. Can anybody help here?
Second are there any limits in how large files exproted to XML, XHTML
etc can be. Does the exporter automatically try to split huge documents
into multiple exported documents when some size is exceeded or was or
is such a feature allways experiemental up to mkIV and what could break
proper slitting which contexts, commands should not be active to avoid
breakage.
My current setup is neither a fresh install of latest standalone nor
texlive installation. This task is still pending. I just have done some
partial update mixing 2020 Texlife with 2021 standlalone by calling
update.sh. So the aborting of the export in the middle of a hundred
pages long document with plenty of floats and the heavy use of Aditya's
t-vim package might additionally be worsened by some inconsistencies of
my currently not clean installation. But to rule out or properly tackle
down I think I believe knowing about possible Limitations of exporter
in mkIV if any to be saving a lot of time
The abort in xml export also occurs when i inline all files exempt t-
vim code snippets, png or svg files replacing meta post images into one
huge document removing any \input commands. Therefore i want to check
first on the inlined document if there would by any asymetric start*
stop* before persuing further.
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2022-03-08 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 19:45 Christoph Hintermüller via ntg-context [this message]
2022-03-08 20:26 ` Marco Patzer via ntg-context
2022-03-09 10:21 ` Christoph Hintermüller via ntg-context
2022-03-09 16:26 ` Christoph Hintermüller via ntg-context
2022-03-09 16:36 ` Hans Hagen via ntg-context
2022-03-08 19:54 Christoph Hintermüller via ntg-context
2022-03-08 20:00 ` Rik Kabel via ntg-context
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=47b198f885e97699b0e71b5e72e6705211d320de.camel@out-world.com \
--to=ntg-context@ntg.nl \
--cc=christoph@out-world.com \
/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).