Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id fB9ILqG09091 for ; Sun, 9 Dec 2001 19:21:52 +0100 Received: by webgate.proteosys.de (8.11.6/8.11.0) with ESMTP id fB9ILpU23935 . for ; Sun, 9 Dec 2001 19:21:52 +0100 MIME-Version: 1.0 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id fB9IDIa13815; Sun, 9 Dec 2001 19:13:18 +0100 (MET) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C180DE.5FB6E000" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id fB9IEAX17597; Sun, 9 Dec 2001 19:14:10 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 0852 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 9 Dec 2001 19:12:47 +0100 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id fB9IClX17586 for ; Sun, 9 Dec 2001 19:12:47 +0100 Received: from smtp.albany.edu (mail1.csc.albany.edu [169.226.1.133]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id fB9IBra13509 for ; Sun, 9 Dec 2001 19:11:53 +0100 (MET) Received: from pluto.math.albany.edu (pluto.math.albany.edu [169.226.23.44]) by smtp.albany.edu (8.11.6/8.11.6) with ESMTP id fB9IBjc20140 for ; Sun, 9 Dec 2001 13:11:50 -0500 (EST) Received: (from hammond@localhost) by pluto.math.albany.edu (8.11.6/8.11.6) id fB9IBjY02792; Sun, 9 Dec 2001 13:11:45 -0500 (EST) Followup-To: comp.text.tex In-Reply-To: Lines: 24 References: Return-Path: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 Content-class: urn:content-classes:message Subject: Re: \verb in \footnote and \section Date: Sun, 9 Dec 2001 19:11:45 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "William F. Hammond" Sender: "Mailing list for the LaTeX3 project" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4174 This is a multi-part message in MIME format. ------_=_NextPart_001_01C180DE.5FB6E000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable "Paulo J. Matos aka PDestroy" writes: > Has anyone any idea how can I do the following without any > errors, or at least get the same result using any other approach? > > \footnote{foo \verb|bar| foo} > > \section{foo \verb|bar| foo} The problem is that \verb may not be used inside the argument of a command (as explained in Lamport's book). Instead one may use \texttt{}, taking care to refer to special characters by their symbolic names, i.e., names like \textgreater, \textasciitilde, ... (Complication: the results obtained for some of the named special characters depend on the font encoding used. Unfortunately, it seems that many of us are stuck with the default OT1 until there is a greater supply of scalable fonts under a suitable public license.) Please note, however, that this question (and its reply) are off topic for this list dedicated to the future development of LaTeX. The newsgroup comp.text.tex would be a better place for this. -- Bill ------_=_NextPart_001_01C180DE.5FB6E000 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: \verb in \footnote and \section

"Paulo J. Matos aka PDestroy" = <pocm@rnl.ist.utl.pt> writes:

> Has anyone any idea how can I do the following = without any
> errors, or at least get the same result using = any other approach?
>
> \footnote{foo \verb|bar| foo}
>
> \section{foo \verb|bar| foo}

The problem is that \verb may not be used inside the = argument of a
command (as explained in Lamport's book).  = Instead one may use
\texttt{}, taking care to refer to special characters = by their
symbolic names, i.e., names like \textgreater, = \textasciitilde, ...
(Complication: the results obtained for some of the = named special
characters depend on the font encoding used.  = Unfortunately, it seems
that many of us are stuck with the default OT1 until = there is a
greater supply of scalable fonts under a suitable = public license.)

Please note, however, that this question (and its = reply) are off topic
for this list dedicated to the future development of = LaTeX.
The newsgroup comp.text.tex would be a better place = for this.

          &nbs= p;            = ;            = -- Bill

------_=_NextPart_001_01C180DE.5FB6E000--