From: Randy Dunlap <randy.dunlap@oracle.com>
To: Borislav Petkov <bbpetkov@yahoo.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [KERNEL-DOC] fix tex error when building pdfdocs
Date: Thu, 12 Apr 2007 16:48:51 -0700 [thread overview]
Message-ID: <20070412164851.0c5d6e54.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070412203842.GA14245@zmei.tnic>
On Thu, 12 Apr 2007 22:38:42 +0200 Borislav Petkov wrote:
> When building pdfdocs, the db2pdf converter bails out because of an
> latex-reserved token - '#' - in the intermediary .tex file which ends up in a
> conversion error with the following error message:
>
> <log>
> [15.0.32])
> ! Incomplete \iffalse; all text was ignored after line 8154.
> <inserted text>
> \fi
> <*> kernel-hacking.tex
> </log>
>
> This is a rather arbitrary fix, so suggest away.
Hi,
I don't have a problem with the change, but I don't get that tex error either.
Here is an extract from the .tex file:
{\def\Element%
{451}\def\ProcessingMode%
{title-sosofo-mode}}\#if\endNode{}\endSeq{}\endLink{}\Seq%
{}\Leader%
{}.\endLeader{}\Link%
> Signed-off-by: Borislav Petkov <bbpetkov@yahoo.de>
>
> Index: 21-rc6/Documentation/DocBook/kernel-hacking.tmpl
> ===================================================================
> --- 21-rc6.orig/Documentation/DocBook/kernel-hacking.tmpl
> +++ 21-rc6/Documentation/DocBook/kernel-hacking.tmpl
> @@ -1138,7 +1138,7 @@ static struct block_device_operations op
> </sect1>
>
> <sect1 id="conventions-ifdef">
> - <title>#if</title>
> + <title>Prepocessor Conditionals</title>
>
> <para>
> It is generally considered cleaner to use macros in header files
>
> -
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-04-12 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 20:38 Borislav Petkov
2007-04-12 23:48 ` Randy Dunlap [this message]
2007-04-13 6:35 ` Borislav Petkov
2007-04-13 15:20 ` Randy Dunlap
2007-04-14 8:14 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070412164851.0c5d6e54.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=bbpetkov@yahoo.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®