{"id":1934,"date":"2019-07-25T20:19:04","date_gmt":"2019-07-25T18:19:04","guid":{"rendered":"https:\/\/it.wordpress.org\/team\/?post_type=handbook&#038;p=1934"},"modified":"2019-07-25T20:19:04","modified_gmt":"2019-07-25T18:19:04","slug":"pte-status-requests-by-devs-for-italian-localization-the-guidelines","status":"publish","type":"handbook","link":"https:\/\/it.wordpress.org\/team\/handbook\/polyglots\/pte-status-requests-by-devs-for-italian-localization-the-guidelines\/","title":{"rendered":"PTE status requests by Devs for Italian localization: the guidelines."},"content":{"rendered":"<p class=\"wp-block-paragraph\">Following the path of some other <em>locales<\/em>, here are the guidelines for all WordPress Devs who wish to have their products (themes, plugins) localized in Italian, to give it a wider chance to be adopted by Italian users.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In order to assure the best possible quality for all translations (and therefore for the products you so dearly worked on), we have established a few rules to grant you PTE (<strong>Project Translator Editor<\/strong>) status for your product(s):<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>If YOU<strong> want to become a PTE<\/strong>, we follow the WordPress <a href=\"https:\/\/make.wordpress.org\/meta\/handbook\/documentation\/translations\/#im-a-plugin-author-how-do-i-become-a-project-translation-editor-for-my-plugin\">meta handbook for translations recommendations<\/a>. We will not accept your request if you don\u2019t speak Italian.<\/li><li>If you <strong>don\u2019t speak Italian<\/strong> and will have a TRANSLATOR working on your product, please <strong>have them work on the <\/strong><a href=\"https:\/\/translate.wordpress.org\/locale\/it\"><strong>WP translate platform<\/strong><\/a><\/li><li>You should all <strong>follow these steps<\/strong> (either YOU, the Dev, or the Translator):<\/li><\/ol>\n\n\n\n<ul class=\"wp-block-list\"><li>Get yourselves (again, you AND\/OR the translator \u2013 both would be best for perfect communication) on the <a href=\"http:\/\/italia-wp-community.slack.com\/\">Italian Slack Community<\/a>.<\/li><li>Translate as a <a href=\"https:\/\/make.wordpress.org\/polyglots\/handbook\/rosetta\/roles-and-capabilities\/#roles-and-capabilities-for-locale-sites\">Contributor<\/a>;<\/li><li>A PTE will review the translations;<\/li><li>A PTE or a GTE (<strong>General Translator Editor<\/strong>) will give you (or translator) the opportune feedback;<\/li><li>If the quality of the translation is <strong>up to the standards<\/strong> we all try to follow (remember, a poor translation is as bad for your product as it is for the entire WP ecosystem) You (or your translator) will be <strong>granted PTE authority<\/strong>.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>WHY WE FOLLOW THESE GUIDELINES?<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>We strive at perfection: we aim at having the <strong>best possible localization<\/strong> for all products in the WP ecosystem. And that requires that <strong>all translations be done in the best possible way<\/strong>.<\/li><li>It helps us create a community of Italian translators that know each other, and that can support each other when needed.<\/li><li>We think globally, and aim at consistency.<\/li><li>It<strong> streamlines and optimizes the process<\/strong>, reducing the amount of \u00abimproper\u00bb translations and, by default, the time spent on rejecting and revising translations. (Thus allowing more time to be devoted to the actual localizing)<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">It is not different as what happens on GitHub, where access is not given directly to original code, but allowed through Forks and Pull Requests (just to give you a metaphor that\u2019s closer to your approach)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We do feel you can understand that these rules are meant <strong>to give You the best possible localization for your product<\/strong>(s), and <strong>to give the entire WP community a better UX, a stronger platform and a healthier ecosystem to work on<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We hope everything is clear. If not, you can always catch us on <a href=\"https:\/\/make.wordpress.org\/chat\/\">Slack<\/a> to discuss this further. Happy coding!<\/p>\n<nav class='o2-post-footer-actions'><ul class='o2-post-footer-action-row'><\/ul><div class='o2-post-footer-action-likes'><\/div><ul class='o2-post-footer-action-row'><li class='o2-post-footer-action'><span class='o2-resolve-wrap'><a href=\"#\" title=\"Da fare\"  class=\"o2-resolve-link o2-disabled-action genericon  genericon-dot\"  data-action=\"resolvedposts\"  data-actionstate=\"normal\" >Da fare<\/a><ul><\/ul><\/span><\/li><\/ul><\/nav>","protected":false},"author":1702,"featured_media":0,"parent":1890,"menu_order":20,"template":"","meta":{"footnotes":""},"class_list":["post-1934","handbook","type-handbook","status-publish","hentry","author-wolly","make-pte-status-requests-by-devs-for-italian-localization-the-guidelines"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/it.wordpress.org\/team\/wp-json\/wp\/v2\/handbook\/1934","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.wordpress.org\/team\/wp-json\/wp\/v2\/handbook"}],"about":[{"href":"https:\/\/it.wordpress.org\/team\/wp-json\/wp\/v2\/types\/handbook"}],"version-history":[{"count":1,"href":"https:\/\/it.wordpress.org\/team\/wp-json\/wp\/v2\/handbook\/1934\/revisions"}],"predecessor-version":[{"id":1935,"href":"https:\/\/it.wordpress.org\/team\/wp-json\/wp\/v2\/handbook\/1934\/revisions\/1935"}],"up":[{"embeddable":true,"href":"https:\/\/it.wordpress.org\/team\/wp-json\/wp\/v2\/handbook\/1890"}],"author":[{"embeddable":true,"href":"https:\/\/it.wordpress.org\/team\/wp-json\/wporg\/v1\/users\/wolly"}],"wp:attachment":[{"href":"https:\/\/it.wordpress.org\/team\/wp-json\/wp\/v2\/media?parent=1934"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}