I can't really translate individual words (translation is done on a sentence-by-sentence basis, so I don't have that data), but I could do transliteration. Perh

I can't really translate individual words (translation is done on a sentence-by-sentence basis, so I don't have that data), but I could do transliteration. Perhaps hovering could transliterate, clicking could translate the whole sentence, and clicking again could reset it. It's difficult balancing the amount of things people want to do with the text (listen to audio, translate the word, translate the sentence, and transliterate the word) with how few input methods there are + text shifting. The context window is only that sentence. It would be technically possible to increase the context window, but it would make it impossible to cache and increase translation costs even without that. Unfortunately the development of Nuenki has been defined by mitigating the cost of translation - before I had my many mitigations my prototype burned through six euros of credit in a day - so it's not practical to expand that context window. I'll definitely recolour that button. Thanks for mentioning it! The incorrect translations are the engine's fault. The version you're using uses https://www.deepl.com/en/whydeepl https://www.deepl.com/en/whydeepl . Looking at my quality data for the new update (which adds Claude and Gemma as translation sources in some circumstances), that'll improve a little soon but ultimately not by much.