Lewis
Tue, 02 Jan 2018 16:23:51
GMT in alt.windows7.general, wrote:
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
Sun, 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.
As far as i'm concerned, SMB is just an attempt to side track the
original discussion. And I see no point in doing that. I made no
claims on suitability for sharing across a network using smb protocol
in the first place. I was simply discussing allowed/not allowed
characters in filenames from the OS perspective itself. And besides,
SMB isn't the only sharing protocol supported or in existance.
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.
Some parts of the Windows OS as a whole do, yes. The OS itself for
the most part, does not. It's mainly an issue with API (formally
interrupts, but that was a long time ago) parsing and file browsing
from a gui perspective which is where you can run into trouble. I
can't state at this point with certainty that Linux based distro's
don't also have more than one character that you can't use for a
filename, but I suspect they do. I can think of atleast one ascii
character that most OSes, I suspect mac included would have a problem
with. The ascii code that represents our enter key; which I think is
still called a return key on macs? Another one, off the top of my
head would be the ascii character code for null as the first letter,
as Windows/DOS systems (Possibly linux/unix as well; I haven't
checked to see exactly how they 'mark' files as deleted) treat that
character as the indicator for file being deleted and previously
allocated space tied to said file now being available.
I'm assuming you know perfectly well what happens when you select a
file for deletion via normal means, so I won't bore you with the
underlying details. If you don't know, I'll take the time and explain
it in further detail.
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.
I don't consider some characters as being reserved so that you
cannot/shouldn't/aren't supposed to use them as part of a filename to
be an issue. For me, it would be like complaining that I couldn't
send any character I wanted to my old printers of yesteryear because
the printer firmware interpreted some of them as control characters
intended for them to change functionality, not print on paper for me.
With that being said, there were other ways to print the control
characters intended for them, but additional steps, a little more
code was required to do it.
That didn't bother me either, as, I understood that some of the
characters the printer normally refused to print were because of the
way in which the technology was originally developed. One character
was to tell the printer the line was finished, advance the paper and
move the print head back to starting position for the next line. For
example.
I treat the filename character limitations you seem to have a problem
with the same way. I don't often find myself needing to use slashes
to represent a date for example. periods work fine for that purpose.
As in 6.18.2027 or something. Personally, I find visually reading it
to be more appealing to my eyes than 06/18/2027 is. YMMV
--
To prevent yourself from being a victim of cyber
stalking, it's highly recommended you visit he
https://tekrider.net/pages/david-brooks-stalker.php
================================================== =
None of your 87 cats lower the toilet seat either.