discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mandoc.bsd.lv
Subject: docbook2mdoc-1.0.0 released
Date: Wed, 17 Apr 2019 21:24:35 +0200	[thread overview]
Message-ID: <20190417192435.GA10272@athene.usta.de> (raw)

Hello,

after doing active development on it for about a month, i just released
version 1.0.0 of the DocBook to mdoc converter, docbook2mdoc(1).

See http://mandoc.bsd.lv/docbook2mdoc/ for all information about the
utility and the release notes http://mandoc.bsd.lv/docbook2mdoc/NEWS
for details about this release.

In a nutshell, docbook2mdoc(1) was brought from experimental status
to an early release that can be considered mostly usable for
production, though no doubt there are still many rough edges.
That's why i called it 1.0.0 and not 1.1.1.

Lots of features were added, formatting was improved in many respects,
and several reorganizations were done with respect to internal code
structure.  The expat library is no longer needed, and no other
dependency is required.

Thanks to Stephen Gregoratto for a number of patches and many useful
reports.

I might submit an article about this release - the motivation, the
architectural decisions involved, and what it is capable of - to
undeadly.org, so maybe check over there in a few days.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv

             reply	other threads:[~2019-04-17 19:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 19:24 Ingo Schwarze [this message]
2019-04-20 19:03 ` Jan Stary
2019-04-20 22:56   ` Anthony J. Bentley
2019-04-21 12:32     ` hyphen-minus, was: " Ingo Schwarze
2019-04-21 16:32       ` Anthony J. Bentley
2019-04-21 11:26   ` Stephen Gregoratto
2019-04-25 17:02     ` Ingo Schwarze
2019-04-21 15:29   ` Ingo Schwarze

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=20190417192435.GA10272@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mandoc.bsd.lv \
    --subject='Re: docbook2mdoc-1.0.0 released' \
    /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

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).