https://issues.apache.org/bugzilla/show_bug.cgi?id=47311
--- Comment #28 from Peter Coppens <[email protected]> 2009-07-28 06:46:26 PST --- > > > > > > fox:crop-box: (trim-box|bleed-box|media-box) > > > Default: media-box > > > The crop box controls how Acrobat display the page or how the > > > Java2DRenderer > > > sizes the output media. The PDF spec defines that the CropBox defaults to > > > the > > > MediaBox, so it makes sense to do the same here. We could define a > > > fox:crop-box > > > extension which could take three "magic" values: "trim-box", "bleed-box" > > > and > > > "media-box" to set the CropBox to one of those three other boxes. That > > > should > > > cover 95% of all use cases. If anyone needs more control, that could > > > easily > > > added later. > > > > I'm really not sure about that one. Calling it 'crop-box' is likely to > > create > > confusion with the 'crop-offset' property above. Apparently the CropBox is > > not > > used in prepress at all, so I would suggest to forget about that for the > > moment. That is, make the CropBox match with the MediaBox. > > Yes, I thought about that naming closeness, too. Not sure if that's so easy to > resolve. If Peter is OK with this, I guess the fox:crop-box could be left out > for the moment. I personally don't need it although at some point, such a > property might be useful to some. > > <snip/> Hmmm...not entirely happy with this unfortunately. We have a webapp that using a flex wysiwyg editor allows creation of print materials but that uses adobe's pdf browser plugin for end-user proofing and approval. In some cases we'd rather display the trimbox iso the mediabox so my guess is we should be able to control the CropBox setting, no? Perhaps a name change for the attribute is sufficient? E.g. something like crop-box-selector, or crop-box-source or something similar? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
