From: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Feature request for export: Interactive Notes
Date: Fri, 24 Apr 2015 18:36:12 -0600 [thread overview]
Message-ID: <op.xxmhamaqpw6hmh@ihamidnb.libarts.colostate.edu> (raw)
Dear gang,
I've spent a considerable amount of time over the past month trying to
master the art of xhtml output. We are close to being able to use ConTeXt
as a replacement for markdown in, e.g., WordPress. Indeed, I plan to
present the results of this experiment (porting an entire academic article
to xhtml and WP) in a future article for one of the TeX journals...
There is at least one crucial feature that's still needed. Perhaps it is
already supported: If so, it would be much appreciated if someone kindly
explained how to do it.
In a web post (or epub), one wants to be able to interact back and forth
with notes. Here is how markdown (extra) does it:
========Input========
That's some text with a footnote.[^1]
[^1]: And that's the footnote.
That's the second paragraph of the note.
More main text
========Output========
<p>That's some text with a footnote.<sup id="fnref:1"><a href="#fn:1"
rel="footnote">1</a></sup></p>
<p>More main text</p>
<div class="footnotes">
<hr />
<ol>
<li id="fn:1">
<p>And that's the footnote.</p>
<p>That's the second paragraph of the note. <a href="#fnref:1"
rev="footnote">↩</a></p>
</li>
</ol>
</div>
=====================
The resulting html file is attached. '↩' corresponds to U+21A9 (↩).
See also
https://michelf.ca/projects/php-markdown/extra/#footnotes
Now we can of course already export xhtml footnotes from ConTeXt but there
will be no interactive links. In the current project, there are 77
footnotes; I had to add the links manually to get the output to do what we
wanted.
[Also note that it makes much more sense to export the footnotes as
endnotes, particularly for long blog posts.]
Is there already a way to get done automatically?
In any case: This feature is a must-do in my humble opinion. Aside from a
few other export bugs, this is one of the few features still needed so
that ConTeXt can completely replace markdown for (advanced) web posts.
Thanks is advance and
Best wishes
Idris
--
Idris Samawi Hamid, Professor
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2015-04-25 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 0:36 Idris Samawi Hamid ادريس سماوي حامد [this message]
2015-04-25 0:44 ` Idris Samawi Hamid ادريس سماوي حامد
2015-04-25 9:05 ` Pablo Rodriguez
2015-04-25 12:19 ` Idris Samawi Hamid ادريس سماوي حامد
2015-04-25 19:19 ` Pablo Rodriguez
2015-04-25 19:34 ` Idris Samawi Hamid ادريس سماوي حامد
2015-04-25 19:35 ` Idris Samawi Hamid ادريس سماوي حامد
2015-04-25 19:37 ` Idris Samawi Hamid ادريس سماوي حامد
2015-04-25 19:42 ` =?iso-8859-6-i?B?SWRyaXMgU2FtYXdpIEhhbWlkIMfP0erTINPlx+jqIM3H5c8=?=
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=op.xxmhamaqpw6hmh@ihamidnb.libarts.colostate.edu \
--to=ishamid@colostate.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).