Re: MIME Type for .ram file: application/ram

Hi,

May I know when this MIME type change for .ram file took
place? i.e.
from which version did the server start returning
"application/ram"
instead of "audio/x-pn-realaudio" as mime type for
.ram files? Helix
server 11 documentation still lists
"audio/x-pn-realaudio" as mime type
for .ram files.

Or is this only applicable to local .ram files? And not to
http request
with ramgen / http request for .ram file?

Thanks,
 Carol.
 

-----Original Message-----
From: datatype-dev-bounceshelixcommunity.org
[mailto:datatype-dev-bounceshelixcommunity.org] On
Behalf Of ext Milko
Boic
Sent: Tuesday, January 23, 2007 7:02 PM
To: Daniel Yek; Datatype Dev
Subject: [datatype-dev] Re: MIME Type for .ram file:
application/ram

At 12:29 AM 1/23/2007, Daniel Yek wrote:
>Thanks, Milko. I saw that in some files before but
didn't recall seeing

>it when I needed it. Almost all the documentation out
there still refer

>to audio/x-pn-realaudio as .ram file's MIME Type, which
is somewhat of
a problem.
>
>Is application/ram registered with IANA?

No.

>I didn't find it here:
>http://www.iana.org/assignments/media-types/application/

>
>Is it "legal" in the application namespace?

It is appropriate.


>I updated Linux players to use this new MIME Type and
I'm trying to get

>FreeDesktop.org to drop .ram glob in the wrong MIME Type
entry and 
>possibly adopt this new MIME Type.
>
>That fixed the double-click problem.
>
>Thanks.
>
>
>--
>Daniel Yek
>
>At 09:19 AM 1/22/2007, Milko Boic wrote:
>
>>New mime-type is not needed.
>>Ram file mime-type is "application/ram" . 
It is already claimed by 
>>the ram plugin.
>>
>>Milko
>>
>>At 08:07 PM 1/21/2007, Daniel Yek wrote:
>>>Hi,
>>>
>>>There is some difficulty in making double-click
works with .ram file 
>>>on Linux GNOME desktop due to the sharing of
audio/vnd.rn-realaudio 
>>>between RealAudio media file and .ram file.
>>>
>>>Here is a user reporting the issue:
>>>http://www.linuxforums.org/forum/linux-desk
top-x-windows/81992-cant-d
>>>ouble-click-ram-file-nautilus.html
>>>
>>>
>>>When double-clicking a .ram file, the user gets
a Nautilus Error:
>>>   The filename
"surroundSoundClips.ram" indicates that this file
>>>   is of type "RealAudio".
>>>   The contents of the file indicate that the
file is of type
>>>   "plain text document".
>>>   If you open this file, the file might present
a security risk to
>>>   your system.
>>>
>>>   Do not open the file unless you created the
file yourself, or
>>>   received the file from a trusted source.
>>>   To open the file, rename the file to the
correct extension for
>>>   "plain text document", then open
the file normally.
>>>   Alternatively, use the Open With menu to
choose a specific
>>>   application for the file.
>>>
>>>There is no checkbox or other way to disable
this dialog box and the 
>>>dialog box isn't just a warning, but stopping
the action from being
taken.
>>>
>>>It appears to me this problem has no workaround
because both the .ram

>>>text file and RealAudio binary media file are
assigned the same MIME
Type.
>>>
>>>The error dialog box will be invoked whenever an
extension glob 
>>>pattern indicates that it is one MIME Type and
its content indicate 
>>>another type (for security reason).
>>>
>>>If you think that this is more a Nautilus bug, I
agree that it is an 
>>>implementation that wasn't executed (in term of
rolling it out) well;

>>>but that is not going to be sufficient, because
this problem has been

>>>there for 3 years and there was also strong
resistance in disabling 
>>>the error dialog box. GNOME/Nautilus developers
were pushing for the 
>>>problems to be resolved in freedesktop.org.xml,
which is a MIME Type 
>>>database shared by Linux Desktops (GNOME, KDE,
etc.) We need to adapt

