text: Freeciv - Bugs: bug #20524, Impossible terrain for city name [Gna!]
  Freeciv - Bugs: bug #20524, Impossible terrain for city name
  Show feedback againbug #20524: Impossible terrain for city name Submitted by: None
  Submitted on: Sun Feb 17 21:47:42 2013
  Open/Closed: OpenRelease: 2.3.3
  Thu Mar 31 00:27:11 2016, comment #2:JFTR, as a side effect of http://gna.org/patch/?7073 I'm now sure that (Glacier) is an allowed terrain in the default/nationlist.ruleset for natural city names. Frank <dunnoob>
  Mon Dec 28 13:25:15 2015, comment #1:Summary after almost two years: 1) In addition to the existing "city name (river)", "city name (ocean)", etc. feature I'd like to have "city name (gold)" for resources, because (gold) is not the same as only (mountain).
  2) I want a base_igloo or another trick to overrule the "no_city" flag for glacier.
  3) If "city name (ocean)" is interpreted as "city with adjacent ocean", then it's not obvious why "city name (glacier)" should not work, but I haven't tested this after 2.3.x.
  Sun Feb 17 21:47:42 2013, original submission:Testing a data/nations/native.ruleset I tried to determine how terrain conditions actually work, e.g., are special resources such as wheat, fruit, or gems also supported. As a quick plausibility check before the tests I started the cities with...
  cities = "Oops (glacier)", ;test impossible terrain
  [other successfully tested cities without terrain conditions]
  ...and got "Oops" as first city, so that test failed. Therefore I modified the syntax to...
  "Oops" (glacier), ;test impossible terrain
  [other successfully tested cities without terrain conditions] ...and the implicitly started server hanged. After some time, while I was already editing this bug report, the client reported the German version of "sorry, you have to start the server manually". Conclusion, the "name (conditions)" syntax in my first attempt was correct, but condition (glacier) has no effect.