Trados Studio
Trados Enterprise
Trados Team
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 Training & Certification
Style Guides
RWS Campus
RWS Enterprise Technology Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Team Ideas
Trados Team Terminology Ideas
Trados Enterprise 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 there!
I'm using Studio 2019 (updated to the latest version). I'm logged in to SDL Language Cloud account.
Last week I wanted to use SDL Language Cloud in one of my language pairs, but there was nothing in the pop-up window of SDL Language Cloud. I thought this was a temporary error and moved on, but today I noticed I still cannot use the LC due to no options in this window. I logged into my SDL Language Cloud account (https://languagecloud.sdl.com/) but there's nothing new there. After reading replies here I also logged into SDL Machine Translation Cloud (is this the same service as LC?) and checked if I used the limit but nope.
I'm not sure if something changed or if there's some error. Does anyone experience the same thing? Does anyone know the solution?
Thanks,
Aleksandra
Hey Guys!
No one replied so I filed a ticket with SDL (https://gateway.sdl.com/WebToCaseLCMT) and they solved the issue (without explaining what caused it). So if you encounter a similar problem, I think it's best to contact support.
Cheers,