[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#311450: marked as done ('man mailto' typos: "comand", "diaplsyed", "impossble", "knowledgable", etc.)



Your message dated Wed, 17 Aug 2005 13:17:17 -0700
with message-id <E1E5ULd-0005iW-00@spohr.debian.org>
and subject line Bug#311450: fixed in metamail 2.7-48
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 1 Jun 2005 05:19:29 +0000
>From agcosta@gis.net Tue May 31 22:19:28 2005
Return-path: <agcosta@gis.net>
Received: from mx03.gis.net [208.218.130.11] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1DdLdY-0005Au-00; Tue, 31 May 2005 22:19:28 -0700
Received: from arf ([207.7.193.216]) by mx03.gis.net; Wed, 01 Jun 2005 01:19:23 -0400
Received: from alfie by Arf with local (Exim 3.36 #1 (Debian))
	id 1DdLeS-0003jy-00; Wed, 01 Jun 2005 01:20:24 -0400
Content-Type: multipart/mixed; boundary="===============0283267441=="
MIME-Version: 1.0
From: A Costa <agcosta@gis.net>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: 'man mailto' typos: "comand", "diaplsyed", "impossble", "knowledgable", etc.
X-Mailer: reportbug 3.12
Date: Wed, 01 Jun 2005 01:19:17 -0400
Message-Id: <E1DdLeS-0003jy-00@Arf>
Sender: A Costa <alfie@Arf>
X-BadReturnPath: alfie@Arf rewritten as agcosta@gis.net
  using "From" header
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

This is a multi-part MIME message sent by reportbug.

--===============0283267441==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: metamail
Version: 2.7-47
Severity: minor
Tags: patch


Found some typos in '/usr/share/man/man1/mailto.1.gz', see attached '.diff'.

Hope this helps...

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.11-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages metamail depends on:
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libncurses5                 5.4-4        Shared libraries for terminal hand

-- no debconf information

--===============0283267441==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="mailto.1.diff"

--- -	2005-06-01 01:17:50.577636000 -0400
+++ /tmp/mailto1.gz.14204	2005-06-01 01:17:50.000000000 -0400
@@ -1,6 +1,6 @@
 .TH MAILTO 1 "Release 1" "Bellcore Prototype"
 .SH NAME
-mailto - Simple mutlimedia mail sending program
+mailto - Simple multimedia mail sending program
 .SH SYNOPSIS
 .ta 8n
 \fBmailto\fP	[-a] [-c] [-s] [recipient name(s)]
@@ -74,9 +74,9 @@
 
 Basically, mailto can include the following things in mail:
 
-1.  Simple formatted text, using the MIME type "text/richtext".  This allows you to add emphasis to your message using underlining, bold text, italic (diaplsyed as reverse video), centering, and the like.
+1.  Simple formatted text, using the MIME type "text/richtext".  This allows you to add emphasis to your message using underlining, bold text, italic (displayed as reverse video), centering, and the like.
 
-2.  Non-text data.  Metamail can include pictures, sounds, and other non-textual data in the middle of any mail message.  The mailcap configuration mechanism can even make this process reasonably user-friendly, but a knowledgable user can include non-textual data even in the absence of a proper mailcap entry.
+2.  Non-text data.  Metamail can include pictures, sounds, and other non-textual data in the middle of any mail message.  The mailcap configuration mechanism can even make this process reasonably user-friendly, but a knowledgeable user can include non-textual data even in the absence of a proper mailcap entry.
 
 3.  Text including non-ASCII characters, such as Hebrew or Russian.  Currently, mailto directly supports only the ISO-8859-* family of character sets, which means that it does not meet the needs of Asian users, in particular.  However, languages that can not be expressed in the ISO-8859 family can still be included in the same way non-text data can be included.
 
@@ -275,7 +275,7 @@
 
 .I 
 Altered editing behavior:
-The ~e and ~v commands, which are used to edit the message being composed, will behave differently in mailto if the mail includes non-text portions.  In such cases, each part will be edited separately, in sequence, which makes it impossble for the user to accidentally mess up the inter-part boundaries.  Moreover, if the mailcap entry for a given data type includes an "edit" field, the user will be given the choice of editing with the program named there or editing with his usual (text) editor.  In most cases, this will be a choice between using a structured editor or editing the raw data stream.
+The ~e and ~v commands, which are used to edit the message being composed, will behave differently in mailto if the mail includes non-text portions.  In such cases, each part will be edited separately, in sequence, which makes it impossible for the user to accidentally mess up the inter-part boundaries.  Moreover, if the mailcap entry for a given data type includes an "edit" field, the user will be given the choice of editing with the program named there or editing with his usual (text) editor.  In most cases, this will be a choice between using a structured editor or editing the raw data stream.
 
 .I 
 Altered behavior for large messages:
@@ -283,7 +283,7 @@
 
 .I
 New -r command-line option 
-The -r comand-line option is not found in standard Berkeley mail.
+The -r command line option is not found in standard Berkeley mail.
 
 .SH SUMMARY OF OPTIONS
 -a <charset> -- specifies an alternate character set in use.  This had better be the one your terminal is actually using.  Currently it must be in the iso-8859 character set family.

--===============0283267441==--

---------------------------------------
Received: (at 311450-close) by bugs.debian.org; 17 Aug 2005 20:25:49 +0000
>From katie@spohr.debian.org Wed Aug 17 13:25:49 2005
Return-path: <katie@spohr.debian.org>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
	id 1E5ULd-0005iW-00; Wed, 17 Aug 2005 13:17:17 -0700
From: Javier Fernandez-Sanguino Pen~a <jfs@computer.org>
To: 311450-close@bugs.debian.org
X-Katie: $Revision: 1.56 $
Subject: Bug#311450: fixed in metamail 2.7-48
Message-Id: <E1E5ULd-0005iW-00@spohr.debian.org>
Sender: Archive Administrator <katie@spohr.debian.org>
Date: Wed, 17 Aug 2005 13:17:17 -0700
Delivered-To: 311450-close@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: metamail
Source-Version: 2.7-48

We believe that the bug you reported is fixed in the latest version of
metamail, which is due to be installed in the Debian FTP archive:

metamail_2.7-48.diff.gz
  to pool/main/m/metamail/metamail_2.7-48.diff.gz
metamail_2.7-48.dsc
  to pool/main/m/metamail/metamail_2.7-48.dsc
metamail_2.7-48_i386.deb
  to pool/main/m/metamail/metamail_2.7-48_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 311450@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Javier Fernandez-Sanguino Pen~a <jfs@computer.org> (supplier of updated metamail package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed, 17 Aug 2005 00:17:20 +0200
Source: metamail
Binary: metamail
Architecture: source i386
Version: 2.7-48
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Javier Fernandez-Sanguino Pen~a <jfs@computer.org>
Description: 
 metamail   - implementation of MIME
Closes: 311450 311451 311452 311453 321473
Changes: 
 metamail (2.7-48) unstable; urgency=low
 .
   * QA Group upload by Javier Fernandez-Sanguino
   * Fix typos in manpages with patches provided by A Costa (Closes: #311450,
     #311451, #311452, #311453)
   * Fix use of temporary files in showpartial so that uses cannot introduce
     a DOS through the use of hard links. Temporary files are created with
     mktemp and their filename is stored in ~/.metamail_treeroot (Closes:
     #321473)
Files: 
 ebab53906f2624a01c6eaea691668a94 700 mail optional metamail_2.7-48.dsc
 89c20ef55357765c2989dfc8ca325b24 342127 mail optional metamail_2.7-48.diff.gz
 4aceb6afcdebb57eea9a86098f3c8740 150156 mail optional metamail_2.7-48_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iQCVAwUBQwJprftEPvakNq0lAQL0jwP/R3uN8LauV/Vy5yFKwwpMAoyJRzqxuQqv
xhc2a7pAmIAiTkSHoIiy+/9avAbYLX4kl9DwibWldKl41jnBt3tiC0f5C8EwkmR1
8s9mdQ6QoCaLvNFcDALfHK/usHzrZZdj7yq6Zw2Z7zl9JyAVjWPWMTL/8pyA6kJ3
1dK4Fx3oRAM=
=SgzR
-----END PGP SIGNATURE-----



Reply to: