SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
We are doing some testing of the TLT and encountered a problem with a custom XML file type. We've been successfully handling our customer's XML files for years in Trados Studio by using a custom file type we created. Now we imported that file type to TLT and did some testing there. The file conversion, processing, translation etc went fine, however the target file generated by TLT could not be imported back into our customer's system. Important to emphasize that there were no tag issues in the file.
Has anybody encountered this?
If you do not translate the file and just copy source to target and then try importing this into the customers system - do you still have issues?Also if you run the file through Studio and TLT - generate the target file and compare the output is there any noticeable difference?
Can you attach the file so can look into this for you?
Sorry for the late reply, for some reason I was notified about your reply.
I've run a comparison on the 2 target XML files (the one generated by Trados Studio - here referred to as First XML document and the one generated by TLT referred to as Second XML document).
The only difference between the two is the way the date is handled under CreatedDate and ModifiedDate for each segment. In the one from Studio these dates are in the format 2019-04-27T13:06:10, whereas in the one from TLT it is 04/27/2019 13:06:10.
There is no setting in either Studio or TLT for this as these are handled as non-translatable parser rules.
HI Csaba Szekeres
What was the format in the original file? Also can you attach the file\filetype so I can test on our side.
The original format was 2019-04-27T13:06:10. This was also investigated by support and it does seem to be a bug that needs to be fixed. Nevertheless, I could send you the files if you provide me an e-mail address where I can send them to.