<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>No Language Left Behind: Scaling Human-Centered Machine Translation · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2207.04672/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2207.04672/feed.xml" rel="self" type="application/rss+xml" /><item><title>No Language Left Behind: Scaling Human-Centered Machine Translation — mentioned by mortimerp9</title><link>https://news.ycombinator.com/item?id=38491905</link><guid isPermaLink="false">urn:hackerpapers:mention:2207.04672:38491905</guid><pubDate>Fri, 01 Dec 2023 20:30:43 GMT</pubDate><description>&lt;p&gt;Sorry if I wasn&amp;#x27;t clear, internally we&amp;#x27;ve been talking about it a lot, but I forgot that it doesn&amp;#x27;t have such a solid definition outside of our work. Thankfully, we try to define it in section 7.3 of the NLLB paper: https://arxiv.org/pdf/2207.04672.pdf The tldr is that if you say: &amp;quot;Thank you for this job offer.&amp;quot; you wouldn&amp;#x27;t want it to be (mis)translated as &amp;quot;Go F*k yourself.&amp;quot;. But if you do say &amp;quot;Go F yourself&amp;quot;, you still want it to be translated as that.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2207.04672/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>No Language Left Behind: Scaling Human-Centered Machine Translation — mentioned by mortimerp9</title><link>https://news.ycombinator.com/item?id=38491835</link><guid isPermaLink="false">urn:hackerpapers:mention:2207.04672:38491835</guid><pubDate>Fri, 01 Dec 2023 20:25:11 GMT</pubDate><description>&lt;p&gt;Our goal is to have a good recall, sometimes to the detriment of precision, so for words with multiple meanings, it might consider them toxic when in the actual context they are used in, they are not. The toxicity mitigation algorithm will search for alternative translations that have the correct meaning but not the potentially toxic word so that there is no added toxicity in the output. This means that sometimes the model might prefer a less coloquial phrasing than what a human would. You can find details on how the multi-language creation of the toxicity lists was done in section 7.3 of the…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2207.04672/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
