Wolf K Sun,
17 Dec 2017 00:23:52 GMT in alt.windows7.general, wrote:

On 2017-12-16 17:59, Char Jackson wrote:
On Sat, 16 Dec 2017 19:49:16 -0000 (UTC), Lewis
wrote:

In message Char
Jackson wrote:
On Fri, 15 Dec 2017 08:47:47 -0000 (UTC), Lewis
wrote:

In message Char
Jackson wrote:
On Thu, 14 Dec 2017 17:24:34 -0000 (UTC), Lewis
wrote:

In message Paul
wrote:
Wolf K wrote:
On 2017-12-14 00:24, Your Name wrote:
On 2017-12-14 03:16:11 +0000, Wolf K said:

On 2017-12-13 19:37, Your Name wrote:
[...]
... you can't rely on the OS to do that since a JPEG
image file can
actually be opened in a text editor as the file's data,
even if it's rarely useful to do so.

That's what Open With is for.

Open With is near useless if you don't know what the file
actually is. You'd have to Open With with every app you
have until you found one that could open it properly.

If we're talking about user convenience, I agree, showing
a file's type as part of the filename is very useful. (But
IMO a three-letter extension is too limited). There are
many other useful conventions, eg, in icon design. These
are converging on a common standard.

If we're talking about choosing a program to open a file,
extenions aren't needed. It would be easy to ensure that
Open With offers only programs that can open a given file
without reference to an extension. Just standardise
metadata (eg, as a series of slots, some which must be
filled, others for dev or user options). Easy peasy.

Have a good day,


Windows is not limited to 8.3.

Might not be in Windows 10 (though I think it is)

Nope. I can't remember what happened before XP, but at least
with XP through 10 you can create a filename with 200+
characters in the extension, as long as you don't exceed the
total number of characters allowed.

Please reread what I said, that file will have an 8.3
representation in the filesystem. This was true in XP and in
Windows 7 and in Windows 8 (Hmm. now I'm not positive about
Windows 8).

Let's try again. Windows filenames are not limited to 8.3.

Not in Win 10, not in 8.x, not in 7, not in Vista, not in XP.
I'll stop there because I don't personally remember when Long
Filename (LFN) support was introduced, but it was somewhere
before that, possibly in Win 95.

You are absolutely wrong.

OK, let's try a third time. It's clear that you're responding
without reading, or at least without understanding, so I'll keep
it simple.

Windows filenames are not limited to 8.3.

There was a time when the "real" filename was 8.3, and the long
file name was metadata. Win 3.x? 9.x? MSDOS 6.x? Can't recall, but
it could cause messes. Seems like Lewis is harking back to those
times.

Windows 9x, yes. win3.x and MSDOS 6.x were not LFN aware. Win9x
changed that... Along with DOS 7 (well, you didn't really think win9x
was it's own OS did you? [g])




--
Please visit our moderators personal page:
https://tekrider.net/pages/david-brooks-stalker.php
Now for a cheeky message from our sponsors:
What's a Fred to do?