Few quick questions

Few quick questions

[Christoph Hintermüller via ntg-context]

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
___________________________________________________________________________________

Re: Few quick questions

[Marco Patzer via ntg-context]

On Tue, 08 Mar 2022 20:45:17 +0100
Christoph Hintermüller via ntg-context <ntg-context@ntg.nl> wrote:

> 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?

  mtxrun --autogenerate --script check <file>

The following will not report missing tags but will find other
common issues and report them on the console:

  context --errors='*' <file>

Marco
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Few quick questions

[Christoph Hintermüller via ntg-context]

Sorry for multi posting. Had yesterday a problem with my mail system
and was not sure if mail was sent at all.


On Tue, 2022-03-08 at 21:26 +0100, Marco Patzer via ntg-context wrote:
> On Tue, 08 Mar 2022 20:45:17 +0100
> Christoph Hintermüller via ntg-context <ntg-context@ntg.nl> wrote:
> 
> > 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?
> 
>   mtxrun --autogenerate --script check <file>
> 


Thank you very much. If there is not any other tool it seems that there
are no errors.


> The following will not report missing tags but will find other
> common issues and report them on the console:
> 
>   context --errors='*' <file>


I guess this is equal to

\enabledirectives[logs.errors]

With which only the following error on plain pdf is remaining after
fixing any other indicated

error logging   > start possible issues

fonts           > start missing characters:
/usr/local/texlive/2021/texmf-dist/fonts/opentype/public/lm/lmroman12-
regular.otf
fonts           >    2  U+00001    START OF HEADING
fonts           > stop missing characters

error logging   > stop possible issues



OK, I guess I figured the cause of why xml export aborts in the middle
of the document. It came to me while writing the above lines and
wanting to report that i see some warnings about fuzzy paragraphs
(forget about them).

To make it short it triggered a memory about a rather old thread, where
Hans mentioned that the exporter is not so fond of and keen about LaTeX
style \chapter, \section commands and that he advises to use
\startchapter \stopchapter, \startsection \stopsection, etc. pairs
instead. So i gave it a try and exchanged all occurrences of \chapter,
\section, \subsection, \subsection by their \start* \stop* equivalents
and now the xml document and the html document are a lot largen. They
now conatin nearly the whole document. 

There are sill plenty of LaTeX style commands around in the document
for which exporter friendly \start* \stop* replacements exist. I will
continue this route and 'am comfident that in the end  will get get a
full xhtml and true e-book for my lecture notes.
:-)

Thank you very much for triggering memories.

Christoph


___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Few quick questions

[Christoph Hintermüller via ntg-context]

Ok replaced everything i could find with \start* \stop* pairs which got
me far down the document just the last about 4 pages.

The only thing when comparing with examples for using exporter which
still differs is that i use blank line in my sources. Does this
implicit definition of paragraphs cause any hickups in exporter and
would it be adviseable to enclose each paragraph in \startparagraph and
\stopparagraph? Or should that be no issue for xmlexporter and would
ensuring clean recent install be more efficient in this case.

Best
Xristoph



___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Few quick questions

[Hans Hagen via ntg-context]

On 3/9/2022 5:26 PM, Christoph Hintermüller via ntg-context wrote:
> Ok replaced everything i could find with \start* \stop* pairs which got
> me far down the document just the last about 4 pages.
> 
> The only thing when comparing with examples for using exporter which
> still differs is that i use blank line in my sources. Does this
> implicit definition of paragraphs cause any hickups in exporter and
> would it be adviseable to enclose each paragraph in \startparagraph and
> \stopparagraph? Or should that be no issue for xmlexporter and would
> ensuring clean recent install be more efficient in this case.
normally there is no need to mark paragraphs

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
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

Few quick questions

[Christoph Hintermüller via ntg-context]

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.



-- 
-- 
Christoph Hintermüller
Dipl.-Ing. Dr. MBA. MSc
JKU Institute of Biomedical Mechatronics
Altenberger Straße 69,
4040 Linz, Austria,
Cell: +43 650 8827347
Tel. +43 732 2468 4813
Email: christoph.hintermueller@jku.at

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Few quick questions

[Rik Kabel via ntg-context]

On 2022-03-08 14:54, Christoph Hintermüller via ntg-context wrote:
> 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?
>
mtxrun --script check <filename>

-- 
Rik

___________________________________________________________________________________
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
___________________________________________________________________________________