Stephan Möbius
My feedback
46 results found
-
1 vote
Please send the following information to sharewithID@adobe.com :
- Reproducible Steps – What were you doing when the issue occurred?
- Video recording of the issue
- Is(Are) the issue related to a specific document(s)/asset(s)? If yes, could you provide us with the document(s)/asset(s)? Please package the entire document (To package the document, choose File → Package…)
Also provide answers to follow queries
1. During IDML workflow , are you opening the indd containing flex in version 20.0-20.5 or you are opening the IDML in version 21.0 onwards?
2. What type of objects / images you are using?
3. are you grouping the items or creating nested flex frames?
4. You are only using object style to flex items or through any other menu?
An error occurred while saving the comment Stephan Möbius
shared this idea
·
-
1 voteStephan Möbius
shared this idea
·
-
681 votes
MathML support was added to InDesign 2025 version.
Work on adding more options in future releases of InDesign has started.
--
Adobe InDesign team
An error occurred while saving the comment Stephan Möbius
commented
What font is Indesign using to render the MathML formulas please?
-
11 votes
An error occurred while saving the comment Stephan Möbius
commented
I have the feeling this has finally been fixed in Indesign 20.1. I just come from a workflow with the dreaded sticky notes and noticed no slowdowns. :) Hooray.
An error occurred while saving the comment Stephan Möbius
commented
Problem still persists in 2024, Indesign (19.5). The PDF-comments workflow is still unbearably slow for sticky notes. It takes several seconds, after i clicked on an item in the PDF Comments Panel, for Indesign to regain responsiveness and to jump to the page with the comments marker. It's different for text-correction comments, like insert-text-comments, or replace-text-comments – these work fine! - but for regular arbitrary placed notes it slows Indesign to a crawl. If i delete all notes PDF comments on the active spread Indesign regains speed.
An error occurred while saving the comment Stephan Möbius
commented
I have this problem in Indesign 18.3 lately and also had this in the update before that. I have this PDF-comment pannel lag problem on one Windows 10 machine, slightly older, but still fast and also on one extremely fast modern PC on Windows 11. The problem persists in two different magazine projects unrelated to each other, each with around 64 pages. Please fix. I made intensive use of this super feature since it was added to indesign.
Stephan Möbius
supported this idea
·
-
12 votes
An error occurred while saving the comment Stephan Möbius
commented
I have the feeling this has finally been fixed in Indesign 20.1. I just come from a workflow with the dreaded sticky notes and noticed no slowdowns. :)
-
75 votes
The fix of the issue is now available in the latest InDesign 2022(v17.0.0.96). We recommend you upgrade to the latest version for the fix.
If you are unable to see the update, go to the Creative Cloud application and click on the context menu on the top right and click on Check for App Updates.
—
Adobe InDesign TeamStephan Möbius
supported this idea
·
-
3 votesStephan Möbius
shared this idea
·
-
32 votes
An error occurred while saving the comment Stephan Möbius
commented
In my version of Indesign (2024, 19.5) the PDF-comments workflow is still unbearably slow. It takes several seconds, after i clicked on an item in the PDF Comments Panel, for Indesign to regain responsiveness and to jump to the page with the comments marker in the documents. It's different for text-correction comments, like insert-text-comments, oder replace-text-comments – these work fine! - but for regular arbitrary placed general comments it slows to a crawl. If i delete all "regular" PDF comments on the active spread Indesign regains speed.
Stephan Möbius
supported this idea
·
-
16 votes
Please describe the issue in more detail.
What is the state of “Preserve Image Dimensions When Relinking” in Preferences – is it checked or unchecked? What is the state of “Auto-Fit” – is it checked or unchecked?—
Adobe InDesign teamStephan Möbius
supported this idea
·
-
2 votesStephan Möbius
shared this idea
·
-
2 votesStephan Möbius
shared this idea
·
-
47 votes
Thanks for reporting. We will review the issue shortly.
-InDesign Team
Stephan Möbius
supported this idea
·
-
3 votesStephan Möbius
supported this idea
·
-
1 vote
The values that are shown in the Text Wrap panel & also the Frame Fitting Options dialog for Crop amounts relate to the inherent image size, not to the size it appears within InDesign – that is, they refer to the image as though it were placed at 100% scale. That means it’s based on the image resolution and the scaling at which it is placed.
To see how this works, when you place an image, just click on the document – it will come at its 100% scale. Now select the Image contents, open the Text Wrap panel, and input 30mm in one of the fields, the value will be correct. Now scale down the image contents to 50% of its size – now measure the text wrap – it will be roughly 15mm in size.Hope it helps.
—
InDesign teamStephan Möbius
shared this idea
·
-
3 votes
An error occurred while saving the comment Stephan Möbius
commented
Try Peter Kahrels "Grep Query Manager". I use it for text-cleanup, running several GREP Search&Replaces .... Its a very old script and a little buggy in some places but the normal required functions to run greps on stories still work very well.
-
7 votesStephan Möbius
supported this idea
·
-
1 vote
An error occurred while saving the comment Stephan Möbius
commented
Probably related: after a crash of indesign and the document recovery, indesign often "recovers" TWO empty new unsaved documents, which i don't know where they are coming from. I certainly did not have those unknown documents open while i was working and while indesign was crashing. Maybe something to do with the *TempScratchDocuments* ???
An error occurred while saving the comment Stephan Möbius
commented
I get this weird -/*TempScratchDocument*/-"error message daily. And i have no clue what leads to it. Certainly nothing to do with those format edits mentioned above.
Stephan Möbius
shared this idea
·
-
1 voteStephan Möbius
shared this idea
·
-
51 votesStephan Möbius
supported this idea
·
-
17 votes
Hi everyone,
You can easily change text cases with just a few clicks, ensuring consistency across your designs. This feature streamlines text editing, saving you time and effort. Enhance your workflow by adjusting text case quickly from the Text or GREP tabs of the Find/Change panel. The feature is now available in the latest InDesign 2024(v19.5.0.084)
Helpx article - https://helpx.adobe.com/in/indesign/using/whats-new/2024-3.html#change-case
Please let us know your feedback in the comments.
—
Sanyam Talwar(he/him)
Stephan Möbius
supported this idea
·
People affected can use this script as a temporary workaround to repair unregistered (disappearing) items in the activeDocument:
=========================================
/* Fix: FlexObject items invisible in Preview mode after IDML roundtrip
Cause: Items exist in page.allPageItems but not spread.allPageItems.
Fix: Cut → Paste-Into temp frame → Cut back out → Paste → restore bounds.
This forces InDesign to re-register items in the spread hierarchy.
Tested with InDesign 2025. Groups all changes into one Undo step. */
(function () {
if (!app.documents.length) { alert("No document open."); return; }
var doc = app.activeDocument;
// Detect unregistered top-level items
var affected = [];
for (var s = 0; s < doc.spreads.length; s++) {
var sp = doc.spreads[s];
var ids = {};
for (var k = 0; k < sp.allPageItems.length; k++) ids[sp.allPageItems[k].id] = 1;
for (var p = 0; p < sp.pages.length; p++) {
var pg = sp.pages[p];
for (var i = 0; i < pg.allPageItems.length; i++) {
var it = pg.allPageItems[i];
if (it.parent.constructor.name === "Spread" && !ids[it.id])
affected.push({ id: it.id, t: it.constructor.name,
st: it.appliedObjectStyle.name, pg: pg.name });
}
}
}
if (!affected.length) { alert("All items registered. No fix needed."); return; }
var msg = affected.length + " unregistered item(s) found:\n";
for (var m = 0; m < affected.length; m++)
msg += " " + affected[m].t + " (ID " + affected[m].id
+ ") p." + affected[m].pg + " [" + affected[m].st + "]\n";
if (!confirm(msg + "\nFix now?")) return;
// Apply fix
app.doScript(function () {
app.scriptPreferences.enableRedraw = false;
var fixed = 0, errs = [];
for (var f = 0; f < affected.length; f++) {
try {
var target = findById(doc, affected[f].id);
if (!target) { errs.push("ID " + affected[f].id + " not found"); continue; }
var ob = target.geometricBounds.slice(0);
var pp = target.parentPage;
app.selection = [target];
app.cut();
var tmp = pp.rectangles.add({ geometricBounds:
[ob[0]-5, ob[1]-5, ob[2]+5, ob[3]+5] });
app.selection = [tmp];
app.pasteInto();
var inner = firstChild(tmp);
if (!inner) { errs.push("ID " + affected[f].id + " inner fail"); tmp.remove(); continue; }
app.selection = [inner];
app.cut();
tmp.remove();
app.paste();
app.selection[0].geometricBounds = ob;
fixed++;
} catch (e) { errs.push("ID " + affected[f].id + ": " + e.message); }
}
app.scriptPreferences.enableRedraw = true;
// Verify
var still = countBroken(doc);
var rpt = "Done. Fixed " + fixed + "/" + affected.length + "."
+ (still ? "\nStill broken: " + still : "\nAll items OK!");
if (errs.length) { rpt += "\nErrors:"; for (var e=0;e<errs.length;e++) rpt += "\n "+errs[e]; }
alert(rpt);
}, ScriptLanguage.JAVASCRIPT, undefined, UndoModes.ENTIRE_SCRIPT,
"Fix unregistered items");
function findById(doc, id) {
for (var s = 0; s < doc.spreads.length; s++)
for (var p = 0; p < doc.spreads[s].pages.length; p++) {
var items = doc.spreads[s].pages[p].allPageItems;
for (var i = 0; i < items.length; i++)
if (items[i].id === id) return items[i];
}
return null;
}
function firstChild(c) {
for (var i = 0; i < c.allPageItems.length; i++) {
var ch = c.allPageItems[i];
if (ch.constructor.name !== "Image" && ch.parent.id === c.id) {
if (ch.constructor.name === "FlexObject") return ch;
return ch;
}
}
return null;
}
function countBroken(doc) {
var n = 0;
for (var s = 0; s < doc.spreads.length; s++) {
var sp = doc.spreads[s], ids = {};
for (var k = 0; k < sp.allPageItems.length; k++) ids[sp.allPageItems[k].id] = 1;
for (var p = 0; p < sp.pages.length; p++)
for (var i = 0; i < sp.pages[p].allPageItems.length; i++) {
var it = sp.pages[p].allPageItems[i];
if (it.parent.constructor.name === "Spread" && !ids[it.id]) n++;
}
}
return n;
}
})();