Scott Keeney
My feedback
4 results found
-
31 votes
Hi,
We are unable to reproduce the issue in-house.In case you have some consistent steps to reproduce the issue from scratch, please feel free to send a mail at amaarora@adobe.com or start a new thread on this portal
Thanks
An error occurred while saving the comment An error occurred while saving the comment Scott Keeney
commented
Hi Aman,
Thanks for the offer. I guess you don’t recognize me. I already provided you a file earlier this year. In fact, I followed up with you just a month ago and you replied to me that “[Adobe is] looking into the problem but currently it is not at high priority. In case you can find a pattern or consistent reproducible steps, we can reprioritise the issue for fixing.”But in my bug report here I gave the only known way that the problem has been reproduced.
To be clear: We first found (and reported on the Adobe forums) this problem in CS5 in 2011. The problem happened at a remote office from our headquarters and initially we could not reproduce the problem here. The problem proved not to be any of the things we thought it might be: Mac OS version, ID version (original problem was in InDesign 7.0.0.355 and we hoped updating to 7.0.3 would resolve it, ha), font management software, Quark 7 being on same Mac, postscript font, etc. The Mac that we eventually reproduced the problem on in 2011 was basically out of the box (I can’t confirm 100%: it was 8 years ago and I did not personally setup the Mac and was not the one spending the time to force the issue to happen, but I was nearby), and it was done using a brand new file with no content other than a small bit of text in Adobe Garamond Pro. The problem has reoccurred, albeit less frequently, in every version of InDesign we’ve used since.
Clearing caches and rebooting Mac before opening a new file helps. (The bug has not been known to happen when doing this step before opening/making any new file.)
Turning off ligatures “fixes” the bug because InDesign seems to be for some reason trying to make ligatures out of pairs that have no business being a ligature. Known problem pairs include hn, hk, io, il, sy, ek, & eh.
The workaround for someone who wants to set ligatures but avoid chance of having this problem is to use a GREP style to apply ligature setting where it is needed, e.g., fi, fl, Th, ct, whatever.
Anyway, thanks for offering to help again. If I can secure rights from one of our clients to share another one of our files where we saw the problem, I will send your way.
Scott Keeney
supported this idea
·
-
18 votes
An error occurred while saving the comment Scott Keeney
commented
Agreed. Endnotes should have the option to restart by Section just like Footnotes.
Scott Keeney
supported this idea
·
-
15 votes
Hello All,
Thank you for reporting the issue to us.
We have fixed the issue in the latest version of InDesign, Id 15.0Please upgrade your InDesign application to the latest version to try out the fix.
If you face any problems with the new update, do let us know in the comments.
You may also follow the below given link for the list of all fixed issues in Id 15.0
https://helpx.adobe.com/indesign/kb/fixed-issues.html-InDesign Team
An error occurred while saving the comment Scott Keeney
commented
This is a serious bug that has been evident for years and still is present in CC2019. When will Adobe address this.
Scott Keeney
supported this idea
·
-
1 voteScott Keeney
shared this idea
·
To help Adobe with clarity as to the issue, I would ask the Anonymous poster who said the issue was only found in the Interactive PDF if they can truly confirm that that is the case?
With this bug you cannot go back into the InDesign file at a later time and expect to see the same result as seen in whatever PDF was created.
The problem is commonly thought to be in a PDF export process because the PDF is where the problem first becomes noticed (how many people are doing cold reads exporting?), but if you setup a process to monitor for this issue I'm pretty sure you'll find that the problem is happening in the InDesign file before the PDF export.
It is not a corruption of the ID file—it is an InDesign bug—so you will not necessarily see the issue when you open the ID file to review why your PDF is all screwed up.