Trados Studio
Trados Live Essential/Live Team/Enterprise
Trados GroupShare
Trados Business Manager
Passolo
MultiTerm
RWS AppStore
Connectors
Beta Groups
Managed Translation
MultiTrans
TMS
WorldServer
Language Weaver
Language Weaver Connectors
Language Weaver Edge
Tridion Docs
Tridion Sites
LiveContent S1000D
XPP
Language Developers
Tridion Docs Developers
Community Help
RWS User Experience
Internal Trados Ideas Community
Mercury
RWS Community Internal Group
RWS Professional Services
RWS Training & Certification
Style Guides
RWS Campus
RWS Enterprise Technology Partners
Trados Approved Trainers
XyUser Group
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion UK Meetup
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Live Team Ideas
Trados Live Essential Ideas
Trados Live Terminology Ideas
Trados Enterprise Ideas
Trados Online Editor Ideas
Trados Business Manager Ideas
MultiTerm Ideas
Passolo Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
TMS Ideas
WorldServer Ideas
LiveContent S1000D Ideas
Contenta S1000D
XPP Ideas
Events & Webinars
To RWS Support
Detecting language please wait for.......
Hi
Can someone tell me where I can find a reference document that explains the meaning of the various elements of the SDLXLIFF format?
I need this to understand the content of an SDLXLIFF file and to be able to make minor changes to it.
My searches in Producthelp, KB and Community have so far been unsucessful. I am sure this information must be available (at least to developers).
Thanks for any hint.
Walter
Hi Walter Blaser
SDLXLIFF is just XLIFF format with some extensions added by SDL.You can find that XLIFF specification below which describes most of the elements:http://docs.oasis-open.org/xliff/v1.2/os…
Walter Blaser
Hello my dear friend Walter,
I did a quick search and found the following link, which you may have already found but just in case not...
Understanding sdlxliff files
I hope you will find…
I hope you will find something there that leads you to what you're looking for!
All the very best!
Ali
Hi Ali
I looked through this post, but didn't find what I was looking for.The OASIS specification suggested by Jesse however is a step forward.
Thanks and stay healthy.Walter
Hi Walter,
I'm glad Jesse Good was able to give you a useful link to the information you need.
Out of interest, what are you planning to do with it?
You stay safe too!
All the best,
Dear Ali
I am trying to fix the problem discussed here:https://community.sdl.com/product-groups/translationproductivity/f/studio/27173/failed-to-save-target-content-because-illustration-was-moved-between-paragraphs/85739#85739
without the need to go back to the source file and do a pretranslate or Perfect Match. Patching the SDLXLIFF file would at least help to continue working on the project.
Dear Walter,
Wow! Good luck with that! Years ago, I used to patch up TTX files that had been cut short due to a TagEditor crash. I did it by carefully copying the missing content across from the untranslated TTX file (by opening them both in Notepad I think) but I wouldn't attempt to do it with an SDLXLIFF. Too complex and my brain isn't up to it these days
Done the same in the past.
In principle you can do the same with sdlxliff, using the file from the source folder.
In case of Walters problem the idea is to locate the offending merged segment and replace the translation unit (which is now one) with the two translation units from the untouched source file. This has good chances to work.
Jerzy Czopik
Hello, my dear friend Jerzy,
In what software would you open the SDLXLIFF? I have just tried it and it looks surprisingly OK in good old Wordpad...
Notepad++. It looks weird, but if you open two instances of N++ on two screens, it is feasible.
Hi Jerzy,
Ah, I did try Notepad++ but it rendered as a very long single line string at the top, then a long vertical column of unintelligible text with no breaks followed by a very long single line string at the bottom.
I guess once you're used to it, that doesn't present a problem...
Very interesting!
Thanks,