Most things were addressed during the last changelog, I'm just thanking people and following up on specific cases:
Already Fixed:
tux0r done, thank you 🙂
Lightnin we doubled/tripled the limits depending on your plan, let us know if this is enough now for your use case.
andelink we got a better source for chinese characters, so it's fixed. Thanks! It was indeed getting the radical strokes.
Still Investigating/Following Up:
Chloe hey there, does this still happen for you? what browser are you using?
tistos investigating this, but so far the likeliest explanation is that standard is simply not good enough for these shorter queries - which counterproductively are actually some of the hardest because of the lack of context. We'll see what we can do.
AlarmedSuccess nice that it works with best, we'll see if we can make it better on standard too. thank you for reporting it.
xobust will talk with the assistant team to see what we can do on that side 🙂
patchmonkey hey, what browser are you using? We should probably review the "automatic" wording 🙂 - the button currently needs to be pressed under the post/content you want to translate, and you should see the translation appear underneath. If it's not working for you, console logs from the page (after you click the button) would be helpful - can you send them over to giorgio@kagi.com? Thanks!
