Moving the Localization Carpet under the Source Text
Here's the mess I face.
The HTML files are filled with paragraphs formatted like this:
Currently, this function gets called for trust overrides and
client authentication. On client authentication, the supplied
interface contains the server's Certificate Authorities Distinguished
Names list (see references) and the negotiation handler
always gets called so as to give a chance to the client to supply
the correct client certificate based on the DN list.
At the end of each line are two hard returns. It wasn't always this way, so each complete sentence is sitting happily in translation memory. Unfortunately, Trados pulls in each of these six 80-character fragments and calls it low- or no-match because it can't find enough of a concordance. This is a classic case of false positives driving up translation costs.
I'm still exploring options. Meanwhile, there's no sense in starting the translation work.
The HTML files are filled with paragraphs formatted like this:
Currently, this function gets called for trust overrides and
client authentication. On client authentication, the supplied
interface contains the server's Certificate Authorities Distinguished
Names list (see references) and the negotiation handler
always gets called so as to give a chance to the client to supply
the correct client certificate based on the DN list.
At the end of each line are two hard returns. It wasn't always this way, so each complete sentence is sitting happily in translation memory. Unfortunately, Trados pulls in each of these six 80-character fragments and calls it low- or no-match because it can't find enough of a concordance. This is a classic case of false positives driving up translation costs.
I'm still exploring options. Meanwhile, there's no sense in starting the translation work.
Labels: Localization, localization project, translation memory
0 Comments:
Post a Comment
<< Home