Description: ------------ I added the hash table support when createing MO file.

Added patch hashtable-support.patch.

clockwerx@clockwerx-desktop:~/pear-svn-git/File_Gettext$ patch -p1 < patch- download.php\?id\=18562\&patch\=hashtable- support.patch\&revision\=1306331662 can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/File_Gettext-0.4.1/Gettext/MO.php b/File_Gettext- 0.4.1/Gettext/MO.php |index 521b489..a84a305 100644 |--- a/File_Gettext-0.4.1/Gettext/MO.php |+++ b/File_Gettext-0.4.1/Gettext/MO.php -------------------------- File to patch: Gettext/MO.php patching file Gettext/MO.php Hunk #1 FAILED at 233. Hunk #2 FAILED at 270. Hunk #3 FAILED at 279. Hunk #4 FAILED at 296. Hunk #5 succeeded at 332 (offset 20 lines). 4 out of 5 hunks FAILED -- saving rejects to file Gettext/MO.php.rej This code is now living on github, so maybe sending in pull request might be easier.

I sent a pull request: https://github.com/pear/File_Gettext/pull/1 Elbandi

Can you run phpcs on your patch to ensure it conform to the PEAR coding standards? Also add docblocks and inline comments for the new methods. I have no idea what they do from a cursory glance. I also recommend more descriptive variable and method names. What does _hashpjw() mean? What is $g?

The all changes come from official GetText. The hash function: http://goo.gl/o2VQO The prime functions: http://goo.gl/Cs1DR And the inserted lines to "save" method: http://goo.gl/Eqru1 I added the coding style fix patch to pull request.

Darned google just shut down all of the codesearch links. We'll take your work from it that these are ported correctly.

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.

Just filed a bug report related to this at https://pear.php.net/bugs/bug.php?id=19419 Not terribly happy with the codesearch shutdown, since I cannot attempt to fix the bug myself now..