1. InDesign CS4 - CC2017




2. Generate an Excel spreadsheet that contains at least one cell with the value "-1". Save as XLSX. Import/place (cmd-d) this file as "unformatted table".




3. the cells with the value "-1" should still have this value.




4. the cells are empty. All other values seem to show up correctly.

Additional information: Working regularly on Annual Reports with 100+ tables, our choice is to import as „unformatted table“ and to do all formatting in InDesign. After changes in Excel, all we have to do is updating the linked tables via the link panel. Table contents change, formatting stays. Perfect. But we are dependent on our clients still willing to use the outdated XLS format.

Please have a look at this problem! Thank you in advance.

Best regards

When working with Arabic and wanting to have Roman Digits, one needs to choose the "Arabic" digits option.
More option that should be set for Arabic are:
Character direction should be set to "default"
Paragraph direction should be set to "Right to Left"
Paragraph composer should be set to "Adobe World-Ready Paragraph Composer"
Language should be set to "Arabic"
Ligatures should be "On"

BUT
If I type a date that suppose to be presented like this:
9/1/2020
as soon as selecting "Arabic" for language the order is reversed to this:
2020/1/9

As digits has a built in Left to Right direction, all neutral characters between the numbers should get the same definition. This is how it worked until the 2020 update.
Now it looks that all the "/" characters where not effected by the numbers direction and remained Right to Left direction.

Mac Pro (Late 2013)
Software OS X 10.14.6 (18G2022)
Processor 3.5 GHz 6-Core Intel Xeon E5
Memory 32 GB 1867 MHz DDR3 ECC
Adobe Software version: 2020

After updated to 2020 version that added support to Asian languages (include Thai), it look like Indesign force user (in my case Thai) to set language in Advanced Character Formats to Thai. After set the language Indesign also require me to use World-Ready Composer to set all tone marks in place.
.
Before the latest version, I always avoid to use World-Ready Composer because it combines a word to single object, not just locks tone mark and float vowel to character in the right position. By which it impossible to navigate with text tool to the position of text that I want to revise, even if I use right/left key to navigate. It mostly skips word by word, not only character by character. And when I delete a word or a character, some time it not only deletes backward but forward too. (I think because of when I delete character form a word Indesign instantly recognises new word and forces to delete that new word.) But After updated to 2020, I think, I anymore cannot avoid World-Ready Composer.
.
After I designed to use World-Ready Composer, I found one more bug. Because in many situations when I craft the spacing in layout (especially in Thai), I always use thin-space to separate character like “ๆ” form word before and after to make the space between them look good. But After I set to World-Ready I found that when thin-space (include other spacial white space like en or em) is in the back of the line the spaces in question act like normal character, so the last character of the line when use left justify do not snap to right frame border. The space still there like It becames one of character. So you can see the gap between the last character and the right frame border. (you can find this instance in attachment in file “space issue.”)
.
But the serious issue still there after the update. I, and all of my co-workers, found that everything about word wrapping in Thai language goes wrong after updated to 2020 version. This never happen in the former versions. I don't understand why this issue is happen. Even if I use Discretionary Line Break to help Indesign to wrap text properly. But It is not productive at all, because I had been forced to read text all over again and to insert Discretionary Line Break to every lines. (you can find this instance in attachment in file “wrap gone wrong.” In the high-light is the words that should be stick together.)
.
PS. while I wrote this issue report, my co-worker tried to migrate back form 2020 to 2019 and she found that when copy revised text back to 2019 it not the same character encoding. I advised her to try to place that text to TextEdit. It appears that some character is changed to something that is not unicode at all. That never happen in previous versions too. ((you can find this instance in attachment in file “text form 2020” and “text form 2020.” the text form 2020 at frist did in 2019 before migrate to 2020.)

Issue: InDesign does not support Mongolian vertical text direction from left-to-right.

Version: InDesign 2019, 14.0.2 x64

Steps:
1. Place or paste Mongolian text into an InDesign text frame by using the attached Word document
2. Skew the text frame 90 degrees (as done with vertical Chinese and Japanese).

Expected result: Please see the attached Word document and screenshot.

Actual result: Notice that the vertical text direction is right-to-left and not left-to-right. Even if the text frame is skewed in the opposite direction (minus 90 degrees) the text is just mirrored and thus not readable.

Test files and screenshot: They are attached. If need be you can download the Google Noto font called Noto Sans Mongolian that we used.