Help figuring why long document stops short in xml export
Hi What command line parameters, trackers etc I should activate when i want to figure why my document lacks content worth of several pages in xml export while the pdf which is created in parallel contains all pages. I'm using mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: <prefixpath>/tex/texmf- context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2021.02.14 16:39 mtx-context | main context file: <prefixpath>/tex/texmf- context/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2021.02.14 16:39 Would switching to lmtx may be helpful in at least figuring why or be the only known solution? The Document it self is my lecture notes which are about 125 Pages long. The xml export ends at Page 63. Are there any known commands which can cause exporter to give up early and thus should in export be avoided or be put in mode dependent block hiding them form exporter. Any hint what i should, would have to check and how to hopefully grabe any hint where to amend the document to get full output. Currently i have not made images mode dependent (pdf:metapost, xml:png/svg). Could that be a reason why exporter finally ends document early? I'm sorry to be so clue less to not be able to provide more information. The document it self is too big to be posted and i do not want to make it public anyway, but if required i can provide a share link. Best Christoph Hintermüller
On 2/24/2021 10:42 AM, Christoph Hintermüller wrote:
I'm sorry to be so clue less to not be able to provide more information. The document it self is too big to be posted and i do not want to make it public anyway, but if required i can provide a share link. You can try to comment some code to see where it fails/succeeds: make a copy and start wiping stuff. Normally that quickly reveals where it goes wrong.
Indeed some real data is needed to see where it fails. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
Hi On Wed, 2021-02-24 at 11:24 +0100, Hans Hagen wrote:
On 2/24/2021 10:42 AM, Christoph Hintermüller wrote:
I'm sorry to be so clue less to not be able to provide more information. The document it self is too big to be posted and i do not want to make it public anyway, but if required i can provide a share link.
You can try to comment some code to see where it fails/succeeds: make a copy and start wiping stuff. Normally that quickly reveals where it goes wrong.
I hoped so too. But the only i figured that it stops between two sections. If i comment the whole set of sections which seem to contain offending content. Than it simply stops at some later section. And if i remove the set before the one seemingly offending it still stops at the section it stopped in the first instant. If there happens to be some pattern i'm not experienced enough to notice it.
Indeed some real data is needed to see where it fails.
May i later send a sharing link to the full sources from our university systems, may be you immediately see what makes it hickup. Best Christoph
Hi On Wed, 2021-02-24 at 15:16 +0100, Christoph Hintermüller wrote:
I hoped so too. But the only i figured that it stops between two sections. If i comment the whole set of sections which seem to contain offending content. Than it simply stops at some later section. And if i remove the set before the one seemingly offending it still stops at the section it stopped in the first instant. If there happens to be some pattern i'm not experienced enough to notice it.
I don't know if that is likely to be related at all, if i insert \showlayout at the beginning of the document the hickup occurs after later section than if it is not present, even if the section it initially stopped is include in the document. Best Christoph
On 2/24/2021 3:16 PM, Christoph Hintermüller wrote:
May i later send a sharing link to the full sources from our university systems, may be you immediately see what makes it hickup. sure,
Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
On Wed, 2021-02-24 at 15:49 +0100, Taco Hoekwater wrote:
On 24 Feb 2021, at 10:42, Christoph Hintermüller < christoph@out-world.com> wrote:
Hi What command line parameters, trackers etc I should activate when i
There is
\enabletrackers[export.*]
Thanks. Not sure if related at all but if i add that to the document i do get the following error. It hicksup at \stopstandardmakeup if i remove the stanard makeup it hicksup at frontmatter etc. I think that has something to do with tracker and not the document itself.If i remove everything up to \stopfrontmatter than it runs until the first custom defined float and again yields the same error. If i explicitly not select export.trace.details no hickup. -------------------------registered function call [188]: ...cal/tex/texmf-context/tex/context/base/mkiv/back-exp.lua:3052: attempt to index a nil value (field '?') stack traceback: ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3052: in upvalue 'showdetail' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3067: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ... (skipping 5 levels) ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3330: in upvalue 'collectresults' ...cal/tex/texmf-context/tex/context/base/mkiv/back- exp.lua:3423: in upvalue 'nodes_handlers_export' [string "local tonut = nodes.tonut..."]:30: in function <[string "local tonut = nodes.tonut..."]:13> (...tail calls...) [string "/usr/local/tex/texmf-context/tex/context/base..."]:34: in function <[string "/usr/local/tex/texmf- context/tex/context/base..."]:33> (...tail calls...) 58 \definemathcommand[ld][nolop]{\mfunction{ld}} 59 \setupcaption[lefthangingfigure][width=\textwidth,align=figure] 60 \setupheadtext[content=Inhalt] 61 %\traceexternalfilters 62 \enabletrackers[export.*] 63 64 \starttext 65 \startstandardmakeup 66 \title{Programmiertechnik 2} 67 \subsubject{Dr. Christoph Hintermüller} 68 >> \stopstandardmakeup 69 \startfrontmatter 70 \completecontent 71 %\placecombinedlist[content] 72 \stopfrontmatter 73 \startbodymatter 74 75 %\showlayout 76 \input ObjektorientierteProgrammierung 77 \placefloats 78 \input DatenStrukturen--------------------------------- Best Xristoph
participants (3)
-
Christoph Hintermüller -
Hans Hagen -
Taco Hoekwater