From: Mica Semrick <paperdigits@gmail.com>
To: lists@meahan.net, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [***SPAM***] Textile
Date: Tue, 19 Nov 2013 13:42:05 -0800 [thread overview]
Message-ID: <CABkompJwK1Nc493EKoo-LJCg=7tTfah38cf=Uhocp0GYSdUcMQ@mail.gmail.com> (raw)
In-Reply-To: <528798BE.9030804@meahan.net>
[-- Attachment #1.1: Type: text/plain, Size: 2115 bytes --]
Bill,
With more recent version of pandoc, you can write filters for it in python.
http://johnmacfarlane.net/pandoc/scripting.html
On Sat, Nov 16, 2013 at 8:09 AM, Bill Meahan <subscribed_lists@meahan.net>wrote:
> To save possibly reinventing the wheel, has anyone written a filter for
> processing Textile markup analogous to the filters for Markdown and
> reStructuredText?
>
> I tried using Pandoc to provide multiple formats of output (ConTeXt, EPUB,
> MS Word) from a common source but Pandoc is excessively tied to Markdown
> which does not understand the difference between emphasized text and italic
> text and only outputs {\em word}, <em>word</em>, \emph{word} and so forth
> which means I have to go through every instance of the tag and change tags
> where I want explicit italics as I use other typographical techniques
> (small-caps or sans-serif or ...) for emphasis but some things (book
> titles, ship names, foreign words/phrases et. al) are always set in italics
> by convention. Pandoc continues its "map everything to <em> ways even if
> the input is textile or (X)HTML. There are some other neat advantages to
> Textile as well such as local styling (CSS or \begin{environment}... or
> \startenvironment ...)
>
> I know a lot of computer languages now and I really don't want to learn
> Lua or Haskell -- I'm retired! :)
>
> --
> Bill Meahan, Westland, Michigan
>
> “Writing is like getting married. One should never
> commit oneself until one is amazed at one's luck.”
>
> —Iris Murdoch
>
> ____________________________________________________________
> _______________________
> 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
> ____________________________________________________________
> _______________________
>
[-- Attachment #1.2: Type: text/html, Size: 2950 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2013-11-19 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 16:09 Bill Meahan
2013-11-19 21:42 ` Mica Semrick [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='CABkompJwK1Nc493EKoo-LJCg=7tTfah38cf=Uhocp0GYSdUcMQ@mail.gmail.com' \
--to=paperdigits@gmail.com \
--cc=lists@meahan.net \
--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).