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 17:26:39 +0100 [thread overview]
Message-ID: <1b5a8354cd0b954198554b053ec1020ddb5fc53e.camel@out-world.com> (raw)
In-Reply-To: <856f8c2d38824d5160670966c62569f95172cbc4.camel@out-world.com>
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-03-09 16:26 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
2022-03-09 16:26 ` Christoph Hintermüller via ntg-context [this message]
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=1b5a8354cd0b954198554b053ec1020ddb5fc53e.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).