This topic and its replies were posted before the current version of LEADTOOLS was released and may no longer be applicable.
#1
Posted
:
Monday, March 11, 2013 12:30:02 AM(UTC)
Groups: Registered
Posts: 4
which leadtols library support converting from doc to tiff
#2
Posted
:
Monday, March 11, 2013 7:26:46 AM(UTC)
Groups: Registered, Tech Support
Posts: 179
Loading DOC file format as images is supported in our Document Imaging module and higher (such as Document Imaging Suite). Please see our Product Comparison Chart on our website.
Mohamed Abedallah
Developer Support Engineer
LEAD Technologies, Inc.
#3
Posted
:
Wednesday, March 13, 2013 4:50:59 AM(UTC)
Groups: Registered
Posts: 4
thanks a lot,
Is there any sample code for this conversion.
I tried loading the doc using RasterCodecs and then save it as tiff but it returns (Invalid file format )
#4
Posted
:
Wednesday, March 13, 2013 10:54:50 PM(UTC)
Groups: Guests
Posts: 3,022
Was thanked: 2 time(s) in 2 post(s)
Shimaa,
In the DotNet libraries, "Invalid File Format" means one of three things:
1. The file is actually invalid or there's a problem with the codec. If you can load the same file in one of our pre-compiled demos that ship with the toolkit, then this is not the case.
2. You did not call RasterCodecs.StartUp() (Only required for versions previous to V17).
3. You are not including as a reference or copying to your .exe's directory the necessary codecs dll for the file format. These dlls follow the naming convention of Leadtools.Codecs.???.dll (e.g. Leadtools.Codecs.Tif.dll, Leadtools.Codecs.Doc.dll). To learn which dlls are necessary for a particular file format, please read the help file article "Files to be Included With Your Application" and find the row for the file format in question.
If none of these solves the problem, Please send an email to
support@leadtools.com and send the following:
1. What is your toolkit serial number (do NOT post it here).
2. What is the build number (file properties version info) of Leadtools.dll that you use?
3. Can you trigger this problem using our C# main demo? You can find it under the name of "CSMainDemo_Original.exe" in the following folder:
[LEADTOOLS Folder]\Bin\Dotnet\Win32
If not, send a small sample project (NOT your full application) that shows the problem, with the steps to reproduce it.
4. Send the DOC file that triggers the problem.
5. A link to this forum post.
Note: If you send any attachments, please put them in a ZIP or RAR file to ensure our server delivers them correctly.
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.