<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exploiting Similarities among Languages for Machine Translation · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1309.4168/</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/1309.4168/feed.xml" rel="self" type="application/rss+xml" /><item><title>Exploiting Similarities among Languages for Machine Translation — mentioned by exgrv</title><link>https://news.ycombinator.com/item?id=13774407</link><guid isPermaLink="false">urn:hackerpapers:mention:1309.4168:13774407</guid><pubDate>Thu, 02 Mar 2017 14:59:05 GMT</pubDate><description>&lt;p&gt;Models are trained independently for each language. So unfortunately, you cannot directly compare words from different languages using these vectors. If you have a bilingual dictionary, you might try to learn a linear mapping from one language to the other (e.g. see https://arxiv.org/abs/1309.4168 for this approach).&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1309.4168/"&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>Exploiting Similarities among Languages for Machine Translation — HN submission</title><link>https://news.ycombinator.com/item?id=10102067</link><guid isPermaLink="false">urn:hackerpapers:submission:1309.4168:10102067</guid><pubDate>Sat, 22 Aug 2015 09:42:49 GMT</pubDate><description>&lt;p&gt;Exploiting Similarities Among Languages for Machine Translation (2013)&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;6 points; 1 discussion reply on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1309.4168/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Exploiting Similarities among Languages for Machine Translation — mentioned by Smerity</title><link>https://news.ycombinator.com/item?id=9716265</link><guid isPermaLink="false">urn:hackerpapers:mention:1309.4168:9716265</guid><pubDate>Sun, 14 Jun 2015 20:41:42 GMT</pubDate><description>&lt;p&gt;I&amp;#x27;m uncertain whether you mean the algorithm or the output. The question is interesting to both however. The most common method for producing word vectors, skip-grams with negative sampling, has been shown to be equivalent to implicitly factorizing a word-context matrix[1]. A related algorithm, GloVe, only uses a word-word co-occurrence matrix to achieve a similar result[2]. You can also view the output as an embedding in a high dimensional space (hence the name word vectors) but more surprisingly you can learn a linear mapping between vector spaces of two languages, which lends it…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1309.4168/"&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>Exploiting Similarities among Languages for Machine Translation — mentioned by eadlam</title><link>https://news.ycombinator.com/item?id=6494924</link><guid isPermaLink="false">urn:hackerpapers:mention:1309.4168:6494924</guid><pubDate>Fri, 04 Oct 2013 12:30:23 GMT</pubDate><description>&lt;p&gt;Stanford Ph.D. student Richard Socher appreciates the work Google and others are doing to build neural networks that can understand human language. He just thinks his work is more useful ... &amp;quot;We’re actually able to put whole sentences and longer phrases into vector spaces without ignoring the order of the words.&amp;quot; Wait, didn&amp;#x27;t Mikolov et al. (Google) [just figure out][1] how to put entire languages into vector spaces? [1]: http://arxiv.org/abs/1309.4168&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1309.4168/"&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>