>>>to the situation and solve the issue from our
end.
>>>
>>>You can find the minimal discussion about the
error dialog box 
>>>checkin in the following thread:
>>>http://www.arcknowledge.com/gmane.comp.gnom
e.documentation/2004-02/ms
>>>g00115.html
>>>
>>>
>>>And more information here:
>>>http://www.arcknowledge.com/gmane.comp.gnom
e.multimedia/2005-02/msg00
>>>005.html
>>>
>>>
>>>We would be able to solve this problem if we
could make .ram MIME 
>>>type a sub-class-of text/plain, but since the
"shared" RealAudio 
>>>isn't also text/plain, we can't really make
audio/vnd.rn-realaudio 
>>>sub-class-of text/plain.
>>>
>>>I only see a workable solution in creating a
separate MIME type for 
>>>.ram file, either for Linux desktop only or for
all application 
>>>dealing with .ram file. Note that Apache is
likely to use the Linux 
>>>desktop's (actually FreeDesktop.org's)
"Shared MIME Types" database
too.
>>>
>>>
>>>NEW MIME TYPE:
>>>--------------
>>>I'm proposing to introduce audio/vnd.rn-playlist
as the MIME type of 
>>>.ram file.
>>>
>>>We probably assigned .ram file the
audio/x-pn-realaudio MIME type out

