-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
I've currently encountered a very strange problem when running a script which creates a ZSLucene index under CLI and under Apache2. I started out under CLI and everything works fine. When I run this creation process over Apache2 I get Notice: iconv() [function.iconv]: Detected an illegal character in input string in Zend/Search/Lucene/Analysis/Analyzer/Common/Text.php on line 56 all over the place. This happens which German umlaut character, but it does *not* happen when running under CLI. So I'm trying to found out what the difference between these two environments is. It' is the same PHP version # php -v PHP 5.2.0-8+etch4 (cli) (built: May 13 2007 18:29:48) from phpinfo() over Apache2: PHP Version 5.2.0-8+etch4 Build Date May 13 2007 18:12:39 Server API Apache 2.0 Handler I then tried to execute them in equally clean environments by wiping the php.ini and only enabling PDO for database access: php -n -d extension=pdo.so -d extension=pdo_mysql.so create.php and this ran fine. I did the same for Apache2 -> same problem. I currently have no clue what the difference (besides SAPI) between this two environments is which would affect character set conversion inside Zend_Search_Lucene. thanks for any pointers, - - Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFG4piu1nS0RcInK9ARAhitAJ4gT3VD7wD5UJV4JO2OJ9Y+6JtGggCXVKoy pzuwwKiuIjA4F4SSdu4lWQ== =jcKg -----END PGP SIGNATURE-----
