I often reply under Japanese posts, and I always assume users will use a translator as I do, but maybe in the context of a Japanese instance or conversation this may look rude?
I often reply under Japanese posts, and I always assume users will use a translator as I do, but maybe in the context of a Japanese instance or conversation this may look rude?
Mer chönd das scho probiere, aber denn müsst mer ja di ganz Ziit en Übersetzer zur Hand ha, wär denn doch nöd die best UX würdi säge. Das würd d’Neuakömmlige nur no meh verschüüche.
That’s not a language, it’s a dialect and nowhere near standard. I think there’s quite a difference between responding in a language that can be translated by existing translation tools vs whatever offshoot of a dialect you wrote that in. After all, people from the UK will respond in English, not Cockney, Geordi, Brummie or whatever else. And they don’t write words how they sound when spoken, which is what you’re doing.
Surprisingly your text was translatable by DeeplL
As to the UX, I don’t see the problem. Lemmy allows you to select which languages you want to see and if people consistently respond in a language you don’t wan to see, you can always block them. It’s a pity Lemmy doesn’t allow deselecting “Undetermined” because it would turn this into a non-issue.
The point is that languages without large speakerbases might consider barging in with the most recognized languages rude, while languages with similar status might find it normal.
I just used the TWP plugin to translate that comment inline and got, “We could try it, but then we’d have to have a translator on hand the whole time, which wouldn’t be the best UX, I think. That would only alienate newcomers even more.”
Is that not correct?
That’s perfect, exactly what I meant to say.
Neat!
My only complaint with the TWP translator - it doesn’t tell me the language/dialect that it translated from. Mind telling me what dialect (of what language) you wrote in?
Swiss/Allemanic German. Specifically I speak Zug’s dialect.
Thanks!