From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: HTML formatting of .IP
Date: Sun, 25 Nov 2018 13:05:28 -0500 (EST) [thread overview]
Message-ID: <381d79bec8f6e5f8@fantadrom.bsd.lv> (raw)
Log Message:
-----------
HTML formatting of .IP
Modified Files:
--------------
mandoc:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.275
retrieving revision 1.276
diff -LTODO -LTODO -u -p -r1.275 -r1.276
--- TODO
+++ TODO
@@ -399,8 +399,14 @@ are mere guesses, and some may be wrong.
in the CSS for .Bl-tag first.
Reminded by Pali Rohar 25 Oct 2018 10:10:35 +0200.
+- format multiple subsequent .IP as a single list
+ rather than opening a new list for each item
+ Pali Rohar 25 Nov 2018 14:34:26 +0100
+ loc * exist ** algo * size * imp ***
+
- format ".IP *" etc. as <ul> rather than <dl>
https://github.com/Debian/debiman/issues/67
+ reminded by Pali Rohar 25 Nov 2018 14:34:26 +0100
loc ** exist ** algo ** size * imp ***
- .Bf at the beginning of a paragraph inserts a bogus 1ex horizontal
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2018-11-25 18:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=381d79bec8f6e5f8@fantadrom.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@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).