Skip Menu | will be shut down on March 1st, 2021.

This queue is for tickets about the Pod-Spell CPAN distribution.

Report information
The Basics
Id: 57492
Status: open
Priority: 0/
Queue: Pod-Spell

Owner: Nobody in particular
Requestors: APOCAL [...]

Bug Information
Severity: Normal
Broken in: 1.01
Fixed in: (no value)

Subject: Ordering of stopwords is important!
Download (untitled) / with headers
text/plain 890b
Hello, I've been using this module for a while and loved it for catching my typos, ha! However, I've always been puzzled that sometimes it would fail tests, telling me that "foo" is misspelled. I've added it to the stopwords list! After giving up and accepting FAILs sometimes, I somehow arrived at the solution for this. This module parses the POD and adds stopwords, and checks the validity of words at the same time. So if you have POD like this: =head1 DESCRIPTION foo is the best! =for stopwords foo It will fail the test, but if you swap the head1 and stopwords like this: =for stopwords foo =head1 DESCRIPTION foo is the best! It will PASS, yay! I think this is a situation where many authors could get tripped over. I don't think the code should be fixed to address this, but just a mention in the POD would be good enough. Thanks again! -- ~Apocalypse
is this still an issue?
Subject: Re: [ #57492] Ordering of stopwords is important!
Date: Thu, 19 Sep 2013 01:06:54 -0500
To: bug-Pod-Spell [...]
From: Caleb Cushing <xenoterracide [...]>
Download (untitled) / with headers
text/plain 505b
probably, but I'm not sure. Pod::Spell needs a lot of work, but is still not as well tested as it should be, and parts of it still seem cryptic. On Wed, Sep 18, 2013 at 10:01 PM, Karen Etheridge via RT <> wrote: Show quoted text
> Queue: Pod-Spell > Ticket <URL: > > > is this still an issue?
-- Caleb Cushing Calendar:
Download (untitled) / with headers
text/plain 431b
On Wed Sep 18 23:01:58 2013, ETHER wrote: Show quoted text
> is this still an issue?
Yes. Pod::Spell is an extended Pod::Parser. It makes a single pass over the file, spewing data to an output handle. It learns stopwords as it goes and uses them on subsequent text. "Fixing" this would probably mean moving away from Pod::Parser and the use of an output handle. I think a documentation fix is sufficient. I've pushed a commit to that effect.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to