Forum: XTM Cloud support
Topic: What is your opinion on XTM Cloud CAT tool?
Poster: Lindsay Cook
Post title: Slow to use...
[quote]Jakov Milicevic wrote:
I have been using XTM for few years now and I must admit that it became one of the most terrible tools (even the new versions are not better than old ones) to work with together with Across. Too many issues with the tools: TM and TB which usually are not working at all, connectivity issues, unsaved segments, useless QA, difficult handling of tags. I have no idea why clients are all changing to XTM for their localization projects since there are on the market much better tools which are more user-friendly and most of all functional. As a senior translator I have proficient knowledge of all tools but this one is really very bad and extremely time consuming. I really apologize to XTM team for my sincere feedback but I really find your tools a major challenge for translators. [/quote]
This is interesting, I came across this thread when doing some research on some XTM issues I have been having in a recent large project.
The 2 main problems we had were:
1. phases where users were logged out every few minutes. when logging back in again, the user was presented a different segment to the one they had been working on and in a project of 3000 segments, navigating around the project, searching, filtering, loading every set of 300 segments etc. was just really slow!
2. periods where XTM became unresponsive so we had to logout and login again. Same problem as above re the segment the user was presented as well as realising part way through the project that changes that had been made had been lost too.
In general, I found XTM pretty slow in general and almost unusable when searching/QA checking/filtering.
I am regular user of smartcat which I don't usually have connectivity issues with, even on large projects and have also used memsource with no problems so I am confident it isn't an issue at my end. Wondering if this is a widespread issue or just something that was happening to me? anyway, it cost me a lot of time and a late delivery sadly...
Topic: What is your opinion on XTM Cloud CAT tool?
Poster: Lindsay Cook
Post title: Slow to use...
[quote]Jakov Milicevic wrote:
I have been using XTM for few years now and I must admit that it became one of the most terrible tools (even the new versions are not better than old ones) to work with together with Across. Too many issues with the tools: TM and TB which usually are not working at all, connectivity issues, unsaved segments, useless QA, difficult handling of tags. I have no idea why clients are all changing to XTM for their localization projects since there are on the market much better tools which are more user-friendly and most of all functional. As a senior translator I have proficient knowledge of all tools but this one is really very bad and extremely time consuming. I really apologize to XTM team for my sincere feedback but I really find your tools a major challenge for translators. [/quote]
This is interesting, I came across this thread when doing some research on some XTM issues I have been having in a recent large project.
The 2 main problems we had were:
1. phases where users were logged out every few minutes. when logging back in again, the user was presented a different segment to the one they had been working on and in a project of 3000 segments, navigating around the project, searching, filtering, loading every set of 300 segments etc. was just really slow!
2. periods where XTM became unresponsive so we had to logout and login again. Same problem as above re the segment the user was presented as well as realising part way through the project that changes that had been made had been lost too.
In general, I found XTM pretty slow in general and almost unusable when searching/QA checking/filtering.
I am regular user of smartcat which I don't usually have connectivity issues with, even on large projects and have also used memsource with no problems so I am confident it isn't an issue at my end. Wondering if this is a widespread issue or just something that was happening to me? anyway, it cost me a lot of time and a late delivery sadly...