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.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
Comments
-
Mark Barnes said:
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
0 -
Mark Barnes said:
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.
Using adventure and community to challenge young people to continually say "yes" to God
0 -
Me alsoBruce Dunning said:Mark Barnes said: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.
L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
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.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Donnie Hale said:
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.)
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
This will be fixed in the next release.
0 -
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Thanks! [Y]Bradley Grainger (Logos) said:This will be fixed in the next release.
L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
Mark Barnes said:
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:
Denise said: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.
0 -
Mark Barnes said:
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.
Logos 7 Collectors Edition
0 -
Mark Barnes said:
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
0 -
Donnie Hale said:
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.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
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. [:)]
0 -
Hmmm ... we're looking at 'early 80s' and '25 years a technologist'. This leaves us a 10 year gap in the recording. Is that Richard .... Dick, is that you?
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Denise said:
Hmmm ... we're looking at 'early 80s' and '25 years a technologist'. This leaves us a 10 year gap in the recording. Is that Richard .... Dick, is that you?
Denise,
Once again, your comments are inscrutable.
I said "> 25 years." I entered the technology workforce in early 1987 and the software industry in mid-'88. MS added spaces into its file systems first in 1994 with Windows NT 3.1 (the first NTFS file system) and then more popularly in Windows 95 (FAT32, IIRC). I don't recall if OS/2 allowed spaces or not (the HPFS file system), but that would precede NT. Support for spaces in *ix (at that point, the couple of flavors of Unix) goes back into the 80s (at least), but that is before me getting into the field.
My main point was that MS diverged from *ix file systems in its use of drive letters and in using backslashes instead of forward slashes. It would have been great if it diverged from them in never supporting spaces, too (IMO).
Donnie
0 -
Donnie, I'm not entirely inscrutable. Just playful with the imagery of hazily described events suggesting a 'gap' and inviting more information.
I entered the computing world with DOS, and the Unix guys were yesterday's Mac-ivelians with long noses, and arguments difficult to argue with.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Donnie Hale said:
My main point was that MS diverged from *ix file systems in its use of drive letters and in using backslashes instead of forward slashes. It would have been great if it diverged from them in never supporting spaces, too (IMO).
Donnie, I think you can even today refer to every file on a MS system in 8.3 notation (which of course takes away from the 8 to show ~ and a consecutive number before the dot).
OT: Don't know what's internally the leading representation, however on Win 7 when copying deep file trees I occasionally run into the issue that the available character space for path & file name is exhausted and attributed it to long filenames. Using "CamelCase" instead of replacing spaces with underscores would only help a bit, though..
Have joy in the Lord!
0 -
NB.Mick said:
Donnie, I think you can even today refer to every file on a MS system in 8.3 notation (which of course takes away from the 8 to show ~ and a consecutive number before the dot).
Not any more (or at least it can be disabled).
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
-
0
-
macOS (Logos Pro - Beta) | Android 13 (Logos Stable)
0
