All,<div><br></div><div>Please ensure that discussion specific to the proposed Guidelines revisions takes place in the comments to the post on the Make site - mainly, to help ensure posterity. (Not everyone follows this list.)</div>
<div><br></div><div>Otto's back-and-forth explanation is exactly the kind of thing that will be beneficial to everyone in the future, should similar questions arise regarding this particular requirement.</div><div><br>
</div><div>Chip<br><br><div class="gmail_quote">On Thu, Nov 10, 2011 at 3:34 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">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;">
Good. Now, _that said_, not all translation programs care about<br>
namespaces there. So some tools do indeed work with variables there,<br>
simply because they're ignoring the namespace anyway.<br>
<br>
However, we do care about namespaces. Especially if some kind of<br>
mechanism was going to be created to make translations much easier all<br>
around...<br>
<br>
-Otto<br>
<br>
<br>
<br>
On Thu, Nov 10, 2011 at 3:31 PM, Tyler Cunningham<br>
<div class="HOEnZb"><div class="h5"><<a href="mailto:seizedpropaganda@gmail.com">seizedpropaganda@gmail.com</a>> wrote:<br>
> Otto,<br>
> Those are good points, I never thought about the translation functions being<br>
> parsed by non-PHP applications/programs.<br>
> I personally have never used a variable in a translation function but from<br>
> the perspective of someone who utilizes variables a lot it struck me as odd<br>
> to deny their use. Now I understand though, so thank you for the<br>
> explanation.<br>
> Regards,<br>
><br>
> Tyler Cunningham | Founder, COO - CyberChimps LLC<br>
> @tylerbcunning<br>
> <a href="http://gplus.to/tylercunningham" target="_blank">http://gplus.to/tylercunningham</a><br>
> <a href="http://linkedin.com/in/tylerbcunningham" target="_blank">http://linkedin.com/in/tylerbcunningham</a><br>
> <a href="mailto:tyler@cyberchimps.com">tyler@cyberchimps.com</a><br>
><br>
> On Thursday, November 10, 2011 at 1:21 PM, Otto wrote:<br>
><br>
> On Thu, Nov 10, 2011 at 3:14 PM, Tyler Cunningham<br>
> <<a href="mailto:seizedpropaganda@gmail.com">seizedpropaganda@gmail.com</a>> wrote:<br>
><br>
> I still think this is a bit much to be a REQUIRED. I see Mark's point and<br>
> I'm sure he's right when it comes to automation, but shouldn't the decision<br>
> ultimately be left up to the theme developer?<br>
> I think this would be a much better RECOMMENDED, does anyone else agree?<br>
><br>
> No. Doing it with variables is just plain wrong, on all levels. It's<br>
> not really a matter of choice, it's a matter of standards. The strings<br>
> need to be capable of being parsed by other code. This is<br>
> code-parsing-other-code here, and that's the basis of all the gettext<br>
> translation mechanism.<br>
> In the plugins area, for example, there's a handy button on the<br>
> backend for plugin developers to generate the POT files for your<br>
> plugin automatically. If you use a variable, then they don't work.<br>
> Why? Because those programs don't *run* your code, they scan it for __<br>
> and _e and similar, then generate the necessary translation files. All<br>
> translation tools work in this manner.<br>
> So put simply, the use of variables for the translation namespace<br>
> fundamentally *doesn't work* with any existing translation tools. The<br>
> code should be machine parse-able, and it is, if you don't rely on any<br>
> variables in your translatable strings.<br>
> -Otto<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>
> _______________________________________________<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>
><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>
</div></div></blockquote></div><br></div>