[theme-reviewers] Proposed WordPress 3.3 Theme Review Guidelines Revisions

[Tyler Cunningham]

Otto, 

Those are good points, I never thought about the translation functions being parsed by non-PHP applications/programs. 

I personally have never used a variable in a translation function but from the perspective of someone who utilizes variables a lot it struck me as odd to deny their use. Now I understand though, so thank you for the explanation.  

Regards,

Tyler Cunningham  |  Founder, COO - CyberChimps LLC (http://CyberChimps.com/)

@tylerbcunning (http://twitter.com/tylerbcunning)
http://gplus.to/tylercunningham
http://linkedin.com/in/tylerbcunningham 
tyler at cyberchimps.com (mailto:tyler at cyberchimps.com)


On Thursday, November 10, 2011 at 1:21 PM, Otto wrote:

> On Thu, Nov 10, 2011 at 3:14 PM, Tyler Cunningham
> <seizedpropaganda at gmail.com (mailto:seizedpropaganda at gmail.com)> wrote:
> > I still think this is a bit much to be a REQUIRED. I see Mark's point and
> > I'm sure he's right when it comes to automation, but shouldn't the decision
> > ultimately be left up to the theme developer?
> > I think this would be a much better RECOMMENDED, does anyone else agree?
> > 
> 
> 
> No. Doing it with variables is just plain wrong, on all levels. It's
> not really a matter of choice, it's a matter of standards. The strings
> need to be capable of being parsed by other code. This is
> code-parsing-other-code here, and that's the basis of all the gettext
> translation mechanism.
> 
> In the plugins area, for example, there's a handy button on the
> backend for plugin developers to generate the POT files for your
> plugin automatically. If you use a variable, then they don't work.
> Why? Because those programs don't *run* your code, they scan it for __
> and _e and similar, then generate the necessary translation files. All
> translation tools work in this manner.
> 
> So put simply, the use of variables for the translation namespace
> fundamentally *doesn't work* with any existing translation tools. The
> code should be machine parse-able, and it is, if you don't rely on any
> variables in your translatable strings.
> 
> -Otto
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org (mailto: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/20111110/496f4e2a/attachment.htm>