[theme-reviewers] Translation-ready themes
Chip Bennett
chip at chipbennett.net
Tue Jun 24 20:17:04 UTC 2014
I don't know if it's explicit in the Guidelines; that's just how we've
enforced it thus far.
(The usual caveat: it is simply impractical to list every detail and nuance
of every Guideline; if we tried to do so, they would be impossibly
detailed, and impossible to follow, implement, or review against.)
On Tue, Jun 24, 2014 at 3:06 PM, Ulrich Pogson <grapplerulrich at gmail.com>
wrote:
> @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.
>
> @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.
>
> @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 https://github.com/grappler/i18n
>
> @Edward -
> https://make.wordpress.org/docs/plugin-developer-handbook/15-internationalization/localization/
>
>
> On 24 June 2014 20:30, Otto <otto at ottodestruct.com> wrote:
>
>> On Tue, Jun 24, 2014 at 1:21 PM, Edward Caissie <edward.caissie at gmail.com
>> > wrote:
>>
>>> @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*)
>>>
>>
>>
>> Yes. Same command, but instead of using "wp-theme", use "wp-plugin".
>>
>> More info at the bottom of this post:
>> http://ottopress.com/2013/language-packs-101-prepwork/
>>
>>
>>
>> @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? :)
>>
>> -Otto
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20140624/f730ee17/attachment.html>
More information about the theme-reviewers
mailing list