We've been making a large catalogue pricelist for over 13 years using indesign.

We're now stuck on the 2017 (12.1.0) version.
We want to update it, but in the latest version, importing our pricelist from excel into a table, slows the whole thing down to an unworkable speed.

info:
the table is around 13000 rows by 10 columns. so not small.
it does import in the 2017 version. slow to import in both, but can use and work on after import in 2017 version.
2019, freezes when scroll used, and take 1-3 mins to unfreeze. Scroll again or do anything much else and freezes again.
I can see it's using 100% of 1 CPU core. And I know Indesign is built in a way that it can only use 1 CPU core! (please fix this!!!!)

Firstly, let me just say a BIG thanks for introducing Column Rules in CC 2020.

However, I've found a couple of problems so far.

1. New File


2. Draw a text frame (no text needed) and set the Columns to 2, and turn ON the Column Rule (all basic, default values).


3. Draw another text or graphic frame (doesn't matter which) and place it anywhere (doesn't matter if it overlays the text frame, or not).


4. Group the two objects.


5. HERE IS THE KEY STEP: With the group selected, turn on Text Wrap (doesn't matter which... anything other than 'None').


6. Move the group ANY amount... e.g., simply nudge it with the arrows on your keyboard. (keyboard or drag with the mouse... the results are the same).

The column rule will disappear!

If you double-click to select the 2nd object drawn (not the text frame) and nudge it on its own, the column rule will re-appear. BUT... as soon as you nudge the text frame (on its own) or nudge the group again, the column rule will disappear again.

The trigger is the Text Wrap. Without it, it behaves normally.

It does not matter if there is Text Wrap applied to the individual objects. The trigger is the Text Wrap applied to the GROUP of objects.

Hope this helps.

Allan

I have set up articles in multiple files InDesign 2020 (files first created in InDesign 2019 and updated to 2020 yesterday and today). When I export to PDF, all image tags are added to a new article in the bottom of the tags panel in Acrobat DC rather than in the articles that I assigned them to in InDesign. Luckily, I preserved a version of InDesign 2019 and can open them in there and export to have the tags show up in the correct place. FYI, I also made sure my layers order in InDesign is as I want it to be.

I am using InDesign 14.0.2.

We are a book publisher, and we sometimes use a special character in some of our academic work: a gothic P—the Unicode character 1D513 (Mathematical Fraktur Capital P). See: https://www.fileformat.info/info/unicode/char/1d513/index.htm

However, it does something very wonky with footnotes, which seems to be a bug. If we insert this character—Unicode 1D513—in the same line as a footnote reference, it makes the footnote reference disappear. The footnote stays in place. We have tried different fonts, but it doesn't seem to be font dependent. However, if it is in the same line, but after the footnote reference, it still appears. So it seems to be some strange interplay of this unicode character and the footnote references.

I don’t know if there are any other characters that do this, but it doesn’t seem to be font dependent. The only way we are able to make the footnote reappear is to make the paragraph use the Adobe Paragraph Composer, instead of the Adobe World-Ready Paragraph Composer. However, this too is a problem because the paragraphs that use this particular Unicode character often have other languages in them as well, such as Hebrew, and we need the World-Ready Paragraph composer on to make those work, so we can’t just switch that so easily.

See the attached InDesign document for an example of what happens. You’ll notice the special character P is right before the second footnote, but it is completely invisible, while still being “there.”

I don’t know if this bug goes beyond this particular Unicode character or not, but it seems strange that InDesign footnotes are not playing well with it.

Thanks for your help.

I have an InDesign file if you need a sample, but the uploaded won't let me attach it. Can I email it to someone?

Search ("find what") and replace ("change to") does not return the expected results when replacing text. It truncates the replacement by one character.

Steps to reproduce
1. Create a new InDesign file (see attached test.indd)
2. Create a text box
3. Add text in the text box including the word "test"
4. Run the following script (see attached) test.scpt
5. Expected the return results to be "foo" but it returns "fo"

tell application "Adobe InDesign CC 2019"

set find text preferences to nothing

set change text preferences to nothing

set properties of find text preferences to {find what:"test"}

set properties of change text preferences to {change to:"foo"}

tell document 1

    set _r to change text

    return _r's first item as string

end tell

end tell

Environment
ProductName: Mac OS X
ProductVersion: 10.13.6 (High Sierra)
BuildVersion: 17G65

Adobe InDesign 14.0.1
AppleScript 2.7
Script Editor 2.10 (194)

The Index panel will cause InDesign to crash if you click the update preview button when a three-layer index entry has no text in the second layer.

I figured out what causes the crash with 100% reproducable results. Here's how you do it.

1) Create a multi-document book.
2) Open one document in the book.
3) Create an index entry with three layers. For example, 'dogs > breed > beagle'.
4) Open a different document in the book.
5) Repeat step 3 in this different document, with the same entry data.
6) In the Index panel you will see two entries that are both three layers deep. Toggle the layer arrows and then double click the second layer heading of 'breed'. Delete the text in the box and hit enter.
7) You will notice in the Index panel that there is a blank space beneath 'dog' and above 'beagle.'
8) Now click the 'cycle' refresh button at the bottom of the Index panel.
9) InDesign will crash.

From a programming perspective I suspect this has something to do with no data being in the entry's second layer. It's finding 'null' and crashing.