<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div>Hi </div><div>I added a summary of fixes to the ticket</div><div><br></div><a href="http://themes.trac.wordpress.org/ticket/5447">http://themes.trac.wordpress.org/ticket/5447</a><div><br></div><div>can it be approved?</div><div>thanks<br><div id="1"><br>---- On Thu, 06 Oct 2011 13:04:38 -0300 <b><<a href='mailto:theme-reviewers-request@lists.wordpress.org' target='_blank'>theme-reviewers-request@lists.wordpress.org</a>></b> wrote ---- <br></div><br><blockquote style="border-left: 1px solid #0000FF; padding-left: 6px;">Send theme-reviewers mailing list submissions to <br> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">theme-reviewers@lists.wordpress.org</a> <br> <br>To subscribe or unsubscribe via the World Wide Web, visit <br> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a> <br>or, via email, send a message with subject or body 'help' to <br> <a href="mailto:theme-reviewers-request@lists.wordpress.org" target="_blank" mailid="theme-reviewers-request%40lists.wordpress.org" subj="">theme-reviewers-request@lists.wordpress.org</a> <br> <br>You can reach the person managing the list at <br> <a href="mailto:theme-reviewers-owner@lists.wordpress.org" target="_blank" mailid="theme-reviewers-owner%40lists.wordpress.org" subj="">theme-reviewers-owner@lists.wordpress.org</a> <br> <br>When replying, please edit your Subject line so it is more specific <br>than "Re: Contents of theme-reviewers digest..." <br> <br> <br>Today's Topics: <br> <br> 1. Re: Localized strings and dynamic text domain. (Chip Bennett) <br> 2. Re: Localized strings and dynamic text domain. (Edward Caissie) <br> <br> <br>---------------------------------------------------------------------- <br> <br>Message: 1 <br>Date: Thu, 6 Oct 2011 10:38:07 -0500 <br>From: Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank" mailid="chip%40chipbennett.net" subj="">chip@chipbennett.net</a>> <br>Subject: Re: [theme-reviewers] Localized strings and dynamic text <br> domain. <br>To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">theme-reviewers@lists.wordpress.org</a> <br>Message-ID: <br> <CAPdLKqe0jUHr1JdG9v0z<a href="mailto:pNKnU4ini-apBTBOiVMiHginto1dvA@mail.gmail.com" target="_blank" mailid="pNKnU4ini-apBTBOiVMiHginto1dvA%40mail.gmail.com" subj="">pNKnU4ini-apBTBOiVMiHginto1dvA@mail.gmail.com</a>> <br>Content-Type: text/plain; charset="iso-8859-1" <br> <br>I am in favor of retaining the requirement that Themes use theme-slug as the <br>textdomain (which is currently the requirement). It is one of the only ways <br>of ensuring a completely unique namespace. <br> <br>Chip <br> <br>On Thu, Oct 6, 2011 at 10:24 AM, Edward Caissie <<a href="mailto:edward.caissie@gmail.com" target="_blank" mailid="edward.caissie%40gmail.com" subj="">edward.caissie@gmail.com</a>>wrote: <br> <br>> So we put the blame squarely on `gettext` and make it a "REQUIRED" item the <br>> textdomain must be a hard-coded string, which we have already recommended it <br>> be the theme-slug. Seems simple enough to me. <br>> <br>> The discussion should continue with whether the theme-slug be the best <br>> practice (required?) string or if another relevant string can be used in its <br>> place ... personally I would side with the textdomain === theme-slug. <br>> Reason being, if the code/application in question advances enough then the <br>> "clever" idea of using a variable/constant might work correctly and the <br>> theme-slug (or plugin-slug as the case may be) is easy enough to grab from <br>> existing data. <br>> <br>> <br>> Cais. <br>> <br>> <br>> <br>> On Thu, Oct 6, 2011 at 8:43 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank" mailid="chip%40chipbennett.net" subj="">chip@chipbennett.net</a>> wrote: <br>> <br>>> No problem; I'll draft something up, and add it to the discussion list for <br>>> the proposed 3.3 guidelines revisions! <br>>> <br>>> Chip <br>>> <br>>> <br>>> On Thu, Oct 6, 2011 at 7:41 AM, Dion Hulse (dd32) <<a href="mailto:wordpress@dd32.id.au" target="_blank" mailid="wordpress%40dd32.id.au" subj="">wordpress@dd32.id.au</a>>wrote: <br>>> <br>>>> Yep! the way that WordPress loads the translations is one set of strings <br>>>> per text domain, if the text domains don't match up, translated strings <br>>>> don't get used, use multiple text domains, and causes problems with multiple <br>>>> translation files.. <br>>>> So when you start to load a automatically generated translation file, <br>>>> suddenly if the author hasn't followed best practice, it might just not work <br>>>> at all. <br>>>> <br>>>> On 6 October 2011 23:37, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank" mailid="chip%40chipbennett.net" subj="">chip@chipbennett.net</a>> wrote: <br>>>> <br>>>>> Absolutely, and I appreciate the clarification. :) <br>>>>> <br>>>>> So, is this an accurate summary: POEdit (etc.) won't care what the <br>>>>> textdomain string is, for a given Theme/Plugin, provided that the string is <br>>>>> consistent throughout the Theme/Plugin. But, *best practice* is to use an <br>>>>> *actual string*, in order to play nicely in an environment where several <br>>>>> textdomains are being declared (such as within WordPress)? <br>>>>> <br>>>>> Chip <br>>>>> <br>>>>> <br>>>>> On Thu, Oct 6, 2011 at 7:32 AM, Dion Hulse (dd32) <<a href="mailto:wordpress@dd32.id.au" target="_blank" mailid="wordpress%40dd32.id.au" subj="">wordpress@dd32.id.au</a> <br>>>>> > wrote: <br>>>>> <br>>>>>> Always use a string.. Don't use a variable, Don't use a Constant. <br>>>>>> <br>>>>>> Gettext applications look at the php files as an onlooker, It can't <br>>>>>> tell what the contents of $lang is, it can't tell the contents of <br>>>>>> CONSTANT_MY_LANG, It just knows the first param is a string, and the second <br>>>>>> is the text domain for it. It's basically the same as running a regex over <br>>>>>> an unknown string, or scanning through a French document looking for the <br>>>>>> word which comes after XYZ.. <br>>>>>> <br>>>>>> When you're generating a .pot file from a single theme/plugin, you can <br>>>>>> specify the text domain you want the resulting file to use.. when you're <br>>>>>> automating translations for thousands of items (like WordPress.org will do <br>>>>>> one day..) then you can't guess.. the authors need to be specific for <br>>>>>> maximum compatibility! <br>>>>>> <br>>>>>> Does that help at all Chip? :) <br>>>>>> <br>>>>>> <br>>>>>> On 6 October 2011 23:23, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank" mailid="chip%40chipbennett.net" subj="">chip@chipbennett.net</a>> wrote: <br>>>>>> <br>>>>>>> Thanks for passing this along, Mike! <br>>>>>>> <br>>>>>>> There seems to be some discussion/disagreement in the comments and via <br>>>>>>> Twitter. What's the consensus? <br>>>>>>> <br>>>>>>> Chip <br>>>>>>> <br>>>>>>> <br>>>>>>> On Thu, Oct 6, 2011 at 1:24 AM, Michael Fields <<a href="mailto:michael@mfields.org" target="_blank" mailid="michael%40mfields.org" subj="">michael@mfields.org</a>>wrote: <br>>>>>>> <br>>>>>>>> Hello! <br>>>>>>>> <br>>>>>>>> This just came through my Twitter feed: <br>>>>>>>> <br>>>>>>>> <a href="http://markjaquith.wordpress.com/2011/10/06/translating-wordpress-plugins-and-themes-dont-get-clever/" target="_blank">http://markjaquith.wordpress.com/2011/10/06/translating-wordpress-plugins-and-themes-dont-get-clever/</a> <br>>>>>>>> <br>>>>>>>> Thought it might make a pretty good addition to the requirements. <br>>>>>>>> It also might be a pretty easy check to work into the Theme Check <br>>>>>>>> plugin. <br>>>>>>>> <br>>>>>>>> I'm guilty of this myself in plugins and think that's it's really <br>>>>>>>> great to have an explanation of why this is wrong :) <br>>>>>>>> <br>>>>>>>> Just wanted to pass it along! <br>>>>>>>> <br>>>>>>>> - Mike <br>>>>>>>> _______________________________________________ <br>>>>>>>> theme-reviewers mailing list <br>>>>>>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>>>>>> <br>>>>>>> <br>>>>>>> _______________________________________________ <br>>>>>>> theme-reviewers mailing list <br>>>>>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>>>>>> <br>>>>>> <br>>>>>> _______________________________________________ <br>>>>>> theme-reviewers mailing list <br>>>>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>>>>> <br>>>>> <br>>>>> _______________________________________________ <br>>>>> theme-reviewers mailing list <br>>>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>>>> <br>>>> <br>>>> _______________________________________________ <br>>>> theme-reviewers mailing list <br>>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>>> <br>>> <br>>> _______________________________________________ <br>>> theme-reviewers mailing list <br>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>> <br>> <br>> _______________________________________________ <br>> theme-reviewers mailing list <br>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>> <br>-------------- next part -------------- <br>An HTML attachment was scrubbed... <br>URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20111006/7eebedff/attachment-0001.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20111006/7eebedff/attachment-0001.htm</a>> <br> <br>------------------------------ <br> <br>Message: 2 <br>Date: Thu, 6 Oct 2011 12:04:14 -0400 <br>From: Edward Caissie <<a href="mailto:edward.caissie@gmail.com" target="_blank" mailid="edward.caissie%40gmail.com" subj="">edward.caissie@gmail.com</a>> <br>Subject: Re: [theme-reviewers] Localized strings and dynamic text <br> domain. <br>To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">theme-reviewers@lists.wordpress.org</a> <br>Message-ID: <br> <CAE5CyMhn3y5x_Lkh92tO<a href="mailto:UXux9yHwU1armSegVPcJ885HuELHKg@mail.gmail.com" target="_blank" mailid="UXux9yHwU1armSegVPcJ885HuELHKg%40mail.gmail.com" subj="">UXux9yHwU1armSegVPcJ885HuELHKg@mail.gmail.com</a>> <br>Content-Type: text/plain; charset="iso-8859-1" <br> <br>Ah, then we should also clarify the theme-slug should be "correctly" <br>formatted. All lower-case, spaces replaced by hyphens, etc. I actually have <br>it on one of my theme's TO-DO list to correct that oversight. <br> <br> <br>Cais. <br> <br> <br>On Thu, Oct 6, 2011 at 11:38 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank" mailid="chip%40chipbennett.net" subj="">chip@chipbennett.net</a>> wrote: <br> <br>> I am in favor of retaining the requirement that Themes use theme-slug as <br>> the textdomain (which is currently the requirement). It is one of the only <br>> ways of ensuring a completely unique namespace. <br>> <br>> Chip <br>> <br>> <br>> On Thu, Oct 6, 2011 at 10:24 AM, Edward Caissie <<a href="mailto:edward.caissie@gmail.com" target="_blank" mailid="edward.caissie%40gmail.com" subj="">edward.caissie@gmail.com</a>>wrote: <br>> <br>>> So we put the blame squarely on `gettext` and make it a "REQUIRED" item <br>>> the textdomain must be a hard-coded string, which we have already <br>>> recommended it be the theme-slug. Seems simple enough to me. <br>>> <br>>> The discussion should continue with whether the theme-slug be the best <br>>> practice (required?) string or if another relevant string can be used in its <br>>> place ... personally I would side with the textdomain === theme-slug. <br>>> Reason being, if the code/application in question advances enough then the <br>>> "clever" idea of using a variable/constant might work correctly and the <br>>> theme-slug (or plugin-slug as the case may be) is easy enough to grab from <br>>> existing data. <br>>> <br>>> <br>>> Cais. <br>>> <br>>> <br>>> <br>>> On Thu, Oct 6, 2011 at 8:43 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank" mailid="chip%40chipbennett.net" subj="">chip@chipbennett.net</a>>wrote: <br>>> <br>>>> No problem; I'll draft something up, and add it to the discussion list <br>>>> for the proposed 3.3 guidelines revisions! <br>>>> <br>>>> Chip <br>>>> <br>>>> <br>>>> On Thu, Oct 6, 2011 at 7:41 AM, Dion Hulse (dd32) <<a href="mailto:wordpress@dd32.id.au" target="_blank" mailid="wordpress%40dd32.id.au" subj="">wordpress@dd32.id.au</a>>wrote: <br>>>> <br>>>>> Yep! the way that WordPress loads the translations is one set of strings <br>>>>> per text domain, if the text domains don't match up, translated strings <br>>>>> don't get used, use multiple text domains, and causes problems with multiple <br>>>>> translation files.. <br>>>>> So when you start to load a automatically generated translation file, <br>>>>> suddenly if the author hasn't followed best practice, it might just not work <br>>>>> at all. <br>>>>> <br>>>>> On 6 October 2011 23:37, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank" mailid="chip%40chipbennett.net" subj="">chip@chipbennett.net</a>> wrote: <br>>>>> <br>>>>>> Absolutely, and I appreciate the clarification. :) <br>>>>>> <br>>>>>> So, is this an accurate summary: POEdit (etc.) won't care what the <br>>>>>> textdomain string is, for a given Theme/Plugin, provided that the string is <br>>>>>> consistent throughout the Theme/Plugin. But, *best practice* is to use an <br>>>>>> *actual string*, in order to play nicely in an environment where several <br>>>>>> textdomains are being declared (such as within WordPress)? <br>>>>>> <br>>>>>> Chip <br>>>>>> <br>>>>>> <br>>>>>> On Thu, Oct 6, 2011 at 7:32 AM, Dion Hulse (dd32) < <br>>>>>> <a href="mailto:wordpress@dd32.id.au" target="_blank" mailid="wordpress%40dd32.id.au" subj="">wordpress@dd32.id.au</a>> wrote: <br>>>>>> <br>>>>>>> Always use a string.. Don't use a variable, Don't use a Constant. <br>>>>>>> <br>>>>>>> Gettext applications look at the php files as an onlooker, It can't <br>>>>>>> tell what the contents of $lang is, it can't tell the contents of <br>>>>>>> CONSTANT_MY_LANG, It just knows the first param is a string, and the second <br>>>>>>> is the text domain for it. It's basically the same as running a regex over <br>>>>>>> an unknown string, or scanning through a French document looking for the <br>>>>>>> word which comes after XYZ.. <br>>>>>>> <br>>>>>>> When you're generating a .pot file from a single theme/plugin, you can <br>>>>>>> specify the text domain you want the resulting file to use.. when you're <br>>>>>>> automating translations for thousands of items (like WordPress.org will do <br>>>>>>> one day..) then you can't guess.. the authors need to be specific for <br>>>>>>> maximum compatibility! <br>>>>>>> <br>>>>>>> Does that help at all Chip? :) <br>>>>>>> <br>>>>>>> <br>>>>>>> On 6 October 2011 23:23, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank" mailid="chip%40chipbennett.net" subj="">chip@chipbennett.net</a>> wrote: <br>>>>>>> <br>>>>>>>> Thanks for passing this along, Mike! <br>>>>>>>> <br>>>>>>>> There seems to be some discussion/disagreement in the comments and <br>>>>>>>> via Twitter. What's the consensus? <br>>>>>>>> <br>>>>>>>> Chip <br>>>>>>>> <br>>>>>>>> <br>>>>>>>> On Thu, Oct 6, 2011 at 1:24 AM, Michael Fields <<a href="mailto:michael@mfields.org" target="_blank" mailid="michael%40mfields.org" subj="">michael@mfields.org</a>>wrote: <br>>>>>>>> <br>>>>>>>>> Hello! <br>>>>>>>>> <br>>>>>>>>> This just came through my Twitter feed: <br>>>>>>>>> <br>>>>>>>>> <a href="http://markjaquith.wordpress.com/2011/10/06/translating-wordpress-plugins-and-themes-dont-get-clever/" target="_blank">http://markjaquith.wordpress.com/2011/10/06/translating-wordpress-plugins-and-themes-dont-get-clever/</a> <br>>>>>>>>> <br>>>>>>>>> Thought it might make a pretty good addition to the requirements. <br>>>>>>>>> It also might be a pretty easy check to work into the Theme Check <br>>>>>>>>> plugin. <br>>>>>>>>> <br>>>>>>>>> I'm guilty of this myself in plugins and think that's it's really <br>>>>>>>>> great to have an explanation of why this is wrong :) <br>>>>>>>>> <br>>>>>>>>> Just wanted to pass it along! <br>>>>>>>>> <br>>>>>>>>> - Mike <br>>>>>>>>> _______________________________________________ <br>>>>>>>>> theme-reviewers mailing list <br>>>>>>>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>>>>>>> <br>>>>>>>> <br>>>>>>>> _______________________________________________ <br>>>>>>>> theme-reviewers mailing list <br>>>>>>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>>>>>>> <br>>>>>>> <br>>>>>>> _______________________________________________ <br>>>>>>> theme-reviewers mailing list <br>>>>>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>>>>>> <br>>>>>> <br>>>>>> _______________________________________________ <br>>>>>> theme-reviewers mailing list <br>>>>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>>>>> <br>>>>> <br>>>>> _______________________________________________ <br>>>>> theme-reviewers mailing list <br>>>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>>>> <br>>>> <br>>>> _______________________________________________ <br>>>> theme-reviewers mailing list <br>>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>>> <br>>> <br>>> _______________________________________________ <br>>> theme-reviewers mailing list <br>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>>> <br>> <br>> _______________________________________________ <br>> theme-reviewers mailing list <br>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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>> <br>-------------- next part -------------- <br>An HTML attachment was scrubbed... <br>URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20111006/ad03f1f5/attachment.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20111006/ad03f1f5/attachment.htm</a>> <br> <br>------------------------------ <br> <br>_______________________________________________ <br>theme-reviewers mailing list <br><a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" mailid="theme-reviewers%40lists.wordpress.org" subj="">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> <br>End of theme-reviewers Digest, Vol 17, Issue 16 <br>*********************************************** <br></blockquote><br></div></body></html>