From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30860 invoked by alias); 2 Dec 2013 19:09:09 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 30843 invoked by uid 89); 2 Dec 2013 19:09:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.0 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: ainaz.pair.com Received: from Unknown (HELO ainaz.pair.com) (209.68.2.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 02 Dec 2013 19:09:07 +0000 Received: from [192.168.0.132] (vie-91-186-144-213.dsl.sil.at [91.186.144.213]) by ainaz.pair.com (Postfix) with ESMTPSA id 063EC3F464; Mon, 2 Dec 2013 14:08:58 -0500 (EST) Date: Mon, 02 Dec 2013 19:09:00 -0000 From: Gerald Pfeifer To: Patrick Marlier cc: gcc@gcc.gnu.org Subject: Re: [doc] Fixing reference inside Extended-Asm.html In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes X-SW-Source: 2013-12/txt/msg00010.txt.bz2 On Wed, 20 Nov 2013, Patrick Marlier wrote: > I have noticed that the link > Extended-asm-with-goto.html#Extended-asm-with-goto is wrong in > http://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html. > Locally when I generate the html doc, the link is good, ie href="#Extended-asm-with-goto">. I had a look, and the way makeinfo generates HTML is, hmm, creative. For an internal reference (@xref) like this it creates a new file based on the reference name -- Extended-asm-with-goto.html -- and that file then only contains a single line which is a redirect back to the original page. And here is our inconsistency since it encodes blank characters as %20 whereas in the document itself it reads > Also the online page for Extended-asm-with-goto.html is wrong, '%20' > instead of '-'. As far as I can tell both approaches to encode blanks would be fine. The problem is that they should be used consistently, which is not what happens on gcc.gnu.org running makeinfo 4.13. > Is the version of texinfo buggy to generate online documentation? That'd be my assumption. Which version are you using locally that does not exhibit this behavior? My guess is you are using a more recent version of makeinfo. Updating gcc.gnu.org will be hard (since its a standard RHEL 6 system) and I won't have the time to hack around this (applying sed magic, say). Gerald