• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 390 subscribers
  • Views 1308 views
  • Users 0 members are here
Options
Related

Issues processing PDF files with SDL SDK

mirimie
Hi all,
It seems that Trados SDK has problems processing PDF files(this happens on analyze files although the scanning task for the file said it is translatable by Trados).The code is the same as in SDK examples.The error appears at Sdl.ProjectApi.AutomaticTasks.Conversion.ConversionTask:

"2013-10-16 08:46:22,191 [2016] INFO Sdl.ProjectApi.AutomaticTasks.Conversion.ConversionTask - ProcessFile: getting filter manager
2013-10-16 08:46:22,191 [2016] INFO Sdl.ProjectApi.AutomaticTasks.Conversion.ConversionTask - ProcessFile: getting converter
2013-10-16 08:46:22,191 [2016] INFO Sdl.ProjectApi.AutomaticTasks.Conversion.ConversionTask - ProcessFile: checking source language
2013-10-16 08:46:22,191 [2016] INFO Sdl.ProjectApi.AutomaticTasks.Conversion.ConversionTask - ProcessFile: checking target language
2013-10-16 08:46:22,191 [2016] INFO Sdl.ProjectApi.AutomaticTasks.Conversion.ConversionTask - ProcessFile: converting file
2013-10-16 08:46:37,838 [2128] ERROR Sdl.ProjectApi.AutomaticTasks.Conversion.ConversionTask - Failed in Framework.dll PdfConverterCreate( 0) == Fail
   at Sdl.FileTypeSupport.Native.PDF.PDFPreTweaker.TweakFilePreParsing(IPersistentFileConversionProperties properties, IPropertiesFactory propertiesFactory)
   at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.RunFileTweakersPreParsing(IPersistentFileConversionProperties properties)
   at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
   at Sdl.ProjectApi.AutomaticTasks.Conversion.ConversionTask.ProcessFile(IExecutingTaskFile executingTaskFile)"
I should add that this error appears intermittently.Do you know what could be the problem?Do you have a fix for it?
Rate translation
×
Suggest better translation
×
Parents
  • 0

    I am working with mirimie on this ... a couple other notes... we are using the following ...

    • Windows Server 2008R2 Standard 64-bit

    • Trados Studio 2011 SP2 – 10.2.3001.0

    Note…we also tried Trados Studio 2011 SP2 – 10.2.3046 in the past, but had problems where we could not access the API at all
  • 0 in reply to walter

    Hi Walter and mirimie,

    Sorry for taking longer to answer this. This is very likely caused by problematic or invalid documents - we tried reproducing this multiple times using the PowerShell toolkit (available elsewhere on this forum) and projects with PDF files were created without any issues. Note that automating PDF files conversion on the server might not be very robust as it might have threading problems (due to third party component being used) - we did not test this thoroughly in server environments even though we know at the same time that our WorldServer team are using this component without problems.

    Also in general - just from a best practices perspective - processing PDF files (in both interactive and automated workflows) is not necessarily the most recommended way of doing translation production. Typically we recommend going back to the original source format as this is typically more robust and localization-friendly way. However sometimes PDF cannot be avoided and then it depends on the underlying file format characteristics in terms of how well it can be processed.

    Thanks

    Daniel

    Daniel Brockmann
    Team Trados @ RWS

Reply
  • 0 in reply to walter

    Hi Walter and mirimie,

    Sorry for taking longer to answer this. This is very likely caused by problematic or invalid documents - we tried reproducing this multiple times using the PowerShell toolkit (available elsewhere on this forum) and projects with PDF files were created without any issues. Note that automating PDF files conversion on the server might not be very robust as it might have threading problems (due to third party component being used) - we did not test this thoroughly in server environments even though we know at the same time that our WorldServer team are using this component without problems.

    Also in general - just from a best practices perspective - processing PDF files (in both interactive and automated workflows) is not necessarily the most recommended way of doing translation production. Typically we recommend going back to the original source format as this is typically more robust and localization-friendly way. However sometimes PDF cannot be avoided and then it depends on the underlying file format characteristics in terms of how well it can be processed.

    Thanks

    Daniel

    Daniel Brockmann
    Team Trados @ RWS

Children
No Data