After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 654596 - [matroskademux] Subtitles tags are not recognized in Matroska files
[matroskademux] Subtitles tags are not recognized in Matroska files
Status: RESOLVED DUPLICATE of bug 616936
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.x
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-07-14 08:58 UTC by Vincent Tschanz
Modified: 2012-02-18 15:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
video file (311.38 KB, video/x-matroska)
2011-07-14 10:07 UTC, Vincent Tschanz
Details

Description Vincent Tschanz 2011-07-14 08:58:09 UTC
In srt subtitles we usually use html tags for text formatting. For example <i></i> when someone speaks offscreen.
Theses tags are not recognized by totem and are displayed with the text.

Instead those tags should be interpreted and the text rendered properly (italic, bold, etc)
Comment 1 Bastien Nocera 2011-07-14 09:02:20 UTC
Please attach an example subtitle file which doesn't work as expected for you.
Comment 2 Vincent Tschanz 2011-07-14 10:07:15 UTC
Created attachment 191945 [details]
video file

Matroska video file witn embedded srt file.
Comment 3 Vincent Tschanz 2011-07-14 10:08:24 UTC
After further investigation I find out that only srt embedded inside Matroska file have this problem.
You can see with the attached file.
Comment 4 Bastien Nocera 2011-07-14 10:18:26 UTC
This is a dupe, but I can't find the bug right now.
Comment 5 David Schleef 2011-07-14 20:11:03 UTC
Perhaps you're thinking of #653768?  Aside from that bug being closed, this one is valid.  As a guess, matroskamux is probably failing to put the right caps on the subtitle pad.
Comment 6 Tim-Philipp Müller 2012-02-18 15:27:16 UTC
This should be fixed in the upcoming -good 0.10.31 release (or 0.10.30.3 pre-release).

*** This bug has been marked as a duplicate of bug 616936 ***