ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Fuzzy paragraph when exporting to XML
Date: Fri, 29 Apr 2022 10:59:54 -0400 (EDT)	[thread overview]
Message-ID: <nycvar.YAK.7.78.908.2204291038070.35610@nqv-guvaxcnq> (raw)

[-- Attachment #1: Type: text/plain, Size: 444 bytes --]

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?

Thanks,
Aditya

[-- Attachment #2: Type: application/x-tex, Size: 614 bytes --]

[-- Attachment #3: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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-04-29 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 14:59 Aditya Mahajan via ntg-context [this message]
2022-04-30  7:54 ` Hans Hagen via ntg-context
2022-04-30 22:17   ` Aditya Mahajan via ntg-context
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.2204291038070.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).