Working with gettext as your translation engine your project? In need of a rough translation of your application for a mockup/preview/…?

Paul Dixon offeres a free service that automatically translates a gettext PO file with Google Translate. I personally use gettext a lot because of its speed and ease of use (with poEdit) and this will certainly be of use.

Of course the results should not be used in a production application.

Although I must admit I didn’t notice it, less than 2 months after it was decided to create a new version for Propel, it was actually released.

Last week, on the 8th of November, the new 1.4.0 version has been released for production use. Additionally they also set up a blog to prove Propel is still very much alive.

Propel 1.4 is a backwards compatible evolution of Propel 1.3. It offers lots of bug fixes, some very interesting new features, speed enhancements, and a very simple upgrade path: rebuild your model after updating Propel, and your application works as always. Except it works better…

It all sounds to good to be true!

A first migration of a project to this new version went smoothly: remember to remove the *-classmap.php file that was generated by 1.3.0 because it has been integrated in the main config file. It’s also recommendable to delete the /map sub-folder in your models folder because 1.4.0 generates newly named *TableMap.php files.

Also good to have: full query logging (Propel 1.3 switched to PDO and lost this feature but it’s back!).

I must also admit I have never actually implemented Doctrine, but that’s also because I haven’t found a reason while using Propel.

After being forced to upgrade to the latest Windows Live Messenger version yesterday, I had to find a solution for the wlcomm.exe error reports I kept getting with this version.

I kept using the old (8.5?) version ever since a new Live Messenger version came out earlier this year because in these new versions I couldn’t sign in: a Windows error report would be generated with each sign in attempt.

The error report showed:

AppName: wlcomm.exe     AppVer: 14.0.8098.930     ModName: crypt32.dll
ModVer: 5.131.2600.5512     Offset: 0000ed05

Several possible solutions failed to fix it for me (and with a search for messenger + wlcomm.exe clearly for a lot of other people too).

While there seem to be different causes, if you have a NVIDIA chipset and use their driver package, the solution is to uninstall the NVidia ForceWare Network Access Manager and you are good to go!

Apparently it is some kind of firewall software for the NVIDIA chipset.