Dear Eric,

do you still have interst for this bug report ?

Have a nice week-end,

-- Charles Plessy

Le Sat, May 03, 2014 at 09:02:28PM +0900, Charles Plessy a écrit :
> Le Tue, Jan 18, 2005 at 09:56:22AM +0100, Eric Lavarde a écrit :
> > 
> > more and more utilities use URL notation to pass around file names,
> > hence it would be very useful to have run-mailcap understand URL and do one 
> > of
> > two things:
> > - handle file:/... URL as normal files.
> > - pass along other kinds of URL (http://, ftp://, etc...) to
> >   sensible-browser.
> > This could be possibly controlled by a switch (e.g. --allow-url) for 
> > security
> > reasons.
> 
> Dear Eric,
> 
> for the first part of your proposition, I think that there is a serious
> obstacle: with the mailcap system, it is not possible to determine if a 
> program
> would be able to use an URL to retreive a file.
> 
> For the second part, here is what we could do:
> 
>  - send a patch to the sensible-utils package, to add two lines in its
>    mailcap file, where the media types x-scheme-handler/http and
>    x-scheme-handler/ftp would be associated to the sensible-browser
>    program.
> 
>  - Detect URLs passed to run-mailcap, and execute what /etc/mailcap proposes
>    for the corresponding media type.
> 
> The problem I have with this approach is that x-scheme-handler media types
> are not registered to the IANA.  As far as I know, they originate from the
> Shared MIME-info Database specification.
> 
>     http://standards.freedesktop.org/shared-mime-info-spec/
> 
> Perhaps it would be better to ask for comments on debian-devel before using
> these unregistered media types outside the scope where thay have been 
> developed
> originally.
> 
> What do you think about this ?
> 
> Have a nice week-end,
> 
> -- 
> Charles Plessy
> Tsurumi, Kanagawa, Japan

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to