Re: [gopher] Hello Gopher Project

Relatedly, is there a way to specify character encoding? This conversation has reminded me that being limited to ASCII < 128 (effectively) is really not fun.

As a great example, go poke around Gopherpedia in most clients. :(

If there's going to be any extension for text "smarts", I'd argue that is more important than supporting Markdown right now. (In any case, it's not worthwhile until Common Mark figures out if their "fork to rule them all" is going to actually reduce fragmentation.)

‎Just my 2 cents (I resisted using non-ASCII there…),

Matt

--
Matt Lewandowsky
Big Geek
Greenviolet
matt@greenviolet.net http://www.greenviolet.net
+1 415 578 5782 (US) +44 844 484 8254 (UK)
Sent from my BlackBerry 10 smartphone.

From: James Mills

Sent: Monday, December 15, 2014 12:55

To: Gopher Project Discussion

Reply To: Gopher Project Discussion

Subject: Re: [gopher] Hello Gopher Project

On Tue, Dec 16, 2014 at 12:27 AM, Nuno Silva <nunojsilva@ist.utl.pt> wrote:

If github's markdown is close to plain text (at least this is the idea
I've got from the couple times I touched markdown documents), I'd rather
serve it as plain text than make markdown files unreadable by clients
which can't render markdown.

Are there any provisions in Gopher+

to tell supported clients the mime-type

of a file they dowlnloaded?

cheers

James

James Mills / prologic

E: prologic@shortcircuit.net.au

W: prologic.shortcircuit.net.au