www.pudn.com > doc2pdf-0_7_1.rar > README


Doc2pdf README v0.3.0
Matt Peterson 
==========================================

1 - Release notes for Doc2pdf 0.7.1
-----------------------------------
There are two chages for Doc2pdf 0.7.1:

   - Check for x-uuencoded messages. This *drastically* decreases the
     number of otherwise unexplained "freezes" and viewer crashes.
   - Fixed problem where encoding conditionals were being made on case
     sensitive values.  This also cuts down on the number of "freezes",
     viewer crashes and converted emails that are still base64 encoded
 

2 - Known Issues
----------------
Please realize that Doc2pdf is still new software.  It has received
significant testing from messages sent to doc2pdf@hotpop.com.  However, I am
still not convinced that all th bugs have been worked out.  Before reporting
problems please be aware of the following list of known issues:

   - As explained in the Doc2pdf Overview, Doc2pdf relies completely
     the free Microsoft viewers to render Microsoft Office documents. 
     The viewers are controlled via the journal playback hook which results
     in a rather obtrusive application.  Know that there are plans in
     future releases to allow those that have purchased Microsoft Office 
     to utilize Microsoft Office components.  Those that do have a
     Microsoft Office license will be able to run Doc2pdf in the less 
     obtrusive mode -- the trade off is that you will have to
     purchase Microsoft Office.  For those of us that want a free doc2pdf,
     the journal playback controlled viewer mode will be refined.

   - Doc2pfd uses window title strings to deterimine the existance of 
     Microsoft viewer windows.  On non-english installations,
     these titles may be translated.  Currently, the expected window title
     strings are hard coded in english, which will cause Doc2pdf to fail
     when translated titles are displayed.  If you suspect that you are
     encountering this problem. Read the build instructions for
     information on how to build Doc2pdf in your language.

   - Though Doc2pdf MIME mail message scanner is better in this
     release it is not fully perfected.  I have tested with a variety of
     mailers, and have fixed all the bugs I have found.	
  
   - Doc2pdf 0.7.0 has only been tested on Windows 98. It is very possible
     that the journal playback hook or possibly the keypress
     messages differ significantly on Windows 2000, Windows ME, and
     Windows XP.


3 - Building Doc2pdf
--------------------
Because of Doc2pdf uses Microsoft viewers to render Microsoft Office
documents, it is not possible to compile or run Doc2pdf on any platform
other than Windows.  Therefore, the Doc2pdf source code is organized
according the standards that are acceptable to Microsoft Visual C++ which is
the only environment to my knowledge that will build Doc2pdf. Doc2pdf can be
built with MSVC version 6 (or higher).  Simply load the workspace and project
by double clicking on the .dsw file then use the usual menu options to build
the project.

Once the doc2pdf.exe executable is built you should follow the instructions
at http://doc2pdf.sourceforge.net/install.html to make sure that everything
is installed correctly before starting Doc2pdf.

If will be running doc2pdf on a non-english installation of Windows, you
will need to translate the expected window title strings.  Read the comments
at the top of doc2pdf_convert.cpp and modify the #define constants as 
necessary.

If you find any bugs, PLEASE email the doc2pdf-devel@lists.sourceforge.net
mailing list.  Thanks!


3 - Installing Doc2pfd
---------------------
The authoritative installation instructions are always found at
http://doc2pdf.sourceforge.net/install.html.  Please read and follow these
instructions carefully.  If you find a problem with the instructions, PLEASE
email the doc2pdf-devel mailing list.  Thanks!

4 - License
------------
Please read the licenses at http://doc2pdf.sourceforge.net/license.html.  If
you are modifying the source code, you must honor restricitions that
described in the comments.  (I put them in the code on purpose -- so that they 
will be in your face while you are contemplating code changes).