Skip to content

Alan

My feedback

8 results found

  1. 33 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)
    Alan supported this idea  · 
    An error occurred while saving the comment
    Alan commented  · 

    Hi Adobe is anyone working on this issue? Version 19 of ID does not fix the issue. We are having problems daily as we are the ones trying to rip the files. The designers are blissfully unaware of the grief this has caused us since v18.5.

    Help Please.

    An error occurred while saving the comment
    Alan commented  · 

    Hi Ravi, is there any progress on this problem. It has become more prevalent as our clients are upgrading to 18.4 and 18.5 and we cannot ask them all to back grade to 18.3.

    Help please.

    An error occurred while saving the comment
    Alan commented  · 

    Hi Ravi, we are seeing various results ranging from image data dropping off to inability to RIP files. I have created a small sample file for you to look at.

    https://filetransfer.typeform.ie/message/R1mou6eaLdBSsnGBxfutjk

    An error occurred while saving the comment
    Alan commented  · 

    Is there any further news on this Ravi? We are seeing more and more random PDFs failing various workflows ..... and everytime if we ask our clients to back grade to ID 18.3 the problem is fixed. This is a huge issue.

    An error occurred while saving the comment
    Alan commented  · 

    We are a PrePress house and we are also seeing random problems with ID generated PDFs in 18.4 and 18.5. We are seeing ripping problems in our Agfa workflows or PDFs that are dropping images and text.

  2. 3 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)
    Alan supported this idea  · 
  3. 4 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)
    Alan supported this idea  · 
  4. 4 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
    Alan commented  · 

    Hi Andy, we are also seeing PDFs failing in various RIPs and workflows. We have supplied files to Adobe support. A real nuisance.

    Alan supported this idea  · 
  5. 12 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)
    Under Review  ·  amaarora responded

    Thanks for reporting the issue. We will review it shortly.

    -InDesign Team

    An error occurred while saving the comment
    Alan commented  · 

    We are still having this issue in version 16.1 (2021). It seems to be down to the auto activation of fonts from the "Document Fonts" folder located on my network server (XiNET). If I use an alternative font management application like Font Agent Pro, the problem is gone. Albeit the fonts are then hosted locally on my Desktop and not in the "Document Fonts" folder with my job on the network server.

    Alan shared this idea  · 
  6. 131 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)
    Closed: Fixed  ·  amaarora responded

    The fix for this issue is now available in the latest update of InDesign – version 16.1

    Please update to this version to get the fix. To prevent problem on existing documents and see the footnotes again, you will have to force recompose the stories.
    To force recompose stories, you can use the shortcut Command-Option-/ (slash) on Mac or Ctrl-Alt-slash on Windows

    -InDesign Team

    An error occurred while saving the comment
    Alan commented  · 

    We are also having this problem in version 15.1.1. This is a very dangerous bug as it's hard to spot.
    Please fix Adobe.

    Alan supported this idea  · 
  7. 148 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)
    Closed: Fixed  ·  amaarora responded

    As confirmed by multiple users, this issue is fixed in latest version of InDesign.

    Thanks for your feedback.

    -InDesign Team

    An error occurred while saving the comment
    Alan commented  · 

    Hi Adobe, we are still having major issues with a lot of spinning wheels in InDesign version 15.1.1. because of the AdobeFnt22.lst files that are created with every document. Basically when we open a document it resyncs/updates the AdobeFnt22.lst file of every document that was previously worked from that Mac. This is causing a lot of network traffic and spinning wheels in InDesign. The problem is fixed if we restart the Mac or rename the "Document fonts" folder so that InDesign no longer uses the fonts so does not create an "AdobeFnt.lst" file. Can you please sort this out, it is killing our production, some of our designers are reverting back to using QuarkXpress.

    An error occurred while saving the comment
    Alan commented  · 

    We are also experiencing this very annoying and dangerous issue. This only happens when you are collecting fonts which creates the AdobeFnt21.lst list. Our designers could quite easily dump the wrong folder when trying to clean up these bug generated folders. Please fix this Adobe.

  8. 135 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)
    FIXED  ·  amaarora responded

    Fix for this issue is now available in the latest update of InDesign 2020 – that is, InDesign 15.1.2

    In the Creative Cloud Desktop application, click on the Updates section on the left. You should be able to see the Update available for InDesign. Please update your InDesign application to this version to try out the fix.

    Let us know in the comments section if you still face this problem.


    Adobe InDesign Team

    An error occurred while saving the comment
    Alan commented  · 

    The same here saving onto a XiNET server (afp mount)

Feedback and Knowledge Base