Re: ANNOUNCE: the new perl.apache.org is alive now!

2002-07-13 Thread Matt Sergeant
On 12 Jul 2002, Randal L. Schwartz wrote: Oh, and add Template Toolkit (www.tt2.org) to that list. You mean like this: Matt EmbPerl, TT, Mason, AxKit, ASP, etc... Perhaps live sites is a more ^^ ;-) -- !-- Matt -- :-Get a smart net/:-

Re: ANNOUNCE: the new perl.apache.org is alive now!

2002-07-13 Thread Stas Bekman
Nick Tonkin wrote: The content seems great. But whatever font you've used is rendering skinny and pixelated and hard to read and makes me want to egt of the site asap ... why not leave font face undetermined so the font that each has chosen for his platform is employed? Agreed 100%, my

Re: ANNOUNCE: the new perl.apache.org is alive now!

2002-07-13 Thread Larry Leszczynski
Hi Stas - We were thinking to try removing font-family completely. Does anybody know of any problems with this approach? I don't think the problem is the font-family but instead specifying font-size in pixels. I'm not a stylesheet expert but we had lots of trouble getting good cross-browser

Re: ANNOUNCE: the new perl.apache.org is alive now!

2002-07-13 Thread allan
Larry Leszczynski wrote: Hi Stas - We were thinking to try removing font-family completely. Does anybody know of any problems with this approach? I don't think the problem is the font-family but instead specifying font-size in pixels. I'm not a stylesheet expert but we had lots of

Re: ANNOUNCE: the new perl.apache.org is alive now!

2002-07-13 Thread Ged Haywood
Hi all, On Sat, 13 Jul 2002, allan wrote: We were thinking to try removing font-family completely. Does anybody know of any problems with this approach? I don't think the problem is the font-family for the major part of the content we haven't specified a font-size at all Once I

Re: ANNOUNCE: the new perl.apache.org is alive now!

2002-07-13 Thread allan
Ged Haywood wrote: Hi all, On Sat, 13 Jul 2002, allan wrote: We were thinking to try removing font-family completely. Does anybody know of any problems with this approach? I don't think the problem is the font-family for the major part of the content we haven't specified