ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Christoph Hintermüller via ntg-context" <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: "Christoph Hintermüller" <christoph@out-world.com>
Subject: Re: Few quick questions
Date: Wed, 09 Mar 2022 11:21:45 +0100	[thread overview]
Message-ID: <856f8c2d38824d5160670966c62569f95172cbc4.camel@out-world.com> (raw)
In-Reply-To: <20220308212639.7ead1416@homerow>


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
___________________________________________________________________________________

  reply	other threads:[~2022-03-09 10:21 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
2022-03-08 20:26 ` Marco Patzer via ntg-context
2022-03-09 10:21   ` Christoph Hintermüller via ntg-context [this message]
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=856f8c2d38824d5160670966c62569f95172cbc4.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).