[vlc-devel] The XSPF issue 2875 (the non-windows one)
remi at remlab.net
Mon Jun 22 19:30:47 CEST 2009
Le lundi 22 juin 2009 04:35:33 Derk-Jan Hartman, vous avez écrit :
> So what is the idea here. Are we storing uncoded, or coded paths in
> the VLC input core (I though uncoded), and why should we have
> different behaviour for URIs when we read the playlist? In my
> assessment, it seems we should just psz_location =
> decode_URI( psz_value ); for xspf reading.
Can you define what you call an uncoded and a coded path?
Personnally, I only know platform-specific paths and Uniform Resource
Locators. Neither of those have coded/uncoded variants.
More information about the vlc-devel