X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18v1HP1aHiUH2XkdTU4PtaP
Date: Fri, 8 Feb 2013 10:03:05 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: One unreadable sentence at http://cygwin.com/setup.html
Message-ID: <20130208150305.GE1184@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20130208021109.GA19883@nt1.in> <575434823.20130208141302@mtu-net.ru> <5114D3E6.2030107@towo.net> <CE9C056E12502146A72FD81290379E9A608E33AD@ENFIRHMBX1.datcon.co.uk> <20130208120428.GB6512@calimero.vinschen.de> <5114EFC6.2050605@towo.net> <20130208130305.GC6512@calimero.vinschen.de> <CE9C056E12502146A72FD81290379E9A608E3622@ENFIRHMBX1.datcon.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CE9C056E12502146A72FD81290379E9A608E3622@ENFIRHMBX1.datcon.co.uk>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Fri, Feb 08, 2013 at 02:19:19PM +0000, Adam Dinwoodie wrote:
>Corinna Vinschen wrote:
>> On Feb  8 13:29, Thomas Wolff wrote:
>>> Am 08.02.2013 13:04, schrieb Corinna Vinschen:
>>>>What would be the right fix?
>>> Very weird; I can't reproduce the issue right now. When I checked
>>> earlier, though, the issue was affected by the line I quoted
>>> (shouldn't be, indeed, maybe a bug in Firefox) while the ".3em" line
>>> does not exist in the style sheet.
>>> I suggest to just remove the dot before "1em" in the "#navbar h4"
>>> style, whatever its purpose might be...
>>
>> Done.  Can you please check if that fixed the OPs problem?
>
>Fixed on my Google Chrome.
>
>Although I'd argue the correct fix would be to replace the <h4>...</h4> with
><p><strong>...</strong></p>.  That makes more semantic sense to me, since that
>line isn't really a header at all.

The <h4> was used to achieve centering.  This problem was just a holdover from
when I redesigned the web site a while ago.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple