[libmail-message-perl] 07/11: add pod-spelling.patch
Damyan Ivanov
dmn at moszumanska.debian.org
Mon Jan 1 20:39:22 UTC 2018
This is an automated email from the git hooks/post-receive script.
dmn pushed a commit to branch master
in repository libmail-message-perl.
commit 98fb06a5695b71e6241e3a1e9b74b5a56cd09535
Author: Damyan Ivanov <dmn at debian.org>
Date: Mon Jan 1 20:34:17 2018 +0000
add pod-spelling.patch
---
debian/patches/pod-spelling.patch | 278 ++++++++++++++++++++++++++++++++++++++
debian/patches/series | 1 +
2 files changed, 279 insertions(+)
diff --git a/debian/patches/pod-spelling.patch b/debian/patches/pod-spelling.patch
new file mode 100644
index 0000000..54b743f
--- /dev/null
+++ b/debian/patches/pod-spelling.patch
@@ -0,0 +1,278 @@
+Description: a couple of spelling mistakes in POD
+Author: Damyan Ivanov <dmn at debian.org>
+Forwarded: https://rt.cpan.org/Ticket/Display.html?id=123993
+Bug: https://rt.cpan.org/Ticket/Display.html?id=123993
+
+--- a/lib/Mail/Box/Parser.pod
++++ b/lib/Mail/Box/Parser.pod
+@@ -355,7 +355,7 @@ Inherited, see L<Mail::Reporter/"Cleanup
+ =item Warning: File $filename changed during access.
+
+ When a message parser starts working, it takes size and modification time
+-of the file at hand. If the folder is written, it checks wether there
++of the file at hand. If the folder is written, it checks whether there
+ were changes in the file made by external programs.
+
+ Calling L<Mail::Box::update()|Mail::Box/"The folder"> on a folder before it being closed
+--- a/lib/Mail/Box/Parser/Perl.pod
++++ b/lib/Mail/Box/Parser/Perl.pod
+@@ -262,7 +262,7 @@ Inherited, see L<Mail::Reporter/"Cleanup
+ =item Warning: File $filename changed during access.
+
+ When a message parser starts working, it takes size and modification time
+-of the file at hand. If the folder is written, it checks wether there
++of the file at hand. If the folder is written, it checks whether there
+ were changes in the file made by external programs.
+
+ Calling L<Mail::Box::update()|Mail::Box/"The folder"> on a folder before it being closed
+--- a/lib/Mail/Message.pod
++++ b/lib/Mail/Message.pod
+@@ -53,7 +53,7 @@ Mail::Message - general message object
+ =head1 DESCRIPTION
+
+ A C<Mail::Message> object is a container for MIME-encoded message information,
+-as defined by RFC2822. Everything what is not specificly related to storing
++as defined by RFC2822. Everything what is not specificaly related to storing
+ the messages in mailboxes (folders) is implemented in this class. Methods
+ which are related to folders is implemented in the L<Mail::Box::Message|Mail::Box::Message>
+ extension.
+@@ -326,11 +326,11 @@ is used mainly for recognizing discussio
+
+ Returns a string representing the location of this part. In case the
+ top message is a single message, 'undef' is returned. When it is a
+-multipart, '1' upto the number of multiparts is returned. A multi-level
++multipart, '1' up to the number of multiparts is returned. A multi-level
+ nested part may for instance return '2.5.1'.
+
+ Usually, this string is very short. Numbering follows the IMAP4 design,
+-see RFC2060 secion 6.4.5.
++see RFC2060 section 6.4.5.
+
+ =item $obj-E<gt>B<print>( [$fh] )
+
+--- a/lib/Mail/Message/Body/Multipart.pod
++++ b/lib/Mail/Message/Body/Multipart.pod
+@@ -613,7 +613,7 @@ C<RECURSE> or a code reference. However
+
+ L<foreachLine()|Mail::Message::Body::Multipart/"METHODS"> should be used on decoded message bodies only, because
+ it would attempt to modify part-headers and separators as well, which is
+-clearly not acceptible.
++clearly not acceptable.
+
+ =back
+
+--- a/lib/Mail/Message/Body/Nested.pod
++++ b/lib/Mail/Message/Body/Nested.pod
+@@ -492,7 +492,7 @@ of the package.
+
+ L<foreachLine()|Mail::Message::Body::Nested/"METHODS"> should be used on decoded message bodies only, because
+ it would modify the header of the encapsulated message. which is
+-clearly not acceptible.
++clearly not acceptable.
+
+ =back
+
+--- a/lib/Mail/Message/Construct/Reply.pod
++++ b/lib/Mail/Message/Construct/Reply.pod
+@@ -98,7 +98,7 @@ method: no reply message produced.
+ Usually, the reply method can create a nice, sufficient message from the
+ source message's body. In case you like more complicated reformatting,
+ you may also create a body yourself first, and pass this on to this
+-C<reply> method. Some of the other options to this method will be ingored
++C<reply> method. Some of the other options to this method will be ignored
+ in this case.
+
+ =item group_reply => BOOLEAN
+--- a/lib/Mail/Message/Field.pod
++++ b/lib/Mail/Message/Field.pod
+@@ -90,7 +90,7 @@ Always true, to make it possible to say
+
+ =item overload: B<cmp>
+
+-(string comparison) Compare the unfolded body of a field with an other
++(string comparison) Compare the unfolded body of a field with another
+ field or a string, using the buildin C<cmp>.
+
+ =back
+@@ -179,7 +179,7 @@ place (without changing the folding stor
+ =item $obj-E<gt>B<toDisclose>()
+
+ Returns whether this field can be disclosed to other people, for instance
+-when sending the message to an other party. Returns a C<true> or C<false>
++when sending the message to another party. Returns a C<true> or C<false>
+ condition.
+ See also L<Mail::Message::Head::Complete::printUndisclosed()|Mail::Message::Head::Complete/"Access to the header">.
+
+@@ -251,7 +251,7 @@ example:
+
+ Returns the body as a set of lines. In scalar context, this will be one line
+ containing newlines. Be warned about the newlines when you do
+-pattern-matching on the result of thie method.
++pattern-matching on the result of the method.
+
+ The optional $body argument changes the field's body. The folding of the
+ argument must be correct.
+@@ -376,7 +376,7 @@ example:
+
+ Mail::Message::Field->toDate(localtime);
+ Mail::Message::Field->toDate; # same
+- # returns someting like:
++ # returns something like:
+ # Wed, 28 Aug 2002 10:40:25 +0200
+
+ =item $obj-E<gt>B<toInt>()
+@@ -619,7 +619,7 @@ contains the timezone difference to UTC,
+ this as comment. Application must ignore this data because the C<Date>
+ field is structured.
+
+-The last field is unstructured. The text between parantheses is an
++The last field is unstructured. The text between parentheses is an
+ integral part of the subject line.
+
+ =head2 Getting a field
+@@ -767,7 +767,7 @@ in case no address is known.
+ =head3 Specifying field data
+
+ Field data can be anything, strongly dependent on the type
+-of field at hand. If you decide to contruct the fields very
++of field at hand. If you decide to construct the fields very
+ carefully via some L<Mail::Message::Field::Full|Mail::Message::Field::Full> extension (like via
+ L<Mail::Message::Field::Addresses|Mail::Message::Field::Addresses> objects), then you will have protection
+ build-in. However, you can bluntly create any L<Mail::Message::Field|Mail::Message::Field>
+--- a/lib/Mail/Message/Field/Attribute.pod
++++ b/lib/Mail/Message/Field/Attribute.pod
+@@ -93,7 +93,7 @@ Encode::encodings(':all').
+
+ =item language => STRING
+
+-RFC2231 adds the possiblity to specify a language with the field. When no
++RFC2231 adds the possibility to specify a language with the field. When no
+ language is specified, none is included in the encoding. Valid language
+ names are defined by RFC2130. This module has only limited support for
+ this feature.
+--- a/lib/Mail/Message/Field/DKIM.pod
++++ b/lib/Mail/Message/Field/DKIM.pod
+@@ -218,7 +218,7 @@ Attributes are not supported here.
+ =item $obj-E<gt>B<addTag>($name, $value|@values)
+
+ Add a tag to the set. When the tag already exists, it is replaced.
+-Names are (coverted to) lower-case. When multiple values are given,
++Names are (converted to) lower-case. When multiple values are given,
+ they will be concatenated with a blank (and may get folded there later)
+
+ =item $obj-E<gt>B<addresses>()
+@@ -340,7 +340,7 @@ When the signature was created in UNIX-l
+
+ =item $obj-E<gt>B<tagVersion>()
+
+-Signature header synax version (usually 1)
++Signature header syntax version (usually 1)
+
+ =back
+
+--- a/lib/Mail/Message/Field/Full.pod
++++ b/lib/Mail/Message/Field/Full.pod
+@@ -102,7 +102,7 @@ L<Mail::Message::Field::Full|Mail::Messa
+ way: the string which is produced by the original object is parsed
+ again. Usually, the string which is parsed is exactly the line (or lines)
+ as found in the original input source, which is a good thing because Full
+-fields are much more carefull with the actual content.
++fields are much more careful with the actual content.
+
+ %options are passed to the constructor (see L<new()|Mail::Message::Field::Full/"METHODS">). In any case, some
+ extensions of this Full field class is returned. It depends on which
+@@ -416,7 +416,7 @@ a '?'.
+
+ Encoding on text is slightly more complicated than encoding structured data,
+ because it contains blanks. Visible blanks have to be ignored between two
+-encoded words in the text, but not when an encoded word follows or preceeds
++encoded words in the text, but not when an encoded word follows or precedes
+ an unencoded word. Phrases and comments are texts.
+
+ =back
+--- a/lib/Mail/Message/Head.pod
++++ b/lib/Mail/Message/Head.pod
+@@ -189,7 +189,7 @@ example:
+
+ =item $obj-E<gt>B<orderedFields>()
+
+-Retuns the fields ordered the way they were read or added.
++Returns the fields ordered the way they were read or added.
+
+ =back
+
+--- a/lib/Mail/Message/Head/Complete.pod
++++ b/lib/Mail/Message/Head/Complete.pod
+@@ -219,7 +219,7 @@ example: of adding a spam group to a hea
+ =item $obj-E<gt>B<count>($name)
+
+ Count the number of fields with this $name. Most fields will return 1:
+-only one occurance in the header. As example, the C<Received> fields
++only one occurrence in the header. As example, the C<Received> fields
+ are usually present more than once.
+
+ =item $obj-E<gt>B<delete>($name)
+--- a/lib/Mail/Message/Head/FieldGroup.pod
++++ b/lib/Mail/Message/Head/FieldGroup.pod
+@@ -115,7 +115,7 @@ Version number for the software which pr
+
+ Add a field to the header, using the field group. When the field group
+ is already attached to a real message header, it will appear in that
+-one as well as being registed in this set. If no header is defined,
++one as well as being registered in this set. If no header is defined,
+ the field only appears internally.
+
+ example: adding a field to a detached list group
+@@ -179,7 +179,7 @@ not too different.
+ =item $obj-E<gt>B<type>()
+
+ Returns an abstract name for the field group; which software is
+-controling it. C<undef> is returned in case the type is not known.
++controlling it. C<undef> is returned in case the type is not known.
+ Valid names are group type dependent: see the applicable manual
+ pages. A list of all types can be retrieved with L<implementedTypes()|Mail::Message::Head::FieldGroup/"Constructors">.
+
+--- a/lib/Mail/Message/Head/ListGroup.pod
++++ b/lib/Mail/Message/Head/ListGroup.pod
+@@ -297,7 +297,7 @@ The L<Mail::Message::Head::ListGroup|Mai
+ mailing lists, some of which are very popular and some of which are
+ rare.
+
+-Numerous fields in a header are addded when the message is passed
++Numerous fields in a header are added when the message is passed
+ through a mailing list server. Each list software has defined its own
+ fields, sometimes woth conflicting definitions. There are also two
+ RFCs about mailing list: C<rfc2919> and C<rfc2369>.
+--- a/lib/Mail/Message/Head/Partial.pod
++++ b/lib/Mail/Message/Head/Partial.pod
+@@ -207,7 +207,7 @@ Inherited, see L<Mail::Message::Head::Co
+ =item $obj-E<gt>B<removeFields>( <STRING|Regexp>, ... )
+
+ Remove the fields from the header which are exactly named 'STRING' (case
+-insensitive) or match the REGular EXPresssion. Do not forget to add the
++insensitive) or match the regular expression. Do not forget to add the
+ 'i' modifier to the Regexp, because fields are case insensitive.
+
+ See also L<removeField()|Mail::Message::Head::Complete/"Access to the header"> which is used to remove one field object from
+--- a/lib/Mail/Message/Part.pod
++++ b/lib/Mail/Message/Part.pod
+@@ -27,7 +27,7 @@ Mail::Message::Part - a part of a messag
+ =head1 DESCRIPTION
+
+ A C<Mail::Message::Part> object contains a message which is included in
+-the body of an other message. For instance I<attachments> are I<parts>.
++the body of another message. For instance I<attachments> are I<parts>.
+
+ READ L<Mail::Message|Mail::Message> FIRST. A part is a special message: it has a
+ reference to its parent message, and will usually not be sub-classed
+--- a/lib/Mail/Message/Replace/MailInternet.pod
++++ b/lib/Mail/Message/Replace/MailInternet.pod
+@@ -283,7 +283,7 @@ but may be different from L<Mail::Intern
+
+ =item Exclude => ARRAY-OF-NAMES
+
+-Remove the fields witht the specified names from the produced reply message.
++Remove the fields with the specified names from the produced reply message.
+
+ =item From => ADDRESSES
+
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 0000000..ad85da2
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+pod-spelling.patch
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libmail-message-perl.git
More information about the Pkg-perl-cvs-commits
mailing list