<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>
<br></div><div>@Christine - Thanks, I'll keep that in mind.</div><div><br></div><div class="gmail_extra"><br clear="all"><div>Edward Caissie<br>aka Cais.</div>
<br><br><div class="gmail_quote">On Tue, Jun 24, 2014 at 1:56 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.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">A PO file is literally just a POT file with the translated parts filled in. Renaming it will work fine for POEdit. <br><br>I don't recommend using POEdit to actually generate POT/PO/MO files from the source code itself, as it is a generic tool and it does not know about the WordPress-specific i18n functions. Nor does it really know about WordPress theme and plugin headers.<br>
<br>The WordPress makepot.php tool uses the actual wp core code to do a lot of the work, so it's up-to-date and will always work correctly. The resulting POT file it generates can then be used in any translation tool, such as POEdit, to do the actual translation.<br>
<br>The handbook mentions the makepot.php file first. This is the recommended method.<br><br><a href="https://make.wordpress.org/docs/theme-developer-handbook/theme-functionality/localization/#generating-pot-file" target="_blank">https://make.wordpress.org/docs/theme-developer-handbook/theme-functionality/localization/#generating-pot-file</a><br>
<br>Note that it says "You need thegettext (GNU Internationalization utilities) package", however I do not believe this is true anymore. I'll investigate, but I've been able to run the makepot.php file on a Windows box with XAMPP installed without issues. Pretty sure it lacks the gettext package. That information may be outdated and need to be revised.<div>
<br></div><div>Additionally, it does not mention that you need to check out the entire /trunk directory, and not just the /tools/i18n directory. The makepot.php file makes references back to the WordPress code in the /trunk/src directory, so the entire copy of WordPress needs to be checked out as well. WordPress does not have to be configured or anything, but the code must be available for usage.<span><font color="#888888"><br>
</font></span><div><div><span><font color="#888888"><br>-Otto</font></span><div><br><br><br><br>On Tue, Jun 24, 2014 at 12:45 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
><br>> Note that I took the "make a .POT file by renaming a .PO file" from the previously linked Codex/Handbook reference:<br>
> <a href="https://make.wordpress.org/docs/theme-developer-handbook/theme-functionality/localization/" target="_blank">https://make.wordpress.org/docs/theme-developer-handbook/theme-functionality/localization/</a><br>
><br>> "There are a few other tools that can be used for generating a pot file. You can use locally Poedit. After generating the po file you can rename the file to POT."<br>
><br>><br>> I've never played with the WP developer tools. I'll have to take a look.<br>><br>><br></div></div></div></div></div>
<br>_______________________________________________<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></blockquote></div><br></div></div>