Subject:
|
Re: LDRAWPREDIRS LDRAWPOSTDIRS - Summary please!
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Mon, 15 Mar 2004 21:34:17 GMT
|
Viewed:
|
4320 times
|
| |
|
|
In lugnet.cad.dev, Don Heyse wrote:
> In lugnet.cad.dev, Michael Lachmann wrote:
> > "Don Heyse" schrieb:
> > > If we're going to use the <LDRAWDIR>\folder syntax with the
> > > slash, should we restrict it to the DOS style since we already
> > > must deal with that inside the official parts files with the
> > > parts\s and p\48 subdirectories. Just a thought...
> >
> > No I don't think so, there will be no old programm reading this file, or the
> > section in it. I think there are no real dos applications created now, or?
> > Even if you create command line applications now, they will be able to work
> > with long file names.
>
> Actually I wasn't thinking about long filenames, just the slashes.
Well, I still compile a 16-bit DOS version of L3P for a few users (2%),
but I think the coming version 1.4 will be the last. The possibilities
when having the full tree in memory are too tempting.
We can recommend the few hardcore DOS users to use 8+3 naming.
> I can never remember which one is called backslash so I probably
> wasn't all that clear. Maybe we should just *recommend* using the
> DOS style slashes as the directory separator, especially for any
> directories that start with <LDRAWDIR> because we know from the
> part files that all programs (new or old) must be able to handle
> the DOS \ path separator character.
My API will provide you with the kind of slashes used on the platform
you are running no matters what's in the ini file.
> > > And I'm curious about the <> characters in filenames. I tried to make
> > > some under Win2K and on a linux EXT2 filesystem and failed. Ok, that's
> > > not a really extensive filesystem test, but do you remember where you
> > > saw them?
> >
> > I must say I didn't try that after windows nt 3.51 which did allow that,
> > when you created a file at least. I will have a test on that.
>
> I wouldn't bother. I bet there are plenty of filesystems where you
> can create really weird filenames as long as you use a program instead
> of the command line to do it. Once someone mentioned doing it that
> way with DOS I remembered running into both UNIX and DOS filenames that
> I had to build special programs to work with.
On Linux try this
touch ' "<|>'
the only illegal characters are '/' and '\0'.
So even double-quotes won't work. I think the *only* correct solution is what James Reynolds
told us Apple uses: <sometag>/Path/><&</sometag>
But we can of course choose to say that we don't support directories with double-quotes...
/Lars
|
|
Message has 1 Reply:
 | | Re: LDRAWPREDIRS LDRAWPOSTDIRS - Summary please!
|
| (...) Hey, this reminded me of something. Is there some flavor of Windows that uses nasty 16 bit unicode filenames? That could get quite messy. I think the unix world is moving toward UTF-8 which sounds a bit more sane, and should work with either (...) (21 years ago, 15-Mar-04, to lugnet.cad.dev)
|
Message is in Reply To:
| | Re: LDRAWPREDIRS LDRAWPOSTDIRS - Summary please!
|
| (...) Actually I wasn't thinking about long filenames, just the slashes. I can never remember which one is called backslash so I probably wasn't all that clear. Maybe we should just *recommend* using the DOS style slashes as the directory separator, (...) (21 years ago, 15-Mar-04, to lugnet.cad.dev)
|
132 Messages in This Thread:
(Inline display suppressed due to large size. Click Dots below to view.)
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
