| | Re: Question for the LSC. Blanks in file names legal? Kevin L. Clague
| | | (...) 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)
| | | | | | | | Re: Question for the LSC. Blanks in file names legal? Steve Bliss
| | | | | (...) 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? Kevin L. Clague
| | | | | (...) I know. It didn't do much for me either. (...) See above. (...) Kevin (20 years ago, 5-Apr-05, to lugnet.cad)
| | | | | | |