The PHP-GTK Community Site has posted about an issue that's been found with PHP-GTK on a Windows Vista machine that can cause problems with how the OS handles memory (by Wim Stockman).

My work station is WinXp system and my friend where I had to create it for has the new Vista and somewhere over 9000 pictures to be managed. On my system everything worked fine, but on my friends system i always got the error can not open file.

Further testing revealed that it was the OS at fault - Vista wasn't handling the memory usage for the application correctly. When it was run directly from the file explorer (versus in the PHP-GTK console) though, it worked just fine.

PHP-GTKers working in English-related applications, don't have a problem with debugging messages output to a console when debugging, but applications on a more international front have issues with their output. But help has been found in this new post on the Riff Blog - a method for correctly encoding PHP-GTK applications.

PHP scripts are typically stored under UTF-8 encoding to limit i18n headaches, while the console in which their output will be displayed is normally configured to some regional encoding, like IBM850 in Windows/XP French.

So we need a workaround...

He splits the process out into a few steps, each with its own explanation and code:

• Builtin tools
• Buffering
• Flushing
• PHP-GTK is not PHP for the Web
• Auto-flushing

All wrapped up with a final solution - using the iconv functionality in combination with some output buffering to correctly display the message.