Corrected typo in summary

We'll also need your dictionary to investigate it.
Though I doubt it has something to do with PHP.
If pspell doesn't use your dictionary, it's hardly PHP problem.

The pspell dictionary or my custom one? The pspell one is a standard English dictionary downloaded from the Aspell website at http://ftp.gnu.org/gnu/aspell/w32/Aspell-en-0.50-2-3.exe. I included my custom dictionary at the bottom of the reproduce code.

Works perfectly fine here, on Linux.
<?php
$spelling = pspell_new_personal('/tmp/.aspell.en.pws', 'en');
$suggestions = pspell_suggest($spelling, 'bloomsbur');
var_dump(print_r($suggestions));
?>
Array
(
    [0] => blooms bur
    [1] => blooms-bur
    [2] => Bloomsbury
    [3] => bloomsbury <--------
    [4] => blooms
    [5] => Bloom's
    [6] => bloom's
)
bool(true)

I tested the code on another XP computer and also on my Linux server, all with PHP 5.2.1 and it doesn't seem to work (even with full permissions).

<?php
$spelling = pspell_new_personal('/home/site/public_html/custom.dict', 'en');		
$suggestions = pspell_suggest($spelling, 'bloomsbur');
echo '<pre>'; print_r($suggestions); '</pre>';
?>

david@server1 [/home/site/public_html]# ls -al
...
-rwxrwxrwx   1 site site    32 Mar 10 19:57 custom.dict*
...

Output:
Array
(
    [0] => blooms bur
    [1] => blooms-bur
    [2] => blooms
    [3] => Bloom's
    [4] => bloom's
    [5] => bloomers
    [6] => Bloomer
    [7] => bloomer
)

So why is that PHP problem?
You pspell doesn't use your custom dictionary, I don't think PHP can fix it.

This is with the bundled library with PHP i.e. php_pspell.dll on Windows. So is that not a PHP problem?

>This is with the bundled library with PHP i.e. php_pspell.dll on
Windows. 
>So is that not a PHP problem?
In the previous post you said you also tested in on Linux (but didn't say what was the result).

In my comment 10 Mar 8:05pm UTC this is the test on Linux with the output i.e. it is the same result as on Windows - not working.

What Pspell/Aspell version are you using?

Windows:

Aspell-0.50-3
Aspell-en-0.50-2

Linux:

International Ispell Version 3.1.20 (but really Aspell 0.50.3)

Try to update it to the latest stable version and see if this fixes the problem.

This is the latest Windows version.

I'm talking about Linux.

Not reproducible on Windows either.
Check your Aspell install and make sure the dictionary format is correct.
Not PHP problem.

I reinstalled Aspell on Windows and am still unable to get it to pick up the custom dictionary. The file format I am using is:

personal_ws-1.1 en 1
bloomsbury

in custom.dict with the code in my original description.

As I said, it works fine here both on Linux and Windows.

Yeah. So how can we go about fixing this? The pspell_new_personal() function doesn't seem to return any kind of error even if the personal dictionary path provided doesn't exist (error reporting all on etc). Is your personal dictionary in the same format as mine?

custom.dict:

personal_ws-1.1 en 1
bloomsbury

>Yeah. So how can we go about fixing this?
First make sure it works for you using Aspell console utilities.

>Is your personal dictionary in the same format as mine? 
It's a copy/paste.

I upgraded to Aspell 0.60 which is the latest version for Linux and it works fine now. The bug exists only in the 0.50 version it seems (this is the only version available for Windows).

I also noticed that if the personal dictionary path provided to pspell_new_personal() doesn't exist or isn't accessible, the function does not return any kind of error or warning. For example if I change the permissions of the custom.dict file so the PHP user cannot access it, the function doesn't error but just doesn't make use of the custom dictionary file. Should I submit this as a separate bug?

>I upgraded to Aspell 0.60 which is the latest version for Linux and
>it works fine now
So I was right and it's not PHP problem.

>Should I submit this as a separate bug?
pspell_new_personal() just modifies the config used further during processing. 
I'd expect the error to appear either when modifying the config or when using its values. In both cases Pspell doesn't report any error.
So yes, you can submit a report, but to Pspell developers, since we can't fix Pspell.