From: Piotr Kopszak <kopszak@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: DocBook in ConTeXt - any new ideas?
Date: Thu, 2 Jun 2011 11:39:46 +0200 [thread overview]
Message-ID: <BANLkTikGVwH0ad-Wb-SkNuhM_62TUFcP5A@mail.gmail.com> (raw)
Dear list,
I am beginning a rather tedious documentation project and will most
probably end up with DocBook. The fact is I haven't used it for any
serious work for about 10 years. Docbook In ConText haven't been
updated since 2003. Does it mean it's so perfect or instead rather
obsolete? Could you recommend other approaches which work
out-of-the-box (or almost). Obviously I would prefer ConTeXt based
solutions. DocBook is not mandatory in fact, I would happily learn other
documentation system. Main prerequisite is utf-8 output at least in
pdf and html and sensible defaults (this time I don't want to be a
typographer, nor I want to fiddle with structure).
Best
Piotr
--
http://okle.pl
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2011-06-02 9:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 9:39 Piotr Kopszak [this message]
2011-06-02 10:20 ` Thomas Schmitz
2011-06-02 10:53 ` Piotr Kopszak
2011-06-02 12:03 ` Hans Hagen
2011-06-02 17:17 ` Bruce
2011-06-02 20:20 ` Hans Hagen
2011-06-03 15:43 ` R. Ermers
2011-06-03 16:28 ` Hans Hagen
2011-06-04 8:21 ` R. Ermers
2011-06-04 9:06 ` Hans Hagen
2011-06-04 9:57 ` R. Ermers
2011-06-04 12:24 ` Aditya Mahajan
2011-06-04 13:25 ` R. Ermers
2011-06-05 10:46 ` Hans Hagen
2011-06-02 11:58 ` Hans Hagen
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=BANLkTikGVwH0ad-Wb-SkNuhM_62TUFcP5A@mail.gmail.com \
--to=kopszak@gmail.com \
--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).