From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15802 invoked by alias); 28 Nov 2019 20:00:02 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 15763 invoked by uid 89); 28 Nov 2019 20:00:02 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=H*f:sk:8de6eea, validator, our X-HELO: hamza.pair.com Received: from hamza.pair.com (HELO hamza.pair.com) (209.68.5.143) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 28 Nov 2019 20:00:01 +0000 Received: from hamza.pair.com (localhost [127.0.0.1]) by hamza.pair.com (Postfix) with ESMTP id 64E1633E18; Thu, 28 Nov 2019 14:59:59 -0500 (EST) Received: from [192.168.1.3] (unknown [178.114.215.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hamza.pair.com (Postfix) with ESMTPSA id B9B5533E13; Thu, 28 Nov 2019 14:59:58 -0500 (EST) Date: Thu, 28 Nov 2019 20:12:00 -0000 From: Gerald Pfeifer To: Mark Eggleston cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org Subject: Making things a bit easier (was: [Patch, gcc-wwdocs] Update to Fortran changes) In-Reply-To: <8de6eea3-ec83-dc45-0bfc-8c647e355a6f@codethink.co.uk> Message-ID: References: <8de6eea3-ec83-dc45-0bfc-8c647e355a6f@codethink.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-IsSubscribed: yes X-SW-Source: 2019-11/txt/msg02590.txt.bz2 On Tue, 26 Nov 2019, Mark Eggleston wrote: > I've check the changes with W3 validator. There are no problems related > to my changes, however, it does object to the lack of character encoding > in the file. My knowledge of HTML is limited, so don't know how to fix > that. Let me take this as good feedback and help make things a bit easier going forward. :-) I just committed a patch a patch that added a tag to all of our HTML files which, also in my own tests with https://validator.w3.org, addresses what you have encountered. Is there anything else we can do to make things easier? Gerald