Google API Access Count and Pricing w/OmegaT Thread poster: flz_watari
|
I was curious about one aspect of using the Google Translation API, which I did not find discussed in the documentation. In particular, I am wondering how many times the API gets accessed when performing a translation using OmegaT, and especially, if one returns to segments that have already been translated (for example, should one be perusing through a project and check back on an already translated segment), will the API be accessed again in that case (with whatever charges applied)? Or does O... See more I was curious about one aspect of using the Google Translation API, which I did not find discussed in the documentation. In particular, I am wondering how many times the API gets accessed when performing a translation using OmegaT, and especially, if one returns to segments that have already been translated (for example, should one be perusing through a project and check back on an already translated segment), will the API be accessed again in that case (with whatever charges applied)? Or does OmegaT recognize that a particular segment is already translated, and hence not make a call to the API again (but simply show whatever the previous result was in the Machine Translation pane). I tend to scroll through previously translated segments multiple times when translating, which I'm sure is quite common. I just want to make sure that I'm not being charged again each time I refer back to an already translated segment for which the Google API was accessed once before. ▲ Collapse | | | Didier Briel France Local time: 13:19 English to French + ... Machine translation requests are cached | May 30, 2017 |
flz_watari wrote: I was curious about one aspect of using the Google Translation API, which I did not find discussed in the documentation. In particular, I am wondering how many times the API gets accessed when performing a translation using OmegaT, and especially, if one returns to segments that have already been translated (for example, should one be perusing through a project and check back on an already translated segment), will the API be accessed again in that case (with whatever charges applied)? Or does OmegaT recognize that a particular segment is already translated, and hence not make a call to the API again (but simply show whatever the previous result was in the Machine Translation pane). I tend to scroll through previously translated segments multiple times when translating, which I'm sure is quite common. I just want to make sure that I'm not being charged again each time I refer back to an already translated segment for which the Google API was accessed once before. Machine translation requests are cached. That means that a source segment already machine translated will not be requested again during the same session (i.e., until OmegaT is closed). For segments already translated (manually), it's up to you to send them or not to the machine translation engine, with the "Untranslated segments only" checkbox. Didier | | |
Machine translation requests are cached. That means that a source segment already machine translated will not be requested again during the same session (i.e., until OmegaT is closed). For segments already translated (manually), it's up to you to send them or not to the machine translation engine, with the "Untranslated segments only" checkbox. ----- That's great, thanks! It seems like the "untranslated segments only" item should simply remain checked... See more Machine translation requests are cached. That means that a source segment already machine translated will not be requested again during the same session (i.e., until OmegaT is closed). For segments already translated (manually), it's up to you to send them or not to the machine translation engine, with the "Untranslated segments only" checkbox. ----- That's great, thanks! It seems like the "untranslated segments only" item should simply remain checked at all times. ▲ Collapse | | | There is no moderator assigned specifically to this forum. To report site rules violations or get help, please contact site staff » Google API Access Count and Pricing w/OmegaT Protemos translation business management system | Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!
The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.
More info » |
| Anycount & Translation Office 3000 | Translation Office 3000
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |