Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
How can you log within a plugin that uses the LanguagePlatform.TranslationMemoryApi SDK for Trados 2021.
I tried to implement the NLog class used in the DeepL Community example from Github but there is no file created during runtime.
Sdl-Community/Log.cs at master · sdl/Sdl-Community (github.com)
There was a mistake in the configuration of the rules for the target as the Logger name pattern was not updated to match the current project, it was left as "*DeepL*".
Hi Colin Harper!
That is not a mistake, *DeepL* translates as find any string which contains DeepL (precedeed and followed by anything else, that's what * does). So, we're adding a rule that any logger…
With the upcoming Trados Studio 2021 CU4 we are going to expose a new API that allows plugins to log information the main Studio log file. This simplifies the setup and maintenance you have to do in your…
Sdl.Community.DeepLMTProvider.Log, lines 39-40
config.AddTarget(target); config.AddRuleForAllLevels(target, "*DeepL*");
That is not a mistake, *DeepL* translates as find any string which contains DeepL (precedeed and followed by anything else, that's what * does). So, we're adding a rule that any logger with a name containing DeepL, should write to the <target> file.
Apologies my answer was not very clear. I should have said, "There was a mistake in MY configuration of the rules for the target..."
When I added the logger code from the SDL Community Github to my project, I should have updated the code to use my project names and remove all use of the "DeepL" naming convention in the logger.
Because I had "*DeepL*" left in the target rule all of my loggers didn't know to write to that <target> file as none of them have DeepL in their names.
Thanks for pointing that out so others don't get mislead by my answer.
No problem, Colin. I'm glad that you were able to sort it out.
With the upcoming Trados Studio 2021 CU4 we are going to expose a new API that allows plugins to log information the main Studio log file. This simplifies the setup and maintenance you have to do in your plugin. Also it helps with product diagnostics as the log information will contain information from plugins. Here's a sample covering the new API - https://github.com/sdl/trados-studio-api-samples/tree/master/TranslationStudioAutomation/Sdl.Logging.Sample