There are multiple listings of the same font in the Find Font menu in CC2019. All information is the same, all applied characters are the same, but there is odd behavior.

--FileACC2019WithDocumentsfontsfolder.png shows double listing of Trade Gothic LT Pro Roman.

--FileACC2019WithoutDocumentfontsfolder.png (when I take away access to Document fonts folder, no other changes), one instance switches to "Regular" instead of "Roman"

--FileACC2017WithDocumentfontsfolder.png shows what happens with I open this file in CC2017 (no double listing)

--FileACC2017WithoutDocumentfontsfolder.png (Document fonts folder hidden) shows what happens with I open this file in CC2017 (no double listing)

I process large volumes of files; this is not an isolated incident nor a corrupted file. Packaging results in InDesign only grabbing the single correct font file, so that isn't broken. This behavior with Find Font is seemingly new to CC2019 (I'm working on 14.0.2). The multiple listing of same font, variation of font name when fonts enabled/disabled, and Find Font showing fonts missing that aren't because of what seems to be a name issue in Find Font. Has something changed in the way that InDesign reads fonts/accesses Document fonts folders?

Windows 10 15.0.3 broke Book TOC when exporting to EPUB; works in 15.0.2

Not only did 15.0.3 eliminate Book > Export to EPUB option of EPUB Version 2.0.1, it changed the Table of Contents to include duplicate entries linking to every PAGE within a chapter. The Book.epub file had a separate .xhtml file for every page in the book, rather than one .xhtml file per chapter and one TOC entry per chapter. This makes the Table of Contents useless.

Reverting InDesign back to 15.0.2 fixes the problem.

Here are the parameters I used to export the EPUB:
Book Menu :
Export Book to EPUB (Reflowable)
General

Version : EPUB 2.0.1

Cover : Rasterize First Page(change later)

Navigation TOC : Multi Level(TOC Style)

TOC Style : Table of Contents Style

Content : Based on Page Layout

Text

Option : NOT Remove Forced Line Breaks

Footnotes : Placement: End of the section(Endnote)

Lists :

Bullets : Map to Unordered Lists

Numbers : Convert to Text

Object

DO Preserve Appearance from Layout(for Graphic / Media objects)

NOT Use existing Image for Graphic Objects

CSS Size : Relative to Text Flow

Layout : Align Center

Space Before : 0 Pixels

Space After : 0 Pixels

NOT Insert Page Break

NOT Ignore Object Export Settings

Conversion Settings

Format : Automatic

Resolution : 300 PPI

JPEG Format : Baseline

JPEG Quality : Maximum

HTML & CSS

Include classes in HTML

Generate CSS

Preserve Local Overrides

Include Embeddable Fonts

JavaScript

Metadata

Identifier : urn:uuid:5365cc97-ed5a-4e7c-b325-715c0649c355

Viewing Apps

Kindle Previewer 3.39.0

I have .indd and .epub files from both 15.0.3 and 15.0.2, but I'd rather not publish them to the world. I'd rather you contact me and I'll e-mail you a link to them.

100% reproducible on InDesign 15.0.2 on Windows 10.
Sample document for easy reproduction: https://www.dropbox.com/s/iirawdsvd27l95l/indesign%20crash.indd?dl=1

Starting point:
1. I have a table containing some footnotes.
2. Footnotes are not allowed to be split.
3. The table (including footnotes) doesn't fit in the frame, so the last row jumps to the next frame.

To crash InDesign:
1. Place the text marker in the paragraph containing the table.
2. Go to Keep Options.
3. Check "Keep Lines Togheter" and "All Lines in Paragraph".

Result: InDesign immediately hangs and you have to force quit.

Please fix? Should be easy to track down the internal cause with the sample document and reliable reproduction. :)

Ps: This was a bit time consuming to track down when my document spanned 100 pages and changes many pages away caused the table to move and crash InDesign. -.-

Using CC2019 on a Mac running High Sierra

Steps to reproduce:
1) Create a document with a few hyperlinks in it.
2) Whilst this document is open, open a 2nd document, and copy/paste the links from one document to the other.
3) Save both and close.
4) Trash source document

Expected result: hyper links should work in Target document as expected.

Actual result: hyperlinks all appear broken in document. Whilst an exported PDF appears to still work, ID reports all those links as broken.

Other details:
If you retrieve the source document from the trash, it the links in the target document suddenly start working again, meaning your not actually pasting the hyperlink, but theres some sort of link that exists between the source and target document.

Saving target file as a new file, saving as idml, has no effect – those links are still tied to the source document.

This in an absolute tragedy if you are working on large documents with lots of links, and needs fixing ASAP

I'm using Indesign 15.0 on MacBook Pro (Retina, Mid 2012) running Mojave version 10.14.6

I'm experiencing a bug with the Source Serif Pro font , which I use extensively in a particular project.

I open an existing document, and the text in Source Serif Pro looks as you'd expect it to. When I start to edit the text however, it all jumps down as if the baseline settings of the text frame has been changed (although checking in the settings confirms they haven't been).

Copying and pasting the frame, or the text into a new frame, doesn't help.

It only happens with Source Serif Pro (all weights) - if I change the font, even to other Adobe Fonts it doesn't happen. It also happens in new documents.

It may be worth mentioning that a colleague works on the same Indesign files on a PC (we share the files via Dropbox) but he doesn't experience the issue.

We both share another related bug with Source Serif Pro in that quotation marks just display as 'straight' even though 'use typographer's quotes' is turned on in preferences. This can't be fixed through the Glyphs panel either.

My feeling is it's something to do with this particular font being used a lot over 2 different platforms.

Thanks

InDesign 14.0.1.209, macOS Mojave 10.14.2

When launched and the following conditions hold, InDesign does not seem to have keyboard focus (i.e.., no keyboard shortcuts work):

1. Show ‘Start’ Workspace When No Documents Are Open is unticked.


2. The Control bar is open in the default workspace.


3. The CC Libraries panel is either not in the default workspace or collapsed.

Note that conditions 2 and 3 are met by several of the standard workspace, for example both Advanced and Typography (but not Book, Essentials or Essentials Classic).

If you choose a menu item or click in an input field, the app gains keyboard focus. Otherwise you seem to be able to type endlessly without any discernible effect.

The inclusion of ~F in a character class invalidates grep expressions in endnotes.

InDesign version: 14.0.2.324 (with the GREP fix installed)

Steps to reproduce:

1. Open the attached document. It contains a single page with text and an endnote.


2. In the GREP tab of the Find/What window, enter the following GREP expression:

\d[^.,;~F]+

And target the document. The expression matches from a digit up to the next period, comma, semicolon, or footnote marker.

Expected result: The expression should match some text in the main text and in the endnote.
Actual Result: The expression does not match anything in the endnote.

To show that it's ~F that's the problem, use this expression:

\d[^.,;]+

It matches in the main text and in the footnote, as expected.

When importing a Word document that contains some indented paragraphs, the left indent being set to 5mm in Word (for example), once placed in InDesign, these 5mm indents typically show as 4.992mm. This would not neccesarily be a problem except that Find/Change in InDesign will not recognise an indent to 3 decimal places and therefore this cannot be located easily and fixed. This is proving to be a big problem in my workflow as I cannot automate the process of re-styling these paragraphs using InDesign Paragraph Styles with Find/Change. This bug occurs whatever measurement system is used, i.e. mm, inches, pts etc. Version of InDesign used: 14.0.3 although the same problem exists back to CS6 at least.