Re: [Swftools-common] Passing swf in stdin/pipe to swfdump

[Romi Kuntsman]

Isn't it possible to read from stdin into a buffer in memory, then
determine it's size, and then go over the data in memory?

On Sun, Aug 26, 2012 at 3:01 AM, Matthias Kramm  wrote:

> On Tue, Aug 07, 2012 at 03:30:20PM +0300, Romi Kuntsman 
> wrote:
> > I'm handling a SWF file in memory in my program, and would like to pass
> the
> > file to swfdump and read the output.
> > How can this be done without writing it to a temporary file on disk and
> > then passing the filename as parameter, for example using a pipe or
> similar
> > option?
>
> Afraid that a temporary file is the only way to do this-
> in its current implementation, swfdump reads the file twice- once
> to determine the file type, and a second time to actually parse,
> so it can't process a stdin stream for that very reason.
>
> Matthias
>
> ---
> SWFTools-common is a self-managed list. To subscribe/unsubscribe, or amend
> an existing subscription, please kindly point your favourite web browser
> at:
>
---
SWFTools-common is a self-managed list. To subscribe/unsubscribe, or amend an 
existing subscription, please kindly point your favourite web browser 
at:

Re: [Swftools-common] Rendering glitches with flatten and ignoredraworder

[Tim Whittington]

- Original Message - 

> From: "Matthias Kramm" 
> To: swftools-common@nongnu.org
> Sent: Sunday, 26 August, 2012 11:50:50 AM
> Subject: Re: [Swftools-common] Rendering glitches with flatten and
> ignoredraworder

> On Tue, Aug 07, 2012 at 11:57:04AM +1200, Tim Whittington
>  wrote:
> > I've observed a couple of glitches when rendering a PDF with the -i
> > (ignoredraworder) option, one of which occurs when it is combined
> > with
> > -G (flatten).

> Well, the whole point of -i is that it allows pdf2swf to do
> destructive
> changes to the layout in order to achieve a minor speed increase.
> It's a pretty old option, and you probably shouldn't be using it
> anymore, unless you have some very good reason. (If so, I'd like to
> hear
> what it is)

In my case it was playing with options to reduce the number of shapes in the 
generated SWF - the conversion in this case blows out the 65k limit on the PDF 
I referenced (at page 245 of 208) unless -i is used. 
If it's not a recommended option, I'll look at generating one SWF per input 
page for larger PDFs instead. 

cheers 
tim 

---
SWFTools-common is a self-managed list. To subscribe/unsubscribe, or amend an 
existing subscription, please kindly point your favourite web browser 
at: