Skip to main content
aarondrowndesign
Participating Frequently
November 26, 2021
Question

Extra extensions during export/save InDesign and Photoshop

  • November 26, 2021
  • 4 replies
  • 614 views

I’ve discovered this annoying bug in both Photoshop 23.0.1 and InDesign 17.0.1, and was wondering if anyone happened to find the same and/or have a solution. I’m running MacOS 12.0.1 on a 13-inch 2017 MacBook Pro, 2.3 GHz Dual-Core Intel Core i5.

 

In the linked screen recording, I’m exporting a PDF from InDesign and using the cursor to insert a version suffix into the file name (“.PROOF1”) prior to the file extension (here, .pdf). When I do, the app adds an additional “.pdf” extension. Then, when I backspace to delete the extra extension, it adds a partial extension as well.

 

As I said, both Photoshop and InDesign are doing this consistently. Wassup with this?

 

Thanks, folks.

This topic has been closed for replies.

4 replies

Community Expert
December 1, 2021

Hi Aaron,

I can see a similar issue with file name suggestions from the Save or Save As dialogs when I like to save an opened IDML file. In my case the number of periods used in the file name is the issue.

 

Let's start with an InDesign document named:

MyDoc-17.0.1.105.indd

to reflect the exact version name of InDesign that created it.

 

Export it to IDML where the name of the IDML file is correctly suggested as:

MyDoc-17.0.1.105.idml

 

Now I open that IDML file and I want to save it to a new name.

The full base name of that IDML file is visible in the tab:

*MyDoc-17.0.1.105 @ 76 %

 

The name suggested now with the Save command is:

MyDoc-17.0.1.indd

The last part of the IDML name, .105 , is missing.

Obviously I used one period too much in the base name.

 

 

This issue is not new. I can see this already in InDesign CC 2018, the first version where not "untitled-1" is showing up as the name of an opened IDML file.

 

Regards,
Uwe Laubender

( ACP )

aarondrowndesign
Participating Frequently
December 1, 2021

Interesting. Perhaps after all this time I've finally reached my dot limit.

 

Thanks for the insight! I greatly appreciate the reply.

 

- Aaron

rob day
Community Expert
Community Expert
November 27, 2021

Hi @aarondrowndesign , OSX reserves names that begin with "." for the system’s hidden files. If I try to make a folder starting with a dot I get this:

 

 

If I show invisible files via Command-Shift+. with Mojave, I can see the system’s hidden files:

 

You also can’t use colons because they are used for file paths in scripting:

aarondrowndesign
Participating Frequently
November 27, 2021

The file name doesn't begin with a period. Thanks, though.

Geоrge
Legend
November 27, 2021

>> Wassup with this?

Don't do like this. Use it "-" or "_" instead "." and forget about it.

 

 

Remember, never say you can't do something in InDesign, it's always just a question of finding the right workaround to get the job done. © David Blatner
aarondrowndesign
Participating Frequently
November 27, 2021

The bug manifests regardless of separator. Thanks, though. 

Scott Falkner
Community Expert
Community Expert
November 26, 2021

It is generally not a good idea to add periods to a filename. There are a lot of little programs and algorithms that are parsing filenames, not all of them are cleverly written. Some might see anything after the first period as the file extension, some might see anything after the last period as the file extension. Period is one of those characters to avoid using in filenames, like / and :

aarondrowndesign
Participating Frequently
November 26, 2021

I suppose it's possible that in thirty years as a designer I've simply been lucky, and that with Adobe's most recent updates my reckless use of periods in file names has finally caught up to me. However, the weirdness I describe also manifests (though a bit differently) if I insert a hyphen or an underscore—so the problem seems to lie pretty clearly with the app rather than my naming convention. Thanks for the reply.

Scott Falkner
Community Expert
Community Expert
November 26, 2021

That I have never seen. And since I don’t use extra periods in filenames (well, not since OS-X) I don't have any experience with them working out fine or of them causing problems. I just avoid them because it seems potentially problematic.