From: Fred Baube <fbaube-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: any plans for dita backend support?
Date: Tue, 9 Jan 2018 02:38:10 -0800 (PST) [thread overview]
Message-ID: <82905ae0-9bd9-4b89-ad2d-40ecc0150769@googlegroups.com> (raw)
In-Reply-To: <82bf95e3-abc2-4c5c-a212-90fcb1c3e1c2-FcCCGceb3axikxaaqjoKslYGCWtFR9XvQQ4Iyu8u01E@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 897 bytes --]
There's LwDITA now too. Much simpler.
Somewhat unrelatedly, I wonder if anyone has written filters in Go.
fred
On Wednesday, February 17, 2010 at 1:39:42 AM UTC+2, Anatoly Yakovenko
wrote:
>
> the dita toolchain is so extremely obnoxious. It would be awesome if
> pandoc could generate some basic dita files as well.
>
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/82905ae0-9bd9-4b89-ad2d-40ecc0150769%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1458 bytes --]
next prev parent reply other threads:[~2018-01-09 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 23:39 Anatoly Yakovenko
2010-02-17 1:38 ` fiddlosopher
[not found] ` <82bf95e3-abc2-4c5c-a212-90fcb1c3e1c2-FcCCGceb3axikxaaqjoKslYGCWtFR9XvQQ4Iyu8u01E@public.gmane.org>
2018-01-09 10:38 ` Fred Baube [this message]
[not found] ` <82905ae0-9bd9-4b89-ad2d-40ecc0150769-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-09 12:00 ` albert.krewinkel-stqabkCVF6SGlKaCpJGLJw
2018-01-11 12:49 ` Fred Baube
2018-03-12 20:11 ` Adam Rice
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=82905ae0-9bd9-4b89-ad2d-40ecc0150769@googlegroups.com \
--to=fbaube-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).