looks cool,it would be useful to have transliterations for non latin alphabet languages,or at least pinyin for Chinese, since learning characters is somewhat orthogonal to the words.
I'm also learning Chinese, and I honestly wouldn't care for Pinyin all that much. (Once you get to an intermediate level of Chinese, you'll want to learn characters anyway, because that's how Chinese is written in the real world.) That said, a hover option to transliterate and translate individual words (instead of the whole sentence at once) would be great.
For a more practical complaint, in the Nuenki browser extension, the settings window has a primary-colored (green) button in the bottom right that says "Log out", but has no "Save" button. I almost clicked "Log out" when I just meant to confirm the settings I had made!
Edit: Also one question, if I may - how large is the context window for the translations? I noticed that the Chinese it generates sometimes feels a little unidiomatic, but I'm not sure whether that's due to too little context, the fault of the translation engine(s) used, or just my feeling as a non-advanced Chinese learner being off.
Edit 2: Some of the translations are definitely just wrong, too. Again, might be the fault of the engines - after all, machine translation, even in the age of LLM, is not perfect.
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 . 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.
