ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Minimal code for exporting custom tags
Date: Tue, 19 May 2020 02:16:02 -0400 (EDT)	[thread overview]
Message-ID: <nycvar.YAK.7.77.849.2005190213060.414636@nqv-guvaxcnq> (raw)
In-Reply-To: <nycvar.YAK.7.77.849.2005190132190.414636@nqv-guvaxcnq>

On Tue, 19 May 2020, Aditya Mahajan wrote:

> On Mon, 18 May 2020, Aditya Mahajan wrote:
>
>>> Thanks! This also helped me find the documentation in hybrid.pdf.
>
> Also epub-mkiv.pdf. Not sure why I didn't think of looking there.
>
>> How do I pass options so that the export is
>>
>> <mycommand name=whatever>...</mycommand>
>>
>> (or some variant of that). I thought that
>>
>> \startelement[mycommand][name=whatever]
>>
>> should work (there are some such examples in the texmf tree), but it does 
>> not.
>
> epub-mkiv.pdf states that I need `\setupexport[properties=yes]`, but that 
> doesn't work either:

There is a bug in back-exp.lua:

--- /tmp/back-exp.lua	2020-05-19 02:13:54.961276226 -0400
+++ /opt/luametatex/texmf-context/tex/context/base/mkiv/back-exp.lua	2020-05-19 02:13:01.687385009 -0400
@@ -2305,8 +2305,10 @@
                  if not p then
                      -- skip
                  elseif exportproperties == v_yes then
+                    n = n+1
                      r[n] = attributes(p)
                  else
+                    n = n+1
                      r[n] = properties(p)
                  end
              end

Patching this fixes the export.

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
___________________________________________________________________________________

      reply	other threads:[~2020-05-19  6:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18  7:09 Aditya Mahajan
2020-05-18  9:34 ` Hans Hagen
2020-05-18 13:50   ` Aditya Mahajan
2020-05-18 17:31     ` Aditya Mahajan
2020-05-19  5:45       ` Aditya Mahajan
2020-05-19  6:16         ` Aditya Mahajan [this message]

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.77.849.2005190213060.414636@nqv-guvaxcnq \
    --to=adityam@umich.edu \
    --cc=ntg-context@ntg.nl \
    /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).