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

Translation consistency verification does not report cross-file inconsistencies

Evzen Polenka

The subject says it all - the Check for inconsistent translations check in QA Checker 3.0 works differently when run inside editor (F8) and when run as Verify Files batch task.
When run inside editor where multiple files are open (virtually merged), it can catch cross-file inconsistencies.
When run as Verify Files batch task, it seems to check each file separately, thus completely ignores cross-file inconsistencies.

Is this really intended behavior?!?!
Looks like a pretty clear and SERIOUS bug... so when we get this fixed?

I'm seriously not willing to waste hours by waiting for Studio to (hopefully) open 1000 files in editor... not mentioning a common translator who a) does not have a machine with specs able to handle so many files at once, and b) is not paid for hours spent by waiting for Studio opening the files in editor.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Moving my comment from other topic here...

    So far it seems like "omission" in functional design - the thing is that all(?) other checks are "self-contained", i.e. they work on a single segment... while this check compares the checked segment against other segments... so the "other segments" scope depends on the context.

    It's related to other BIG annoyance - that the message says "segment is inconsistent with segment XY", but DOES NOT SAY FROM WHICH FILE :(...
    Plus, the message is attached only to ONE of the segments, so searching for the second segment (with which is the first one inconsistent) is TERRIBLY DIFFICULT... especially in projects with hundreds/thousands of files... Filter "with messages" is useless because it displays only the 'first' segment of the inconsistent pair, but not the second one...
    So one has to manually filter using source text filter, which is ___HORRIBLY___ SLOW (ever tried to use the filter with hundreds of files and 40000+ segments?). Fixing one inconsistent pair can take 10 minutes because of all the waiting for Studio to reload/redraw the editor... so imagine fixing 50 errors...
  • 0 in reply to Evzen Polenka
    The consistency check (or partial lack thereof) is one of my bigger gripes with Studio, it really looks like a sloppy implementation. It furthermore gives the impression that nobody at SDL has actually ever used the consistency check in a production environment. It really is a shame since consistency checks in both directions have enabled us regularly to discover serious issues.
  • 0 in reply to Raphaël Toussaint

    Unknown said:
    It furthermore gives the impression that nobody at SDL has actually ever used the consistency check in a production environment.

    That's EXACTLY what I think about number of other features too!
    Or at least they were not used for reasonably sized projects (i.e. more than few ridiculously simple Word files) or by reasonably thinking engineers/PMs (i.e. not willing to spend their life by clicking like mad or staring at hourglass, waiting for Studio to finally do something).
Reply Children
No Data