public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Devin Prater <r.d.t.prater-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Org to Markdown PHP_extra
Date: Tue, 15 Oct 2019 19:11:52 -0500	[thread overview]
Message-ID: <F995005F-67D2-4F84-961B-E9A4E9778219@gmail.com> (raw)

Hi all. I’m attempting to move from org-mode exported HTML in Moodle courses I manage to simple, easily updated markdown, which I hope will be as powerful to write as Org-mode. Moodle, for some reason, uses PHP Markdown, instead of Pandoc Markdown or even Multi-markdown. So, we do have definition lists, thankfully, but the <aside> element is made, from Org-mode, to the <div> with simply the class of aside, markdown =“1”. The only problem is, screen readers, which is why I use <aside> anyway, for blind people like myself to know that something is a note. This helps audit-orally separate notes from the main text, and probably does something visual too. I’d like this to simply be <aside markdown=“1”>
Input:

* Test of aside conversion to Markdown
This is a paragraph.

#+begin_aside
This is a /note/.
#+end_aside
End of test.

Output:

Test of aside conversion to Markdown {#test-of-aside-conversion-to-markdown}
====================================

This is a paragraph.

<div class="aside" markdown="1">

This is a *note*.

</div>

End of test.


I hope this makes sense. I’m not a programmer, just the one in a million blind person that actually cares about formatting.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/F995005F-67D2-4F84-961B-E9A4E9778219%40gmail.com.


             reply	other threads:[~2019-10-16  0:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16  0:11 Devin Prater [this message]
     [not found] ` <F995005F-67D2-4F84-961B-E9A4E9778219-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-10-16  9:38   ` BP Jonsson
     [not found]     ` <CAFC_yuTgZCtpd5fNVBOR5ZaYF4G6jowF_9k2igOLq8nDM=hFCg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-10-16 13:11       ` Devin Prater

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=F995005F-67D2-4F84-961B-E9A4E9778219@gmail.com \
    --to=r.d.t.prater-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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).