 | | Is anyone working on the hail fire droid wheel ?
|
|
I was going to take a stab at this, but if someone else is already working on it, I'll tackle something else. PLMK, -JSM (20 years ago, 5-Apr-05, to lugnet.cad.dat.parts)
|
| |
| | Re: Question for the LSC. Blanks in file names legal?
|
|
(...) I know. It didn't do much for me either. (...) See above. (...) Kevin (20 years ago, 5-Apr-05, to lugnet.cad)
|
| |
| | 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 (...) (20 years ago, 5-Apr-05, to lugnet.cad, FTX)
|
| |
| | 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 (...) (20 years ago, 5-Apr-05, to lugnet.cad, FTX)
|
| |
| | Re: Question for the LSC. Blanks in file names legal?
|
|
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 (...) (20 years ago, 5-Apr-05, to lugnet.cad, FTX)
|
| |
| | Re: Question for the LSC. Blanks in file names legal?
|
|
(...) It's not just you. Is the new version of the spec better? It still carries the overloaded definition, but it doesn't rely on it as heavily. The new version of the spec is at: (URL) Can we choose a different word for the textual representation (...) (20 years ago, 5-Apr-05, to lugnet.cad)
|
| |
| | Re: Question for the LSC. Blanks in file names legal?
|
|
(...) <snip> (...) Thanks Steve! (...) Kevin (20 years ago, 5-Apr-05, to lugnet.cad)
|
| |
| | 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 (...) (20 years ago, 5-Apr-05, to lugnet.cad)
|
| |
| | Re: Question for the LSC. Blanks in file names legal?
|
|
(...) As a followup question, at first read/reread, the document is a bit confusing. The term "line" is overloaded. In one case line means, text as it would be viewed on a terminal, and in the other it is a graphical representation of what (...) (20 years ago, 5-Apr-05, to lugnet.cad)
|
| |
| | Question for the LSC. Blanks in file names legal?
|
|
Is it legal to have blanks in file names in type 1 records? I looked at (URL) it does not specify. I'd guess that LDRAW.EXE cannot handle them. What is the LSC's position on this issue. Kevin (20 years ago, 5-Apr-05, to lugnet.cad)
|
