We’re not going to introduce more compound strings with the redesign.

I’m saying the designers want to have that button say a certain thing and with our current dynamic/static code we can’t have that. I’m reconsidering what we call “dynamic” since it essentially doesn’t change (and, therefore, isn’t really dynamic). The proposal above would introduce new (and separate) static strings for each place the category name is used.

This probably won’t happen in time for the redesign so I expect we’ll change the button label to something non-specific like “See All Add-ons” (to the chagrin of the designers, I’m sure).

Compound strings / dynamic strings suck, because they cause havoc (i.e. ugly hacks) with languages that require inflecting nouns etc. to the correct declension.

Using dynamic strings would be ok if the dynamic (%s) part is only used in a single sense and *not* reused, and when the strings are also clearly marked as being the dynamic part in some specific (again, single) structure. I understand this could seem excessive for most (all?) romance language locales, but I believe the rest of us would benefit.