Trados Live Essential/Live Team/Enterprise
Trados Business Manager
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Ideas Community
RWS Community Internal Group
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Approved Trainers
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
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Support
Detecting language please wait for.......
Using the app to get the edits (incl. comments) made by my reviser back to my SDLXDLIFFs. 14 files in total, in most cases the app works fine. 4 files however give the following error message:
"The string '1963-14-20T31:36:00Z' is not a valid AllXsd value"
Does anyone have an idea what this cryptic message means and how to fix it?
I have no idea what this message relates to. But perhaps try using the out of the box "Export for External Review" instead. Does this still happen?
That's exactly what I used originally - export for bilingual review, update from bilingual review - makes sense. No luck, however, "The document layout cannot be identified" error occurs.
I'm aware also of the process using Glossary Converter (I remember, you once described this in your blog). However, I would like to use it as a very last resort, since this won't bring over into Trados the comments made by my reviser. And I need those comments, which we use to discuss, argue and justify.
Can you post the problematic file(s) ?
I'd like to take a look at it.
Sdlxliff is a (kind of) text file.
Hi Paul and Kelly
The problem has been solved! I did a little searching in the knowledge base and found an article that involved a workaround - the files just needed to be copied and pasted into new ones, after which the upgrading went smoothly. Thanks anyway!