PDF Validator

[murrjames]

Does anyone know of a PDF validator on-line. I use PAC 2 but I am getting a weird error and it stops testing. the error is

Error while parsing the PDF Document (name too long (6677))

This is the file name;

Registration_Form_Pers_Production-engAug22.pdf

I have had longer names and they pass. any ideas?

[gkaiseril]

What is the full path name?

Many OS's have a path and file name length limit.

[murrjames]

C:\Users\gghjghjgh\Downloads\bhkjhhkgbhk\Registration_Form_Pers_Production-engAug22.pdf

[gkaiseril]

This sounds like your accessibility checker error. Can you get a more detailed explanation for your checker?

Have you checked that all characters in you file name are valid for accessible document file names?

[murrjames]

All characters are valid.

I tried this path as well, same error.

E:\Registration_Form_Pers_Production-engAug22.pdf

[George_Johnson]

Note that it doesn't say "file name too long", so I think you may be looking at the wrong cause. The term "name" in a PDF has a specific meaning that you can read about in the PDF specification. This could be what that message is referring to. The maximum length of a name in a PDF is (usually) 127 bytes.

[murrjames]

You are correct, there are brackets separating that.
Error while parsing the PDF Document (name too long (35404))

Can you clarify this: The term "name" in a PDF has a specific meaning that you can read about in the PDF specification.

I may know different terminology, but what do you mean Read PDF Specification?

[George_Johnson]

The PDF specification (aka PDF Reference) can be found here: PDF Reference and Adobe Extensions to the PDF Specification | Adobe Developer Connection

See section 7.3.5 and Table C.1 for more information.

[MichaelCooperEliquo]

This is a very late reply, but I had the same issue just now and was finally able to troubleshoot to narrow it down and solve it. The "name" is referring to a property name or value, not the filename (as George_Johnson mentioned). The number is the object reference in the PDF stream (which you are unlikely to find, so not very helpful). In my case it was a radio button that had lengthy value text. I shortened the value text and voilà!

My troubleshooting method:

1. Extract all pages separately and run them through the PAC (ignore all errors except the PDF syntax error).
2. On any pages with the PDF syntax error, delete all form fields and if it passes the PAC you know it's the same issue as mine (lengthy text on a form field property such as name, tooltip, or value) - If you have no form fields, you will have to delete content until it passes the PAC to find the offending tag/container/content
3. Replace the offending content (for form fields, copy/paste them back in one at a time from the original form to find the one that "breaks" the PAC, then check the properties and shorten any lengthy text; for content, check the tag/container properties and shorten any lengthy values such as alt text, titles, etc.)
4. Once you have all the individual pages passing the PAC PDF syntax error, merge them back together, clean up the tags and add doc properties (title, lang, PDF/UA identifier, etc.), save and run the PAC (repairing any final errors), and you should be good

Hope this helps you too, or anyone who finds this thread like I did by searching, "Error while parsing the PDF Document (name too long)".

Not enough documentation on these PAC errors!