 | | 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)
|
