• State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 4161 views
  • Users 0 members are here
Options
Related

Error prevents export of target text - Help! (Studio 2015)

Narins

I have a large (novel-length) translation I now can't get out of the Trados Studio 2015.

I'm trying to export target translation text - but it won't work.
 
It's from a Word document (.docx format).
I use Windows 7 Ultimate, office 2007, and really no antivirus except for what's built into windows.
 
Here are the error details:
 
<?xml version="1.0"?>
-<SDLErrorDetails time="5/17/2016 7:11:57 PM"><ErrorMessage>Failed to save target content: Unknown error when reading plug-in filter definition file \TsarDocs\Profession\Translation\Russia_21stC\Zvezdnaya\ak-pr-1.doc</ErrorMessage>-<Exception><Type>Sdl.FileTypeSupport.Framework.FileTypeSupportException, Sdl.FileTypeSupport.Framework.Core, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</Type><HelpLink/><Source>Sdl.FileTypeSupport.Framework.Adapter.Framework1</Source><HResult>-2146233088</HResult>-<StackTrace>
<![CDATA[ at Sdl.FileTypeSupport.Framework.Adapter.Framework1.AbstractFramework1Adapter.ReThrowFilterFramework1Exception(Exception* x) at Sdl.FileTypeSupport.Framework.Adapter.Framework1.Writer.StartOfInput() at Sdl.FileTypeSupport.Framework.Integration.NativeWriterMessagesProxy.StartOfInput() at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.CallStartOfInput() at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.SetFileProperties(IFileProperties fileInfo) at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.SetFileProperties(IFileProperties fileInfo) at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.SetFileProperties(IFileProperties fileInfo) at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.SetFileProperties(IFileProperties fileInfo) at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.SetFileProperties(IFileProperties fileInfo) at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_Visit(TmfcReaderImpl* , FrameworkFileContainerField* field) at FrameworkFileContainerField.vv_AcceptFrameworkVisitor(FrameworkFileContainerField* , FrameworkFieldVisitor* visitor) at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_VisitStartEndField(TmfcReaderImpl* , StartEndField* startEnd) at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.b_VisitNext(TmfcReaderImpl* ) at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReader.ParseNext() at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext() at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext() at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse() at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.SaveMonolingualAsJobRequest.Execute(IJobExecutionContext context) at Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__3() at Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action) at Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]>
</StackTrace></Exception>-<Environment><ProductName>SDL Trados Studio</ProductName><ProductVersion>12.0.0.0</ProductVersion><EntryAssemblyFileVersion>12.2.5099.5</EntryAssemblyFileVersion><OperatingSystem>Microsoft Windows 7 Ultimate </OperatingSystem><ServicePack>Service Pack 1</ServicePack><OperatingSystemLanguage>1033</OperatingSystemLanguage><CodePage>1252</CodePage><LoggedOnUser>ThuleIV\-</LoggedOnUser><DotNetFrameWork>4.0.30319.34209</DotNetFrameWork><ComputerName>THULEIV</ComputerName><ConnectedToNetwork>True</ConnectedToNetwork><PhysicalMemory>33434864 MB</PhysicalMemory></Environment></SDLErrorDetails>
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hi Rhoda,

    I think the solution is going to be that you prepare the source file again as a new project and then pre-translate it from your Translation Memory.  It would also make sense to use the new Word filetype as this is more robust.  So before you prepare the project make sure this is enabled in the File -> Options -> Filetypes.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    Paul, thanks. Where does it say "Rhoda?"

    First of all, that's very difficult, as I often split segments to get more useful translation results. Very slow, a lot of work.

    Second - it would seem this shouldn't have happened in the first place, that it should be fix-able, and that if we don't think about those things nothing prevents this from happening again and again.

    Thoughts?
  • 0 in reply to Narins

    Unknown said:
    First of all, that's very difficult, as I often split segments to get more useful translation results. Very slow, a lot of work.

    Yes, if you split a lot then this is going to be a lot of work to correct it.  You may be able to use Perfect Match if I give you a Professional License for a month to sort this out and this might help you there.  But my one concern here would be that the splitting caused the problem in the first place.  However, using the new filetype is better and more robust so it's worth a try.

    Unknown said:
    Second - it would seem this shouldn't have happened in the first place, that it should be fix-able, and that if we don't think about those things nothing prevents this from happening again and again.

    Well obviously it shouldn't happen in the first place and if we knew why then we would fix it.  I think perhaps one of the reasons for moving to the new word filetype was to provide a more stable platform that isn't so susceptible to problems like these.  So the fix is the new filetype.

    Let me know if you want to try Perfect Match... or if you like I'd be happy to try this for you if you don't mind giving me your files?

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Reply
  • 0 in reply to Narins

    Unknown said:
    First of all, that's very difficult, as I often split segments to get more useful translation results. Very slow, a lot of work.

    Yes, if you split a lot then this is going to be a lot of work to correct it.  You may be able to use Perfect Match if I give you a Professional License for a month to sort this out and this might help you there.  But my one concern here would be that the splitting caused the problem in the first place.  However, using the new filetype is better and more robust so it's worth a try.

    Unknown said:
    Second - it would seem this shouldn't have happened in the first place, that it should be fix-able, and that if we don't think about those things nothing prevents this from happening again and again.

    Well obviously it shouldn't happen in the first place and if we knew why then we would fix it.  I think perhaps one of the reasons for moving to the new word filetype was to provide a more stable platform that isn't so susceptible to problems like these.  So the fix is the new filetype.

    Let me know if you want to try Perfect Match... or if you like I'd be happy to try this for you if you don't mind giving me your files?

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Children
No Data