Adobe illustrator 10 (only version i have to check with) exports SVGZ which is simply an SVG file gzipped. The Adobe SVG browser plugin displays these files. if you were to save an SVG file 'rectangle.svg' for example and save a copy of it as SVGZ you would get *exactly* the same file contents in gzip archive called rectangle.svgz, the archive would contain one file called 'rectangle' (no extension)
link added severity changed to enhancement
SVGZ will work if the HTTP response header includes: Content-Type: image/svg+xml Content-Encoding: x-gzip Thus this is an issue with server configuration, not Mozilla.
It would be nice if .svgz files could be viewed with Mozilla, in which case there is no server for us to configure. Also, .svgz files are supported by more SVG viewers than Adobe's plug-in alone. It may be expedient to special-case this format for the sake of people who have checked their site on MSIE + AdoveSVGViewer and are suprised when Mozilla still cannot display it.
FIXED/INVALID? Files with extension .svgz on a server can be viewed when the HTTP headers are set correctly, and opening .svgz files locally also works (try viewing, and downloading and viewing the file linked to below). Mozilla does not and will not decide how to handle remote files depending on file name extension for security reasons. http://www.pinkjuice.com/svg/svgz/es.svgz
Assigning to me so I remember to find out after doing mass reassign.
Closing. One way to configure Apache to to send the correct headers for SVG files it to add the following to a .htaccess file in a root directory. AddType image/svg+xml .svg AddType image/svg+xml .svgz AddEncoding x-gzip .svgz
Reopening. I would have sworn that Mozilla could view .svgz files loaded from the hard drive, but apparently this has never worked. I think the times I tested it previously, I first downloaded the .svgz files over HTTP and encountered bug 283272. Hence the .svgz files that I thought were compressed actually weren't.
*** This bug has been marked as a duplicate of 52282 ***
Not sure if fixing 52282 will support the following use case (So I will post this same comment in 52282 and in 157514: A data:url containing svgz. The data url syntax doesn't have a way to specify that the content is gzip compressed, and there is only one MIME type for svg. Mozilla throws up an XML parsing error. Opera handles it. Why inline svgz in a data:url instead of using a compound XML document and compressing the whole thing? 1) Why not. 2) The whole XML / DTD doctype conunundrum to get the latter approach working. 3) I want to send the svg back to the server, and prefer to send compressed data.