We have FrameMaker 2-17 Paragraph Formats for Figures and Tables.
In FrameMaker these are just fine in FM2017 as they were in FM12.
However, when we generate a PDF from any document or book from FM2017, then there is an additional graphic added to every Figure or Table name. This is creating a noticeable CHANGE in each and every book that we PDF from FrameMaker. This shows up in compares and will trigger change notifications in all of our translations.
See below the image of an extra line that shows up on each FIGURE and TABLE name. This was never the case in FM12 to PDF conversion.
Our documents are worldwide and require translation, and this kind of issue will increase our translation costs exponentially.
We need to hear that someone is addressing this issue ASAP.
Copy link to clipboard
That looks like an on-going bug from the previous version, where underlines where appearing as part of the auto-number for the non-printing tab-character. You're seeing the overline at the tab character at the start of the "O".
Please report this bug using the Tracker database: https://tracker.adobe.com/#/home
Did you specify the "Compare Text Only" option in Acrobat for the comparisons? IIRC, this should ignore any overlines/underlines.
Have you tried doing the compares in FM?
thanks for your input!
we'll report to dbase...however it was not allowing logins today.
We've done the compare in FM and no issue.
It seems to be an issue only when going from FM to PDF (or .ps with distiller).
I just ran a PDF compare to compare ONLY text. RESULT: yes, that overline is still there visually (because it is in FM2017 PDF generation), but is not picked up in the compare to the FM12.
Thanks for your discussion...we'll await...
What browser are you using? I have not been able to log on to Tracker with Internet Explorer for some time. No problem with Edge.
Works with Chrome and Firefox for me.
We have been working with Adobe TCS support and we have a temporary solution: Using the SAVE AS PDF and the CMYK option was selected. (do not use print to .ps or use distiller)
Here is our team’s most recent
*BOOK Saved as PDF locally on
*A PDF window with options appeared
and ensure the CMYK option is selected.
*I pressed Set.
Just for fun, I Saved as PDF
again. This time I changed the setting to RGB.
Result: Not good. issues reappeared.
Next, I used the same book but
Saved as PDF with CMYK selected from the NETWORK release patch folder.
So, we have determined SAVE AS to PDF with CMYK selected works for
both a singular doc and a book, and works locally as well as across the network.
If this is the “fix”, we need clarification on this. And it may require our release process to change. I am
sure others have used .ps/distiller as well (and often if they teams have set up scripts for their document release process, this could require updates for their tools).
THIS IS NOT FULLY RESOLVED, YET. We consider this a workaround.
I love the end of your post!!!
Aren't our careers themselves dedicated to creating workarounds for our "current condition"?
FYI, the SaveAsPDF route using CMYK still uses Distiller and .ps, you just don't see what's happening (same as for the RGB route).
The CMYK route uses a different postscript header (based upon the older Unix Level 1 postscript and is hard-wired into the FM code). The RGB route uses an external ps header file [that a knowledgeable user could modify to make specific "adjustments"].
FM writes a temporary postscript file (.tps), calls a few post-proessing routines to go over the .tps file (these routines can be disabled in the maker.ini file) and then hands the .tps file over to Distiller. When Distiller finishes, it returns control back to FM.
Copy link to clipboard
Are omitting the overline, or using a Frame Above options until the "bug" is resolved?
I am trying to insert overline text into photoshop cc 2020 but no can do today