Server Side Tips
Posted: Thu Sep 05, 2024 1:14 pm
Copied from my gophersite, some tips for writing mapfiles which every (as far as I've tried) client can successfully read:
* Some clients get confused about empty lines. If you want
an empty line, make it a blank "i" line.
* On that topic, some clients are picky about "i" lines,
make sure that you have *3* tabs at the end so that
all the "fields" are correctly there.
* On that topic even more: some clients ignore "i" lines
completely, don't make your content dependent on it.
Especially try to make sure that there's at least one
link per screenful of text because this breaks some
weird gopher clients.
* There's no spacing at all between the type and the
pretty name. The correct way to start a textfile
is just "0this is my name"
* Make sure your editor isn't expanding tabs. You need
real tabs. As in ^I.
* Some clients get confused about empty lines. If you want
an empty line, make it a blank "i" line.
* On that topic, some clients are picky about "i" lines,
make sure that you have *3* tabs at the end so that
all the "fields" are correctly there.
* On that topic even more: some clients ignore "i" lines
completely, don't make your content dependent on it.
Especially try to make sure that there's at least one
link per screenful of text because this breaks some
weird gopher clients.
* There's no spacing at all between the type and the
pretty name. The correct way to start a textfile
is just "0this is my name"
* Make sure your editor isn't expanding tabs. You need
real tabs. As in ^I.