From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: pod2mdoc, docbook2mdoc
Date: Thu, 03 Apr 2014 18:51:28 +0200 [thread overview]
Message-ID: <533D9190.9000408@bsd.lv> (raw)
In-Reply-To: <20140403135302.GA22574@iris.usta.de>
>>> * .Bd -literal + #include <foo> + Ed -> .In foo
>
>> Yes, this is TODO for more Smarts.
>
> - *.pod only has a leading blank character.
> - *.man has .Vb, see above, almost nothing.
> - *.xml has:
>
> <funcsynopsisinfo>
> #include <openssl/dsa.h>
>
> </funcsynopsisinfo>
>
> That's pathetic. It doesn't even remove the leading blank
> and provides almost no semantics. So again, Thomas, you aim
> well beyond the state of the art. That's already the second
> case of an easy smart that doclifter fails to deliver.
With this last commit, leading #include statements in SYNOPSIS verbatim
paragraphs are rendered with In.
Example:
=head1 SYNOPSIS
#include <openssl/ssl.h>
#include <asdfopenssl/ssl.h>
SSL *SSL_new(SSL_CTX *ctx);
Now rendered as:
.Sh SYNOPSIS
.In openssl/ssl.h
.In osdfpenssl/ssl.h
.Bd -literal
SSL *SSL_new(SSL_CTX *ctx);
.Ed
So state of the art!
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2014-04-03 16:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20140330-202333-+022.64-1@spamfilter.osbf.lua>
2014-03-30 18:23 ` Kristaps Dzonsons
2014-03-31 9:09 ` Thomas Klausner
2014-03-31 10:30 ` Kristaps Dzonsons
2014-03-31 16:13 ` Ingo Schwarze
2014-03-31 19:40 ` Kristaps Dzonsons
2014-03-31 20:57 ` Ingo Schwarze
2014-03-31 21:30 ` Thomas Klausner
2014-03-31 21:54 ` Kristaps Dzonsons
2014-03-31 22:21 ` Ingo Schwarze
2014-03-31 22:31 ` Thomas Klausner
2014-04-03 12:02 ` Kristaps Dzonsons
2014-04-03 12:17 ` Thomas Klausner
2014-04-03 12:33 ` Kristaps Dzonsons
2014-04-03 13:53 ` Ingo Schwarze
2014-04-03 16:51 ` Kristaps Dzonsons [this message]
2014-04-03 22:06 ` Thomas Klausner
2014-04-04 13:43 ` Kristaps Dzonsons
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=533D9190.9000408@bsd.lv \
--to=kristaps@bsd.lv \
--cc=discuss@mdocml.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).