[vlc-devel] [RFC] input_item_t->psz_uri

Rafaël Carré funman at videolan.org
Fri Oct 12 02:49:55 CEST 2007

Hash: SHA1


I'm having a look at xsfp import/export modules, i.e. I would like to
use the xspf extension to display the ml.xsp (Media Library) as nodes.

We use a vlc-specific extension to xspf to display the Media Library in
a hierarchical way, since XSPF doesn't support that (at least version 1).

In the meantime, I made ml.xsp comply to XSPF specification, i.e.
<image> & <location> tags must be URI encoded.

However, I'm not sure I'm doing the right thing © here, since URI is a
bit complex,

Some special characters are used as general delimiters in special URIs,
':', '"', '?', '#', '[', ']', '@'

So those characters should be URI encoded, unless they are used as

input_item->psz_uri is specified as a 'mrl' which stands for "Media
Resource Location".

I wonder if there is a formal specification for "MRL", and if those
general delimiters are used in VLC.

For more information you may want to read RFC 3986:
Uniform Resource Identifier (URI): Generic Syntax

The main problem here is that those general delimiters aren't used in
"file:" URIs, which are exclusively what I'm using in my *own* Media
Library. So URI-encoding them make my ml.xsp a valid xspf file
(according to libspiff validator).

However those characters MAY be used in other URIs.

Please find my patch against XSPF muxer and demuxer (mainly muxer).

Maybe input_item_t->psz_uri should be a REAL and VALID URI, maybe not.

- --
Rafaël Carré
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: xspf.diff
Type: text/x-patch
Size: 5769 bytes
Desc: not available
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20071012/884d3a48/attachment.bin>

More information about the vlc-devel mailing list