Lightroom: Export settings for filename are not taken into accont

  • 1
  • Problem
  • Updated 4 years ago
  • (Edited)
When you export a file in Lightroom 5.6 64 bit (Windows or MacOS) the file name settings are not taken into account.



On this screenshot Lightroom should put a file named exactly the same as the original (1944 - .jpg in this example) into the mod subfolder of the current picture directory.

It however creates a "1944 - _.jpg" file instead hence not taking the correct filename into account.

In this example:



It should overwrite the original file in its current location, but it also creates a "1944 - _.jpg" file in the directory.
What is the point of the Overwrite WITHOUT WARNING and Same folder as original photo options if they are not taken into account correctly ?

I have also tried to tick the Rename to: and then select Filename option but the "_" is always added.
Photo of Sebastien Harnist

Sebastien Harnist

  • 6 Posts
  • 0 Reply Likes
  • frustrated

Posted 4 years ago

  • 1
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3829 Posts
  • 1268 Reply Likes
It can't overwrite originals. That would be completely against its non-destructive ethos.

The 'overwrite without warning' option is there for overwriting earlier imports (perhaps if you've changed a setting and want to reexport)
Photo of Sebastien Harnist

Sebastien Harnist

  • 6 Posts
  • 0 Reply Likes
I am not really interested in any kind of ethos discussion to be honest, Lightroom is a piece of software that is not doing what its GUI says it does.

I am sorry but coming from the IT side of this world I can't really get used to software (and I've been using Lightroom for years now) that doesn't do what its interface describes. Even if this is by design, it should then not be possible to configure the settings in the interface to do something it simply won't do in the end.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3162 Posts
  • 515 Reply Likes
I am not able to duplicate this.

When I attempt the first example I end up with a /mod/1994-.jpg as expected.

When I attempt the second example I end up with a single file called 1994-.jpg but, I do get a message saying the file cannot be written as the file would replace the existing photo.

I must be missing something in your steps.

Testing on Mac 10.9.5
Photo of Sebastien Harnist

Sebastien Harnist

  • 6 Posts
  • 0 Reply Likes
I would love to be able to give more details, unfortunately that's all I'm doing.

I have tested in on Mac OS (my main workflow is on Mac OS) and now on Windows 8.1. This is an absolutely fresh install hence excluding any kind of customization.

Please note there are 2 blanks in the filename. It's "1994 - .jpg" not "1994-.jpg".
To be absolutely accurate the file I obtain is named "1994 -_.jpg" so it looks to as if Lightroom would replace the space after the "-" with an underscore.

I never get any kind of error message, so it could definitely be Lightroom is handling the blanks wrongly and replace them with an underscore.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3157 Posts
  • 514 Reply Likes
Yes. That is it. XXXX[Space]-[Space].jpg does save as xxxx[Space]-[Underscore].jpg. I didn't see the space between the "-" and "."

Using the file name with a space before the 'dot' causes the underscore to be substituted.

From: http://en.wikipedia.org/wiki/Filename

In Windows utilities the space and the period are not allowed as the final character of a filename.[16] The period is allowed as the first character, but certain Windows applications, such as Windows Explorer, forbid creating or renaming such files (despite this convention being used in Unix-like systems to describe hidden files and directories). Among workarounds are using different explorer applications or saving a file with the desired filename from within an application.[17]

This makes me wonder if there maybe there is an OS consideration intruding here.
Photo of Sebastien Harnist

Sebastien Harnist

  • 6 Posts
  • 0 Reply Likes
You are not reading this appropriately, the final character cannot be a space or a dot, but this is the filename including the extension. So "1994 - .jpg" is allowed, "1994 - .jpg " is not allowed.

In fact when you try the latter the file explorer will automagically remove the trailing space.

Then again, in OS X Lightroom does the same, and it's not a technical limitation of the OS in either way, looks like a pure bug to me.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3157 Posts
  • 514 Reply Likes
What I am saying is that there may be an OS-based reason that Lightroom is doing this. The above was merely an example of how OS's handle spaces differently.
Photo of Sebastien Harnist

Sebastien Harnist

  • 6 Posts
  • 0 Reply Likes
I understand what you are saying even though I can't really follow your reasoning.

There is no reason be it on Mac OS X or on Windows to replace a space with an underscore, both OSes support the space as a valid character before the extension and Lightroom exists only on those OSes.

How can I raise this a bug in the software to be fixed ? Can you escalate this internally and maybe at the same time try to find out if there may be a reason we can't see for LR to do it like this ?
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3157 Posts
  • 514 Reply Likes
This is an official place to report things. Consider it filed.
Photo of Sebastien Harnist

Sebastien Harnist

  • 6 Posts
  • 0 Reply Likes
Just created a file name "1994-.jpg" and there I can confirm, this is not happening... So it definitely seems to me like Lightroom is handling trailing spaces corretcly and changes them to underscores.