<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 24 May 2013 08:03:43 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Christian Weiske's Blog: Generating CHM files w/Wine on Linux & a bit about PEAR's PhD trasition]]></title>
      <guid>http://www.phpdeveloper.org/news/12039</guid>
      <link>http://www.phpdeveloper.org/news/12039</link>
      <description><![CDATA[<p>
<i>Christian Weiske</i> has <a href="http://cweiske.de/tagebuch/Generating%20CHM%20files%20with%20Wine%20on%20a%20Linux%20server%2C%20and%20a%20bit%20about%20PEAR%27s%20PhD%20transition.htm">posted a guide</a> to generate CHM files dynamically in in a Wine instance on a machine running some form of Linux.
</p>
<blockquote>
The only way to generate .chm files is to use Microsoft's HTML Help Compiler hhc.exe from the HTML Help Workshop. It can be downloaded free of charge from their website. While the workshop tool is a GUI application, hhc.exe can run completely without any windowing environment on a server - ideal for an headless web server like pear.php.net. I already got it running on my Linux desktop at home using <a href="http://winehq.org/">Wine</a>, so I chose to go the same way on the server. 
</blockquote>
<p>
He actually starts out the post with a brief history of some of the work that's been done on the PhD tool to incorporate things like screenshots and image support as well as improvements to character set handling.
</p>
<p>
As far as installing the Help Complier, he offers two helpful tips on things to watch for - the need for X forwarding to display the windows for the installation and a need to install some extra DLL files to correct <a href="http://bugs.winehq.org/show_bug.cgi?id=7517">this bug</a> with Wine.
</p>]]></description>
      <pubDate>Fri, 27 Feb 2009 12:55:01 -0600</pubDate>
    </item>
  </channel>
</rss>
