<div dir="ltr">The template file should be `theme-slug.pot`. The `theme-slug.mo` is useless and not needed.<div><br></div><div>You can read up here on how to generate the POT files.</div><div><a href="https://make.wordpress.org/docs/theme-developer-handbook/theme-functionality/localization/">https://make.wordpress.org/docs/theme-developer-handbook/theme-functionality/localization/</a><br>

</div><div><br></div><div>@Edward - Interesting that you changed your view. A few months ago you thought that the POT file should not be compulsory.</div><div><br></div><div>PSA - Generate your own mo files when receiving a translation as the mo file could contain different strings to the po file. The po file is human readable but the mo file is not.</div>

</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 24 June 2014 15:20, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</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">I've never included a .POT file; I've only ever included POMO files?</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 24, 2014 at 8:06 AM, Justin Tadlock <span dir="ltr"><<a href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.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">I think it would be preferable to have a POT file.  It should be named `theme-name.pot`.</div><div class="gmail_extra">


<br><br><div class="gmail_quote"><div>On Tue, Jun 24, 2014 at 7:59 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
</div><div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">IIRC, translation-ready requires proper implementation of translation strings, proper theme declaration of translation, and inclusion of a .po file.</div>



<div><div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Jun 24, 2014 at 7:54 AM, Jose Castaneda <span dir="ltr"><<a href="mailto:jomcastaneda@gmail.com" target="_blank">jomcastaneda@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">I was wondering that the other day too. I feel that is should have either a .po or .pot file</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 24, 2014 at 5:33 AM, esmi at quirm dot net <span dir="ltr"><<a href="mailto:esmi@quirm.net" target="_blank">esmi@quirm.net</a>></span> wrote:<br>





<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If a theme is tagged as "translation-ready", shouldn't it include a default .po file? Just been dealing with a support request regarding <<a href="https://wordpress.org/themes/serene/" target="_blank">https://wordpress.org/themes/<u></u>serene/</a>> and languages. The theme is tagged as "translation-ready" and functions.php appears to point to a /languages folder but there is no such folder in the theme.<br>






<br>
What would the requirements actually be in such a case?<br>
<br>
Mel<span><font color="#888888"><br>
-- <br>
<a href="http://quirm.net" target="_blank">http://quirm.net</a><br>
<a href="http://blackwidows.co.uk" target="_blank">http://blackwidows.co.uk</a><br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</font></span></blockquote></div><br></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></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></div></div><br></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></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></div>