Re: [xine-devel] gnome-vfs input plugin

[Michael R. <mr...@us...>]

Hi Bastien,

> > > Because the '%' separator is real broken, imo.
> >
> > humm - it was the result of a lengthy discussion on the xine
> > mailing lists, i think it was ':' before. this one had the benefit
> > if tab completion still working, but people with mac-filesystems
> > were unhappy with it.
> >
> > anyway, any such separator is broken in its own way since all these
> > characters can be part of a unix file name so potentially they
> > could be causing trouble for people.
>
> Yeah, but if we want to deal with URIs, # isn't broken at all. The
> only reason you would use this character is for the fragment
> identifier.
>
> my file is named: "Foo Bar.mpeg" so its escaped URI would be
> file:///fullpath/Foo%20Bar.mpeg"
> Here the file input tries to load the subtitle 20Bar.mpeg. Eeek.
>
> But if I have my file called "#1.mpeg", the # could be escaped. Ie.
> it would end up with a URI like:
> file:///fullpath/%501.mpeg (%50 isn't the escape char for #, don't
> know it on top of my head).
>
> My point is that you can't load URIs with % as the subtitle
> separator, but you can work around # as a separator.

The whole separate subtitle code needs to be looked over when the 
streams API is ready. If we manage to turn the sputext decoder into a 
real decoder reading data from the fifo and write a demuxer plugin for 
text subtitle files, it should be possible to use two streams (video + 
subtitle) for this application. This is IMHO the cleanest solution.
And it will enable text subtitles for all kinds of formats, not only avi 
as it is now.

Michael

-- 
panic("esp: what could it be... I wonder...");
	2.2.16 /usr/src/linux/drivers/scsi/esp.c