Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
0

Bug Report: No error message if filepath too long and cuts off filename

New Here ,
Oct 06, 2020 Oct 06, 2020

Copy link to clipboard

Copied

We have a customer which, Using Acrobat Reader, does not receive an error message upon saving a file to a location with a long path, but Acrobat cuts off the filename after the 255th character (including path) without warning or notice.

This is not an issue with the filesystem, as the file can be renamed to be longer without issue.

 

TOPICS
Crash or freeze , General troubleshooting , Windows

Views

3.9K
Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Oct 06, 2020 Oct 06, 2020

Copy link to clipboard

Copied

This has been answered before, and I think that even when there are correct answers out there in these forums, the topic itself is somewhat confusing.

 

For starters, Adobe Acrobat or Reader do have a limitation in filiesize length (which include punctuations and some special characters, but this is not recommended) plus the file path length.

 

It limits to 255 charachters length for filename plus the file path together.

 

Since you mentioned that the issue is not manifesting in Adobe Reader, in which version of Adobe Acrobat Pro is this happening?

 

And when you say that Acrobat Pro truncates the filename, does that mean that Acrobat is connecting to the same network server to open the same file as the user that is using it with Reader ?

 

Or,

 

Is this happening because the user is sharing the file directly from his computer with other users that have Acrobat?

 

Or, are you saying that both programs, Acrobat Pro and Reader are opening the same file in the same computer? If yes, what is the operating system?

 

From what you've  explained it gives the impression that this is happening after the fact

that the file is Saved As from Reader. In which case, Adobe recommends to limit a filename to no more than 8 characters when performing PDF file creation.

 

This explained in page 158,  "Chapter 3: Creating PDFs " of the Adobe Acrobat DC Help.

 

 

See this part:

 

  • Creating PDFs - Click Open to convert the file to a PDF. Depending on the type of file being converted, the authoring application opens automatically, or a progress dialog box appears. If the file is in an unsupported format, a message appears, telling you that the file cannot be converted to PDF. 5 When the new PDF opens, choose File > Save or File > Save As, and then select a name and location for the PDF. Note: When naming a PDF that’s intended for electronic distribution, limit the filename to eight characters (with no spaces) and include the .pdf extension. This action ensures that email programs or network servers don’t truncate the filename and that the PDF opens as expected

 

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 07, 2020 Oct 07, 2020

Copy link to clipboard

Copied

LATEST

Thanks for the reply ls_rbls, but the issue is the lack of an error message when trying to save a file which goes over character limit.
Instead of providing an error message en needing you to provide a different path/filename, it truncates and saves the file without extension and missing part o/t filename.

 

We're trying to educate the users, but this is an issue which needs a fix, not a workaround.

 

Some more background:
A file is opened from within an application, which launches Reader to open the file.
The User then selects Save As and tries to save it to a network location. The filename+path is too long, but there is no error message, but the name is truncated and missing part o/t name + the extension.
The customer in question is a government body with certain naming policies resulting in ridicilously long file-/pathnames.
This issue has been raised, but the still leaves Acrobat Reader performing abysmally leading to documents not being readable.
File cannot be opened after adding the extention manually, so Reader is writing a corrupt file.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines