Copy link to clipboard
Copied
I have had a major glitch with InDesign, and I want to report it to Adobe, but I don't know how to. Does anyone know how to report to Adobe?
Copy link to clipboard
Copied
"how do I report a bug in InDesign"
But to file a bug report you’ll need to describe the steps needed to reproduce the bug. If the bug can’t be reproduced I don’t see how Adobe can provide a fix?
Copy link to clipboard
Copied
It may be even related to just a version of the CPU or OS...
@ZeroLJ and @leo.r - could you please specify your exact configurations? As detailed as possible.
I know it might sound crazy - but Google for "solar flare flipping bits in memory or cpu".
Here is a nice list of possible - and not so crazy - other possibilities:
https://www.google.com/amp/s/amp-blog.robertelder.org/causes-of-bit-flips-in-computer-memory/
Copy link to clipboard
Copied
At the time of the anomoly/issue which was 2-3 weeks ago, I was on OS Ventura 13.6 (the last update before Sonama), and am on a 2021 release 27" Intel iMac with 40GB RAM
Copy link to clipboard
Copied
It happened to a customer on a Mac several months ago.
Copy link to clipboard
Copied
I've actually seen this happen quite a few times. It's challenging to reproduce, but I bet it can be done; all it requires is an update to text rendering that would require stories to be recomposed. (Also to recreate my own experience of this, I'd need to repeatedly uninstall and reinstall obsolete versions of InDesign.)
I found it because I had a client who insisted 1) that all text frames be snapped to content, and 2) that I always update to the latest version of InDesign as soon as it was available. Now, I was unenthusiastic regarding instruction number two, but he was convinced that immediate update of all software tools was always advisable. (He was a computer security wonk, a paranoid Red Team stereotype.) So I was working on alternate format statements that included a bunch of SE Asian complex script lanugages - Khmer, Burmese, Lao, and Thai. The frames containing these stories were of course snapped to content as per client spec. Then an update came out - I couldn't tell you if it was 13.0 to 13.1 or 13.1 to 13.2, but I dutifully upgraded, finished my document, and exported a PDF without thought.
All of the text frames for the SE Asian languages overflowed, and I didn't get a warning from the PDF export tool, just as ZeroLJ describes. In troubleshooting the issue, I found that the way to fix the overset text was actually to Recompose All Stories. There isn't a menu item for it, so far as I know, but it can be found in the Text & Tables section of the Keyboard Shortcuts, with a default shortcut of Control + Alt + /. Whacking that shortcut caused the overset text to reappear.
ZeroLJ, you said in your second post that
My only suspicion is the InDesign did an auto-update between version 7 of my amends and the final artwork version, and this version altered the text boxes slightly (we are talking fractions here— I literally touched the text boxes in question, and the text re-appeared), BUT even if it did shrink the text box, it still didn't flag the 'over-set text' issue up at PDF stage.
I personally don't think it shrank the text boxes; my gut feeling is that it adjusted the leading, paragraph spacing, something along those lines. Periodically, we get warnings with new releases of InDesign that text might reflow; this is an example of that reflow. The fact that just "literally touching" the text boxes inclines me to believe that some action to recompose the stories is really what is called for.
I suppose you could check my hunch by figuring out when you applied the 18.5 update, and seeing if it was after your last edits to your version 7 but before you exported your final artwork. Like you, I was relying on the PDF export tool to inform me of overset text. I don't do that anymore; now I have a variety of preflight profiles, and I always look at it before export. I also always whack Control + Alt + / on every single document I touch that was not produced in the exact dot version of InDesign that I happen to be using. It only rarely causes visible reflow, but every time I see it visibly having an effect on what I'm working on - one doc out of twenty? fifty? no idea, it's unusual but not rare to see - I breathe a sigh of relief, and remember how bad Pagemaker was. I don't know if you were ever a Ragemaker user, but I had to use the hidden "diagnostic recompose" constantly to get around layout issues like this one.
Copy link to clipboard
Copied
P.S. Ok I looked up my email exchange with the customer who had the issue just to make sure I got everything right. It turned out that I didn't recollect some details precisely accurately but it still looks like it's a variation of the same bug. Here's the exact account:
The affected text frames were large price bubbles with only a few characters, for example a large "3.99".
When the issue happened, the text just entirely disappeared from the frames (so it was instantly obvious that the text is gone).
The overset sign did appear in the frame.
The frame dimensions did not change.
After using the "Fit frame to content" command, the text reappeared BUT the frame size still didn't change.
So apart from the overset text sign everything seems to be similar to the @ZeroLJ's issue. This difference may be related to the contents of text frames (multi-line text vs. price bubbles).
Copy link to clipboard
Copied
But as you've had overset "+" sign - it's completely different situation...
And you may think that size haven't changed after "fit" - but what you see is rounding up to 2 or 3 places - internally InDesign stores values with much greater precision - so you see "4.27 mm" but internally InDesign may have it as "4.2700004".
Or, to be even more precise - it stores values as Points and only converts for displaying in UI to "mm" - or any other unit ...
Copy link to clipboard
Copied
<post removed to re-check details>
Copy link to clipboard
Copied
@Robert at ID-Tasker : It's a valid point (even though in the case of inches InDesign rounds up the UI values to 1/10000 of an inch).
So I dug yet deeper and found that I still have the original InDesign files supplied by the customer. Two files: before (with text intact in the frame) and after (text missing).
I checked the visible bounds of the same text frame in both documents with a script. They are identical. With text, without text, and after applying the Fit frame to content command which reveals the text:
{5.133942498101, 0.631944681167, 5.560081422329, 2.159722458945} <- text intact
{5.133942498101, 0.631944681167, 5.560081422329, 2.159722458945} <- no text
{5.133942498101, 0.631944681167, 5.560081422329, 2.159722458945} <- after 'Fit frame to content'
Copy link to clipboard
Copied
Any chance you can share on priv those files for deeper examination?
Not sure if it would be easy for you to get automatically all properties of the object - in JS - but i could run it though my ID-Tasker and compare instantly all 700+ graphic properties + 400+ text.
Copy link to clipboard
Copied
Any chance you can share on priv those files for deeper examination?
By @Robert at ID-Tasker
If I get a permission from the customer to share a corporate font used in the file I'll share this frame with anyone who's curious enough to explore.
Copy link to clipboard
Copied
Hi @leo.r , If you run an InDesign Preflight on the Converted file does it catch the Overset instances?
Copy link to clipboard
Copied
Hi @leo.r , If you run an InDesign Preflight on the Converted file does it catch the Overset instances?
By @rob day
Yes, the overset instances are indicated and caught by preflight as expected.
That's the main difference between this case and the original report.
I, obviously, don't know for sure if it's a variation of the same bug or something different with certain similar symptoms.
Like I mentioned earlier, I can speculate that this difference is caused by the fact that in my case the entire text was pushed out of the frame, while other cases described in this thread involved only a small portion of the text. That's, again, just my speculation.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now