<div dir="ltr">@Otto or @Ulrich: Is using grunt-wp-i18n as good as <span style="font-family:arial,sans-serif;font-size:12.800000190734863px">i18n tools?</span><div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br>
</span></div><div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px">I haven't noticed any differences when switching to </span>grunt-wp-i18n. And I think more and more devs are using Grunt and in the same time automating .pot file with grunt-wp-i18n.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 24 June 2014 23:06, Ulrich Pogson <span dir="ltr"><<a href="mailto:grapplerulrich@gmail.com" target="_blank">grapplerulrich@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>@Sami - Poedit Pro does include the translator comments and is able to automatically generate a PO file without any previous information. I know the developer is working to add header support in the future.<br>
</div><div><br></div><div>@Chip - Where is it in the guidelines that the translation-ready is just for the front end? This is suboptimal experience for users looking for a fully translation-ready theme. So the user needs to check if the back is also translation ready.</div>
<div><br></div>@Otto - You are right the tool depends on wp-includes/pomo/po.php The documentation has been updated. From looking at the code it look like the `msguniq` gettext command is called. Where is the best place to contribute to the i18n tools. I have fixed a few of the strict errors. You can see it here <a href="https://github.com/grappler/i18n" target="_blank">https://github.com/grappler/i18n</a><div>
<br></div><div>@Edward - <a href="https://make.wordpress.org/docs/plugin-developer-handbook/15-internationalization/localization/" target="_blank">https://make.wordpress.org/docs/plugin-developer-handbook/15-internationalization/localization/</a></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On 24 June 2014 20:30, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>On Tue, Jun 24, 2014 at 1:21 PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br>
</div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">@Otto42 - Slightly off-topic, but quickly, can the "makepot.php" be applied to plugins as well ... or is there a similar functionality for plugins in a different folder? (I'll look into it more later, just being a bit a lazy *grin*)</div>
</blockquote><div><br></div><div><br></div></div><div>Yes. Same command, but instead of using "wp-theme", use "wp-plugin".</div><div><br></div><div>More info at the bottom of this post:</div><div><a href="http://ottopress.com/2013/language-packs-101-prepwork/" target="_blank">http://ottopress.com/2013/language-packs-101-prepwork/</a><br>
</div><div><br></div><div><br></div><div><br></div><div>@Joe Dolson: The tool in the directory indeed runs the makepot.php functionality, however the tool on .org is not quite up-to-date and needs to be updated. It mostly works though. I recommend using the makepot.php file yourself instead. It's also good to simply have your development environment, you know? :)</div>
<span><font color="#888888">
<div><br></div><div>-Otto</div></font></span></div></div></div>
<br></div></div><div class="">_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Sami Keijonen<br>Fox Holding Oy<br><a href="mailto:sami.keijonen@foxnet.fi" target="_blank">sami.keijonen@foxnet.fi</a><br><a href="http://foxnet.fi" target="_blank">foxnet.fi</a><div>
<a href="http://foxnet-themes.fi" target="_blank">foxnet-themes.fi</a></div></div>
</div>