--===============0854147181==
Content-Type: multipart/signed;
  boundary="nextPart1247901.VNvkSHbYLD";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1247901.VNvkSHbYLD
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

hi,
perhaps it should be stated more clearly:

if you change any css in standard.css, keep in mind:

=2D kde.org and subpages use it, no problem as long as you adjust header/fo=
oter
=2D bugs.kde.org uses it AND NOT header/footer -> any change in css must be=
=20
backward compatible, until you send in a patch for coolo (and perhaps have=
=20
tried it, but that's not that easy without settings bugzilla up, like I=20
learned with my missing </div>
=2D developer.kde.org uses OWN copy of css + header/footer, but should stay=
=20
consistent with kde.org, perhaps we could do there some server side sharing=
=20
of the css stuff, but than, same as for bugs.kde.org

cu
Christoph

=2D-=20
Christoph Cullmann
KDE Developer, kde.org Maintainance Team
http://www.babylon2k.de, cullmann@kde.org

--nextPart1247901.VNvkSHbYLD
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCI4iuyPjDGePm9UIRAusGAKDZOG5O5nkGtFADx2H68sy3Sew2nACfdflR
gkjT6qaPNdSrmnxKvivMHwQ=
=umv2
-----END PGP SIGNATURE-----

--nextPart1247901.VNvkSHbYLD--

--===============0854147181==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-www mailing list
kde-www@kde.org
https://mail.kde.org/mailman/listinfo/kde-www

--===============0854147181==--