From: Ingo Schwarze <schwarze@usta.de>
To: "J. Lewis Muir" <jlmuir@imca-cat.org>
Cc: tech@mandoc.bsd.lv
Subject: Re: Inconsistent docbook2mdoc experimental status
Date: Mon, 11 Jan 2021 17:00:43 +0100 [thread overview]
Message-ID: <X/x2K/wn71Ql61Ue@asta-kit.de> (raw)
In-Reply-To: <20210111145155.6t4eilqrxonic4k2@mail.imca-cat.org>
Hi Lewis,
J. Lewis Muir wrote on Mon, Jan 11, 2021 at 08:51:55AM -0600:
> Thank you, Developers, for writing mandoc and docbook2mdoc!
You are welcome. :-)
> Just a quick note that in the "Related information" section at
>
> https://mandoc.bsd.lv/
>
> it says that docbook2mdoc is experimental:
>
> docbook2mdoc - an experimental utility to convert documents from the
> commercial OASIS DocBook format to mdoc(7)
>
> Yet at
>
> https://mandoc.bsd.lv/docbook2mdoc/
>
> it says docbook2mdoc is not experimental:
>
> docbook2mdoc is no longer experimental
Good point, thanks for reporting.
I just deleted the word "experimental" from https://mandoc.bsd.lv/.
I considered adding a less dire warning like "under development"
because people might be disappointed that results will not yet be
ideal for all DocBookk input pages.
Then again, the docbook2mdoc entry on https://mandoc.bsd.lv/
is already the longest, https://mandoc.bsd.lv/docbook2mdoc/
already describes the details of the status, and saying more
on https://mandoc.bsd.lv/ would be likely to ultimately end up
outdated again. So i decided against any qualification.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
prev parent reply other threads:[~2021-01-11 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 14:51 J. Lewis Muir
2021-01-11 16:00 ` Ingo Schwarze [this message]
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=X/x2K/wn71Ql61Ue@asta-kit.de \
--to=schwarze@usta.de \
--cc=jlmuir@imca-cat.org \
--cc=tech@mandoc.bsd.lv \
/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).