Subject:
|
Re: Trouble creating building instructions using lpub and mpd file
|
Newsgroups:
|
lugnet.cad, lugnet.cad.mlcad
|
Date:
|
Fri, 8 Apr 2005 13:23:23 GMT
|
Viewed:
|
1113 times
|
| |
|
|
In lugnet.cad, Kevin L. Clague wrote:
> I decided to take the pragmatic way
> out, and adjust my parsing to support file names with blanks.
>
> I think that warnings will lead to just as many emails as the current
> situation (not a lot, but still.... ;^). The content will change to "MLCad
> handles this. Why not LPub?". Rather than spout statements from the spec,
> I'd rather the issue just go away.
>
> So you get blanks in file names! Yay!
I think you made the right decision, but I have a question. Do the
filenames with embedded spaces have quotes around them, or do they just
use up all the space to the end of the LDRAW type 1 command line? The
reason I ask is because I seem to recall some programs treating extra
stuff after the end of the LDRAW commands as comments. It's briefly
mentioned here.
http://news.lugnet.com/cad/dev/?n=7696
FWIW Ldlite has allowed file names with embedded spaces for years
as long as they're "in quotes". Unfortunately for me, the l3 parser
in ldglite only allows this on the command line, not inside the files.
Don
|
|
Message has 1 Reply:
Message is in Reply To:
17 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
|
|
|
|
