24.12.2007 02:33
<< Weekly Status Report, W51/2007 | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>
Specifying codecs for the web
You might remember the recent blog post about codecs for <video> we saw on Planet Mozilla recently. I immediately informed my favorite online magazine about open source, LWN.net, about this when I read it, as they and their readers usually are quite interested in anything involving open standards and patents.
A few days later, they ran an article called Specifying codecs for the web about this topic:
As it got public this week (the "weekly edition" is subscriber-only for 7 days), this should be also worth a read by anyone in the Mozilla community who is interested in the HTML5 <video> tag.
A few days later, they ran an article called Specifying codecs for the web about this topic:
Quote:
Audio and video content are increasingly important components of the World Wide Web, which some of us remember, initially, as a text-only experience. Users of free software need not be told that the multimedia aspect of the net can be hard to access without recourse to proprietary tools. So the decisions which are made regarding multimedia support in the next version of the HTML specification are of more than passing interest. A current dispute over the recommended codecs for HTML5 shows just how hard maintaining an interoperable web may be.
As it got public this week (the "weekly edition" is subscriber-only for 7 days), this should be also worth a read by anyone in the Mozilla community who is interested in the HTML5 <video> tag.
Beitrag geschrieben von KaiRo und gepostet am 23. Dezember 2007 19:40 | Tags: codec, Mozilla, patents, video | 1 Kommentar | TrackBack
Kommentare
| Autor | Beitrag |
|---|---|
Anonymous aus ... |  Even without recommended codecs, the video tag still provides a huge win if sites use it. Currently, sites that want to embed videos use an object or embed tag, which specifies a player to use (which does not necessarily correspond to one the user has or wants), or worse a Flash video player. With the video tag, browsers that favor what users want can easily use a well-integrated video player, and provide features such as better streaming, real full-screen support (not just full-page), better seeking, better local caching, and a download button. |