I am on an iMac running Mojave. Since I am a graphic artist, I create large Illustrator files that need to be converted to PDFs and emailed for proofing. However, when the files are optimized through Adobe Acrobat Pro DC, the resulting PDF has numerous white lines running through it. I would like to see a quick, efficient way to reduce files that are around 100mgs and still be sharp, clean files with no lines. I understand that they don't print, but my clients always question them and are skeptical when I try to explain that the lines won't print. Please help! I have tried EVERYTHING and the minute I get the file small enough to email (10 - 13mgs) the lines come back.

The 3rd of several problems in how PDF Maker (and InDesign's export to PDF utility) tag PDFs.

In complex tables (that is, a table with multi-row column headers, multi-column row headers, merged cells, or sub-headers in the middle of the table)...

1. Each <TH> must have a unique header ID, and

2. Each data cell <TD> must be associated with one or more header IDs.

This is required per the PDF/UA-1 accessibility guidelines, and is outlined in the Tagged PDF Syntax Guide, Sec. 5.4.1 (the Syntax Guide is available for free from https://www.pdfa.org/resource/tagged-pdf-best-practice-guide-syntax)

At this time, we can autogenerate the Header IDs (Table Editor / right-click on any cell, select Autogenerate Header Cells ID). Thank you for that, Adobe!

But we need the other half of this requirement: auto-associate each <TD> table cell with one or more Header Cell IDs. It's difficult and very time consuming to manually make these associations on long tables, plus former shortcuts that let us select multiple cells and apply an ID have now failed. See this Forums post https://community.adobe.com/t5/acrobat/accessibility-of-tables-does-it-have-to-take-hours/td-p/12143085.

This is a failure of Acrobat and along with missing Scope and Span on the header cells, causes most tables to fail accessibility checkers and take an inordinate amount of time to fix manually. (See scope and span at https://acrobat.uservoice.com/forums/590923-acrobat-for-windows-and-mac/suggestions/41399425-pdfmaker-set-the-scope-row-span-and-column-span )

Expected Outcome:
That after running a utility for tables, the tables have not just Header IDs (already there), but the association to the <TD> data cells.

And, of course, Scope and Span, too.

2 of several problems in how PDF Maker tags tables.

Extra unnecessary tags are created by Adobe's PDF Maker plugin for MS Office. These tags cause the PDF to be inaccessible. See the attached screen captures of a PDF from Word 365 with PDF Maker 21.5.80.

The unnecessary <P> holds Path Path graphic data for the borders around each cell in a row.

No human being wants to hear Path Path Path Path Path Path Path Path Path Path Path Path Path Path when they access each table row. Screen readers voice the content of these tags, which is what a screen reader is supposed to do.

From PDF Maker for Office, a <P> Path Path tag is placed at the start of each <TR> row.

( KUDOS, you corrected tables from Adobe InDesign's built-in export utility, which used to create an <Artifact> tag (not the artifact attribute) with Path Path graphical data.)

Problem:

PROBLEM: it causes Path Path Path Path Path Path Path Path Path Path Path Path to be voiced each time the tag is encountered in the table.

THEREFORE, remediators must locate each instance of this tag (one for each row of every table) and manually artifact it the correct way. Such a time-waste.

EXPECTED RESULT:
These <P> and <Artifact> tags with Path Path Path Path Path Path Path Path Path Path Path Path should never ever appear in the tags tree at all, and are correctly artifacted out of the way for screen reader users.

Using Abobe Acrobat Standard 2017 - Version 2017.011.30169

MS Office 2013

The issuse occurs when using the Create PDF tool with MS Word and MS Excel files. You pick your file > Create > get an error from Adobe PDFMaker "An unexptected error occured. PDFMaker was unable to produce the Adobe PDF."

The file is then silently held open in 'read only mode' and you have to kill WINWORD.exe or EXCEL.exe in task manager to release the file.

In Word/Excel File > Save as Adobe PDF works and Printing to Adobe or Microsoft PDF works. Seems isolated to CreatePDF tool.

We've reinstalled Adobe. repaired Office, reinstalled Office, updated c++ redistributables, recreated local profiles, tested on newly imaged laptop. We always get the error. The printing options are an acceptable workaround, but we have some people that like to use the create tool

I just purchased a brand new Dell with "supposedly" current version of Adobe Acrobat.

I learn today that the version installed by Dell does not include the global preference setting to set file name instead of document title.

This is EXTREMELY frustrating lack of a basic setting. Why would anyone think that the user's preferred name for a document is less relevant than where ever it came from.

I can have hundreds of documents that need to be submitted in very short periods of time and now I have to go in and change each and every one to show the file name in order to differentiate it from all the others.

I see in responses to other similar bug reports that this issue is supposedly fixed ....yet the version I just purchase (May 2021), does not have this feature.

Please tell me you have a patch/or something i can easily get to fix this. My version code is 2020.001.30025