3 ms·

If anyone is interested in reading the GIF specification, I reformatted the plain text version into HTML: https://www.nayuki.io/page/gif89a-specification-html h

• andai 5y ago
  Neat! Is there an automated tool for the conversion? Preferably hooked up to a RFC database?
  • nayuki 5y ago
    I'm not aware of any tools; I converted this document by hand in a few hours. GIF is a popular standard with cultural value, which is why I would do this; I wouldn't do it for any random obscure document. The IETF RFC website has links to HTML and PDF versions, but... For most standards documents, the HTML and PDF versions look just like the plain text version, adding little or no value (e.g. https://www.rfc-editor.org/rfc/rfc1321.txt https://www.rfc-editor.org/rfc/rfc1321.txt ; https://www.rfc-editor.org/rfc/rfc1321.html https://www.rfc-editor.org/rfc/rfc1321.html ; https://www.rfc-editor.org/rfc/pdfrfc/rfc1321.txt.pdf https://www.rfc-editor.org/rfc/pdfrfc/rfc1321.txt.pdf ). The only standard I am aware of with a decently formatted version is DEFLATE ( https://www.rfc-editor.org/rfc/rfc1951.txt https://www.rfc-editor.org/rfc/rfc1951.txt ; https://www.rfc-editor.org/rfc/rfc1951.pdf https://www.rfc-editor.org/rfc/rfc1951.pdf ).
  • deleted 5y ago
    [deleted]
• sbierwagen 5y ago
  My favorite piece of GIF trivia is that in the original spec, GIF animations would play once and only once. Netscape used the Application Extension block to add number of loops or loop indefinitely. An Application Extension requires an application identifier. So basically every animated GIF ever made has the string `NETSCAPE2.0` in it. https://en.wikipedia.org/wiki/GIF#Animated_GIF https://en.wikipedia.org/wiki/GIF#Animated_GIF
• kragen 5y ago
  Thank you, this is wonderful!