pspell_new_config

(PHP 4 >= 4.0.2, PHP 5, PHP 7, PHP 8)

pspell_new_configCarrega um novo dicionário com configurações baseadas em uma configuração fornecida

Descrição

pspell_new_config(PSpell\Config $config): PSpell\Dictionary|false

pspell_new_config() abre um novo dicionário com configurações especificadas em um config, criado com pspell_config_create() e modificado com funções pspell_config_*(). Este método oferece a maior flexibilidade e possui todas as funcionalidades fornecidas por pspell_new() e pspell_new_personal().

Parâmetros

config

O parâmetro config é aquele retornado por pspell_config_create() quando a configuração foi criada.

Valor Retornado

Retorna uma instância de PSpell\Dictionary em caso de sucesso, ou false em caso de falha

Registro de Alterações

Versão Descrição
8.1.0 O parâmetro config agora espera uma instância de PSpell\Config; anteriormente, um resource era esperado.
8.1.0 Agora, retorna uma instância de PSpell\Dictionary; anteriormente, um resource era retornado.

Exemplos

Exemplo #1 pspell_new_config()

<?php
$pspell_config
= pspell_config_create("en");
pspell_config_personal($pspell_config, "/var/dictionaries/custom.pws");
pspell_config_repl($pspell_config, "/var/dictionaries/custom.repl");
$pspell = pspell_new_config($pspell_config);
?>

adicione uma nota

Notas Enviadas por Usuários (em inglês) 1 note

up
2
soapergem at gmail dot com
16 years ago
Today I ran into an interesting problem that I thought I'd share here to save the next developer that ends up in the same situation a whole lot of trouble. I have been running PHP5 as a FastCGI module on a Windows IIS server, and I recently installed the Aspell library and enabled the pspell extension in my php.ini file. I also installed the English Aspell dictionary. But when I went to use pspell, I was getting ambiguous errors that would terminate script execution without warning.

So I started to break things down, and came to the conclusion that the following code successfully executed its first line, but broke on the last line with the call to pspell_new_config:

<?php

$pspell_config
= pspell_config_create('en');
$pspell_link = pspell_new_config($pspell_config);

?>

This returned a FastCGI error in the browser, with error number -2147467259 (0x80004005). By luck, I happened to think to try the same script via the command line, which gave a much more descriptive error. What happened was that the dictionary installer created the *.dat files in the Aspell\data directory using the Windows standard CRLF "\r\n" instead of the UNIX standard "\n" for line feeds. By changing these all back to the UNIX standard, everything worked. It's apparently very touchy about these line feeds, so if you're wracking your brain over why pspell_new_config is breaking your scripts and you're using a Windows server, start by ensuring that there aren't any extraneous "\r" characters in your dictionary files.
To Top