The description of Too Localized:
This question is unlikely to ever help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet.
If a question asking for a dictionary in a particular language could be useful to other visitors, it should stay (assuming it fails no other criteria for a good question).
Questions relevant to all of China should NOT be closed as Too Localized. Joel's written about this before:
"Too localized" should be used for very tiny geographic regions or
vanishingly small periods of time. It is used when a question cannot
possibly be answered because nobody participating in the site is
likely to know the answer, and even if it were answered, nobody else
For me, the canonical "too localized" question would be:
Why is there a green Honda Civic parked out in front of my house?
This is too localized because:
- Who cares?
- Is it even still there? Go check.
- What are the chances that this question could ever be answered in a
way that would benefit anyone else?
- Now is it there?
There seems to be some knee-jerk closing of questions as "too
localized" throughout Stack Exchange simply because they mention a
time span or because they mention a geography. There are many
questions which are limited in time or which are limited in geography,
which, nevertheless, must not be closed as "too localized." For
A question about handling special characters which only appear in
Turkish. Even though, yes, Turkey is a place, and only reflects a
small portion of the developers in the world, the question is still
A question about software companies in
Believe me, there are way more programmers in Montreal than there are
and I've never seen anyone suggest that an OCaml question should be
closed. If the question were about one street in Montreal it might
be too localized to get an answer. (BTW that question would no longer
be considered on topic for Stack Overflow, but "too localized" it is
A question that only applies to a certain build of software. For
example, a developer discussing a bug that only occurs in a certain
version of the .NET framework. Sure, that version is going to be
replaced with another version, which might fix the bug, but we're
still going to answer it!
I am increasingly seeing trigger-happy people who misunderstand the
purpose of this close reason... yesterday someone on Meta.SO voted to
close a question about Stack Overflow Dev Days 2011 on the grounds
that it was "too localized." COME ON!
IMO, Diago's reasoning about service providers in the question you linked is wrong. The UK is not so tiny that a question about it is Too Localized. The real problem with it is that "the best service provider" is subjective and, even with well-defined criteria, it's a shopping recommendation (which is off-topic). Nothing else needs factor into the decision to close such a question.
Your question is valid for a simple reason: It is solving a computer related problem. The problem has nothing to do with what language is in question, it has to do with a computer problem. – Diago♦
That comment is also wrong. Imagine the following question:
I disconnected my desktop from all power sources and now it won't start up. What's wrong?
This is Too Localized because no one else would ask or need the answer to such a ridiculous question. It doesn't matter that it's computer-related.