From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Improving pandoc's ConTeXt output
Date: Mon, 6 Jun 2022 22:47:18 +0200 [thread overview]
Message-ID: <aaeb774d-a351-cdf0-ab51-4576f523b8f3@fiee.net> (raw)
In-Reply-To: <878rqbp47d.fsf@zeitkraut.de>
Am 05.06.22 um 16:30 schrieb Albert Krewinkel via ntg-context:
>>>> 2. Similarly, I'd like to start wrapping paragraphs with
>>>> `\startparagraph`/`\stopparagraph`. It is important for me to get
>>>> properly tagged PDF,
>> \startparagraph can lead to unwanted side effects (I can't remember the details)
>> and \bpar ... \epar is the safer alternative to add tags.
>
> Thank you Wolfgang, I wasn't aware! Searching the wiki brought me to
> <https://wiki.contextgarden.net/Epub_Sample>. It states:
>
>> In places where \startparagraph does not work, such as itemizations,
>> where it causes a blank line after the bullet and before the item
>> text, use \bpar (and closing \epar) to tag paragraphs.
>
> It's probably more consistent then to use \bpar ... \epar everywhere.
If I understood Hans right, \start/stopparagraph is not necessary any
more to get properly tagged XML. I didn’t check it yet myself – my
DOCX-to-ConTeXt converter still produces this markup.
One case where it’s probably in the way is if you need settings like
\looseness – before \startparagraph is too early, and after it is too
late (in LMTX), you need \updateparagraphproperties in such cases, but
you can possible avoid that without \startparagraph – need to check...
Hraban
___________________________________________________________________________________
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-06-06 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 7:07 Albert Krewinkel via ntg-context
2022-06-05 8:20 ` juh via ntg-context
2022-06-05 9:39 ` Denis Maier via ntg-context
2022-06-05 14:15 ` Albert Krewinkel via ntg-context
2022-06-05 16:38 ` juh+ntg-context--- via ntg-context
2022-06-05 23:52 ` Thangalin via ntg-context
2022-06-06 5:21 ` Problem with SVG an conversion mp (was: Improving pandoc's ConTeXt output) Jan U. Hasecke via ntg-context
2022-06-06 5:51 ` Improving pandoc's ConTeXt output juh+ntg-context--- via ntg-context
2022-06-05 9:46 ` Denis Maier via ntg-context
2022-06-05 10:01 ` Hans Hagen via ntg-context
2022-06-05 11:08 ` Wolfgang Schuster via ntg-context
2022-06-05 14:30 ` Albert Krewinkel via ntg-context
2022-06-06 20:47 ` Henning Hraban Ramm via ntg-context [this message]
2022-06-08 13:43 ` Albert Krewinkel 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=aaeb774d-a351-cdf0-ab51-4576f523b8f3@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).