{"id":15,"date":"2006-11-29T19:59:47","date_gmt":"2006-11-30T02:59:47","guid":{"rendered":"http:\/\/blog.mozilla.org\/axel\/2006\/11\/29\/der-tellerrand\/"},"modified":"2007-04-30T17:35:00","modified_gmt":"2007-05-01T00:35:00","slug":"der-tellerrand","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/axel\/2006\/11\/29\/der-tellerrand\/","title":{"rendered":"Der Tellerrand"},"content":{"rendered":"<p>I&#8217;ve spent the last few days catching up on <a href=\"http:\/\/sourceforge.net\/mailarchive\/forum.php?forum_id=7939\" title=\"list archive\">years of archive of translate-i18n<\/a>. It&#8217;s been an interesting read so far, the challenges we face are the same in other places, and are pretty independent of the used technology. Given the recent 50-2-100 discussion in .l10n and .planning, I found two threads from April this year particularily interesting. <a href=\"http:\/\/sourceforge.net\/mailarchive\/forum.php?thread_id=10225758&amp;forum_id=7939\" title=\"thread archive\">Morale<\/a> and <a href=\"http:\/\/sourceforge.net\/mailarchive\/forum.php?thread_id=10255957&amp;forum_id=7939\" title=\"thread archive\">Draft of awareness-raising email to maintainers<\/a>. The first is somewhat of a corresponding thread to 50-2-100 on their side, and the latter is a resulting inquiry for project maintainers to see if they do the right thing for localizers. As the survey is kind-of fun and adds some non-Mozilla context, I took the freedom to fill it out for you.<\/p>\n<ol>\n<li>Do you freeze your strings at least two weeks before release?<br \/>\n(a) <strong>Yes<\/strong><br \/>\n(b) No<br \/>\n(c) What strings?<\/li>\n<li>Do you send in a pre-release POT file, at least two weeks before<br \/>\nrelease?<br \/>\n(a) <strong>Yes<\/strong><br \/>\n(b) No<br \/>\n(c) POT? Not. What rot!<br \/>\n&#8230; as tempting as (c) is :-)<\/li>\n<li>Do you fill in the Report-Msgid-Bugs-To address in the PO file<br \/>\nheader?<br \/>\n(a) <strong>Yes<\/strong><br \/>\n(b) No<br \/>\n(c) I&#8217;m in hiding.<\/li>\n<li>Do you supply contextual comments for complex strings?<br \/>\n(a) <strong>Yes<\/strong><br \/>\n(b) No<br \/>\n(c) I don&#8217;t understand them either.<\/li>\n<\/ol>\n<p>The message? No, we&#8217;re not done, by far. But we&#8217;re addressing the right targets, and we&#8217;re improving in key areas that are of concern to localizers, inside and outside of the Mozilla project.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve spent the last few days catching up on years of archive of translate-i18n. It&#8217;s been an interesting read so far, the challenges we face are the same in other places, and are pretty independent of the used technology. Given the recent 50-2-100 discussion in .l10n and .planning, I found two threads from April this [&hellip;]<\/p>\n","protected":false},"author":17,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/posts\/15"}],"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=15"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/posts\/15\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/media?parent=15"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/categories?post=15"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/tags?post=15"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}