From: <bar...@t-...> - 2002-10-14 14:09:20
|
hallo bastien, > > 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. oki - but so far nobody has specified that mrls conform to uris - but of course this is a valid point. however, i was hoping that a new, clean specification for what an mrl really is would have a clean concept for how to specify multiple streams and maybe also stream options (things like volume, start time, audio channel etc.) - so people could do really nice things with mrls. > My point is that you can't load URIs with % as the subtitle separator, > but you can work around # as a separator. again, a avery good point. maybe the file plugin should switch to # as the separator ? :) > > on the other hand - it shouldn't be an issue with more advanced frontends > > which should be able to present a nice dialog in which the user can > > specify media and subtitle files easily. > > But the intelligence is still in the input plugin, so it's still quite > broken. what is "broken" about that? i think it's quite right that input plugins define the mrls they can handle and do the parsing. so when i'm talking about a clean concept i'm merely thinking about writing a guideline document on how mrls are to be built. maybe it will turn out to make sense to have the engine parse some part of the mrl, but i don't see that need at the moment. > Time for: > xine_open_with_subtitle (xine_t *xine, char *mrl, char *subtitle_mrl) ? that looks really broken to me - have an extra api call for the special case of external subtitles 8-} think about microdvds - who should call this funtion in that case? cheers, guenter -- A transistor protected by a fast-acting fuse will protect the fuse by blowing first. |