• State Verified Answer
  • Replies 5 replies
  • Subscribers 432 subscribers
  • Views 3197 views
  • Users 0 members are here
Options
Related

Saving/exporting to target document crashes when comments present

Sebastian Schleussner

Hello there!

Another bug report, a bit more serious than the other one, I would say.

As soon as we have added a comment to a project document in Studio, we get an exception when trying to Save Target As or Export. Below are the error details from one attempt (note: independent of the document, and where/how many comments are present, Line/LinePosition are always 2/2484).

When we remove the comment(s), everything goes back to working normally, so that is an (albeit rather kludgey) workaround.

Export for Bilingual Review works all the time (i.e. also with comments present).

Best, Sebastian

<SDLErrorDetails time="4/26/2016 11:43:33 AM">
<ErrorMessage>Failed to save target content: Name cannot begin with the '&lt;' character, hexadecimal value 0x3C. Line 2, position 2484.</ErrorMessage>
<Exception>
<Type>System.Xml.XmlException, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
<LineNumber>2</LineNumber>
<LinePosition>2484</LinePosition>
<SourceUri>file:///C:/Users/convertus/AppData/Local/Temp/SDLTempFileManager/s4seomku.dbn/635972677984066606_Extract4uesmd4w.bd3.docx/word/styles.xml</SourceUri>
<HelpLink />
<Source>Sdl.FileTypeSupport.Filters.Word</Source>
<HResult>-2146232000</HResult>
<StackTrace><![CDATA[ at Sdl.FileTypeSupport.Filters.Word.Common.FilterException..ctor(Exception ex)
at Sdl.FileTypeSupport.Filters.Word.FileFormat.DocumentControllerFramework.TransformHelper.Transform(String filePath, String xsltPath, DataProcessor urnObject, RuleFileType fileType, Boolean overrideSource)
at Sdl.FileTypeSupport.Filters.Word.FileFormat.DocumentControllerFramework.Specialized.DocumentParser.WriteStyles()
at Sdl.FileTypeSupport.Filters.Word.FileFormat.DocumentControllerFramework.Specialized.DocumentParser.WriteDocument(IVisitor visitor)
at Sdl.FileTypeSupport.Filters.Word.FrameworkImpl.Common.DocumentExtractImpl.Update(IVisitor visitor)
at Sdl.FileTypeSupport.Filters.Word.FrameworkImpl.Generator.WriterImpl.EndOfInput()
at Sdl.FileTypeSupport.Filters.Word.FrameworkImpl.Generator.FileWriter.EndOfInput()
at Sdl.FileTypeSupport.Framework.Integration.NativeWriterMessagesProxy.EndOfInput()
at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.CallEndOfInput()
at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.FileComplete()
at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.FileComplete()
at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.FileComplete()
at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
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.5087.4</EntryAssemblyFileVersion>
<OperatingSystem>Microsoft Windows 7 Ultimate </OperatingSystem>
<ServicePack>Service Pack 1</ServicePack>
<OperatingSystemLanguage>1033</OperatingSystemLanguage>
<CodePage>1252</CodePage>
<LoggedOnUser>win7\convertus</LoggedOnUser>
<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
<ComputerName>WIN7</ComputerName>
<ConnectedToNetwork>True</ConnectedToNetwork>
<PhysicalMemory>2096696 MB</PhysicalMemory>
</Environment>
</SDLErrorDetails>
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Paul
    Hi Paul,
    Thanks for the quick reply! I'm not sure I'm allowed to share those particular documents at present (several were affected, all of them docx), but I'll check and otherwise try and create a demonstration project. Will reply by mail soon.
    Regards,
    Sebastian
  • 0 in reply to Paul
    Hi,

    I know this post is a couple months old but I've had the same issues with multiple files and I am wondering if there is a way to avoid this problem: maybe it is linked to comments put on a text including tags or around tags. The error message varies from one time to another but often, the solution is just deleting the comments.

    We work a lot with comments and even though we know we just have to deleted them in order to generate the target, it is sometimes annoying as we want to keep the comments.

    Could you please help find a permanent solution?

    Thank you very much.

    Kind regards,

    Marine
  • 0 in reply to Marine Tresnie

    Hi Marine,

    I'll gladly share our findings. With any luck, they can be transferred directly to your cases.

    The solution for us was, prompted by a tip from Paul, to make sure that the *modern* Word file filter ("Microsoft Word 2007–2016") was enabled and placed higher up in the filter list than the (obsolescent and, as this ticket shows, buggy) older one ("Microsoft Word 2007–2013").

    Globally ("File" > "Options" > "File Types", coming into effect for entirely new projects), that should be set up correctly during Studio 2015 installation.

    However, the property can be set differently on a per-project basis ("Project Settings" > "File Types") – and this is inherited from any custom template that you may have used in creating the project. That was exactly the case in those projects of ours that had this issue. Their templates had been created a long time back in Studio 2014, when the filters probably had a different order.

    Hence, as an acute bug fix for the troubled files, put the filters into the proper order in the respective projects, then exporting of the files with comments should work right away. As a permanent fix, also update all templates and the global settings (of each installation).

    Kind regards,
    Sebastian

    EDITED to update UI details after I had a chance to check in the program.
  • 0 in reply to Sebastian Schleussner
    Hi Sebastian,

    Thanks for the detailed answer. It sure helps to understand better.

    However, the proposed solution won't work for us (if I understood well your explanations) because our clients and translators are not working with Studio 2015 (which is the only version that works with this "modern" file-type). The incompatibility of this file-type (2007-2016) with Studio 2014 is thus a problem for us: translators and clients using Studio 2014 can open the sdlxliff files created with this file-type but cannot save nor generate the target file.

    Hopefully, those problems will be solved in the next versions of Studio.

    Thanks aain,

    Kind regards,
    Marine