{"id":627,"date":"2013-07-26T11:47:42","date_gmt":"2013-07-26T11:47:42","guid":{"rendered":"http:\/\/blog.mozilla.org\/calendar\/?p=627"},"modified":"2013-07-26T11:47:42","modified_gmt":"2013-07-26T11:47:42","slug":"lightning-2-5-localization-issues","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/calendar\/2013\/07\/lightning-2-5-localization-issues\/","title":{"rendered":"Lightning 2.5+ Localization Issues"},"content":{"rendered":"<p>Hello Folks,<\/p>\n<p>As you may have noticed if you are using the beta versions, there have been a few localization problems in the past. This is not the localizers fault, but rather a problem with our build infrastructure.<\/p>\n<p>I have been working on moving the Lightning builds from their own build machines to building together with Thunderbird. This doesn&#8217;t mean that Lightning will be pre-installed with Thunderbird, it just saves time while building since I don&#8217;t have to maintain a separate set of build machines.<\/p>\n<p>Unfortunately, since Lightning is just piggybacking the Thunderbird build targets, this causes a dilemma for the localized builds. Before the localization process begins, the language files are downloaded from the mercurial server and updated to the specific version which was signed-off by a Thunderbird localizer. As Lightning can only hook into the build process itself, there is no previous step to update the language files to the version which was signed-off by the Lightning localizers. Adding this step is non-trivial.<\/p>\n<p>In some cases it will magically work, if the Thunderbird localizer signed off a later version than the Lightning localizer, because the Lightning changes will then be contained too. Right now I don&#8217;t have a good solution other than to ask localizers to sign off on the Thunderbird dashboard. I&#8217;m trying to figure out some alternatives, in the worst case I will have to do the language repackaging manually for Thunderbird 24 \/ Lightning 2.6.<\/p>\n<p>If you have some experience with Mozilla&#8217;s release engineering and have an idea how to solve this, I&#8217;m happy to hear it!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Hello Folks, As you may have noticed if you are using the beta versions, there have been a few localization problems in the past. This is not the localizers fault, but rather a problem with our build infrastructure. I have been working on moving the Lightning builds from their own build machines to building together [&hellip;]<\/p>\n","protected":false},"author":460,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18,199],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/calendar\/wp-json\/wp\/v2\/posts\/627"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/calendar\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/calendar\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/calendar\/wp-json\/wp\/v2\/users\/460"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/calendar\/wp-json\/wp\/v2\/comments?post=627"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/calendar\/wp-json\/wp\/v2\/posts\/627\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/calendar\/wp-json\/wp\/v2\/media?parent=627"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/calendar\/wp-json\/wp\/v2\/categories?post=627"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/calendar\/wp-json\/wp\/v2\/tags?post=627"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}