public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: fiddlosopher <fiddlosopher@gmail.com>
To: pandoc-discuss <pandoc-discuss@googlegroups.com>
Subject: Re: any plans for dita backend support?
Date: Tue, 16 Feb 2010 17:38:00 -0800 (PST)	[thread overview]
Message-ID: <ad44624e-b875-46ff-a4fc-a1fa3ac07328@a17g2000pre.googlegroups.com> (raw)
In-Reply-To: <82bf95e3-abc2-4c5c-a212-90fcb1c3e1c2@k5g2000pra.googlegroups.com>


I don't know anything about dita, and don't use it.  But if you know
any
Haskell, it might be a pretty easy modification of the DocBook
writer...

On Feb 16, 3:39=A0pm, Anatoly Yakovenko <aeyakove...@gmail.com> wrote:
> the dita toolchain is so extremely obnoxious. =A0It would be awesome if
> pandoc could generate some basic dita files as well.

--=20
You received this message because you are subscribed to the Google Groups "=
pandoc-discuss" group.
To post to this group, send email to pandoc-discuss@googlegroups.com.
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe@go=
oglegroups.com.
For more options, visit this group at http://groups.google.com/group/pandoc=
-discuss?hl=3Den.


  reply	other threads:[~2010-02-17  1: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 [this message]
     [not found] ` <82bf95e3-abc2-4c5c-a212-90fcb1c3e1c2-FcCCGceb3axikxaaqjoKslYGCWtFR9XvQQ4Iyu8u01E@public.gmane.org>
2018-01-09 10:38   ` Fred Baube
     [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=ad44624e-b875-46ff-a4fc-a1fa3ac07328@a17g2000pre.googlegroups.com \
    --to=fiddlosopher@gmail.com \
    --cc=pandoc-discuss@googlegroups.com \
    /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).