I disagree. Not all pig questions involve the language.
For example, questions about downloading, building, installing, configuring, system requirements, API, unit testing, etc. do not have anything to do with the language layer, and therefore should only be tagged pig. This is probably why the tag wiki says nothing about piglatin.
You could argue that the ...
jQuery should be used everywhere especially when creating native applications on mobile devices.
Yes, it does. When I'm looking for something and I know there is a tag for it, I want to simply type [something] in search window and I don't expect to miss some questions on that topic due to them being too old to be properly tagged.
From the tag synonym page (emphasis mine):
If you know of common, alternate spellings or phrasings for this tag, add them here so we can automatically correct them in the future. For example, suggest “bike” as a synonym for bicycle, or “sock” for socks.
This is literally one of the reasons tag synonyms exist. We should most definitely synonymize table to ...
The request was closed because it was made obsolete soon after.
You just can't close something as obsolete (and no longer needing any attention) without also saying it's off topic. Even if it was on topic.
The question then becomes what use is a retag/merge/burninate request that was not debated and does not follow through to live tags as initially ...
I would suggest jquery-datatables for the jQuery plugin. It fits the convention that seems to be used for jQuery plugin tags such as: jquery-isotope, jquery-masonry, jquery-cycle, etc.
The -plugin suffix only really gets used in a couple of instances:
struts2-jquery-plugin (which apparently coexists with struts2-jquery and should probably be made a synonym)...
No, don't merge a generic tag (7666 questions have it) with a specific one (608).
The generic tag is used for all kinds of vectors currently, so retagging it would cause a ton of trouble, as not all questions currently tagged vector are about stdvector.
Unless you're planning on manually going through almost eight thousand questions to find out which of ...
excel-vba refers to VBA when specifically applied to Excel. vba is more generic and specifically reference to VBA in any application (Outlook, Word, Access)
excel is a different tag is while it could refer to Excel and VBA, it could also refer to Excel on its own. While asking about specific formulas in excel, there are some questions that have been ...
The language name is Go, not golang. It's fine to use golang when a context makes it very difficult for Go to be used properly, but StackOverflow is not such a case:
In your commendable quest for order in the tags related to Apple technologies you seem to forget that they also carry some very useful meta information.
Assuming a run-of-the-mill coding question regarding functionality from the standard framework (Cocoa/Cocoa Touch), a rough taxonomy of tags looks like this, in my personal and one-eyed analysis:
I think that given the ambiguous name factor-lang or factor-language would be acceptable.
A brief search shows similar examples for specific languages, although even the suffixes used are not consistent: julia-lang, slim-lang, q-lang, golang, cg-language, curl-language, nice-language, false-language
I also think that r-factor is more appropiate for the R ...
Looks like a synonym for shopping-cart. cart is commonly used in the US, whereas basket in the UK.
As a reference: "Shopping basket" or "shopping cart".
That being said I'd treat basket as identical to shopping-cart
As animuson mentioned, merges and synonyms are different.
Take a look at the tag synonym list.
Take a tag synonym that wasn't approved by a moderator, such as:
css -> max-width
This is a tag synonym. If you try to ask a question with the max-width tag, you will get the following tag suggestion:
You can still label max-width, but it ...
This answer is to keep track of how many of these still need to be closed / looked at.
@any3k+user keep in mind that you can filter on these tags with the close review queue if you wish to get a few reviews in (if they already have close votes / flags).
design-tool - Gone
design-tools - Gone
development-tools - Gone
collaboration-tools - Gone
Instead of burninating it I suggest asking a moderator to merge the how-to tag into the support tag with the latter being the master and leaving the former as a synonym to it.
If there are any questions for which a tag of support is unsuitable then re-tagging them prior to the merge would be appropriate.
iPhone and iOS should be merged under ios-provisioning, since (to my information, I only learned of this just now) these refer to the exact same technical meaning of "provisioning" for iOS developers, and "iPhone" is inaccurate, as this process is device independent.
provisioning should not be merged as that includes many, many questions under various ...
No, I don't think this is a good idea. The terms "key value observing" and "key value coding" are well-understood, and people know how to tag things with those as appropriate. I never refer to these concepts using the specific protocol names, so I see no reason to rename the tags to them.
I think this would cause more confusion than the way things are now.
It really would seem to me that both tags could be cleaned up and burninated.
A scripting tag seems about a useful as a Programming tag. A cleanup effort would involve determining what language the script in question is referring to and replace the script/scripting tag with that language's tag.
Retagging is not wrong or abusive to the site. The user is contributing value to the site.
If you can't keep up then just ignore it. No one said you have to do everything yourself.
Rejecting them is actually a significant problem since you are destroying his efforts to improve the site. Why didn't you just edit whatever other obvious aspects that needed to ...
I manually burninated reformating (while fixing the other issues in the posts, of course).
I suggest going the other way though, formatting ← format. Tags are mainly nouns; most of our tags are like that (for example, writing (ugh that's also a terrible tag), debugging, sorting, parsing, etc).