You are embedding full fonts ( --fonts ) in the swf. Thye are being temporarily cached on first run ( as you so rightly guessed ). Use one of the levels of verbose, say -vv,
pdf2swf.exe -vv --fonts --stop --flashversion 10 shed.pdf -o output.swf and/or output to a file, pdf2swf.exe -vv --fonts --stop --flashversion 10 shed.pdf -o output.swf > log_file and you should see what is actually happening. HTH. Regards, Chris. On 20 February 2010 20:43, Matt Long <[email protected]> wrote: > I came across a PDF that took around 30 seconds to process with pdf2swf > within my app. This was curious since it was a single page PDF (granted with > a lot of graphics on it). > I ran pdf2swf manually on the command line to verify the time. The first > time I ran it on the command line, it took a similar ~30 seconds to convert. > However, I ran the conversion again (with the same parameters) on the > command line a few minutes later and it finished almost instantaneously. Now > every time I run it, it's speedy and I'm unable to reproduce the 30second > runtime. > I assume something is being cached somewhere after the first run. Even if I > change the input file name and move to a different directory, it's still > runs quickly. Can someone please explain what's going on here? > I observed the same behavior on my desktop (fairly powerful Windows 7 > machine) and a virtualized Windows Server 2008 machine. > I'm using pdf2swf v0.9.0 > Here's my command. > pdf2swf.exe --fonts --stop --flashversion 10 sched.pdf -o output.swf > PDF in question is available > here: http://www.caltrain.com/pdf/Holiday_Schedules/Caltrain_Weekend_Holiday_Schedule_08-31-2009.pdf > > Thanks! > Matt > -- > Matt Long > Lead Developer > 650-963-942 > webnotes.net >
