[wp-hackers] Internationalizing Plugins and Themes Solutions

Jacob Santos wordpress at santosj.name
Thu Mar 6 18:15:56 GMT 2008

Dan Coulter wrote:
> On Thu, Mar 6, 2008 at 11:05 AM, Jacob Santos <wordpress at santosj.name>
> wrote:
>> This has already been done and rejected as unacceptable, both as
>> practice/security and for convenience.
> Fair enough.  It just seemed like a relatively simple solution for the
> plugin developer and wouldn't require the sort of over-engineering and
> inconvenience to the plugin author that some of the other solutions seem to.

It is frustrating and I wish I never got involved with the ticket, "Hey, 
this ticket doesn't seem like it'll be hard, I can knock this out 
quickly." (Actual thought I had with the ticket in question.) Basically, 
I had no problem with what you described and what the patch did, however 
the arguments made against it are logical.

It will be worth it. There have been many times when I've been 
frustrated with the perceived lack of interest or arguments against 
something only to have something really awesome come out of it. I have 
faith that eventually "The Best" solution will be made that plugin and 
theme authors, as well as the core team will be happy with. Whether that 
is part of the three solutions or some other better solution, which has 
not been mentioned before.

There is a great amount of material for what solutions and counter 
arguments to many of them. Several solutions had almost all negative 
responses to them.Unless there is a patch or code that can be tested, 
then really this problem may never be resolved.

If this is something that many people feel passionate about and needs a 
solution, then a solution needs to be written. All that is needed is a 
patch which provides a solution and you will have more than enough 
people to test it. I'll be a tester and I believe others will also.

I invested enough time with the ticket, that I would love to discuss 
solutions which haven't been made before. However, I really hate 
conversations which go in loops. Already been there, done that, was a 
total waste of time, because the ground work had already been made and 
was just remade needlessly. I'd hate for another person to waste time in 
an debate/conversation that had already been hashed out before.

(Although, who is to say that this hasn't already been hashed out before 
this year, could have been discussed during the initial implementation 
of the plugin system leading up to now.)

What I've found, is that the best way to end a infinitely reoccurring 
conversational loop with similar solutions/point being made each 
iteration, is to just provide a solution and break out of it.

Please note, that the usage of "you" is not directed personally at the 
author who I'm replying to, but can be anyone willing to put in the legwork.


Jacob Santos

http://www.santosj.name - blog
http://funcdoc.wordpress.com - WordPress Documentation Blog/Guide Licensed under GPLv2

Also known as darkdragon and santosj on WP trac.

More information about the wp-hackers mailing list