ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jan Tosovsky" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: docbook(5) to context conversion
Date: Tue, 12 Apr 2016 22:12:20 +0200	[thread overview]
Message-ID: <15786.8987801068$1460491982@news.gmane.org> (raw)
In-Reply-To: <029201d16f59$33b7efc0$9b27cf40$@tosovsky@email.cz>

On 2016-02-25 Jan Tosovsky wrote:
> On 2016-02-23 David Nebauer wrote:
> > On 23/02/16 06:33, Jan Tosovsky wrote:
> > > On 2016-02-22 David Nebauer wrote:
> > > >
> > > > Are there any publicly available solutions for 
> > > > converting docbook/docbook5 to context? ...
> > > >
> > > > * dbcontext - part of dblatex, abandoned ~10 years ago
> > >
> > > I used this way some time ago, but it required tweaks in 
> > > approx 10 xslt files to make it compatible with Context MkIV
> >
> > Cool. Any chance you could post your amended xslt files to give a
> > newbie a head start?
> 
> Ok, I will publish it on my GitHub account later next week (after
> necessary cleanup).

As promised, I've published a set of XSLT stylesheets for DocBook to ConTeXt conversion.

Details can be found at http://doctribute.com/blog/

There is also a step by step description how to test stylesheets on a sample DocBook v4 book.

As you can see, I've changed my mind and instead of patching dbcontext project I created a new one. It finally took more time than originally estimated.

If you encounter any misleading info or inclarity, let me know.

Thanks, Jan

___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2016-04-12 20:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 10:08 David Nebauer
2016-02-22 10:10 ` Jan U. Hasecke
2016-02-22 11:09   ` David Nebauer
2016-02-22 21:03 ` Jan Tosovsky
     [not found] ` <020001d16db4$725810d0$57083270$@tosovsky@email.cz>
2016-02-23  8:16   ` David Nebauer
2016-02-23  8:34     ` Hans Hagen
2016-02-24 23:15     ` Jan Tosovsky
     [not found]     ` <029201d16f59$33b7efc0$9b27cf40$@tosovsky@email.cz>
2016-02-25 14:20       ` David Nebauer
2016-04-12 20:12       ` Jan Tosovsky [this message]
     [not found]       ` <01ad01d194f7$9f3c7ef0$ddb57cd0$@tosovsky@email.cz>
2016-04-13  4:24         ` Henning Hraban Ramm

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='15786.8987801068$1460491982@news.gmane.org' \
    --to=j.tosovsky@email.cz \
    --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).