From: Maurice Diamantini <Maurice.Diamantini@ensta.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Maurice Diamantini <Maurice.Diamantini@ensta.fr>
Subject: Re: markup format ---> ConTeXt
Date: Tue, 3 Jun 2008 08:48:39 +0200 [thread overview]
Message-ID: <AEC7658C-3655-4451-8F34-B70E913F7DC8@ensta.fr> (raw)
In-Reply-To: <alpine.DEB.1.00.0805300721030.1584@nqv-yncgbc>
Le 30 mai 08 à 13:22, Aditya Mahajan a écrit :
> On Fri, 30 May 2008, Gour wrote:
>
>> Some of the more popular markup-formats are AsciiDoc
>> (http://www.methods.co.nz/asciidoc/index.html) and reStructuredText
>> (http://docutils.sourceforge.net/rst.html), but according to what I
>> see
>> both are missing ConTeXt back-end (latex only) :-(
>>
>> Any suggestion for 'popular' markup with ConTexT back-end?
>
> Have a look at pandoc which converts markdown to ConTeXt and also to
> many
> other formats including html. There was also some discussion for
> conversion to OO, but I do not know the current status of that.
>
> http://johnmacfarlane.net/pandoc/
Just some remarks/questions:
- docbook seems to be the standard for describing documentation data,
- dblatex seams to be a currently good supported tools for **easely**
provide pdf
output from docbook input, and cutomize the output with .xsl
parameters or
LaTeX .sty files
- dbcontext seams not to be maintained very much
- ConTeXt seams to be able to directly parse xml without external tools
So, what about make ConTeXt directly reading dokbook file and output
pdf file?
I see the http://www.leverkruid.eu/context/index.html page from Simon
Pepping.
But it seems that this project is down.
If ConTeXt provide an easy way for translate docbook to pdf file
(usable by
a non (ie. not yet) ConTeXt user as dblatex is), I think poeple could
switch
to ConTeXt only for that feature (not everybody have dependency with
LaTeX!)
Then the problem would resume to find a good "yourPreferedWikiFormat" to
docbook...
(I'v not seen any "t-bocbook" file on http://dl.contextgarden.net/modules)
-- Maurice
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-03 6:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 8:39 Gour
2008-05-30 11:22 ` Aditya Mahajan
2008-05-30 15:18 ` Gour
2008-06-03 6:48 ` Maurice Diamantini [this message]
2008-06-03 7:43 ` Wolfgang Schuster
2008-06-03 13:00 ` Maurice Diamantini
2008-06-03 13:11 ` Hans Hagen
2008-06-03 13:21 ` Wolfgang Schuster
2008-06-04 7:49 ` Maurice Diamantini
2008-06-04 13:34 ` Gour
2008-06-04 14:53 ` markup format ---> ConTeXt (Out of Topic) Maurice Diamantini
2008-06-04 19:34 ` Gour
2008-06-05 6:55 ` Maurice Diamantini
2008-06-05 7:15 ` luigi scarso
2008-06-06 5:57 ` Maurice Diamantini
2008-06-06 7:06 ` luigi scarso
2008-06-04 20:46 ` Gour
2008-06-03 14:09 ` markup format ---> ConTeXt Gour
2008-06-03 18:22 ` nico
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=AEC7658C-3655-4451-8F34-B70E913F7DC8@ensta.fr \
--to=maurice.diamantini@ensta.fr \
--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).