From MAILER-DAEMON Mon Feb 22 20:14:13 2016 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1aY1YL-0000ko-OR for mharc-bug-gnu-utils@gnu.org; Mon, 22 Feb 2016 20:14:13 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58011) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aY0an-0003nL-SE for bug-gnu-utils@gnu.org; Mon, 22 Feb 2016 19:12:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aY0an-0003Tj-3Q for bug-gnu-utils@gnu.org; Mon, 22 Feb 2016 19:12:41 -0500 Received: from mail-wm0-x231.google.com ([2a00:1450:400c:c09::231]:33084) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aY0am-0003TS-Sw for bug-gnu-utils@gnu.org; Mon, 22 Feb 2016 19:12:41 -0500 Received: by mail-wm0-x231.google.com with SMTP id g62so179401176wme.0 for ; Mon, 22 Feb 2016 16:12:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=99xqkrSGB8W0CN68KgE9aEpXeD3p+gO/RfJSr+qcCnc=; b=koCxiCQX9HllKbzQQsTDGwTaq9LdW8bLBCIiB5owMwkVoTDQghvFEI9Pzn5Ew3GlhO kzmzHzdka7+JOnFAUf5ZZay//wPiwVDHvMsgUChbp7KdAa0r6UBtlbu0b2wEImCm6Nq1 TYk4kz3qIFCVD3eGVd8aQDANyQlT7frayFiERUKyBvDzKOIaHoVQtc/o9+eR2tpc1wYQ 4Rh7aIgM/j2hv2y+Rsr9uVSgMN9G501d6KIt+lQzquWFd5BtBqQ7Xkm6OMAkhz2BsN4z t2GizjVpenwHG5f2KDLn72FygoS7Y8+pfpfemRp1ImFRESn0ElNRfRw3AHZfVB8HTlBm 1/sQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=99xqkrSGB8W0CN68KgE9aEpXeD3p+gO/RfJSr+qcCnc=; b=agy/n+wg0VUvPDwmzYfLDtycZbg7YNmtBt+cyXSqJSbK275D8nm3OrDa2PMgAhD0x9 Mgj9kA3tyadMuPB9oFKlPmIRQDi1ZyMsra70etAC93zLosBMaUh006tWz0PuEkiEKPm2 HXsf2sC1MIxGxNv7/PTzWtMY1+1EDqG2I8mv0HvifzotTa1qyoa6RjrZMUFs2NPwrysE lybYxme5ADrN1zrRF3Y7gvbCEE5QCji3sXTma/zkgfEYKuxD6KxuKwNwG5J8jTffqZz9 4KN4/MYoUQlKaqa84ruYYb7Ap0lNjz2FPBfmgFlow4MK7BXlEvb0aitww2MahUQu9EiL zsIQ== X-Gm-Message-State: AG10YOTcQ2RhqpT/zAdZRgweeoMC/AIrp9Tx4MzjRuKP0K929H2r/ivvhcGutKcy654Hu8CpJT6bCGU+yBj0RA== MIME-Version: 1.0 X-Received: by 10.28.214.6 with SMTP id n6mr15511623wmg.49.1456186359999; Mon, 22 Feb 2016 16:12:39 -0800 (PST) Received: by 10.194.89.66 with HTTP; Mon, 22 Feb 2016 16:12:39 -0800 (PST) Date: Mon, 22 Feb 2016 18:12:39 -0600 Message-ID: Subject: uuencode (GNU sharutils) 4.7 From: srihari D To: bug-gnu-utils@gnu.org X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:400c:c09::231 X-Mailman-Approved-At: Mon, 22 Feb 2016 20:14:12 -0500 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: bug-gnu-utils@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU utilities List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Feb 2016 00:12:42 -0000 Hi, We are experiencing issues with uuencode, we wanted to send files as attachments by using uuencode, but it's displaying the contents of file as body of the email. Below is the syntax being used, please help me on this issue. uuencode myfile.txt Display_name.txt|mail haridusi.us@gmail.com Regards, Srihari Dusi. From MAILER-DAEMON Mon Feb 22 23:43:32 2016 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1aY4ou-0006EV-GJ for mharc-bug-gnu-utils@gnu.org; Mon, 22 Feb 2016 23:43:32 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43846) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aY4or-0006DI-VJ for bug-gnu-utils@gnu.org; Mon, 22 Feb 2016 23:43:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aY4oo-0007z7-QU for bug-gnu-utils@gnu.org; Mon, 22 Feb 2016 23:43:29 -0500 Received: from havoc.proulx.com ([96.88.95.61]:51149) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aY4oo-0007z3-LJ for bug-gnu-utils@gnu.org; Mon, 22 Feb 2016 23:43:26 -0500 Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id B2CFC559; Mon, 22 Feb 2016 21:43:25 -0700 (MST) Received: from hysteria.proulx.com (hysteria.proulx.com [192.168.230.119]) by joseki.proulx.com (Postfix) with ESMTP id 5BC372183B; Mon, 22 Feb 2016 21:43:25 -0700 (MST) Received: by hysteria.proulx.com (Postfix, from userid 1000) id 1D05A2DC5A; Mon, 22 Feb 2016 21:43:24 -0700 (MST) Date: Mon, 22 Feb 2016 21:43:24 -0700 From: Bob Proulx To: srihari D Subject: Re: uuencode (GNU sharutils) 4.7 Message-ID: <20160222213511357322643@bob.proulx.com> Mail-Followup-To: srihari D , bug-gnu-utils@gnu.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 96.88.95.61 Cc: bug-gnu-utils@gnu.org X-BeenThere: bug-gnu-utils@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU utilities List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Feb 2016 04:43:30 -0000 srihari D wrote: > We are experiencing issues with uuencode, we wanted to send files as > attachments by using uuencode, but it's displaying the contents of file as > body of the email. Below is the syntax being used, please help me on this > issue. > > uuencode myfile.txt Display_name.txt|mail haridusi.us@gmail.com The above does not "attach" the file to the email. The above inserts the output of uuencode into the body of the message. There is no attachment in the above. In the above uuencode is working as it has been designed to work. All is correct. These days you probably should want to use MIME attachments instead of uuencode. I am not saying anything bad about uuencode. It does exactly what it does and the command is still needed in order to access uuencoded files. But these days MIME attachments are generally the prefered method. I hesitate to suggest a way to do attachments because it depends so much upon your environment. But 'mutt' handles attachments well. echo Attached is the myfile.txt file | mutt -s "subject line here" -a myfile.txt -- haridusi.us@gmail.com Bob From MAILER-DAEMON Tue Feb 23 15:23:47 2016 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1aYJUp-0005LQ-RT for mharc-bug-gnu-utils@gnu.org; Tue, 23 Feb 2016 15:23:47 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38961) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYJUn-0005Ki-OB for bug-gnu-utils@gnu.org; Tue, 23 Feb 2016 15:23:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aYJUm-0005xg-Jy for bug-gnu-utils@gnu.org; Tue, 23 Feb 2016 15:23:45 -0500 Received: from mail-wm0-x236.google.com ([2a00:1450:400c:c09::236]:35419) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYJUm-0005xL-AE for bug-gnu-utils@gnu.org; Tue, 23 Feb 2016 15:23:44 -0500 Received: by mail-wm0-x236.google.com with SMTP id c200so239135431wme.0 for ; Tue, 23 Feb 2016 12:23:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=xlFpJULCGAjxRGtSDamd+AHV27GMiGbNuQh6UPSncSA=; b=l9TFDEKIgErS08dFehdNOpywhv5jBwUuUPrlUoE5BN/wp0IDB1V/OQeynsf2nfcDav xAmJQLIMeKaoCLef+4v179R7nrYqF6Df8EYx1oISbzMlCuD3gT7VijMBT5Oh3RymgxAM PRkprJl/jxVz3NO9ycaYs8OWXT9w5lsu0LkJ5Ox14CCOqtNWI58ryGqj+r31HZ/5MvU7 Tn58ji15QLz1ZBIhdmQStu9+3N/6TBY/epz/8wIdHn8j/Esj0nabNfx7x4qSGZzxAYPX s0H8fGh8pvpfxz3ZHVfrIy8oli4VcCJrMCoMOiFWMxEEEihOL8tSaASiuHw37/05ba1/ lxSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=xlFpJULCGAjxRGtSDamd+AHV27GMiGbNuQh6UPSncSA=; b=hOQEXzcsb6Gvq3cdQMwgHp/Nx+z7RdJpVyM6JiB65xXxUjjzFLz8dfhTLNOwky7pik 1uLi0FrRRR8S914D7vP6RX+jXhdfCjiNejPfg5zOJ+ubEYmWRp5ddNO1XytNaAGb+KOV 2y0kII2kffT4zDccshOndTbpBujvBTfYRpY200Lno25Wj5VYXo+owCsEwdN8P9sdXmot JBztzXIqx2FtSxH6EfjRvnm7YJaefYIuJbQn6MpryKDbw28eEgOTveKwV0DjtYCffu64 WdBORq3aAI7tJbbAcLcm6Ef9EQVim4N6p4cdUU8c5y+MvCJhfm1WG2DzRuu6O8T8RegU etOw== X-Gm-Message-State: AG10YOQw2XLchnsn4Z6TYwUy2i210v4JPEVcI5x/bzI+KA57ZgSiP81zPlNDigCE+pXu2n3kAgqR8fkxUmQyNg== MIME-Version: 1.0 X-Received: by 10.28.57.68 with SMTP id g65mr21201764wma.56.1456259023687; Tue, 23 Feb 2016 12:23:43 -0800 (PST) Received: by 10.194.89.66 with HTTP; Tue, 23 Feb 2016 12:23:43 -0800 (PST) In-Reply-To: <20160222213511357322643@bob.proulx.com> References: <20160222213511357322643@bob.proulx.com> Date: Tue, 23 Feb 2016 14:23:43 -0600 Message-ID: Subject: Re: uuencode (GNU sharutils) 4.7 From: srihari D To: srihari D , bug-gnu-utils@gnu.org X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:400c:c09::236 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: bug-gnu-utils@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU utilities List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Feb 2016 20:23:46 -0000 Okay thanks for your email, Actually we use the same syntax to attach and send emails on our AIX server, it was doing the same. So thought it will do the same on RHEL server as well, Syntax on AIX: uuencode file.txt file.txt|mail haridusi.us@gmail.com above used to send emails with file.txt as attachment. On Mon, Feb 22, 2016 at 10:43 PM, Bob Proulx wrote: > srihari D wrote: > > We are experiencing issues with uuencode, we wanted to send files as > > attachments by using uuencode, but it's displaying the contents of file > as > > body of the email. Below is the syntax being used, please help me on this > > issue. > > > > uuencode myfile.txt Display_name.txt|mail haridusi.us@gmail.com > > The above does not "attach" the file to the email. The above inserts > the output of uuencode into the body of the message. There is no > attachment in the above. > > In the above uuencode is working as it has been designed to work. All > is correct. > > These days you probably should want to use MIME attachments instead of > uuencode. I am not saying anything bad about uuencode. It does > exactly what it does and the command is still needed in order to > access uuencoded files. But these days MIME attachments are generally > the prefered method. > > I hesitate to suggest a way to do attachments because it depends so > much upon your environment. But 'mutt' handles attachments well. > > echo Attached is the myfile.txt file | > mutt -s "subject line here" -a myfile.txt -- haridusi.us@gmail.com > > Bob > From MAILER-DAEMON Tue Feb 23 17:02:23 2016 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1aYL2F-0002Fa-2D for mharc-bug-gnu-utils@gnu.org; Tue, 23 Feb 2016 17:02:23 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36339) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYL28-0002FM-V9 for bug-gnu-utils@gnu.org; Tue, 23 Feb 2016 17:02:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aYL25-0005fV-Ob for bug-gnu-utils@gnu.org; Tue, 23 Feb 2016 17:02:16 -0500 Received: from havoc.proulx.com ([96.88.95.61]:56742) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYL25-0005fK-G8 for bug-gnu-utils@gnu.org; Tue, 23 Feb 2016 17:02:13 -0500 Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id BF0CC1FB; Tue, 23 Feb 2016 15:02:12 -0700 (MST) Received: from hysteria.proulx.com (hysteria.proulx.com [192.168.230.119]) by joseki.proulx.com (Postfix) with ESMTP id 6C6AF219B6; Tue, 23 Feb 2016 15:02:12 -0700 (MST) Received: by hysteria.proulx.com (Postfix, from userid 1000) id 5DBA32DC5A; Tue, 23 Feb 2016 15:02:12 -0700 (MST) Date: Tue, 23 Feb 2016 15:02:12 -0700 From: Bob Proulx To: srihari D Subject: Re: uuencode (GNU sharutils) 4.7 Message-ID: <20160223143951165324905@bob.proulx.com> Mail-Followup-To: srihari D , bug-gnu-utils@gnu.org References: <20160222213511357322643@bob.proulx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 96.88.95.61 Cc: bug-gnu-utils@gnu.org X-BeenThere: bug-gnu-utils@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU utilities List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Feb 2016 22:02:21 -0000 srihari D wrote: > Okay thanks for your email, > > Actually we use the same syntax to attach and send emails on our AIX > server, it was doing the same. So thought it will do the same on RHEL > server as well, Maybe yes and maybe no. You were using the "mail" command. Which mail command is that on AIX? It has been a few years since I regularly used AIX and I don't remember. At one time it was the /bin/mail command which was a very simple mailer. Later it might have been the BSD mailx command which was much more powerful (powerful then but considered limited by comparison to later mailers). Neither /bin/mail nor mailx supported attachments. Nor MIME either as they predated the standard. Therefore I wonder what version this actually was and how this was creating attachments for you on AIX. Maybe it is a custom something there? For more details about the various history of mail, Mail, and mailx I think this is a pretty reasonable reference. There are others too. With these differences in mind you will see why I am asking. http://heirloom.sourceforge.net/mailx_history.html RHEL and other GNU/Linux distributions all came much later and they generally only include the newer mailx version of the command. They would generally symlink it to "mail" and "Mail" so that all called names would invoke the mailx command. The mailx command might be the heirloom version or might be the BSD version. Every distribution is different and I don't remember which is which and would need to look. > Syntax on AIX: uuencode file.txt file.txt|mail haridusi.us@gmail.com > > above used to send emails with file.txt as attachment. I wonder if perhaps we are using the term attachment to mean different things. Within the context of email I refer to the MIME standard. An overview reference it here: https://en.wikipedia.org/wiki/MIME Strictly speaking sending a file in the body of an email is not an attachment. That is simply in the body of the mail. Your syntax to uuencode a file and then send it as the body of an email is fine as far as that goes. (Usually the two names on the uuencode command line are the same however.) That should work the same on both legacy Unix systems and GNU/Linux systems such as RHEL. If you would be so kind as to satisfy my curiosity it would be great if you were to send me one of those messages from your AIX mail as an attachment. I would like to see what headers are produced and how it is attached. srihari D wrote: > We are experiencing issues with uuencode, we wanted to send files as > attachments by using uuencode, but it's displaying the contents of > file as body of the email. Below is the syntax being used, please > help me on this issue. > > uuencode myfile.txt Display_name.txt|mail haridusi.us@gmail.com Perhaps the difference is not at the sending side but at the reading side. Reading a mail generated as above would show the uuencoded block in the body of the email. That is expected since you have uuencoded a file and sent that in the body of the email. But perhaps you were using a special mailer that natively understood about uuencoded blocks and displayed that specially? Just guessing here but a difference in how you have read these may be all that is different. Bob From MAILER-DAEMON Mon Feb 29 06:35:35 2016 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1aaM6x-0004jS-5C for mharc-bug-gnu-utils@gnu.org; Mon, 29 Feb 2016 06:35:35 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53914) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaM6t-0004hd-LT for bug-gnu-utils@gnu.org; Mon, 29 Feb 2016 06:35:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aaM6q-000054-J0 for bug-gnu-utils@gnu.org; Mon, 29 Feb 2016 06:35:31 -0500 Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5]:50750 helo=snark.thyrsus.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaM6q-00004u-DA for bug-gnu-utils@gnu.org; Mon, 29 Feb 2016 06:35:28 -0500 Received: from [127.0.1.1] (localhost [127.0.0.1]) by snark.thyrsus.com (Postfix) with ESMTP id DDFD113A10D4 for ; Mon, 29 Feb 2016 06:35:27 -0500 (EST) X-Mailbox-Line: From nobody Mon Feb 29 06:35:27 2016 Content-Type: multipart/mixed; boundary="===============6379901228714039440==" MIME-Version: 1.0 To: bug-gnu-utils@gnu.org Subject: Problems in ode.1, plot.1, plotfont.1, tek2plot.1 Message-Id: <20160229113527.DDFD113A10D4@snark.thyrsus.com> Date: Mon, 29 Feb 2016 06:35:27 -0500 (EST) From: esr@thyrsus.com X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 71.162.243.5 X-BeenThere: bug-gnu-utils@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU utilities List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 11:35:33 -0000 --===============6379901228714039440== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database. See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification date of any manual page. You may wish to do that by hand. I apologize if this message seems spammy or impersonal. The volume of markup bugs I am tracking is over five hundred - there is no real alternative to generating bugmail from a database and template. -- Eric S. Raymond --===============6379901228714039440== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Problems with tek2plot.1: Missing or garbled name section. The most common form of garbling is a missing - or extra -. Or your manual page may have been generated by a tool that doesn't emit a NAME section as it should. Or your page may add running text such as a version or authorship banner. These problems make it impossible to lift the page to DocBook. They can also confuse third-party manpage browsers and some implementations of man -k. --- tek2plot.1-unpatched 2012-07-18 22:48:17.175686575 -0400 +++ tek2plot.1 2012-07-18 22:49:06.371687430 -0400 @@ -1,12 +1,9 @@ .TH TEK2PLOT 1 "Jun 2000" "FSF" "GNU Plotting Utilities" -.SH NAME -tek2plot \- translate Tektronix files to other graphics formats -.ig -Not all man macros define SB (and not all whatis parsers stop on .\") -.. .de SB \&\fB\s-1\&\\$1 \\$2\s0\fR .. +.SH NAME +tek2plot \- translate Tektronix files to other graphics formats .SH SYNOPSIS .B tek2plot [ --===============6379901228714039440== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Problems with ode.1: Macro definitions in the NAME section confuse doclifter and are likely to screw up third-party man viewers with their own parsers. --- ode.1-unpatched 2012-07-02 12:38:51.157056771 -0400 +++ ode.1 2012-07-02 12:41:46.497053492 -0400 @@ -1,12 +1,10 @@ .TH ODE 1 "Dec 1998" "FSF" "GNU Plotting Utilities" -.SH NAME -ode \- numerical solution of ordinary differential equations -.ig -Not all man macros define SB (and not all whatis parsers stop on .\") -.. .de SB \&\fB\s-1\&\\$1 \\$2\s0\fR .. + +.SH NAME +ode \- numerical solution of ordinary differential equations .SH SYNOPSIS .B ode [ --===============6379901228714039440== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Problems with plot.1: Missing or garbled name section. The most common form of garbling is a missing - or extra -. Or your manual page may have been generated by a tool that doesn't emit a NAME section as it should. Or your page may add running text such as a version or authorship banner. These problems make it impossible to lift the page to DocBook. They can also confuse third-party manpage browsers and some implementations of man -k. --- plot.1-unpatched 2012-07-06 13:21:02.614546256 -0400 +++ plot.1 2012-07-06 13:21:51.350545344 -0400 @@ -1,12 +1,6 @@ .TH PLOT 1 "Jun 2000" "FSF" "GNU Plotting Utilities" .SH NAME plot \- translate GNU metafiles to other graphics formats -.ig -Not all man macros define SB (and not all whatis parsers stop on .\") -.. -.de SB -\&\fB\s-1\&\\$1 \\$2\s0\fR -.. .SH SYNOPSIS .B plot [ @@ -15,6 +9,9 @@ .I files ] .SH DESCRIPTION +.de SB +\&\fB\s-1\&\\$1 \\$2\s0\fR +.. .LP .B plot translates files in GNU metafile format to other graphics formats, or --===============6379901228714039440== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Problems with plotfont.1: Missing or garbled name section. The most common form of garbling is a missing - or extra -. Or your manual page may have been generated by a tool that doesn't emit a NAME section as it should. Or your page may add running text such as a version or authorship banner. These problems make it impossible to lift the page to DocBook. They can also confuse third-party manpage browsers and some implementations of man -k. --- plotfont.1-unpatched 2012-07-05 17:31:24.527881120 -0400 +++ plotfont.1 2012-07-05 17:31:41.015880808 -0400 @@ -1,12 +1,9 @@ .TH PLOTFONT 1 "Jun 2000" "FSF" "GNU Plotting Utilities" -.SH NAME -plotfont \- produce character maps of fonts supported by the plotting utilities -.ig -Not all man macros define SB (and not all whatis parsers stop on .\") -.. .de SB \&\fB\s-1\&\\$1 \\$2\s0\fR .. +.SH NAME +plotfont \- produce character maps of fonts supported by the plotting utilities .SH SYNOPSIS .B plotfont [ --===============6379901228714039440==--