From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: html div positioning
Date: Tue, 14 Dec 2010 02:09:05 +0100 [thread overview]
Message-ID: <4D06C3B1.6020702@bsd.lv> (raw)
In-Reply-To: <273936.43197.qm@web31402.mail.mud.yahoo.com>
> First, thank you for mdocml! I have been searching for a way to get
> the man pages put together into an epub file for offline reading on
> something like a Nook or Kindle. The ebook readers have very narrow
> screens. man2html just wraps up the man pages in pre tags, which
> doesn't allow the man pages to fit an entire line of text on the
> narrow screen. mdocml is much closer, and the html displays well
> even down to a 640x480 resolution. There is still some absolute
> positioning going on in the html output, such as "padding-left:
> 16.00em" on certain div tags. These add up on some portions of the
> man pages, and produce the following example of a.out(5) on a Nook:
> http://cisx1.uma.maine.edu/~wbackman/photo-1.JPG I'm not sure I can
> override this with the -Ostyle=mycss.css option. Thoughts?
>
> And thank you once again. A fast and versatile tool.
Will, welcome! Awesome use of mandoc, by the way...
This is an issue with the browser's rendering of mandoc's heavy-handed
CSS2. Basically, the only way I've found that produces ok-looking "Bl
-tag" output is
[div margin-left=xx]
[div margin-right=-xx float=left]
Left
[/div]
[div]
Right
[/div]
[/div]
where "xx" is the width of "Left" (usually given by the -width tag).
This mark-up handles overruns in the left column more-or-less how they
appear on a terminal, only without the line-break (I couldn't find a way
to preserve it exactly). However, it only works with new browsers, and
specifically, new browsers that I've tried.
From mandoc.1:
CAVEATS
The -Thtml and -Txhtml CSS2 styling used for -mdoc input lists
does not render properly in older browsers, such as Internet
Explorer 6 and earlier.
If you can suggest mark-up that works in this situation across more
browsers, I'll immediately jump on implementing it. If, however, you've
any even more awesome ideas, then I'm all ears: -T[x]html isn't burdened
by "prior art".
This has long since been an open issue, so any suggestions you have are
very welcome!
Thanks,
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-12-14 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 0:17 Will Backman
2010-12-14 1:09 ` Kristaps Dzonsons [this message]
2010-12-14 1:21 ` Kristaps Dzonsons
2010-12-14 20:23 ` Ingo Schwarze
2010-12-14 21:04 ` Kristaps Dzonsons
2010-12-15 2:21 ` Will Backman
2010-12-15 23:00 ` Kristaps Dzonsons
2010-12-15 23:36 ` Will Backman
2010-12-14 19:08 ` Will Backman
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=4D06C3B1.6020702@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).