In reply to Clyde Smith.

It's the same issue: You take a specific template and try to use it for everything. For generic scenarios, it is going to work. For strongly localized scenarios, it is most likely going to fail, if you do not plan for compromises = adaptions.

We've got the very issue with a big client site, where regular i18n methods simply fail, because they were not designed for strong localization, eg. WPML. The client has a strong focus on this, delivering localized prices and specific products for eg. the German-speaking area ("GAS") or Greater China.

Now for a vice-versa example, which would fit better in the case of "meet ups": Webmontag. It Is focused on local, city-based meetups, but fails in the case of NRW (mostly). There, the population is so dense, that big cities go over into each other, eg. Bochum, Essen or Dortmund; all of them are in the metropolis city category, but just a few kilometres apart. In any other part of Germany, you got lots of smaller cities, surrounding a bigger one, and thus the city-vs-big-area concept works quite well.

Aside of that: i18n and l10n go hand in hand. Wikipedia is still your better friend (over a search engine), though: https://en.wikipedia.org/wiki/Internationalization_and_localization
(try searching for "i18n" in Wikipedia; you will be redirected to above article).

cu, w0lf.