• Replies 1 reply
  • Subscribers 431 subscribers
  • Views 1274 views
  • Users 0 members are here
Options
Related

Why Studio's QA is not enough?

Paola

I have been using Studio since its first release in 2009, but 2 years ago, after a couple of clients started sending me QA reports done with Apsic Xbench after my delivery, I realized how much Studio's QA (F8) was missing. So I had to buy Apsic Xbench myself, which costs 99 EUR per year, but I don't like that I have to rely on complementary plugins, softwares, and app for features that could be easily* embedded in Studio. I'd rather rely on Studio's features because I know I am gonna get support for those in case of issues or Studio updates/upgrades.

I don't like I have to pay 99 EUR per year to have a decent QA after buying the most expensive CAT on the market, and I also do not like that nor Studio nor Xbench are not 'complete' in their QA.

For example, some double spacing are caught in Xbench, but not in Studio, though Studio has the double spacing check as part of its QA as well. On the contrary, Studio catches an 'Extra space at the end of the segment' whereas Xbench does not.

I haven't noticed many advances in Studio's QA since its release. Why?

 

Things I'd like to see in Studio's QA:

  1. Better 'double spacing' catching
  2. Capitalization error overridden if the previous segment ends with : (colon) [option in setting]
  3. Check for inline tags, such as  Click the <b>Continue</b> button to proceed
  4. Check for ALL CAPS in target such as The DNA and RNA samples...
  5. Accept spelled out numbers instead of numbers, i.e. don't flag The 1st thing to do is...  - La primera cosa para hacer es...  [option in setting]
  6. Better space fixing around tags, for example if the target contains [word][space][TAG][space][word] it gets flagged as double spacing, but when I use the Change feature in the prompt, it eliminates the tag because the end result I get is [word][space][word]

 

---

*many plugins are free, so if a third party developer did it on his own and give it away for free, it mustn't be that hard or time consuming for SDL to do it themselves
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • Please do not get me wrong, but it seems you are not using many already existing options in Studio QA...

    1. Double space can be easily found with the search and replace function. Also some simple regex will deliver an error on that
    2. This is bad segmentation, in a language where after colon no major case is expected, colon should be removed from the segmentation.
    3. In Studio ALL tags are checked
    4. Indeed, not checked - again, here a regex could be helpful
    5. Does Xbench really support this? I doubt this really, as this would mean knowing all spelled out numbers in any language... Who should code all that.
    6. This indeed a bit of pain, but quite simple to differ fom a "real" double space issue, when checking the error report

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

Reply
  • Please do not get me wrong, but it seems you are not using many already existing options in Studio QA...

    1. Double space can be easily found with the search and replace function. Also some simple regex will deliver an error on that
    2. This is bad segmentation, in a language where after colon no major case is expected, colon should be removed from the segmentation.
    3. In Studio ALL tags are checked
    4. Indeed, not checked - again, here a regex could be helpful
    5. Does Xbench really support this? I doubt this really, as this would mean knowing all spelled out numbers in any language... Who should code all that.
    6. This indeed a bit of pain, but quite simple to differ fom a "real" double space issue, when checking the error report

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

Children
No Data