I\u2019m Telling You, There Is No Word For \u2018Yes\u2019 Or \u2018No\u2019 In Irish<\/p><\/blockquote>\n
from Brendan Caldwell<\/a><\/cite><\/p>\n The art of localizing a piece of software with a Yes<\/em> button is to know what that button will do. This is an example of software UI that makes assumptions on language that hold for English, but might not for other languages. A more frequent example in both UI and languages that are affecting is piecing together text and UI controls:<\/p>\n In the localization tool, you’ll find each of those entries as individual strings. The localizer will recognize that they’re part of one flow, and will move fragments from the shared string to the drop-down as they need. Merely translating the individual segments is not going to be a proper localization of that piece of UI.<\/p>\n If we were to build a rule-based<\/a> machine localization system, we’d find rules like<\/p>\n Map the shared fragment to the localization of the English shared fragment\n<\/ul>\n Now that’s rule-based, and it’d be tedious to maintain these rules. Neural Machine Translation<\/a> (NMT) has all the buzz now, and Machine Learning in general. There is plenty of research<\/a> that improves how NMT systems learn about the context of the sentence they’re translating. But that’s all text.<\/p>\n It’d be awesome if we could bring Software Analysis into the mix, and train NMT to localize software instead of translating fragments.<\/p>\n For Firefox, could one train on English and localized DOM? For Android’s XML layout, a similar approach could work? For projects with automated screenshots, could one train on those? Is there enough software out there to successfully train a neural network?<\/p>\n Do you know of existing research in this direction?<\/p>\n","protected":false},"excerpt":{"rendered":" TL;DR: Is there research bringing together Software Analysis and Machine Translation to yield Machine Localization of Software? I\u2019m Telling You, There Is No Word For \u2018Yes\u2019 Or \u2018No\u2019 In Irish from Brendan Caldwell The art of localizing a piece of software with a Yes button is to know what that button will do. This is […]<\/p>\n","protected":false},"author":17,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,5],"tags":[23779,23778],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/posts\/599"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/comments?post=599"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/posts\/599\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/media?parent=599"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/categories?post=599"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/tags?post=599"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/blog.mozilla.org\/axel\/files\/2018\/07\/Pieced-together-UI-300x94.png\")
<\/a><\/p>\n\n
gaelic-yes<\/code>:
\nIf the title of your dialog contains a verb, localize Yes<\/em> by translating the found verb.<\/p>\npieced-ui<\/code>:
\nFor each variant,<\/p>\n\n