- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Jun 2019 20:31:08 +0000
- To: public-svg-issues@w3.org
The SVG Working Group just discussed `A separate MIME type for svgz files is needed`. <details><summary>The full IRC log of that discussion</summary> <krit> topic: A separate MIME type for svgz files is needed<br> <krit> GitHub: https://github.com/w3c/svgwg/issues/701<br> <krit> chris_: there is a content type and a content encoding<br> <krit> chris_: I remember ppl had mime types for svg+gzip<br> <krit> chris_: over time it got clarified and the SVG spec is the way it is<br> <krit> chris_: there also was a desire to do compression for the server since it was uncommon to zip dynamically.<br> <krit> chris_: if we change the mime type now, svgz would stop working.<br> <krit> chris_: I think the original commenter is wrong<br> <krit> chris_: Maybe I can give the issue creator give the history and maybe it convinces him<br> <krit> myles: how can applications differ between the 2 types today?<br> <krit> chris_: I think implementations just look at the first bytes.<br> <krit> chris_: In moder use you just drop an SVG file on the server and the server will do the compression on the fly.<br> <krit> chris_: we were competing with flash and it was important to have small files.<br> <krit> chris_: but having a separate mime type might never fly.<br> <krit> chris_: of course I can argue against having 2 types sharing the same mime type but that is history.<br> <krit> krit: chris_ will reply on the thread and we will pick it up again if there is a negative response.<br> <krit> trackbot, end telcon<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/svgwg/issues/701#issuecomment-505168669 using your GitHub account
Received on Monday, 24 June 2019 20:31:10 UTC