Comment 8 for bug 118789

That somebody was me by the way, I stumbled upon this issue while researching another property (PageRange) which is also a sub property of FilterData. Took me about 2 hours before I found B Marcelly's post mentioned above. I initially had some trouble finding out there was a PageRange property at all (for example it's not described in the spec linked above), however all properties seem to be listed in ImpPDFTabDialog::GetFilterData (see: http://lxr.go-oo.org/source/framework/filter/source/pdf/impdialog.cxx).

I was going to try and summarize the issue but since my experience with the UNO stuff is severely limited (to today) there's nothing I can add. Thought I'd at least take the time to post a patch for the previously attached ooextract.py. Here's the important snippet:

filterOptions = uno.Any("[]com.sun.star.beans.PropertyValue", (
    PropertyValue( "ExportFormFields", 0, False, 0),
),)

Notice how the uno.Any function is used to wrap the filterOptions tuple, or set the type to []com.sun.star.beans.PropertyValue (which I assume means an array of com.sun.star.beans.PropertyValue). B Marcelly explains the reason for this wrapping in this specific post over at the OOo forums (http://www.oooforum.org/forum/viewtopic.phtml?t=58792#233845).

I'll add a couple of keywords to this post so hopefully other people will stumble on this bug report when they're facing the same problems.

Keywords: writer_pdf_Export, PageRange, PropertyValue, filters, PyUNO

P.S.

Thanks to cl over at #dev.openoffice.org for his assistance with this issue.