Menu

Why one translation is never enough when the relationship is the message
πŸ“°
0

Why one translation is never enough when the relationship is the message

DEV CommunityΒ·J NowΒ·about 1 month ago
#TccWJkSw
#ai#nlp#showdev#writing#konid#three
Reading 0:00
15s threshold

I was drafting a message to a colleague in French β€” someone I'd worked with for two years but never quite knew how to place on the formality dial. I ran it through Google Translate, got one sentence back, and had no idea if it read as warm, cold, or weirdly stiff. I sent it anyway. I still don't know how it landed. That's the actual problem with literal translation tools: they return one answer and leave you to guess whether it fits the moment. But in almost any language, the same thought exists in at least three registers β€” one you'd use with a close friend, one for a colleague, one for someone you're trying to show respect. The gap between those isn't just vocabulary. It's whether you sound like you understand the relationship. So I built konid. You describe what you want to say, and it returns three options ordered casual to formal, with each register explained and a note on the nuance between them.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More