Saiga

Tags is powerful, but need to be per-defined. for example content can be tags by many tags like "content" or "ip.content" or "ccs" . so if the author1 tag it by "content" and author2 tag it using "ccs" and so .........., a lot of drama will happened later with unlimited tags.

Tags are perfect only if it is per-defined in my opinion.

Yeah I tagged my gallery hooks with "ip.gallery" and found out later that other people have been tagging with "gallery"...

If I need to see a doctor, what makes the most sense to me if I don't know the name of a doctor and I am in the lobby of a medical building? Not a list of latin names or Borsky, Horowitz, and Golab.  This makes the most sense:

 

Brain Doctor

Eye Doctor

Skin Doctor

Finger Doctor

Bone Doctor

Guy's Junk Doctor

Girl's Junk Doctor

Foot Doctor

Hair Doctor

Artificial Limb Doctor

and so on...

If you think about it...this is exactly how the Marketplace is set up now.

Oh. Yeah, I realized later what I said was kind of irrelevant..

%s is actually a PHP thing, not something we control. We just do a simple sprintf() on the replacement, which is why %s is used (as we're typically using a string for the replacement).
 
http://www.php.net/m...ion.sprintf.php

Ryan, the suggestion is to use sprintf in more places. So in the IP.Downloads template instead of doing "{$numberOfDownloads} {$this->lang->words['downloads']}" it would be "{parse expression="sprintf($this->lang->words['downloads'], $numberOfDownloads)"}" where in the first one the langbit is "Downloads" and in the second one it's "%s Downloads". That way the bit can be translated to "Downloads: %s" without the need for template edits. Although I suppose in this example it would be %d.

Kind of hand in hand with this IPS should start using placeholders. So %1$s and %2$s instead of %s so that any issues with languages which don't follow the same subject verb order as English can be completely avoided. Though I suppose the person editing the language bits can do it themselves...