You are currently working on UAT 

  • State Suggested Answer
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 430 subscribers
  • Views 4054 views
  • Users 0 members are here
Options
Related

Partial project analysis in XBench - best way to do this?

Neil Allen

If I want to analyse only part of a project using the XBench plugin, I imagine that the best (or possibly only) way to do this would be to use the xliff toolkit to create an xliff file of only the relevant segements and import that into XBench.

Or is there some way of doing this more directly?

Thanks,

Neil
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Hello Neil,

    I guess you already tried ignoring context matches or untranslated segments in xbench.

    What kind of parameters would you need to filter the segments?
  • 0 in reply to Enrico Rosso
    Ideally I'd like a way of excluding locked segments from going to XBench, but it's not critical. I just wondered whether there was any easy way to do this.
  • 0 in reply to Neil Allen
    Hi

    It looks as though this is an outstanding task in Xbench to enable this feature:

    forum.xbench.net/.../5

    might be able to help?

    Paul Filkin | RWS

    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul Filkin
    Ok, thanks Paul. There are certain circumstances where it might be desirable to exclude some (but not all) ICE segments from XBench (for example, if a previous XBench QA has already been run on to check a proofread pretranslation before starting the rest of the translation, one wouldn't need it run again on those segments, but one would on future ICE segments). I'm glad to know the XBench team are looking into this; I have been an XBench subscriber for quite a few years now and find it complements CAT tools really well.
  • 0

    I am not familiar with XBench. Just have seen its consistency report several times (not so impressive).

    Just out of curiosity.

    Is there any (big) differencies between SDL Trados Studio's QA and XBench's ? Can you tell me one item that SDL Trados Studio can not do it but XBench can ?

    When you tell me about it. I will show you SDL Trados Studio can do it too (much better than that).

    For your main question, if XBench have time filtering option, things solved very easily. Filter out older segments, right ? SDL Trados Studio already have it(Lock/UnLock too, perfectly). 
  • 0 in reply to AnonymousUser
    XBench serves two completely unrelated functions, terminology management and QA.

    My XBench termbase is kept loaded into live memory and currently contains 1,795,217 entries. I don't want these loaded into a CAT tool termbase because it would slow it down to a crawl and every source segment would flag entries that would be irrelevant to the current project. All I want in my CAT tool termbase are entries relating to the current project (for automatic QA) and nothing else.

    As regards QA, spellchecking is far better than in any CAT tool because only one instance of questionable spelling is flagged and, if necessary, these can be corrected en masse in the CAT tool.

    QA is much more configurable than in Trados Studio, with checklists that can be programmed to look for common dictation errors (such as the French word "principe" being translated as "principal" instead of "principle") and that can be configured in ways that Studio termbases cannot. All potential errors are shown grouped together across the entire project and can be ignored en masse instead of having to tediously look at hundreds of individual messages. Number checking is far better than in Studio, even with the Number Verifier plugin installed. Depending on how Studio is configured, it either throws up lots of false positives or it misses errors. For example, it flags this: 122,45 € > €122.45 as an error because it doesn't like the currency symbol stuck to the number. Many times I have found number errors (particulary added numbers) that Trados QA has not caught, particularly in memories provided to me, presumably because the previous translator has configured the number checking to reduce all the false positives.

    "When you tell me about it. I will show you SDL Trados Studio can do it too (much better than that)". I am not interested in getting involved in arguments about what various tools can do and trying to prove that one is better than another. Such arguments resemble discussions about religion and serve no purpose. If you like XBench, then use it. If you don't, then don't use it.

    Neil
  • 0 in reply to Neil Allen

    Oh I see

    I do not agree with you some of items mentioned above - because the "Studio" you mentioned is a company which is just a big, slow and try not to listen to its own customers wishes. But, the "Studio" I'm using is totally different from it. It is talented, flexible and do whatever I wanted.

    On 2nd thought, I have cancelled my suggestion regarding XBench.
    XBench is post stage tool. I am mostly interested in something that is dynamic - working with me at real time. Currently I have no inconveniencies using it including all kinds of QAs.

    Anyways, appreciated good and kind explanations. I will use XBench when I have some extra money.

    regards
  • 0 in reply to AnonymousUser

    Ah one more thing.
    Once I was participated in a Big project - approximately 40 full time translators and lasts almost a year.
    They have their own TM (about a million TUs) and TB (just 7 thousands items).
    My point is, You do not have to maintain and compare almost 2 million TB items for each and every unique projects.
    All projects are totally different (if not that is a really good news) and their maximum items are not so much big.
    (I am not pretty sure though the biggest IT giant of this world "Microsoft", its TB is also far less than a million-most of them are duplication. )

    Maybe your job is so different.

    regards