From patchwork Wed Dec 12 23:48:19 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Benjamin Kosnik X-Patchwork-Id: 205689 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) by ozlabs.org (Postfix) with SMTP id 31A282C00A4 for ; Thu, 13 Dec 2012 10:48:33 +1100 (EST) Comment: DKIM? See http://www.dkim.org DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=gcc.gnu.org; s=default; x=1355960914; h=Comment: DomainKey-Signature:Received:Received:Received:Received:Received: Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: Mime-Version:Content-Type:Mailing-List:Precedence:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:Sender: Delivered-To; bh=2JzQ8khO/MFAC370MSiWkyvS/U8=; b=Bb8DFRa0LnlSVn+ SEa8tktE0exLPF5tdOmq0g5ghpHqWRdWeCFEGX25CfIBRNv/2IB0M3xNUlRIU7vH HUqs+QVgL3uR0v0b+VULKc9pxyWT6iEFFenIg7Aex47eDP8dRr+je9/sloVs0TEv HJN4m1UjxvMmNHKzSbM42LgvZCoo= Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gcc.gnu.org; h=Received:Received:X-SWARE-Spam-Status:X-Spam-Check-By:Received:Received:Received:Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:Mime-Version:Content-Type:Mailing-List:Precedence:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender:Delivered-To; b=XOatZ38DaimNW4Qg35NTrlPdj3jFeIQ3yOf5kS7Y8K4FHjMdPhZpZGFtIeS4Xn RpfNoC5eSs6AkBFp660vlrZJ5Dq0pMkUHIUdauKotpV//m2xJoAxra78m2gttP0V vT8d5glHxQbPWZ78QBzjTvUR5DuoKaYuLY6dL36oDU8Ow=; Received: (qmail 9975 invoked by alias); 12 Dec 2012 23:48:29 -0000 Received: (qmail 9957 invoked by uid 22791); 12 Dec 2012 23:48:28 -0000 X-SWARE-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL, BAYES_00, KHOP_RCVD_UNTRUST, KHOP_THREADED, RCVD_IN_DNSWL_HI, RP_MATCHES_RCVD, SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 12 Dec 2012 23:48:20 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qBCNmKKL015131 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 12 Dec 2012 18:48:20 -0500 Received: from oakwood (ovpn-113-59.phx2.redhat.com [10.3.113.59]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id qBCNmJPc026574; Wed, 12 Dec 2012 18:48:19 -0500 Date: Wed, 12 Dec 2012 15:48:19 -0800 From: Benjamin De Kosnik To: Benjamin De Kosnik Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: [v3] docbook vs. texlive > 2007 Message-ID: <20121212154819.4d7133d2@oakwood> In-Reply-To: <20121210181440.5eec0110@oakwood> References: <20121210181440.5eec0110@oakwood> Mime-Version: 1.0 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Delivered-To: mailing list gcc-patches@gcc.gnu.org Fixup for a typo, on trunk and 4.7 -benjamin 2012-12-12 Benjamin Kosnik * doc/xml/manual/documentation_hacking.xml: Fix validation issue. diff --git a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml index 91d16dd..05c05a6 100644 --- a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml +++ b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml @@ -383,6 +383,8 @@ refman.out + + A log of the compilation of the converted LaTeX form to pdf. This is a linear list, from the beginning of the @@ -394,10 +396,20 @@ incorrect, or will have clues at the end of the file with the dump of the memory usage of LaTeX. - + + If the error at hand is not obvious after examination, a + fall-back strategy is to start commenting out the doxygen + input sources, which can be found in + doc/doxygen/user.cfg.in, look for the + INPUT tag. Start by commenting out whole + directories of header files, until the offending header is + identified. Then, read the latex log files to try and find + surround text, and look for that in the offending header. + +
Markup @@ -872,7 +884,7 @@ make XSL_STYLE_DIR="/usr/share/xml/docbook/stylesheet/nwalsh" - If the issue is not obvious after examination, or if one + If the error at hand is not obvious after examination, or if one encounters the inscruitable Incomplete \ifmmode error, a fall-back strategy is to start commenting out parts of the XML document (regardless of what