From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Fuzzy paragraph when exporting to XML
Date: Sat, 30 Apr 2022 18:17:05 -0400 (EDT) [thread overview]
Message-ID: <nycvar.YAK.7.78.908.2204301815190.35610@nqv-guvaxcnq> (raw)
In-Reply-To: <8a483542-d92c-160f-edcc-4424b68972b1@xs4all.nl>
On Sat, 30 Apr 2022, Hans Hagen via ntg-context wrote:
> On 4/29/2022 4:59 PM, Aditya Mahajan via ntg-context wrote:
> > Hi,
> >
> > I am trying to debug a bug-report for t-vim:
> https://github.com/adityam/filter/issues/64 Exporting with trackers=export*
> gives a warning:
> >
> > backend > export > fuzzy paragraph:
> >
> > I have managed to narrow it down to the attached MWE (which does not depend
> on the t-vim module at all). Compiling it using
> >
> > $context --trackers=export\* lines
> >
> > gives the fuzzy paragraph warning. Any hints on how to resolve this?
> As you like challenges ... you can way more narrow it down ...
>
> \setupbackend[export=yes]
>
> \starttext
> {
> \forgetall
> % \forgeteverypar
> x\strut\par
> }
> \stoptext
>
> the problem is that you basically loose *all* par related tagging now so
> you need to bring that back, which is (of course i had to look it up) is
> done with for instance \forgeteverypar which forgets (as in \forgetall)
> but not really all
Thanks!
I manually tag start and end of lines anyways (using \SYNBOL ... \SYNEOL), so I can add \dotagsetparcounter in \SYNBOL and that removes the warning!
Thanks,
Aditya
___________________________________________________________________________________
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-04-30 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 14:59 Aditya Mahajan via ntg-context
2022-04-30 7:54 ` Hans Hagen via ntg-context
2022-04-30 22:17 ` Aditya Mahajan via ntg-context [this message]
2022-05-01 9:01 ` Hans Hagen 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=nycvar.YAK.7.78.908.2204301815190.35610@nqv-guvaxcnq \
--to=ntg-context@ntg.nl \
--cc=adityam@umich.edu \
/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).