- From: <bugzilla@jessica.w3.org>
- Date: Mon, 29 Sep 2014 16:32:49 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26924 --- Comment #3 from Aaron Colwell <acolwell@google.com> --- (In reply to Cyril Concolato from comment #2) > (In reply to Aaron Colwell from comment #1) > > In your case, "und" is present. > The problem is that "und" is present as a default in many MP4 files, because > people forgot or did not know how to tag their files with a proper language. > If I make an application that uses this kind of content and I know it's in > French but don't have the means to change the file because it's hosted > somewhere else, I'll be stuck. My concern is that we have a slippery slope here. We are going from just filling in info that isn't there to overriding info in the init segment. I can understand the desire to "correct" the language information in this case because you don't own the source files, but what if the files actually have completely bogus information in them. You wouldn't be able to correct for that with your proposed solution. It seems like we should either reflect what is in the init segment and only fallback to the defaults if nothing is present (like we do now) or allow a default to always override what is in the init segment. Special casing 'und' just doesn't feel right to me. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 29 September 2014 16:32:54 UTC