Subject:
|
Re: Question for the LSC. Blanks in file names legal?
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Tue, 5 Apr 2005 13:16:14 GMT
|
Viewed:
|
993 times
|
| |
|
|
How about this for a File Naming section to be added to the file spec?
(the following text is formatted for FTX display; it will be reformatted for
HTML display when it is added to the LDraw.org File Format document)
File Names in LDraw
The LDraw language was originally developed for use with DOS 8.3 file names.
This is generally the most restrictive file naming standard, so continuing to
follow it will result in the greatest portability across computer platforms.
However, most LDraw tools allow greater flexibility in naming model files.
In general, the following restrictions apply to LDraw files:
- No space characters allowed in file names. This restriction is required for any file that will be referenced by another LDraw file. The LDraw language does not support space characters embedded in file names.
- No space characters in directory names. This varies between tools, but is generally a good rule to follow.
- File names should be considered case-insensitive.
- Backslash (\) is used as the delimiter in path names.
- Long file names are generally allowed.
- Files in the LDraw.org Modeling Library must follow the DOS 8.3 naming standard, along with a number of other restrictions. See the FAQ for Part Numbers, in the PT Reference pages.
- Standard model files should use the LDR extension. LDR is for LDraw file.
- Files in the LDraw.org Modeling Library use DAT extension. DAT is a generic file extension (standing for Data), and is been used for LDraw files since the beginning of LDraw-history.
- Compound files use an extension of MPD, for Multi-Part DAT. See the MPD Language Extension.
|
|
Message has 3 Replies:
 | | Re: Question for the LSC. Blanks in file names legal?
|
| (...) I like it Steve. Thanks much. I've gotten problem reports over the last week or so that brought this to light for me. MLCad allows blanks in file names, and LPub percieves them as separate tokens in a type 1 text line, and ignores the extra (...) (19 years ago, 5-Apr-05, to lugnet.cad, FTX)
| | | Re: Question for the LSC. Blanks in file names legal?
|
| (...) See below. I've rearranged the order of the bullets to fit my comments. (...) Change to no whitespace characters, this way we exclude tabs, etc. (...) How about: Long file names are allowed. File names may be restricted to 8.3 format at the (...) (19 years ago, 5-Apr-05, to lugnet.cad, FTX)
| | | Re: Question for the LSC. Blanks in file names legal?
|
| (...) You might want to take a look at 2593.dat (including the author ;-). (In your defense, that's a really old file.) Having said that, most places in the parts library, backslash (\) is used as the delimiter in path names. However, there are some (...) (19 years ago, 6-Apr-05, to lugnet.cad, FTX)
|
Message is in Reply To:
| | Re: Question for the LSC. Blanks in file names legal?
|
| (...) No. LDraw commands are space-delimited, so a filename containing blanks would result in a 'Part' command with invalid formatting/syntax. That is, it would have too many parameters. (...) Hmm. It should be more explicit on this point. It should (...) (19 years ago, 5-Apr-05, to lugnet.cad)
|
14 Messages in This Thread:
 
  
- 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
|
|
|
|
