Hi,
I have to make terminology changes in a project that contains 200 + files, divided among folders, sub folders and sussubfolders . Knowing that the terminology can be spread against files in different folders or sub-folders do you have an idea as how to that in the best way while using SDLXLIFF Toolkit ? Or is there another tool ? With kind regards, Manuella
When you use the SDLXLIFFToolkit and drop the project in there you should find every single file in the project. So you can then select them all and search and replace as needed. In principle it's as easy as that. Have you tried it and found something more complex to address?
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
Thank you Paul. It works for having all the files but it is not satisfying as I can not change the gender of the replacing word, nor the spelling of the verbs. So I have opened all the files in one view and now I have a different issue with the "find". The tool does not find locutions such as "signaux d'alerte" and after a few searches I get the well known "Object not set as an instance" and I have to close and restart Studio. Very annoying...
Translate
<SDLErrorDetails time="15/07/2020 11:11:16">
<ErrorMessage>Failed to save bilingual as : Exception of type 'System.OutOfMemoryException' was thrown.</ErrorMessage>
<Exception>
<Type>System.OutOfMemoryException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
<HelpLink />
<Source>mscorlib</Source>
<HResult>-2147024882</HResult>
<StackTrace><![CDATA[ at System.String.ReplaceInternal(String oldValue, String newValue)
at System.String.Replace(String oldValue, String newValue)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XmlNodeBuilder.XmlBuilder.XmlEscape(String unescaped)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XmlNodeBuilder.XmlBuilder.AddText(String text)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.FileManager.WriteZippedFile(XmlBuilder builder, String filePath)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.EmbedDependencyFile(XmlBuilder builder, IDependencyFileProperties file)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.AutoEmbedOrLinkDependencyFile(XmlBuilder builder, IDependencyFileProperties file)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.AddDependencyFile(XmlBuilder builder, IDependencyFileProperties file)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.SetDependencyFiles(FileSkeleton fileHeader, XmlBuilder builder)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.WriteFileComplete(FileSkeleton fileHeader, XliffFormattingXmlTextWriter writer)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.WriteSdlXliff(XliffFormattingXmlTextWriter writer)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileWriter.Complete()
at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.Complete()
at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.Complete()
at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.Complete()
at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.SaveBilingualImpl(String[] bilingualFilePaths, Boolean copy, IJobExecutionContext context, Boolean isAutoSaved)
at Sdl.TranslationStudio.Editor.TranslationEditor.SaveBilingualAsJobRequest.Execute(IJobExecutionContext context)
at Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__47_0()
at Sdl.Desktop.Logger.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>15.0.0.0</ProductVersion>
<EntryAssemblyFileVersion>15.2.7.2849</EntryAssemblyFileVersion>
<OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
<ServicePack>NULL</ServicePack>
<OperatingSystemLanguage>1033</OperatingSystemLanguage>
<CodePage>1252</CodePage>
<LoggedOnUser>DESKTOP-IARU67P\Manuella</LoggedOnUser>
<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
<ComputerName>DESKTOP-IARU67P</ComputerName>
<ConnectedToNetwork>True</ConnectedToNetwork>
<PhysicalMemory>8257560 MB</PhysicalMemory>
</Environment>
</SDLErrorDetails>
It works for having all the files but it is not satisfying as I can not change the gender of the replacing word, nor the spelling of the verbs.
Hmnn... maybe you can provide some search and respective target change examples? I am conscious you may be asking the tool to do a bit more than the original simple request to just change some terminology. But if you can provide some examples maybe we can help.
after a few searches I get the well known "Object not set as an instance"
Only the title is well known... the underlying cause could be thousands of things Anyway, I think you should upgrade your version of Trados first. The current version of 2019 (which is almost out of support anyway) is Trados Studio 2019 SR2 - 15.2.8.3007 (and MultiTerm 2019 - 15.0.6.56482), and you are using 15.2.7.2849. I don't really know if this will solve your problem but before we do anything you should at least be using the latest version since it will contain more fixes than any of the previous versions.
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
It works for having all the files but it is not satisfying as I can not change the gender of the replacing word, nor the spelling of the verbs.
Hmnn... maybe you can provide some search and respective target change examples? I am conscious you may be asking the tool to do a bit more than the original simple request to just change some terminology. But if you can provide some examples maybe we can help.
after a few searches I get the well known "Object not set as an instance"
Only the title is well known... the underlying cause could be thousands of things Anyway, I think you should upgrade your version of Trados first. The current version of 2019 (which is almost out of support anyway) is Trados Studio 2019 SR2 - 15.2.8.3007 (and MultiTerm 2019 - 15.0.6.56482), and you are using 15.2.7.2849. I don't really know if this will solve your problem but before we do anything you should at least be using the latest version since it will contain more fixes than any of the previous versions.
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