9735 offers to save local compressed SVG files rather than
display them

This didn't happen with the last build I had installed, but attempting to  
open a compressed SVG file with a .svgz extension from disk in 9735  
results in a save dialogue appearing on the screen rather than displaying  
the image like it does if the same (compressed) file has a .svg extension.  
The dialogue correctly identifies the file type of the download as  
Scalable Vector Graphics despite not displaying it.

Was there really a need for the W3C to recommend people use a different  
extension for compressed files? Current programs don't seem to have a  
problem working out whether JPEGs are progressive or not when they're  
trying to open/display them regardless of the extension or MIME type, so  
is it really a major hassle for any program smart enough to display SVG  

On Wed, 27 Feb 2008 16:22:56 -0000, Eik <spam@hotmail.com> wrote:

>This didn't happen with the last build I had installed, but attempting to  
>open a compressed SVG file with a .svgz extension from disk in 9735  
>results in a save dialogue appearing on the screen rather than displaying  
>the image like it does if the same (compressed) file has a .svg extension. 

>The dialogue correctly identifies the file type of the download as  
>Scalable Vector Graphics despite not displaying it.

In Prefs > Advanced > Downloads, does it make a difference if you set
the svgz extension to open in Opera?

-- 
Tim Altman
Desktop QA
Opera Software

On Fri, 29 Feb 2008 02:20:58 -0000, Tim Altman <do.not@spam.me.invalid>  
wrote:

> In Prefs > Advanced > Downloads, does it make a difference if you
set
> the svgz extension to open in Opera?

Well I think I might have found a bug. I checked the 'Downloads' settings  
and the three SVG MIME types only have svg listed as an extension, whereas  
previous versions have a comma-separated list that includes svgz. So I  
added it and Opera 9.5b opened these files ok. However the next time I  
opened it, the problem was back.

I've scrolled through all the default MIME types and not one of them has  
more than one extension listed, so I think there's some kind of new bug  
where comma-separated lists get truncated at the first comma when Opera  
closes and saves this data to the INI file. It's possible the original  
MIME data included in the build did have svgz but it was lost when Opera  
was installed and started. I've tried to add comma-separated lists  
repeatedly and although it remembers them while it's still running, as  

On Fri, 29 Feb 2008 05:53:38 -0000, Eik <spam@hotmail.com> wrote:

>On Fri, 29 Feb 2008 02:20:58 -0000, Tim Altman
<do.not@spam.me.invalid>  
>wrote:
>
>> In Prefs > Advanced > Downloads, does it make a difference if you
set
>> the svgz extension to open in Opera?
>
>Well I think I might have found a bug. I checked the 'Downloads' settings  
>and the three SVG MIME types only have svg listed as an extension, whereas 

>previous versions have a comma-separated list that includes svgz. So I  
>added it and Opera 9.5b opened these files ok. However the next time I  
>opened it, the problem was back.
>
>I've scrolled through all the default MIME types and not one of them has  
>more than one extension listed, so I think there's some kind of new bug  
>where comma-separated lists get truncated at the first comma when Opera  
>closes and saves this data to the INI file. It's possible the original  
>MIME data included in the build did have svgz but it was lost when Opera  
>was installed and started. I've tried to add comma-separated lists  
>repeatedly and although it remembers them while it's still running, as  
>soon as it's closed and restarted it loses all but the first extension.

Yes, that's a bug we fixed quite a while ago.  If you're still using
9.5 Beta 1, you'll run into it, though.

-- 
Tim Altman
Desktop QA
Opera Software

On Wed, 05 Mar 2008 19:22:31 -0000, Tim Altman <do.not@spam.me.invalid>  
wrote:

> Yes, that's a bug we fixed quite a while ago.  If you're still using
> 9.5 Beta 1, you'll run into it, though.

I thought I was on the latest, though when I upgraded last week I used the  
classic installer, linked to at the bottom of the desktop blog. It reports  
to be 9735 though I notice the download links at the top of the blog (for  
the MSI) is for 9815 so now I'm not sure what I'm using. The previous  
build didn't have this problem and was an MSI installer (I switched to the  
classic due to problems the MSIs were causing), though I can't remember