Hi Yasemin Ak 

Thank you for reaching out! 

This can happen if you have the Cloud resources and/or the Language Weaver provider activated. See this articles that explain a bit what happens and what you can do:

https://gateway.sdl.com/apex/communityknowledge?articleName=000018765

https://gateway.sdl.com/apex/communityknowledge?articleName=000008379

Basically the machine translation provider, Cloud Resources or LW Plugin, is used by Trados Studio like a Translation Memory, searching it at every segment. If you perform also pre-translate and then go segment by segment, you can end up with extra usage. 

You can monitor your usage in Language Weaver as shown in this article: https://gateway.sdl.com/apex/communityknowledge?articleName=000013218

My suggestion is to try on a smaller document, to see how what you in do in Trados Studio affects your LW machine translation usage. 

Hope this helps, 

Radu

Hi Radu, 

Yes, I use Pretranslate (to use 'change all' option for certain terms) and then I go segment by segment. In this case, Weaver must be using its resources two times for each segment, thereby doubling the used character count. I have not considered it before. Thanks for clarifying the issue.

Kind regards, 

Yasemin 

Hi Radu, 

Yes, I use Pretranslate (to use 'change all' option for certain terms) and then I go segment by segment. In this case, Weaver must be using its resources two times for each segment, thereby doubling the used character count. I have not considered it before. Thanks for clarifying the issue.

Kind regards, 

Yasemin