Skip to content

Brett Wieland

My feedback

2 results found

  1. 59 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    The fix for this issue is available in the InDesign PreRelease build(v21.4.0.068) and above.

    Please check if the issue is now resolved.

    Download/Update the latest InDesign PreRelease build in Creative Cloud under the “Prerelease” category(Refer to “Prerelease_CreativeCloud.png” for reference)

    Please apply to the InDesign PreRelease in case you don’t have access to the InDesign PreRelease build – https://www.adobeprerelease.com/beta/C6DFA254-C40C-4EEB-8F6D-F4AEDA2E6171

    If you still encounter any issues, please drop a mail to sharewithID@adobe.com.

    Adobe InDesign team

    An error occurred while saving the comment
    Brett Wieland commented  · 

    1. ID 21.2
    2. Open a file made before the latest Windows update, its fonts will now be the incorrect version and appear as missing
    3. InDesign should use the installed font
    4. It's necessary to find/replace fonts on every file before it can be used. This also causes scripting issues.

    This also effects Library files made before the OS update.

    It appears Windows updated TNR and Calibri with the last few updates and this is causing issues with InDesign. ID is the only Adobe product affected by this problem. The others (AI, PS and Pr) seem fine. The version of Windows is 26200.7840.

    Screenshot attached. Calibri (OTF) is not a font we've ever used, and doesn't exist. The correct font is still called Calibri, so the replacement is Calibri (OTF) -> Calibri. This is for the entire family.

    This problem also affects Times New Roman.

    Should also mention that this exact problem exists on 5 different machines all running the same versions.

    Thank you.

    Brett Wieland supported this idea  · 
  2. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Brett Wieland commented  · 

    This remains an issue in 2023 and, for my use case, makes cross-references near useless. I'm aware of the workarounds and have a script that does it also, but it's a bit ridiculous to go that far just to get this to behave the way it should out of the box.