>>>of convenience (I'm guessing here) that the
browser would invoke 
>>>RealPlayer, but an unknown MIME Type wouldn't,
but it is suboptimal 
>>>to use it beyond the initial transition period.
>>>
>>>I'll need to request FreeDesktop.org to remove
.ram glob from 
>>>audio/vnd.realaudio entry in freedesktop.org.xml
that Linux desktops
are using.
>>>
>>>I will need to add audio/vnd.rn-playlist to
Linux's realplay.xml MIME

>>>Types database that Linux RealPlayer installs.
>>>
>>>I'll also request for this entry to be added
into freedesktop.org.xml

>>>MIME Types database.
>>>
>>>
>>>IMPLICATION:
>>>------------
>>>The core would need to recognize
audio/vnd.vnd.rn-playlist as RAM
file. 
>>>Windows RealPlayer would also have to change.
>>>
>>>Then, the server can change to use this new MIME
type.
>>>
>>>This will solve the double-click problem on
Linux desktop.
>>>
>>>
>>>
>>>RELEVANT NAUTILUS SOURCE CODE:
>>>http://svn.gnome.org/viewcvs/nautilus/branc
hes/gnome-2-16/src/file-ma
>>>nager/fm-directory-view.c?view=markup
>>>
>>>    activate_check_mime_types()
>>>    {
>>>        guessed_mime_type =
nautilus_file_get_guessed_mime_type
(file);
>>>         mime_type = nautilus_file_get_mime_type
(file);
>>>
>>>         if (gnome_vfs_mime_type_get_equivalence
(mime_type,
>>> guessed_mime_type)
>>>             == GNOME_VFS_MIME_UNRELATED) {
>>>
>>>             default_app =
>>>               
gnome_vfs_mime_get_default_application (mime_type);
>>>             guessed_default_app =
>>>               
gnome_vfs_mime_get_default_application 
>>> (guessed_mime_type);
>>>
>>>             if (default_app != NULL &&
guessed_default_app != NULL
&&
>>>               !gnome_vfs_mime_application_equal
(default_app,
>>>                                                
 
>>> guessed_default_app)) {
>>>
>>>                         if (warn_on_mismatch)
{
>>>                                
warn_mismatched_mime_types (view,
file);
>>>                         }
>>>                         ret = FALSE;
>>>              }
>>>           }
>>>       }
>>>
>>>Opinions welcome! Thanks.
>>>
>>>
>>>--
>>>Daniel Yek



_______________________________________________
Datatype-dev mailing list
Datatype-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/da
tatype-dev

_______________________________________________
Datatype-dev mailing list
Datatype-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/da
tatype-dev

Hi Carol,

I don't have an answer to the server question. Maybe asking
in the Helix 
server email list? I am interested in the answer too.

What I did was mainly desktop Linux changes.

Thanks.


-- 
Daniel Yek


At 05:00 PM 2/9/2007, Carol.i.Chennokia.com wrote:
>Hi,
>
>May I know when this MIME type change for .ram file took
place? i.e.
>from which version did the server start returning
"application/ram"
>instead of "audio/x-pn-realaudio" as mime type
for .ram files? Helix
>server 11 documentation still lists
"audio/x-pn-realaudio" as mime type
>for .ram files.
>
>Or is this only applicable to local .ram files? And not
to http request
>with ramgen / http request for .ram file?
>
>Thanks,
>  Carol.
>
>
>-----Original Message-----
>From: datatype-dev-bounceshelixcommunity.org
>[mailto:datatype-dev-bounceshelixcommunity.org] On
Behalf Of ext Milko
>Boic
>Sent: Tuesday, January 23, 2007 7:02 PM
>To: Daniel Yek; Datatype Dev
>Subject: [datatype-dev] Re: MIME Type for .ram file:
application/ram
>
>At 12:29 AM 1/23/2007, Daniel Yek wrote:
> >Thanks, Milko. I saw that in some files before but
didn't recall seeing
>
> >it when I needed it. Almost all the documentation
out there still refer
>
> >to audio/x-pn-realaudio as .ram file's MIME Type,
which is somewhat of
>a problem.
> >
> >Is application/ram registered with IANA?
>
>No.
>
> >I didn't find it here:
> >http://www.iana.org/assignments/media-types/application/

> >
> >Is it "legal" in the application
namespace?
>
>It is appropriate.
>
>
> >I updated Linux players to use this new MIME Type
and I'm trying to get
>
> >FreeDesktop.org to drop .ram glob in the wrong MIME
Type entry and
> >possibly adopt this new MIME Type.
> >
> >That fixed the double-click problem.
> >
> >Thanks.
> >
> >
> >--
> >Daniel Yek
> >
> >At 09:19 AM 1/22/2007, Milko Boic wrote:
> >
> >>New mime-type is not needed.
> >>Ram file mime-type is
"application/ram" .  It is already claimed by
> >>the ram plugin.
> >>
> >>Milko
> >>
> >>At 08:07 PM 1/21/2007, Daniel Yek wrote:
> >>>Hi,
> >>>
> >>>There is some difficulty in making
double-click works with .ram file
> >>>on Linux GNOME desktop due to the sharing
of audio/vnd.rn-realaudio
> >>>between RealAudio media file and .ram
file.
> >>>
> >>>Here is a user reporting the issue:
> >>>http://www.linuxforums.org/forum/linux-desk
top-x-windows/81992-cant-d
> >>>ouble-click-ram-file-nautilus.html
> >>>
> >>>
> >>>When double-clicking a .ram file, the user
gets a Nautilus Error:
> >>>   The filename
"surroundSoundClips.ram" indicates that this file
> >>>   is of type "RealAudio".
> >>>   The contents of the file indicate that
the file is of type
> >>>   "plain text document".
> >>>   If you open this file, the file might
present a security risk to
> >>>   your system.
> >>>
> >>>   Do not open the file unless you created
the file yourself, or
> >>>   received the file from a trusted
source.
> >>>   To open the file, rename the file to the
correct extension for
> >>>   "plain text document", then
open the file normally.
> >>>   Alternatively, use the Open With menu to
choose a specific
> >>>   application for the file.
> >>>
> >>>There is no checkbox or other way to
disable this dialog box and the
> >>>dialog box isn't just a warning, but
stopping the action from being
>taken.
> >>>
> >>>It appears to me this problem has no
workaround because both the .ram
>
> >>>text file and RealAudio binary media file
are assigned the same MIME
>Type.
> >>>
> >>>The error dialog box will be invoked
whenever an extension glob
> >>>pattern indicates that it is one MIME Type
and its content indicate
> >>>another type (for security reason).
> >>>
> >>>If you think that this is more a Nautilus
bug, I agree that it is an
> >>>implementation that wasn't executed (in
term of rolling it out) well;
>
> >>>but that is not going to be sufficient,
because this problem has been
>
> >>>there for 3 years and there was also strong
resistance in disabling
> >>>the error dialog box. GNOME/Nautilus
developers were pushing for the
> >>>problems to be resolved in
freedesktop.org.xml, which is a MIME Type
> >>>database shared by Linux Desktops (GNOME,
KDE, etc.) We need to adapt
>
> >>>to the situation and solve the issue from
our end.
> >>>
> >>>You can find the minimal discussion about
the error dialog box
> >>>checkin in the following thread:
> >>>http://www.arcknowledge.com/gmane.comp.gnom
e.documentation/2004-02/ms
> >>>g00115.html
> >>>
> >>>
> >>>And more information here:
> >>>http://www.arcknowledge.com/gmane.comp.gnom
e.multimedia/2005-02/msg00
> >>>005.html
> >>>
> >>>
> >>>We would be able to solve this problem if
we could make .ram MIME
> >>>type a sub-class-of text/plain, but since
the "shared" RealAudio
> >>>isn't also text/plain, we can't really make
audio/vnd.rn-realaudio
> >>>sub-class-of text/plain.
> >>>
> >>>I only see a workable solution in creating
a separate MIME type for
> >>>.ram file, either for Linux desktop only or
for all application
> >>>dealing with .ram file. Note that Apache is
likely to use the Linux
> >>>desktop's (actually FreeDesktop.org's)
"Shared MIME Types" database
>too.
> >>>
> >>>
> >>>NEW MIME TYPE:
> >>>--------------
> >>>I'm proposing to introduce
audio/vnd.rn-playlist as the MIME type of
> >>>.ram file.
> >>>
> >>>We probably assigned .ram file the
audio/x-pn-realaudio MIME type out
>
> >>>of convenience (I'm guessing here) that the
browser would invoke
> >>>RealPlayer, but an unknown MIME Type
wouldn't, but it is suboptimal
> >>>to use it beyond the initial transition
period.
> >>>
> >>>I'll need to request FreeDesktop.org to
remove .ram glob from
> >>>audio/vnd.realaudio entry in
freedesktop.org.xml that Linux desktops
>are using.
> >>>
> >>>I will need to add audio/vnd.rn-playlist to
Linux's realplay.xml MIME
>
> >>>Types database that Linux RealPlayer
installs.
> >>>
> >>>I'll also request for this entry to be
added into freedesktop.org.xml
>
> >>>MIME Types database.
> >>>
> >>>
> >>>IMPLICATION:
> >>>------------
> >>>The core would need to recognize
audio/vnd.vnd.rn-playlist as RAM
>file.
> >>>Windows RealPlayer would also have to
change.
> >>>
> >>>Then, the server can change to use this new
MIME type.
> >>>
> >>>This will solve the double-click problem on
Linux desktop.
> >>>
> >>>
> >>>
> >>>RELEVANT NAUTILUS SOURCE CODE:
> >>>http://svn.gnome.org/viewcvs/nautilus/branc
hes/gnome-2-16/src/file-ma
> >>>nager/fm-directory-view.c?view=markup
> >>>
> >>>    activate_check_mime_types()
> >>>    {
> >>>        guessed_mime_type =
nautilus_file_get_guessed_mime_type
>(file);
> >>>         mime_type =
nautilus_file_get_mime_type (file);
> >>>
> >>>         if
(gnome_vfs_mime_type_get_equivalence (mime_type,
> >>> guessed_mime_type)
> >>>             == GNOME_VFS_MIME_UNRELATED)
{
> >>>
> >>>             default_app =
> >>>               
gnome_vfs_mime_get_default_application (mime_type);
> >>>             guessed_default_app =
> >>>               
gnome_vfs_mime_get_default_application
> >>> (guessed_mime_type);
> >>>
> >>>             if (default_app != NULL
&& guessed_default_app != NULL
>&&
> >>>              
!gnome_vfs_mime_application_equal (default_app,
> >>>
> >>> guessed_default_app)) {
> >>>
> >>>                         if
(warn_on_mismatch) {
> >>>                                
warn_mismatched_mime_types (view,
>file);
> >>>                         }
> >>>                         ret = FALSE;
> >>>              }
> >>>           }
> >>>       }
> >>>
> >>>Opinions welcome! Thanks.
> >>>
> >>>
> >>>--
> >>>Daniel Yek


_______________________________________________
Datatype-dev mailing list
Datatype-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/da
tatype-dev

application/ram was always supported in Helix code - no
change there.
Use of "audio/x-pn-realaudio" for ram files is
historic and prevalent.

The change is driven by Linux desktop issues. It has not
happened yet and 
it will not happen quickly.  It can only happen once the
ecosystem is 
widely supporting the new mime-type.  Linux team should
drive this or push 
for Linux desktop tools to allow for audio/x-pn-realaudio
association to a 
text file (simpler and more effective solution).

Robust applications should recognize and register
"application/ram" and 
"audio/x-pn-realaudio" mime-types.

Milko

At 07:42 AM 2/14/2007, Daniel Yek wrote:
>Hi Carol,
>
>I don't have an answer to the server question. Maybe
asking in the Helix 
>server email list? I am interested in the answer too.
>
>What I did was mainly desktop Linux changes.
>
>Thanks.
>
>
>--
>Daniel Yek
>
>
>At 05:00 PM 2/9/2007, Carol.i.Chennokia.com wrote:
>>Hi,
>>
>>May I know when this MIME type change for .ram file
took place? i.e.
>>from which version did the server start returning
"application/ram"
>>instead of "audio/x-pn-realaudio" as mime
type for .ram files? Helix
>>server 11 documentation still lists
"audio/x-pn-realaudio" as mime type
>>for .ram files.
>>
>>Or is this only applicable to local .ram files? And
not to http request
>>with ramgen / http request for .ram file?
>>
>>Thanks,
>>  Carol.
>>
>>
>>-----Original Message-----
>>From: datatype-dev-bounceshelixcommunity.org
>>[mailto:datatype-dev-bounceshelixcommunity.org] On
Behalf Of ext Milko
>>Boic
>>Sent: Tuesday, January 23, 2007 7:02 PM
>>To: Daniel Yek; Datatype Dev
>>Subject: [datatype-dev] Re: MIME Type for .ram file:
application/ram
>>
>>At 12:29 AM 1/23/2007, Daniel Yek wrote:
>> >Thanks, Milko. I saw that in some files before
but didn't recall seeing
>>
>> >it when I needed it. Almost all the
documentation out there still refer
>>
>> >to audio/x-pn-realaudio as .ram file's MIME
Type, which is somewhat of
>>a problem.
>> >
>> >Is application/ram registered with IANA?
>>
>>No.
>>
>> >I didn't find it here:
>> >http://www.iana.org/assignments/media-types/application/

>> >
>> >Is it "legal" in the application
namespace?
>>
>>It is appropriate.
>>
>>
>> >I updated Linux players to use this new MIME
Type and I'm trying to get
>>
>> >FreeDesktop.org to drop .ram glob in the wrong
MIME Type entry and
>> >possibly adopt this new MIME Type.
>> >
>> >That fixed the double-click problem.
>> >
>> >Thanks.
>> >
>> >
>> >--
>> >Daniel Yek
>> >
>> >At 09:19 AM 1/22/2007, Milko Boic wrote:
>> >
>> >>New mime-type is not needed.
>> >>Ram file mime-type is
"application/ram" .  It is already claimed by
>> >>the ram plugin.
>> >>
>> >>Milko
>> >>
>> >>At 08:07 PM 1/21/2007, Daniel Yek wrote:
>> >>>Hi,
>> >>>
>> >>>There is some difficulty in making
double-click works with .ram file
>> >>>on Linux GNOME desktop due to the
sharing of audio/vnd.rn-realaudio
>> >>>between RealAudio media file and .ram
file.
>> >>>
>> >>>Here is a user reporting the issue:
>> >>>http://www.linuxforums.org/forum/linux-desk
top-x-windows/81992-cant-d
>> >>>ouble-click-ram-file-nautilus.html
>> >>>
>> >>>
>> >>>When double-clicking a .ram file, the
user gets a Nautilus Error:
>> >>>   The filename
"surroundSoundClips.ram" indicates that this file
>> >>>   is of type "RealAudio".
>> >>>   The contents of the file indicate
that the file is of type
>> >>>   "plain text document".
>> >>>   If you open this file, the file
might present a security risk to
>> >>>   your system.
>> >>>
>> >>>   Do not open the file unless you
created the file yourself, or
>> >>>   received the file from a trusted
source.
>> >>>   To open the file, rename the file to
the correct extension for
>> >>>   "plain text document",
then open the file normally.
>> >>>   Alternatively, use the Open With
menu to choose a specific
>> >>>   application for the file.
>> >>>
>> >>>There is no checkbox or other way to
disable this dialog box and the
>> >>>dialog box isn't just a warning, but
stopping the action from being
>>taken.
>> >>>
>> >>>It appears to me this problem has no
workaround because both the .ram
>>
>> >>>text file and RealAudio binary media
file are assigned the same MIME
>>Type.
>> >>>
>> >>>The error dialog box will be invoked
whenever an extension glob
>> >>>pattern indicates that it is one MIME
Type and its content indicate
>> >>>another type (for security reason).
>> >>>
>> >>>If you think that this is more a
Nautilus bug, I agree that it is an
>> >>>implementation that wasn't executed (in
term of rolling it out) well;
>>
>> >>>but that is not going to be sufficient,
because this problem has been
>>
>> >>>there for 3 years and there was also
strong resistance in disabling
>> >>>the error dialog box. GNOME/Nautilus
developers were pushing for the
>> >>>problems to be resolved in
freedesktop.org.xml, which is a MIME Type
>> >>>database shared by Linux Desktops
(GNOME, KDE, etc.) We need to adapt
>>
>> >>>to the situation and solve the issue
from our end.
>> >>>
>> >>>You can find the minimal discussion
about the error dialog box
>> >>>checkin in the following thread:
>> >>>http://www.arcknowledge.com/gmane.comp.gnom
e.documentation/2004-02/ms
>> >>>g00115.html
>> >>>
>> >>>
>> >>>And more information here:
>> >>>http://www.arcknowledge.com/gmane.comp.gnom
e.multimedia/2005-02/msg00
>> >>>005.html
>> >>>
>> >>>
>> >>>We would be able to solve this problem
if we could make .ram MIME
>> >>>type a sub-class-of text/plain, but
since the "shared" RealAudio
>> >>>isn't also text/plain, we can't really
make audio/vnd.rn-realaudio
>> >>>sub-class-of text/plain.
>> >>>
>> >>>I only see a workable solution in
creating a separate MIME type for
>> >>>.ram file, either for Linux desktop
only or for all application
>> >>>dealing with .ram file. Note that
Apache is likely to use the Linux
>> >>>desktop's (actually FreeDesktop.org's)
"Shared MIME Types" database
>>too.
>> >>>
>> >>>
>> >>>NEW MIME TYPE:
>> >>>--------------
>> >>>I'm proposing to introduce
audio/vnd.rn-playlist as the MIME type of
>> >>>.ram file.
>> >>>
>> >>>We probably assigned .ram file the
audio/x-pn-realaudio MIME type out
>>
>> >>>of convenience (I'm guessing here) that
the browser would invoke
>> >>>RealPlayer, but an unknown MIME Type
wouldn't, but it is suboptimal
>> >>>to use it beyond the initial transition
period.
>> >>>
>> >>>I'll need to request FreeDesktop.org to
remove .ram glob from
>> >>>audio/vnd.realaudio entry in
freedesktop.org.xml that Linux desktops
>>are using.
>> >>>
>> >>>I will need to add
audio/vnd.rn-playlist to Linux's realplay.xml MIME
>>
>> >>>Types database that Linux RealPlayer
installs.
>> >>>
>> >>>I'll also request for this entry to be
added into freedesktop.org.xml
>>
>> >>>MIME Types database.
>> >>>
>> >>>
>> >>>IMPLICATION:
>> >>>------------
>> >>>The core would need to recognize
audio/vnd.vnd.rn-playlist as RAM
>>file.
>> >>>Windows RealPlayer would also have to
change.
>> >>>
>> >>>Then, the server can change to use this
new MIME type.
>> >>>
>> >>>This will solve the double-click
problem on Linux desktop.
>> >>>
>> >>>
>> >>>
>> >>>RELEVANT NAUTILUS SOURCE CODE:
>> >>>http://svn.gnome.org/viewcvs/nautilus/branc
hes/gnome-2-16/src/file-ma
>> >>>nager/fm-directory-view.c?view=markup
>> >>>
>> >>>    activate_check_mime_types()
>> >>>    {
>> >>>        guessed_mime_type =
nautilus_file_get_guessed_mime_type
>>(file);
>> >>>         mime_type =
nautilus_file_get_mime_type (file);
>> >>>
>> >>>         if
(gnome_vfs_mime_type_get_equivalence (mime_type,
>> >>> guessed_mime_type)
>> >>>             ==
GNOME_VFS_MIME_UNRELATED) {
>> >>>
>> >>>             default_app =
>> >>>               
gnome_vfs_mime_get_default_application (mime_type);
>> >>>             guessed_default_app =
>> >>>               
gnome_vfs_mime_get_default_application
>> >>> (guessed_mime_type);
>> >>>
>> >>>             if (default_app != NULL
&& guessed_default_app != NULL
>>&&
>> >>>              
!gnome_vfs_mime_application_equal (default_app,
>> >>>
>> >>> guessed_default_app)) {
>> >>>
>> >>>                         if
(warn_on_mismatch) {
>> >>>                                
warn_mismatched_mime_types (view,
>>file);
>> >>>                         }
>> >>>                         ret = FALSE;
>> >>>              }
>> >>>           }
>> >>>       }
>> >>>
>> >>>Opinions welcome! Thanks.
>> >>>
>> >>>
>> >>>--
>> >>>Daniel Yek
>
>
>_______________________________________________
>Datatype-dev mailing list
>Datatype-devhelixcommunity.org
>http://lists.helixcommunity.org/mailman/listinfo/da
tatype-dev



_______________________________________________
Datatype-dev mailing list
Datatype-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/da
tatype-dev