The number one "bug" (which is not a "bug" but a missing feature, but I'll explain that later) in WP2PDF is missing or little UTF(8) support. I get lots of bug reports and complains which all sound very similar: "I just installed WP2PDF and certain characters look garbled". This is a known problem and I'm working on it since some time now.
What about UTF-8?
UTF8 is the standard character set used by WordPress, and if the user doesn't change it (which is probably true for most WP installations), all entries submitted with WordPress use UTF8. This is not a problem until the user installs WP2PDF. WP2PDF does not support UTF8. It uses the font's format, which is ISO-8859-1 (also known as Latin1) for all supplied fonts. Since UTF-8 uses the basic ASCII character set and each of these characters have the same position as in ISO-8859-1, some characters will look right, while some other characters (for example Umlauts: , , ) have a different position in UTF-8. Most users with a blog in English language will not even note the difference - all characters look right to them. But if you've typed text in French, German, Italian, Swedish or any other non-English language, some characters will look garbled.... read more
I'm sorry for this late release and for the late answers of support requests. I was on vacation and after that very busy with work for the university.
This is just a very small bug fix. In WP 1.5, the "the_time()" function contains a bug that would output the time (rather than putting it into a variable) and thus break the whole PDF output of WP2PDF. It works fine now with WP 1.5.
The other bug was a missing output of the current header text in the output setup area.
Version 0.4.1 of WP2PDF, the WordPress to PDF converter, has been released. This release does not add new features (except the custom font listing/remove function) but changes the settings from static files to MySQL. There are also some other changes. This update is strongly recommended for all users.
Changes:
- Using MySQL for settings now. No more static files are necessary.
- Much better installation script with upgrade option.
- Using the WordPress login now; no more separate username/password and authentification is needed
- Custom fonts are listed on the font settings page and can be removed
- Language files/translation settings removed. There will be a better solution for this in a later version.
- Temporarily removed the variable [EMAIL] from the comment infobar text
- General code cleanup
The new version of WP2PDF, the WordPress to PDF converter, has been released. The update includes a rewritten HTML conversion part. Tables are now supported, as well as many other HTML-tags that have not been supported before. The list of supported tags now includes: <cite>, <ins>, <address>, <big>, <small>, <bdo>, <s>, <strike>, <del>, <font>, <center>, <sup>, <sub>, <input>, <select>, <textarea>, <title>, <form>, <ol>, <ul>, <li>, <h1>, <h2>, <h3>, <h4>, <pre>, <b>, <u>, <i>, <a>, <img>, <p>, <br>, <strong>, <em>, <code>, <th>, <blockquote>, <hr>, <td>, <tr>, <table>, <div>. There are also some other smaller improvements and bug fixes. See the project homepage (http://wp2pdf.sourceforge.net/) for more information, including a full online demo.
Don't worry. The project is not dead. I'm just very busy writing reports for the university and I just don't have any time for WP2PDF. I will continue work in August and you can expect a new version coming around September 10th. It will include support for tables, so stay tuned ;)