Lightroom no longer accepts a dot in the catalog filename.

  • 1
  • Problem
  • Updated 2 years ago
  • Solved
I regularly use the 'export this folder as a catalog' feature to make catalog backups of certain subsets of my pictures. My naming convention has always been in the form of YYYMMDD.HHmm

With LightroomCC version 2015/9 (OS X version) I noticed that Lightroom now truncates the catalog name used after the dot, so it becomes 'YYYYMMDD'. This also happens when creating a new catalog through the File->New Catalog menu.

Is there a reason that this restriction on the catalog name has been introduced?
Photo of MBerlage

MBerlage

  • 6 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5867 Posts
  • 1282 Reply Likes
Official Response
This is a known issue. We are currently working on a fix. 
Photo of MBerlage

MBerlage

  • 6 Posts
  • 0 Reply Likes
Thanks for the reply. I'll await an update then :).
Photo of Arnold Hoddevik

Arnold Hoddevik

  • 62 Posts
  • 14 Reply Likes
Dot in file name usually seperate the file name from extention (.lrcat), right?. Why not use _ or - in stead?
Photo of MBerlage

MBerlage

  • 6 Posts
  • 0 Reply Likes
An extension is just a representation/interpretation of the given filename. Nothing more than making it easier for us humans to have an idea what a file contains, without having to look at the contents.

Sure, I could use some other separator. Point is there is no technical reason for the software to have this behaviour. Dots are a valid character in filenames.
Photo of Michel BRETECHER

Michel BRETECHER, Champion

  • 1256 Posts
  • 267 Reply Likes
The reasons are not technical. Everyone is free to prefer his own code. But language (and characters) imply that you can be understood by others; there must be a minimum set of rules like spelling, punctuation, even common usage for SMS language.
Use of the dot character has been reserved for separating extensions since more than 30 years, the @ has a common meaning for anybody. Older users of computers and programmers have been taught to only use underscore or hyphens in file names or naming computer entities.
You are right that there is no technical reason in this case (since Rick Flohr admits it...), but the world is divided in two categories:
- those who are right to think there is no technical reasons; they will have problems some days...
- those who follow the good old rules; they'll never be bothered.
(Edited)
Photo of MBerlage

MBerlage

  • 6 Posts
  • 0 Reply Likes
Sorry, but no. It's not a 'rule', and never has been on anything younger than MS-DOS.
Photo of Michel BRETECHER

Michel BRETECHER, Champion

  • 1256 Posts
  • 267 Reply Likes
Call it as you like.
As we say here:
"C'est vous qui voyez...
Y'en a qui ont essayé.
Ils ont eu des problèmes."
Photo of Robert Frost

Robert Frost

  • 427 Posts
  • 73 Reply Likes

Agree with Michel, I also use date-time filenames, but I separate the date and time with a dash. It's been the convention for many, many years that . is used for separating the filename from the extension. It's a good convention that most computer users and programmers know about, so why do away with it because you don't want to observe the convention.

Bob Frost

Photo of john beardsworth

john beardsworth

  • 1223 Posts
  • 316 Reply Likes
Agree with Michael and Bob here. It would be surprising if Lightroom deliberately allowed this naming practice.
(Edited)
Photo of MBerlage

MBerlage

  • 6 Posts
  • 0 Reply Likes
As you can read in my original post, Lightroom did allow this.
Photo of john beardsworth

john beardsworth

  • 1223 Posts
  • 316 Reply Likes
I don't doubt you, but it might have been an oversight or bug.
Photo of Cristen Gillespie

Cristen Gillespie

  • 1705 Posts
  • 569 Reply Likes
I never name with a dot. Too old-school, I guess. But if you use the Finder's own Compress feature on a file with filename.jpg, or similar, it will be filename.jpg.zip. It's been doing this for a very long time. So it is perfectly legal, even if it bothers me to see it. Lightroom should allow as legal what Apple says is legal, imo.
Photo of john beardsworth

john beardsworth

  • 1223 Posts
  • 316 Reply Likes
No, Lightroom should follow generally-accepted, cross-platform best practice.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5867 Posts
  • 1282 Reply Likes
Official Response
Lightroom CC2015.12/6.12 was released today and should address this issue.  Please update your Lightroom to the latest version and let us know if you continue to see the issue. Thank you for your patience.

http://blogs.adobe.com/lightroomjournal/2017/07/lightroom-cc-2015-12-now-available.html
Photo of MBerlage

MBerlage

  • 6 Posts
  • 0 Reply Likes
Yes, it looks like it's fixed. Thanks!