October 4th, 2011· Error could occur page size was too large.
· Language file for Japan updated.
October 14th, 2010· Special Processes: When specifying a target file with the wild card, the file extension of the output files did not always use what was specified.
September 24th, 2010· PDF to DOC enhancments
September 24th, 2010· Images not embedded in output file was not working since version 6.12. Now working
September 24th, 2010· Command line improved for Windows Vista, Windows 7 and greater. The manifest file was renamed so that running the ConvertDoc.EXE won't bring up the UAC (User Account Control) approval dialog by default. Command line users must understand that if they have UAC enabled, and they are doing a command line with output to a protected folder, the results will be placed in the %localappdata%\VirtualStore folder. If you think UAC is having an effect on the command line you can quickly change the name of the program in your command line from ConvertDoc.EXE to ConvertDoc.Admin.EXE. Doing this will enable a prompt to elevate security before the command line is fully executed.
· Numerous fixes for the conversion to/from HTML and RTF files
· Improved conversion of files with PNG and JPGs.
· Improved PDF/A conversion output
September 24th, 2010· Windows 7 compatibility enhancements made. Default report folders now updated.
· Working well now with Office 2010
September 24th, 2010· Command line: Conversion from PDF to DOCX: Regardless of what was chosen in the user interface, MS Word was never being used for the final generation of the DOCX.
September 24th, 2010· Conversion from PDF to TXT: File moving/deleting of input files after conversion was not working.
July 12th, 2010· Conversion from PDF to DOCX: File moving/deleting of input files after conversion was not working.
July 12th, 2010· Conversion of DOC: Table formatting sometimes missing
· Conversion of DOC: Conversion errors occurred when rectangles of zero height or width were found
· Conversion of DOCX: "Open XML SDK 2.0" generated files were not able to be read
· Conversion to HTML: Truncation of base64 data could occur
· Conversion to HTML: References to missing images within the input document caused an error
· Conversion to HTML: Documents with hyperlinks within text frames could cause an error
· Conversion of HTML: Character entities (i.e. semi-colon, ;) without semicolon would cause an error
· Conversion of HTML: The content of td and tr tags in the wrong places would be ignored
· Conversion of HTML: Embedded images in link caused an error
· Conversion of HTML: Hidden lists were being shown, or caused empty rows
· Conversion of HTML: Some whitespace characters between hyperlinks disappeared
· Conversion: JPG files lacking resolution information are not converted properly
· Conversion to RTF: OLE objects without a metafile caused an error
· Conversion to RTF: Properties of paragraphs inside text fields in wrong place
· Conversion of RTF: Empty section and a bookmark at the end of the input document caused an error
· Conversion of RTF: nested table inside field not read properly
May 19th, 2010· Conversion of PDF to DOC/RTF. In some complex PDF's text was not found.
April 24th, 2010· Server operating systems running 5.655 had an issue. Error 13 has been resolved.
April 24th, 2010· Normal.DOT was being asked to be saved on some systems when 'MS Word' method was chosen.
· Conversion to RTF: Numbered list within a table are not converted properly
· Conversion to PDF, there were issues with link targets
· Conversion of files with some embedded TIFs were causing an issue
· Conversion of RTF files, properties of table rows after the table would break the table
· Conversion of RTF files, an empty field at the very end of a document would cause an error
· Conversion of HTML: Some links were causing an error
· Conversion of HTML: Anchored images in the last paragraph were omitted
· Conversion of HTML: Standalone XHTML tags were not being converted properly
· Conversion of HTML: If a list entry is empty then the closing tag (UL) is missing and the html would be considered invalid.
· Conversion of DOC files, Anchored images that were exported could not be loaded
· Conversion of DOC/DOCX Files: Wrong font character set data
· Conversion of DOCX: After a forced page break, additional paragraphs occurred.
February 4th, 2009· Conversion of very large PDF to DOC was timing out
October 13th, 2008· Conversion From PDF to DOC/RTF: Japanese PDF's were not always converting.
July 17th, 2008· Conversion of Chinese PDF's now handled properly.