I believe the right way is to develop on HTML5 for everyone involved, and these are my five reasons why it is better to Flash:

1. It is native. No need for plugins , extra amenities or load external components to the browser. Flash, unfortunately, being heavy and often need to consume so many resources faster the battery and use a large percentage of the processor.
2. It does not belong to anyone, is a markup language that can be used by anyone and is supported by all modern browsers. Flash, however, is the owner, serves the interests of one company, Adobe. May be altered to taste them if needed (for whatever reason, economic, by company policy, etc.)
3. Maintains the overall user experience the web, run the previous and next buttons in the browser, does not operate within a “sandbox” as with Flash, is not limited to the area assigned to the plugin.
4. All items with all effects and all hierarchies needed to build a fully functional graphical interface to support a web application is 100% possible using HTML5 + CSS + Javascript. Flash was used as a replacement. Gmail is the perfect example. Even more so if viewed from a mobile device. Did you know that the version of Gmail for IPAD is much higher than the native application made by Apple?
5. Adaptable, flexible, scalable platform. While insisting Adobe, Flash on mobile phones remains a goal too far, meanwhile build interfaces for the desktop or the mobile is quite real today on the two platforms.

Is there hope for Flash? Of course, but not in the platform development of applications or in building web sites made of 100% with this plugin. I think that Flash works well for games and animation elements for certain very particular, very far away from this “solution for anything” that Adobe (or Macromedia before being acquired) tried to sell for years.

Share on Facebook

<video src="http://example.com/video.ogv" controls>
<text category="CC" lang="en" type="text/x-srt" src="caption.srt"></text>
<text category="SUB" lang="de" type="application/ttaf+xml" src="german.dfxp"></text>
<text category="SUB" lang="jp" type="application/smil" src="japanese.smil"></text>
<text category="SUB" lang="fr" type="text/x-srt" src="translation_webservice/fr/caption.srt"></text>
</video>

As we can see in the above code, we would be including the text tag that would allow us to establish the lang attribute of the subtitle language and select it from your control in your browser (the preset default language of your browser) .

The tag <text />
Only indicate the location of the subtitle file to load src indicating the language lang and type type of a subtitle that we carry.

For now …
At the moment we can make use of SRT jQuert to simulate the result with Javascript.

<!-- Javascript -->
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="jquery.srt.js"></script>

<!-- HTML  -->
<video src="http://example.com/video.ogv" id="video" controls>
<div class="srt"
data-video="video"
data-srt="http://example.com/video.srt" />

The idea is interesting when the films arrive officially to the Internet. Huh?

Share on Facebook

External Link: What is HTML5 via WiseCodes

Share on Facebook

New Elements

HTML 5 provides a number of new elements and attributes that reflect the typical use of modern web sites. Some of them are technically similar to the labels
<div> and <span> but have a semantic meaning, eg <mav> (block site navigation) and <footer> Other elements provide new functionality through an interface such as elements <audio> and <video>
Some elements of HTML 4.01 are obsolete, including purely presentation as <font> and <center> whose effects are handled by the CSS. There is also a renewed emphasis on the importance of scripting DOM for behavior on the web.

HTML 4

HTML 5

External Link: via W3C

Share on Facebook