Excel filter rejects custom Cell Range for 26-column sheets (.xlsx-only)

Steps to reproduce the issues:
1. Create a new document.
2. Select File > Place, check Show Import Options, select attached Columns_26.xlsx file.
3. Note nonstandard default Cell Range: A1:A@10 (should be A1:Z10).
4. Enter custom (valid) Cell Range "A1:E5"

Expected result:
No error and a table containing cells A1 through E5.

Actual result:
Error message, "You have not entered a valid 'Cell Range'. (See attached screenshot.)

This error is given for any sheet whose right-most column is a multiple of 26 (so Z, AZ, BZ, etc.). Place the attached Columns_52.xlsx with range "A1:E5", for example.

Adding/removing a column (attached Columns_27.xlsx file) avoids the error.

Versions of Adobe InDesign:
CS6 through CC 2018.0, Windows and macOS

Test files and screenshot of error attached.

When i drag and drop a Textframe my Screen flickers black for a second - almost every damn time. This happens for me and most of my colleagues and it is horrible to work with.

I feel like it got worse after installing the latest "Tablehead" fix that fixed the disapearing tableheads.

Build 12.1.0.56
OS X El Capitan 10.11.6
iMac (Retina 4K, 21.5", 2015)
3,3 GHz Intel Core i7
16 GB 1867 MHz DDR3
Intel Iris Pro Graphics 6200 1536 MB

2nd Monior is a DELL U2414H, 23,5" at 1800p

This is happening on quite a lot of machines in my Company and also for Persons i know using a 4K Retina iMac. and Really is a pain to work with. - It is NOT visible in a Screenrecording the only option would be to record a Video from my Smartphone if needed...

Thanks!

Adding Hunspell dictionaries breaks code-signing, and results in the whole of InDesign's spelling system being sand-boxed by OSX.

Steps to reproduce:

1. On High Sierra and InDesign CC, add a Hunspell dictionary, as detailed here: https://helpx.adobe.com/indesign/kb/add_cs_dictionaries.html

2. Spell-check any InDesign document using the new dictionary and spell-checking then becomes unusable, until InDesign is uninstalled then re-installed.

The following types of errors are produced in the console, showing that it's a code-signing issue, caused by dictionaries being installed within the Hunspell plugin bundle.

Can I suggest that there should be another place to install additional languages, outside the InDesign application.

The only way I can work with Latin and Ancient Greek languages currently is to use an El Capitan Mac, which does not have the sandboxing.

AMFI: Check-fix enabled for binary '/Applications/Adobe InDesign CC 2018/Resources/Dictionaries/LILO/Linguistics/Providers/Plugins2/AdobeHunspellPlugin.bundl e/Contents/MacOS/AdobeHunspellPlugin' with TeamID 'JQ525L2MZD', identifier 'com.adobe.adobehunspellplugin2': broken signature treated as unsigned without privileges. This workaround will not work for software built on or after 10.12.

The last cell in a table is a “dead” cell as far as Track Changes is concerned. If you copy cells from another row and paste them in the last table row, if the selection you are pasting into contains the last cell in the table, the pasted text will not be marked as a change. Likewise, inserting a new row in a table as the last row via drag and drop isn’t marked as an insertion at all. Inserting a new column in a table as the last column via drag and drop is tracked as an insertion for each cell in the column, except for the bottom cell.

I recognize that there are some limitations with Track Changes in tables, but the Track Changes feature should work consistently whether or not the bottom-right cell of the table is selected.

InDesign CC 2018.1, Mac OS X 10.12.6

VERSIONS
Windows 7, CC 2015.4 and CC 2017.0
Windows 10, CC 2015.4 and CC 2017.0
macOS 10.12, CC 2015.4
even CS6 versions are affected...

- - - - - - - - - - - - - - - - - - - - -

STEPS TO REPRODUCE
1. Create an InDesign document with several pages
2. Define the text frame options with two columns
3. Link all frames and fill with placeholder text
4. Create a new paragraph style with the option "span columns" (e.g. title)
5. Define several parts of the layout with the new paragraph style
6. Edit some text near the paragraph style
--> the performance while typing is very very bad!!!

- - - - - - - - - - - - - - - - - - - - -

EXPECTED RESULT
InDesign and InCopy should still be usable when a layout file was built using either "span column" or "split column" (e.g. using a paragraph style > "Span Columns").

- - - - - - - - - - - - - - - - - - - - -

ACTUAL RESULT
Very bad performance - working is NOT possible anymore

1) This bug occurred on InDesign cc2017 and CS6. 2) Follow these steps to replicate the bug: create a shape, let's say a circle, and then copy this circle and paste it in a separate layer directly over the top of the first. To better see the effects of the bug, make the fill of the top circle red, and the bottom blue. At this point, the bottom blue circle is completely hidden by the red circle above it. Now put a 4pt stroke with an outside alignment on the bottom blue circle. The blue circle is still hidden, and now it appears as if the red circle on top has a stroke. Before making any changes to the shapes, make sure the Dimensions Include Stroke Weight and Adjust Stroke Weight when Scaling are DESELECTED in the Transform panel options. Make sure both the Info palette and the Transform palette are visible so you can read the starting and ending measurements in both palettes. Using the selection tool, select BOTH circles together, and then pull on any corner to enlarge the two shapes together. 3) EXPECTED RESULT: the two shapes should scale together. They start with the equal measurements in both the Info and Transform palettes, and once scaled, the shapes and the measurements should still read as being equal (albeit larger) sizes. 4) THE ACTUAL RESULT: the two shapes are different sizes after scaling. Remember that Dimensions Include Stroke Weight was deselected, so the stroke shouldn’t have any effect on the shape size, and yet, the bottom shape is slightly bigger than the top. Not only is the blue circle now clearly visible and peeking out from beneath the red circle, but the Info and Transform palettes read TWO different sizes. The following are images that illustrate the bug: