Skip to main content
Tony Seddon
Inspiring
March 4, 2020
Answered

InDesign 2020 (15.0.2) is creating extra folders (AdobeFnt.lst ) automatically after packaging files

  • March 4, 2020
  • 48 replies
  • 18753 views

Has anyone noticed that the latest version of InDesign 2020 (15.0.2) is recreating extra folders after files have been packaged with images and fonts? Basically, I just packaged a layout by saving it to an alternative 'work' folder that sits on my desktop. Once that was complete I moved the packaged folder back to the original job folder alongside other material associated with the project.

The issue occurred as soon as I opened that InDesign file once again. After doing this, a new folder (same name as the packaged material) reappeared in the 'work' desktop folder. It only contains a Document Fonts folder, so no duplicate Links or a copy of the InDesign files itself. Weird behavior though, I've not seen anything like this before and it's only started happening after the very recent upgrade.

At least the awful CMD-Z undo bug seems to have been fixed though.

 

 

{Renamed by MOD}

This topic has been closed for replies.
Correct answer Srishti Bali

Hi,

 

Sorry about the trouble this issue has caused. We've fixed this in the latest release. Please update your InDesign to v 15.0.3 to get this fixed.

Here's a link with more details: https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/39846805-adobefnt-lst-automatically-reappears-after-deletin

 

Regards,

Srishti

48 replies

Participating Frequently
March 15, 2020

I am having the same issue, packaging files is creating to export folders, one folder has all the file contents. The other just document fonts.

 

Even when I delete it, it comes back

Participating Frequently
March 15, 2020

CORRECTION

 

After I package a file, change the folder name and open up the indesign file a new folder is created with the original package file name with only a 'document fonts' folder

 

 

Pooja Rathi
Adobe Employee
Adobe Employee
March 16, 2020

Thank you all for raising this issue. We are working on its fix and will provide an update in upcoming releases.

 

Regards

Pooja Rathi

Community Expert
March 12, 2020

Hi together,

voted and commented the bug report on InDesign UserVoice:

 

My experience with the bug is this:

1. Package the active document with Links, Document fonts, IDML and PDF to the suggested folder of function Package For Print.
2. Move the folder of the package to a different folder.
3. Close the active document

 

4. Here comes the bug:
In the moment* I am using InDesign's Open command with the ORIGINAL InDesign document that I packaged before, a new folder is created.

The name of that new "ghost folder" is the same of the moved packaging folder.

The folder's position in the file system is the same of the packaged folder where it was created before moving it.

The contents of this new folder is a Document fonts folder with one single file: AdobeFnt21.lst

 

If I open a different document that was not packaged in the same session a new "ghost folder" is not created.

( I define one session as the period between "Start InDesign" and "Quit InDesign" )

 

If I also move or remove the "ghost folder" it will be re-created if I open the document where the once packaged folder was created from. I can stop that behavior: Quit InDesign. Restart InDesign.

 

* I know this exact moment because I have a event listening script installed that opens the folder of any exported file in the file system. In the moment the "ghost folder" is created the event "afterExport" is fired.

 

Regards,
Uwe Laubender
( ACP )

Participant
March 12, 2020

We have exactly the same issue on two machines here... I think it's a dangerous bug, because you could overwrite the wrong folder... and it's also confusing people

Colin Flashman
Community Expert
Community Expert
March 12, 2020

Appears to be a new bug associated with 15.0.2 - drove my colleagues and I up the wall. Initially thought it was a folder creation script an ex colleague had written, but after we stopped using it and tracking each time it happened, the adobefnt21.list was the common denominator and I looked up the indesign.uservoice bug reports and sure enough, people are noticing.

If this is annoying you, let the engineers know here: https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/39846805-adobefnt-lst-automatically-reappears-after-deletin

If the answer wasn't in my post, perhaps it might be on my blog at colecandoo!
chrisd37765479
Participant
March 12, 2020

Yes. I'm having the same problem.

Legend
March 10, 2020

I'm having a bad case of this today. The file in question was packaged earlier today, and is not longer open. I have been deleting the rouge folders when one appears, but they keep on showing up. 

Here are the ones in my trash so far today:  (each one contains only a Docuemnt Fonts folder with a file called AdobeFnt21.lst )

Tony Seddon
Inspiring
March 10, 2020

Did you try quitting InDesign then relaunching? If you do that, the folder should stop reappearing. You need to do this every time you've packaged something at the moment, unfortunately, but it's a simple way to stop the problem until Adobe fixes it.

Known Participant
March 10, 2020

Yes, thanks. We did find a workaround but damned annoying and a big waste of time when archiving multiple projects.

Frans v.d. Geest
Community Expert
Community Expert
March 9, 2020

Ah, I saw that happen as well and considered it an OS error first! Happens here as well...

The bugs in 2020 just keep coming. Worst release ever...

Known Participant
March 9, 2020

Has anyone from Adobe chimed in on this yet? This is a troublesome problem for those of us who have to archive packaged projects!

BobLevine
Community Expert
Community Expert
March 9, 2020

I see a number of issues reported here.

The "new folder" thing seems to be a result of moving a folder while files are open. I get that the Mac OS will allow it but it's bad practice.

Type 1 fonts should be avoided if for no other reason than their lack of cross-platform compatibility. If you are going to use them put them in a document fonts folder and use them on a project by project basis.

Tony Seddon
Inspiring
March 9, 2020

Could you clarify the point about moving folders when a file is open, please?

It's true that this isn't a good idea, but how can you package a file if it isn't open? I've been seeing this behaviour when packaging a file along with its fonts and links to another folder, usually my 'Today's Work" folder which sits at the side of my desktop.

BobLevine
Community Expert
Community Expert
March 9, 2020
I'm talking about moving the folder if the InDesign file in it is open. I may have read the OP's post incorrectly and if so, I apologize but it's still something to be aware of.
Known Participant
March 9, 2020

I am having the same issue -Very frustrating. InDesign 2020 is a work in progress. I also have a particular family Postscript Font (Helvetica Neue) that InDesign absolutely will not accept, even if I put the Font in the System Library and do a restart. The InDesign file says there is no Font Error; However, when the file is packaged or a Hi Res Proof is generated, the Font is garbled. I have loved working in InDesign but the Font issues have caused me a lot of problems.

Known Participant
March 9, 2020

I woudl agree with Bob to stop using the Postscript versions of these fonts and move to the OpenType versions. Are you using a font manager of any type?

Known Participant
March 9, 2020

I am using the latest Suitcase Fusion that suppose to sync with the Adobe software - has worked great in the past but not for the one Font family I mentioned. I have been in Graphics 32 years, long before OpenType Fonts seemed to be available. In other words, I have numerous Screen/Postscript Fonts.

 

The difficult thing for me to understand is: I can shut the Suitcase Fusion down and put the Font family in my System Font Library and do a restart.

 

The InDesign file will read, "No Errors" but the Font is still garbled.  I can copy it to a new document and even if the font looks good, then, when I go to Package, it is garbled again.