So glad to have your post on a subject that has concerned me since the first memoQ Fest. I should have gotten it out sooner, but as you know, recent months have been challenging.
Both repetitions and internal fuzzies should be counted within the documents that are assigned to a translator. This would be the objectively correct way: the companies could start to calculate and apply "discounts" that actually make sense.
For this, the tools should have a concept of an "assignment" (for lack of a better word), i.e. the set of documents that are assigned to a person in a project. If the tools would have such a concept (maybe some of them do, I have no idea, I just know that memoQ doesn't really have it), then they could start working towards useful features like statistics done by "assignment".
Actually, it's not even very complex, it would be a logical iterative next step that wouldn't really turn too many things upside down. I see two possible problems working against this. One is that nobody is really mounting the pressure on the tool makers to make this happen. The other is that the more complex a tool is, the more possible directions there are for "next steps." With every door they open, there are several or many doors they can open next.
Thanks, Kevin, for having me as a guest. :)
I probably never would have started writing without your encouragement and guidance. Also thanks for that.
So glad to have your post on a subject that has concerned me since the first memoQ Fest. I should have gotten it out sooner, but as you know, recent months have been challenging.
Modern translations environments have built-in counting of internal fuzzies, yet they do not offer any means to isolate such segments. Ironic...
Both repetitions and internal fuzzies should be counted within the documents that are assigned to a translator. This would be the objectively correct way: the companies could start to calculate and apply "discounts" that actually make sense.
For this, the tools should have a concept of an "assignment" (for lack of a better word), i.e. the set of documents that are assigned to a person in a project. If the tools would have such a concept (maybe some of them do, I have no idea, I just know that memoQ doesn't really have it), then they could start working towards useful features like statistics done by "assignment".
Actually, it's not even very complex, it would be a logical iterative next step that wouldn't really turn too many things upside down. I see two possible problems working against this. One is that nobody is really mounting the pressure on the tool makers to make this happen. The other is that the more complex a tool is, the more possible directions there are for "next steps." With every door they open, there are several or many doors they can open next.