You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the entire input gets sent to the selected translation service. If multiple translations are executed on a block of text (say, when the user is typing in the Translation View and they wish to check if their intermediate result is correct), the amount of characters sent to the service will grow exponentially - even more so if the user has auto translate enabled.
The solution for this problem is to only translate the new text. Below are some approaches that could be taken:
Caching
Cache translation results of the service
Implement rudementary cache inside DummyTranslate
After each request, add translation for sentence
Issues
What is a sentence? Not all languages end on periods, so how should those be processed?
(cont.) How do you properly split a body of text such that the meaning is still identical?
Only changes
Only translate parts of the entered text that were changed
Issues
Might be hard to implement (what constitutes as a change? one letter can cause an entirely different interpretation of a sentence)
The text was updated successfully, but these errors were encountered:
Currently, the entire input gets sent to the selected translation service. If multiple translations are executed on a block of text (say, when the user is typing in the Translation View and they wish to check if their intermediate result is correct), the amount of characters sent to the service will grow exponentially - even more so if the user has auto translate enabled.
The solution for this problem is to only translate the new text. Below are some approaches that could be taken:
Caching
Cache translation results of the service
Issues
Only changes
Only translate parts of the entered text that were changed
Issues
The text was updated successfully, but these errors were encountered: