Dan Kerr
My feedback
2 results found
-
216 votes
Fix for this issue is available in the latest InDesign 2026 release (21.2.0.30), please update to this release from CCD app.
--
Adobe InDesign team
An error occurred while saving the comment An error occurred while saving the comment Reporting that we are observing this issue as well. We use InDesign in a high-volume environment with a high degree of accuracy required. If staff are uncertain if a step has been undone and can't monitor their work through the history panel, that introduces a significant chance for error or lost work which would need to be redone. Our interim process is to save a copy of the document after each major step but that introduces its own potential for version conflicts etc.
-
109 votesClosed: Not Reproducible ·
AdminSanyam Talwar
(Senior Lead Software Engineer, Adobe InDesign)
responded
To identify the cause of this issue, we started our investigation to resolve it. You might have also received an email from us seeking more details to help in our investigation.
We’ve concluded our investigation and came up with the following: Either the issue is fixed in the latest release of InDesign or the issue was intermittent at the time of its reporting and is not reproducible now.
We recommend you upgrade to the latest version of InDesign 2026(v21.0.0.192) as it is more robust and contains a lot of bug fixes.
We seek your support in our continual effort to improve InDesign.
—
Adobe InDesign Team
An error occurred while saving the comment We are encountering this issue using the HTML (Legacy) export feature. Unfortunately, it appears to be somewhat random what character gets replaced. For a while it was a lowercase 'u' and now it is uppercase 'P'. Same file but after modifying the export tagging class names to try to fix the problem. I am on the latest InDesign 20.2 x64.
As with most commenters here, we're trying to use this feature in a high production workflow. We'll be generating 10 to 20 files a week using this feature. We'll need to spend extra development time creating a scripted/XSLT solution to this issue!
Just making a request for an update from Ravi Kiran or the admin team on what the expected timeline is for the release of the version with this bug fix. As a few others have already said, many organizations, ours included, will not widely deploy prerelease software to production teams. It would be great to be able to tell the affected staff that the solution is coming in days, weeks, next month or?
My thanks to the others who have been able to test the prerelease version and report back. That's helpful for the rest of us stuck on the release cycle!