diveintomark / diveintohtml5

Dive Into HTML5 online book
https://diveintohtml5.info/
Other
777 stars 187 forks source link

Remove Theora as a suggested encoding option? #8

Closed Hooloovoo closed 11 years ago

Hooloovoo commented 13 years ago

I hate to dare mention it, but I was reading: http://diveintohtml5.info/video.html and the statement that: "For maximum compatibility, here’s what your video workflow will look like:

Make one version that uses WebM (VP8 + Vorbis).
Make another version that uses H.264 baseline video and AAC “low complexity” audio in an MP4 container.
Make another version that uses Theora video and Vorbis audio in an Ogg container.
Link to all three video files from a single <video> element, and fall back to a Flash-based video player. "

I wonder if this should be revised to simply recommend WebM and H.264, with a Flash fall-back (as an aside, it would probably be worth mentioning that the Flash fallback can use the H.264 video). As far as I can see, the only users that would need Ogg Theora are people on FF3.5 or Opera 10.5--and those users are very likely to have already upgraded to later versions (as they are normally more tech-savvy users).

mfn commented 12 years ago

Hello,

if you read the whole page, you'll find multiple mentions of FF 3.5+ and considering that it's written "For maximum compatibility" it is the only right answer.

If you suggest to remove this codec, you'd have to rephrase the "Maximum compatibility"-phrase and/or remove the references to the older browsers.

I'd suggest in respect of a "reference book" this things should be kept in. Everyone reading this guide thus can choose for himself whether FF 3.5 counts or not.

Just my 2c.

jonathantneal commented 11 years ago

I understand the perspective, and I updated the language to reflect the current landscape. I think you'll both find these changes quite reasonable. If not, feel free to reopen.

https://github.com/diveintomark/diveintohtml5/commit/a58f25e50cc8a8b0c04434b498c9199105bca367