Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 4 Feb 2007 17:39:59 +0100
From:      Fabian Keil <freebsd-listen@fabiankeil.de>
To:        Greg 'groggy' Lehey <grog@FreeBSD.org>
Cc:        www@FreeBSD.org
Subject:   Privoxy filter for FreeBSD.org (was: [RFC] Proposed changes for the website)
Message-ID:  <20070204173959.4f850be6@localhost>
In-Reply-To: <20070202232350.GA96920@wantadilla.lemis.com>
References:  <45C3C140.7000601@FreeBSD.org> <20070202232350.GA96920@wantadilla.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_UBEond75QAShCp61MKfmoyZ
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Greg 'groggy' Lehey <grog@FreeBSD.org> wrote:

> On Friday,  2 February 2007 at 23:54:56 +0100, Gabor Kovesdan wrote:

> > I'm starting this thread to discuss these changes before I commit them.
> >
> >
> > 2, Changing the format of the news entries
>=20
> Not just the news entries!  The whole site is broken at 2048x1536.
> It's really a very poor advertisement for us.  Fixed size fonts live a
> life of their own (can often be double the size of proportional, or
> more), headings overlap, and as you say the indentation is crazy.  I'd
> be really happy if you would fix it.

FYI: I've been using the following Privoxy filter for several months now:

FILTER: freebsd.org Hides some design bugs that show up if you are using sl=
ightly different browser settings than the "designer".
s@</head>@<style type=3D"text/css">\n\
 /* Style sheet inserted by Privoxy's freebsd.org filter */\n\
 body {width: auto; font-size: 100%; min-font-size: 0.8em /*CSS3*/}\n\
 /* Lots of braindead margings that try to\n\
  * shift the content out of the viewport.\n\
  * This width works for me, but as the margins\n\
  * scale with the font-size, it's not a real solution\n\
  * and the margins should be fixed instead */\n\
 body.SECT1, body.ARTICLE {width: 80%}\n\
 \#containerwrap, \#CONTAINERWRAP {width: auto;}\n\
 \#headercontainer, \#HEADERCONTAINER {width: auto;\n\
  /* Makes horizontal scrollbar for the PR pages less likely\n\
   * but causes some white space if the TOPNAVLIST needs more\n\
   * than one line */\n\
  padding-right:0.3em}\n\
 \#container, \#CONTAINER {width: auto;}\n\
 \#contentwrap, \#CONTENTWRAP {padding-left: 0.5em;}\n\
 \#TOPNAVLIST, \#topnavlist { background-color: \#eee; height: auto; opacit=
y: 0.7; \n\
  /* In case it doesn't fit on one line. Only tested in Firefox. If it caus=
es scrollbars,\n\
   * the browser is broken. */\n\
  width: 100.5% }\n\
 \#TOPNAV, \#topnav {width: auto;}\n\
 \#TOPNAV ul, \#topnav ul {text-align: center;}\n\
 \#SIDENAV, \#sidenav {padding-left: 0.1em; width: auto; clear:both;}\n\
 /* Color doesn't match exactly, but at\n\
  * least it keeps the search button text visible */\n\
 \#SUBMIT, \#submit {background-color: \#7b0000 !important;}\n\
 em, pre, tt {font-size: 1em; /* ridicilous */}\n\
 .mfield, .replyblock {width: auto;}\n\
 \#footer, \#FOOTER {width: auto; padding-left: 0.5em;}\n\
 td .content {width:auto; overflow: visible}\n\
 \#search, \#SEARCH, \#SEARCHNAV, \#seachnav {padding-right: 0.1em}\n\
 \#SEARCHNAVLIST li:first-child, \#searchnavlist li:first-child {display: n=
one; /* Broken links */}\n\
 \#content, \#CONTENT {padding-left: 0.8em; padding-right: 0.8em; width: au=
to;}\n\
 \#MIRRORSEL, \#mirrorsel, \#FRONTNEMSCONTAINER, \#frontnemscontainer {widt=
h: 100%;}\n</style>\n$0@i
s@</(?:title|h1)>@ (CSS modified) $0@ig

It works around the problems that annoyed me the most, you might
want to give it a try to see if it improves things for you as well.

I'm aware that it doesn't hide all problems, but so far I
didn't run into a single page that looked worse than
before.

The filter works by overruling the original CSS files,
mostly to honor the user's default settings which should
be perfect. If the browser doesn't support that,
the filter will not have the desired results and might
even make things worse.

If the fixes would be applied to the original CSS files
(one can dream) this wouldn't be a problem.

Given the fact that FreeBSD.org is broken for quite some
time now, I'm tempted to include the filter in the
Privoxy port and have it enabled by default.

In other words: feedback welcome.

If you don't use Privoxy and don't feel like installing it,
you can quickly test the filter by accessing FreeBSD.org
through the HTTP proxy "tor.fabiankeil.de:8118".

Please note that the Privoxy version running there is based
on alpha code and verbose logging is enabled for debugging purposes
(currently that includes client headers and client IP addresses).

Also the hardware has issues and as a result the
server will not be available 24/7.

Fabian

--Sig_UBEond75QAShCp61MKfmoyZ
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQFFxgxpBYqIVf93VJ0RAg36AJ9+/5XxQMTgoX+cignASYGw8nM+KgCgwpfu
nZeWN8mC9Fcv74m+SEg2DxY=
=I3oE
-----END PGP SIGNATURE-----

--Sig_UBEond75QAShCp61MKfmoyZ--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070204173959.4f850be6>