In message 66N Diesel wrote:
Lewis
Fri, 29 Dec 2017 14:10:59
GMT in alt.windows7.general, wrote:

In message
XnsA859B16E258BDHT1@xhJI5gJTbKLpQ4Eq6Ez94drHGcwsn 569oeX.T2d
Diesel wrote:
Paul news 17 Dec 2017 11:01:28 GMT in alt.windows7.general, wrote:

Can I use é in 8.3 ? Probably not :-) They "hadn't invented
foreigners yet", when they did 8.3 :-)

This might surprise you to learn then...

8.3 will use 'extended ascii' aside from a couple. [g] And, even
those, as long as they aren't used as the first character *can*
be used. AFAIK, You can do the same with LFN based names. How do
I know this? Personal experience. I've done it. Even went so far
as to do something very sneaky and wrote a tiny program that
would not only rename folders/files to 8.3 extended ascii, but
occasionally play with the hidden/system bit settings for them as
well. It did a fairly good job of simulating a 'hard disk crash'
to the untrained eye.

However, many many characters will break in SMB, so ig you name a
file

SMB wasn't being discussed. Allowed characters in a filename were.
From the OS perspective, the majority of the extended ascii character
set is allowed and has been for a long long time.

Ignoring SMB issues when talking about Windows filenames is myopic in
the extreme.

The use with Windows files names it that it forbids MANY common
characters. while every other OS seem to be fine forbidding a single
character.

Blow my network up? Assuming I can share a folder with an extended
ascii name in the first place, worst case scenario I can't share it,
and/or it'll timeout when I try to access it from a non local machine
if it does lemme share it. But, it's not going to blow anything up if
it fails. Just cause a delay in access followed up by an error
message. That's Windows and Linux for you. YMMV with Mac.

Macs don't have issues with filenames, networked or not.

--
Well, we know where we're goin'
But we don't know where we've been
And we know what we're knowin'
But we can't say what we've seen