Hum, using the #emacs #gopher client seems to work for UTF-8 gopher sites like my gopher wiki. But not for lynx. Hrm.
@ckeen Actually my gopher server double encoded the UTF-8 upon printing. Today I just removed some encoding and decoding statements on the server side and suddenly gopher.el started to work correctly, no change required. But for Lynx, I'm not sure. Perhaps Lynx expects URL-encoded selectors? Right now I have no time to investigate, sadly.
Not sure if this helps, but the Lynx documentation on Gopher URL handlong says:
"Any reserved characters in the selector should be hex escaped (%hh), including slashes, although hex escaping of slashes is not required by Lynx in gopher URLs." (from http://lynx.invisible-island.net/lynx2.8.8/lynx_help/lynx_url_support.html)