qt4: control_(Add/Remove/Exists) are not ready yet. (and btw, the previous commit also introduced last.fm settings in the simple preferences)

Qt4 - make the Browse Device button to actually do something. Fix Trax#49. This has to be checked when you want to open a VIDEO_TS folder (reading V_T or V_T/.. ?)

Add support for converting RGBA into YUVA using ffmpeg libswscale capabilities when available. This makes the Teletext subtitles streamable with dvbsub encoder/decoder.

xspf writer: forget to increment the source pointer in [22665], that would result in file://file://file:///path/to/input entries in ml.xspf

telepathy: register the callbacks only when we are connected to the bus, to avoid the module being unloaded, while the callbacks are still active

Fixed use of uninitialized data for CC detection.

We don't do that on other URIs because those characters may be used as delimiters, and must not be percent encoded.

Now produces valid XSPF-1 files.

* don't use the text archive format for nibs, as the binary version is faster to load and smaller to store. Additionally, it's a lot better for diffing on trac, as humans should't understand the text format anyway.

playlist_CreateNode(): add an argument to specify an input_item_t to be linked with the node, rather than creating a new input.
Setting that argument to NULL will make playlist_CreateNode() behave like previously.

That way we can create only one input per pair of node (for local playlist, media library, and service discovery)
Previous behaviour was to create 2 inputs with the same i_id member, but we would store both input in a binary search tree (sorted by i_id), and that kind of tree MUST NOT have 2 items with the same key, else we will get some bad memory corruption when the wrong input is removed from the tree (the other being left in the tree while the memory referred by it was freed).
Note that this breaks ABI

* implemented the generic VLC media player Help window on OSX to match the QT4 interface. Additionally, I modified the HTML source a bit, so potential umlauts won't be displayed as UTF-16 on OSX, which would lead to German umlauts being Chinese characters, etc. BTW. Withthis commit, we also link against the WebKit framework..