| Summary: | Some players require DOS folder seperators | ||
|---|---|---|---|
| Product: | media-player-info | Reporter: | William Witt <william> |
| Component: | General | Assignee: | Martin Pitt <martin.pitt> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
William Witt
2011-08-28 14:20:14 UTC
Do any of the existing player applications (Rhythmbox, Banshee, Amarok, etc.) already support these fields? Is there a corresponding bug report for these? Banshee has at least these two bug reports requesting this feature (gnome's bugzilla is down at the moment, or I'd look for more): https://bugzilla.gnome.org/show_bug.cgi?id=587964 https://bugzilla.gnome.org/show_bug.cgi?id=609488 I've been doing some minor hacking on Banshee and would be more than willing to write a submit a patch for this feature. Definition of the properties: http://cgit.freedesktop.org/media-player-info/commit/?id=b2ebb64c1d6797f7b9e8bda0cbbbe61484fb54a2 Fuze: http://cgit.freedesktop.org/media-player-info/commit/?id=16d027f9687038f801ff2f6f62ad4f18523dc842 Does that look appropriate to you? If so, I'll make a new release this week. I ran into an issue trying to read a "FolderSeparator=\" from a hand edited .mpi file. Either it was confused because \ is the unicersal sign to continue on the next line, or because it was trying to escape the line feed. I could read "FolderSeparator=\\" just fine (but it in fact was decoded as "\\"). We might be better off with either "UNIX" or "DOS". Ah, that might depend on the implementation then indeed. I tried it with Python's ConfigParser, and it reads a single '\' just fine. But similarly to LineEnding we can just use symbolic names. http://cgit.freedesktop.org/media-player-info/commit/?id=916cee7bb2664029e16633af4fac4915de28049c This requires some more logic on the player side, but should be safe. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.