Tips for using PowerPoint (R Microsoft Corp)

with SVGmaker (TM Software Mechanics)

Pagination PowerPoint presentations of more than one slide are multi-page documents. With SVGmaker you can create a multi-page document as a single SVG file, or create one SVG file per page. The best approach to use can depend on what you are trying to achieve with your presentation and on the equipment your audience will use to view the presentation. If you store your presentation as a single SVG or SVGZ file you'll be able to easily move it, copy it, email it or post it on a server because you'll only be dealing with one file. For the pagination to work your document will require a JavaScript enabled viewing agent. Sample multi-page SVG output (requires JavaScript) [140 Kb] If your presentation gets so large that it takes a long time to load in the browser, or if you want your presentation to be accessible to non-JavaScript enabled viewing agents, print it one page at a time instead and use SVGmaker to create a two frame browser display of your document. The page index of your presentation will be in the left frame (HTML), and each slide (SVG) will be displayed in the right frame. Sample 1 file per page SVG output [average ~30 Kb per slide] By default, the HTML index will refer to each slide of your presentation as something like "Page n". Customize the index for your presentation by editing the HTML index file. In general, PowerPoint presentations of up to 60 or so slides perform acceptably as single file documents on average computers today. You will notice a longer load time as your document grows. The high efficiency of SVG for text (when gzipped as SVGZ) and the relatively low density of text in PowerPoint slides means that 60 slides of PowerPoint text isn't going to bloat your output file beyond the capability of most viewing agents today. If you end up with a bloated SVGZ representation of a PowerPoint presentation, the reason most probably will have to do with one or more of the Known Considerations with PowerPoint expanded on below. There may be something you can do about it.

Known Considerations with PowerPoint 1. Perpendicular gradient fills are much more efficient than diagonal gradient fills SVGmaker detects and encodes horizontal and vertical gradient fills a lot more efficiently than diagonal gradient fills. Use horizontal (most efficient) or vertical (ok efficiency) gradient fills instead of diagonal gradient fills (inefficient). 2. Transparent bitmaps can print bogusly PowerPoint may print transparent bitmaps in an inefficient way. The way is inefficient no matter what printer driver is used. For example (if you have some time on your hands), notice how slow the pages are displayed in this PDF file [502 Kb] when you page down. It is a consequence of the way PowerPoint prints transparent bitmaps. If you are using transparent bitmaps and you notice that your SVGZ file seems bloated or the load time is excessive, try using opaque bitmaps instead. PowerPoint prints opaque bitmaps OK. SVGmaker downsamples bitmaps to 96 dpi. 3. Swapping to Internet Explorer and back can hang PowerPoint We're not sure if this is still a problem for XP users of Office and Windows, but if you are using earlier versions of these products, don't swap between Internet Explorer and PowerPoint after printing. Because of an interaction between IE and PowerPoint, PowerPoint can stop responding. Close PowerPoint before using Internet Explorer. 4. Animations aren't supported SVGmaker prints each slide as a static page without animations or page transitions. Are you determined to use animations or transitions in your PowerPoint presentation? Well you're out of luck today, but If you can share a copy of your presentation please email it to animations05@svgmaker.com. 5. Mobil devices aren't supported Not yet, but... Do you have an SVG enabled phone or mobile device? Would you like to test Basic or Tiny output? Please send email with your information to mobile09@svgmaker.com.

Software Mechanics Pty Ltd
2003

Close this window