A plea: A tiny change to make Logos catch up thirty years!

When you save as a file from Print/Export, Logos pre-fills the the filename for you with the name of the resource. Great!

But it also replaces all the spaces in the filename with underscores. Not great! I understand the need to eliminate invalid characters like the colon, but spaces have been valid on Windows since 1995! It looks horrible, and serves no useful purpose, and my tidy mind 'has' to correct them all (which is fine for Common_Grace, but a real pain for Praying_Backwards__Transform_Your_Prayer_Life_by_Beginning_in_Jesus_Name, or A_Dictionary_of_the_Bible__Including_Biography_Natural_History_Geography_Topography_Archæology_and_Literature.

Find more posts tagged with

Comments

Donnie Hale

It looks horrible, and serves no useful purpose, and my tidy mind 'has' to correct them all

On the other hand, if it generated the filename with spaces, my tidy mind would eliminate them all with underscores and/or dashes as appropriate. While spaces are allowed in filenames, that doesn't mean it's a good idea.

Donnie

Bruce Dunning

But it also replaces all the spaces in the filename with underscores. Not great! I understand the need to eliminate invalid characters like the colon, but spaces have been valid on Windows since 1995! It looks horrible, and serves no useful purpose, and my tidy mind 'has' to correct them all (which is fine for Common_Grace, but a real pain for Praying_Backwards__Transform_Your_Prayer_Life_by_Beginning_in_Jesus_Name, or A_Dictionary_of_the_Bible__Including_Biography_Natural_History_Geography_Topography_Archæology_and_Literature.

I have wondered about this for a long time but never verbalized it out loud. I usually end up manually changing the titles to remove the underscores and replace them with spaces. I would love to see this change in Logos.

abondservant

But it also replaces all the spaces in the filename with underscores. Not great! I understand the need to eliminate invalid characters like the colon, but spaces have been valid on Windows since 1995! It looks horrible, and serves no useful purpose, and my tidy mind 'has' to correct them all (which is fine for Common_Grace, but a real pain for Praying_Backwards__Transform_Your_Prayer_Life_by_Beginning_in_Jesus_Name, or A_Dictionary_of_the_Bible__Including_Biography_Natural_History_Geography_Topography_Archæology_and_Literature.

I have wondered about this for a long time but never verbalized it out loud. I usually end up manually changing the titles to remove the underscores and replace them with spaces. I would love to see this change in Logos.

Me also

DMB

Interesting 'deja vu'. I remember when Microsoft allowed 'spaces'. It was pretty scary at the time. File names often carried a lot of info and an unexpected 'space' would foul up the parsers.

I don't really care regarding Logos. But I always code to avoid delimiters embedded in file names since the files often end up in non-Windows environments where no telling how the software was written.

Mark Barnes

On the other hand, if it generated the filename with spaces, my tidy mind would eliminate them all with underscores and/or dashes as appropriate. While spaces are allowed in filenames, that doesn't mean it's a good idea.

Out of interest, why? (The only reason I can think of is if you're uploading files to the internet, but modern browsers can even cope with that nowadays.)

Bradley Grainger (Logos)

This will be fixed in the next release.

Mark Barnes

This will be fixed in the next release.

Thank you!

abondservant

This will be fixed in the next release.

Thanks! [Y]

Drew Hannay

Out of interest, why? (The only reason I can think of is if you're uploading files to the internet, but modern browsers can even cope with that nowadays.)

For me personally, Denise hit the nail on the head:

File names often carried a lot of info and an unexpected 'space' would foul up the parsers. [...] But I always code to avoid delimiters embedded in file names since the files often end up in non-Windows environments where no telling how the software was written.

Matthew C Jones

my tidy mind 'has' to correct them all (which is fine for Common_Grace, but a real pain for Praying_Backwards__Transform_Your_Prayer_Life_by_Beginning_in_Jesus_Name, or A_Dictionary_of_the_Bible__Including_Biography_Natural_History_Geography_Topography_Archæology_and_Literature.

I laughed out loud reading this. I, too, feel compelled to remove all the underscores.

Donnie Hale

Out of interest, why?

Denise alluded to it. I've been a technologist for > 25 years. Filenames that I happen to see in a GUI are incidental. How am I going to deal with them when I get to a command line? Not completely rational, to be sure. But if MS wouldn't have followed *ix file systems in this one thing, as they didn't in so many others, we wouldn't be having this debate.

Donnie

Mark Barnes

Denise alluded to it. I've been a technologist for > 25 years. Filenames that I happen to see in a GUI are incidental. How am I going to deal with them when I get to a command line? Not completely rational, to be sure. But if MS wouldn't have followed *ix file systems in this one thing, as they didn't in so many others, we wouldn't be having this debate.

When I programming I tend to use short lowercase filenames and underscores. But in normal life I use normal English (and therefore I use normal English in Logos).

On the command line I deal with them by simply by using double quotes around the name.

Erwin Stull, Sr.

OT: Wow Donnie. you remember *ix OS? Bringing back memories here. The closest I got to that pre-*os OS was in the design and test of telecommunications systems in the very early 80's. [:)]

Robert M. Warren

This will be fixed in the next release.

Customer service lives here.