[scribus] Empty text frame error when exporting a PDF form
goss at fstrf.org
Fri Oct 7 13:02:40 UTC 2016
I've entered issue #0014306 for this.
How would a PDF profile check work? Would there need to be separate profiles for PDF 1.5 and PDF 1.5 (form)? You'd basically need a "form version" of all the existing PDF profiles. That seems a bit overkill--I can't think of much that a PDF form check would do differently from a normal PDF check (other than ignoring empty text frame errors and possibly validating JS code attached to fields). For now, just making the existing profiles ignore empty text fields that are also PDF form fields is probably sufficient.
David Goss , Technical Writer
Frontier Science | www.fstrf.org
4033 Maple Rd, Amherst, NY 14226
(716) 834-0900 extension 7204
----- Original Message -----
From: "Craig Bradney" <cbradney at scribus.info>
To: "scribus" <scribus at lists.scribus.net>
Sent: Thursday, October 6, 2016 10:32:22 AM
Subject: Re: [scribus] Empty text frame error when exporting a PDF form
What we need is a form based PDF profile check.
> On 6 Oct 2016, at 14:44, Gregory Pittman <gpittman at iglou.com> wrote:
>> On 10/06/2016 08:28 AM, ale rimoldi wrote:
>>> On 06/10/16 14:17, David Goss wrote:
>>> When I export a layout that has PDF form fields on it, I get error
>>> messages from the preflight verifier about empty text frames. It then
>>> lists all of the PDF fields.
>>> This basically renders the preflight useless, because a real empty
>>> text frame error could be hidden in the list of false positives. Is
>>> there anything I can do to my text frames or an error checking setting
>>> to avoid these errors?
>>> Note: This happens with Scribus 1.5.2--if I recall correctly, this
>>> didn't happen when exporting the same PDF using Scribus 1.4.x
>> while your concern is correct and deserves a bug report (please fill one
>> : - ), i would say that if you're creating PDF forms you can almost
>> safely ignore all the warnings from the preflight verifier.
>> they are thought for the professional printing workflow (where you do
>> not want to notice a "frame error" when you get thousands of copies back
>> from the printer.
> As a.l.e says, don't take the warnings too seriously. It's worth
> scanning any errors just to make sure you're aware of them.
> I recently played a bit with a textfield form so that I could answer a
> question on the list, and encountered the same issue with an empty
> textfield frame. What was more concerning was that I couldn't seem to
> enter anything in the PDF form. What got around this was to put
> something in it -- it might be just a space. That way, you don't get the
> warning, and you shouldn't have any trouble entering info in the textfield.
> Scribus Mailing List: scribus at lists.scribus.net
> Edit your options or unsubscribe:
> See also:
Scribus Mailing List: scribus at lists.scribus.net
Edit your options or unsubscribe:
This message was secured by ZixCorp(R).
More information about the scribus