From: "Fatih Tümen" <fthtmn+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ridiculously wide handbook pages
Date: Mon, 4 Oct 2010 20:06:35 +0300 [thread overview]
Message-ID: <AANLkTine-g2wuoJcSSWSX_W1eCZrpWAmMN+QThnuhufb@mail.gmail.com> (raw)
In-Reply-To: <20101002001821.4dcadddc@mating-tux>
On Sat, Oct 2, 2010 at 1:18 AM, Renat Golubchyk <ragermany@gmx.net> wrote:
> Unfortunately Gentoo documentation uses table layout instead of
> relying entirely on CSS. Therefore it is not easy to make the docs
> beautiful for everybody right now. But there is a simple workaround
> which you may find good enough. Add the following CSS rule into your
> ~/.mozilla/<...your profile...>/chrome/userContent.css or install the
> Stylish add-on [3] and create a style with the rule:
>
> -------------------------------------------------------------
> @namespace url(http://www.w3.org/1999/xhtml);
>
> @-moz-document domain("gentoo.org") {
> td.content p {
> width: 40em;
> }
> }
> -------------------------------------------------------------
>
> Change "40em" to anything you like.
>
>
Thank you very much for this tip. I use chromium and fortunately there
exists the Stylish chrome extension. I got it working with the code
you gave by just snipping the moz-document line.
When I inspect the element and check the page source I understand
where td.content and p comes from but could you explain what 'em'
suffix to 40 means please?
--
Fatih
next prev parent reply other threads:[~2010-10-04 18:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 17:13 [gentoo-user] ridiculously wide handbook pages Grant Edwards
2010-09-30 17:26 ` Volker Armin Hemmann
2010-09-30 17:57 ` [gentoo-user] " Grant Edwards
2010-09-30 17:59 ` [gentoo-user] " Darren Kirby
2010-09-30 18:18 ` [gentoo-user] " Grant Edwards
2010-09-30 18:31 ` Darren Kirby
2010-09-30 18:36 ` Grant Edwards
2010-09-30 18:55 ` Darren Kirby
2010-09-30 19:23 ` Grant Edwards
2010-09-30 20:34 ` Jörg Schaible
2010-09-30 20:55 ` Grant Edwards
2010-09-30 21:13 ` Grant Edwards
2010-09-30 18:35 ` Grant Edwards
2010-09-30 18:39 ` Dale
2010-09-30 18:50 ` Grant Edwards
2010-09-30 19:14 ` Dale
2010-09-30 19:42 ` Grant Edwards
2010-09-30 19:50 ` Dale
2010-09-30 20:05 ` Grant Edwards
2010-09-30 20:41 ` Dale
2010-09-30 18:11 ` [gentoo-user] " Al
2010-09-30 18:19 ` [gentoo-user] " Grant Edwards
2010-09-30 18:23 ` Nikos Chantziaras
2010-09-30 18:34 ` [gentoo-user] " Mark Knecht
2010-09-30 18:39 ` Darren Kirby
2010-09-30 18:49 ` [gentoo-user] " Grant Edwards
2010-09-30 18:39 ` Grant Edwards
2010-09-30 22:53 ` [gentoo-user] " Jacob Todd
2010-09-30 23:15 ` [gentoo-user] " Grant Edwards
2010-09-30 23:18 ` Jacob Todd
2010-10-01 0:27 ` Dale
2010-10-01 0:59 ` Jacob Todd
2010-10-01 22:18 ` [gentoo-user] " Renat Golubchyk
2010-10-02 2:16 ` Stroller
2010-10-02 9:06 ` Renat Golubchyk
2010-10-03 17:32 ` Peter Humphrey
2010-10-04 2:00 ` Renat Golubchyk
2010-10-04 6:24 ` Mick
2010-10-04 10:20 ` Peter Humphrey
2010-10-02 3:21 ` [gentoo-user] " Grant Edwards
2010-10-04 17:06 ` Fatih Tümen [this message]
2010-10-04 18:24 ` Grant Edwards
2010-10-04 18:27 ` [gentoo-user] " Derek Tracy
2010-10-04 19:20 ` Fatih Tümen
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=AANLkTine-g2wuoJcSSWSX_W1eCZrpWAmMN+QThnuhufb@mail.gmail.com \
--to=fthtmn+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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