Hans, the attached file contains the corrections of two typos and the addition of a (in my opinion, much needed) pair of commas.
I hope it helps, Pablo -- http://www.ousia.tk
--- mkiv/lpdf-wid.lua 2018-07-02 14:45:34.000000000 +0200 +++ lpdf-wid.lua 2018-07-02 19:41:11.766997567 +0200 @@ -10,12 +10,12 @@ -- First we had movies and sound, quite easy to deal with, but obsolete now. Then we -- had renditions but they turned out to be unreliable from the start and look -- obsolete too or at least they are bound to the (obsolete) flash technology for --- rendering. They were already complex constructs. Now we have rich media which --- instead of providing a robust future proof framework fo rgeneral media types --- again seems to depend on viewers built in (yes, also kind of obsolete) flash +-- rendering. They were already complex constructs. Now we have rich media which, +-- instead of providing a robust future proof framework for general media types +-- again, seems to depend on viewers built in (yes, also kind of obsolete) flash -- technology, and we cannot expect this non-open technology to show up in open -- browsers. So, in the end we can best just use links to external resources to be --- future proof. Just look at the viewer prferences pane to see how fragile support +-- future proof. Just look at the viewer preferences pane to see how fragile support -- is. Interestingly u3d support is kind of built in, while e.g. mp4 support relies -- on wrapping in swf. We used to stay ahead of the pack with support of the fancy -- pdf features but it backfires and is not worth the trouble. And yes, for control
_______________________________________________ dev-context mailing list dev-context@ntg.nl https://mailman.ntg.nl/mailman/listinfo/dev-context
