This content has been marked as final. Show 2 replies
I suppose I should preface what I'm about to say with the simple fact that I know how to say "SVG" and that's about it. If I'm understanding you correctly, a SVG is a scalable vector graphic? I've never used these, but somehow always assumed they were like .GIF, .JPG or other image formats and we inserted them as we do images. The fact you mention "EMBED" makes me think that perhaps they must be inserted like Captivate movies are.
I'm totally lost as far as your mention of something called EOLAS? When I first saw the post, I figured EOLAS was someone you were replying to. What is it? Looks like an acronym for something.
You can get more information of the XML based Scalable Vector Graphic or SVG at:
EOLAS refers (as I understand it) basically to a one man company that patented the technology for embedding plugins within browsers. Anyway, EOLAS filed suit for patent infringement and now IE (as of this year) has changed their browser in response. What this means for you and me, is that we can not embed Flash, SVGs and other plugins into an HTML page and have it be interactive from the start. There is now a "Click here to activate this control". So, I had to find a work-around to allow a RoboHelp based IETM or Interactive Electronic Technical Manual, to be fully functional from the start. Who wants to click on an SVG twice to see roll over effects and pop-up menus. I know my clients don't. I hear that Dreamweaver has been updated to 8.02 to compensate to the new changes to Internet Explorer. It looks like the Adobe folks have made applicable updates to some of the other Adobe/Macromedia products too. I hope that they will incorporate a patch/update to RoboHelp X5 (or X6?) to deal with this issue. As it stands now, to bypass this issue, I am doing the following:
1. Create and store SVG (i.e Intro.svg) in graphics folder.
<!-- HTML File -->
<body leftmargin=0 topmargin=0 scroll=no>
That's what I use for now and it eliminates the "Click here to activate this control" message and avoids using the "EMBED" tag in the destination HTML page.
If anyone can give me some insight on the legalities of the "EMBED" (also "APPLET" and "OBJECT") tag, then I would be very appreciative. It would seem that we all need to make the changes, else why is Microsoft (makers of a web browser) and Adobe (makers of products that create web pages) changing their applications around this EOLAS agreement.
I wonder also if this issue extends to all browsers in general (i.e. Firefox, Opera, Netscape, Sea Monkey, Safari) or only to Internet Explorer (IE).
Thanks for any insights.