 | | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) 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 (...) (19 years ago, 8-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) Hi Don, Using MLCad as a benchmark, the name with blanks is *not* enclosed in quotes. I use the remainder of the line, sans end of line as the file name. Alas, my efforts are for naught. L3P quietly ignores the lines that have names with (...) (19 years ago, 8-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) I am currently going through the L3P code and I have now added support for filenames with spaces, both in linetype 1 and in "0 FILE xxx". It now uses the rest of the line as the filename. It also accepts filenames in double-quotes. /Lars (19 years ago, 10-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
Hmmm, I'm not sure if this effort is actually making things more compatible. (...) I just did a little testing myself. MLCad seems to strip off any whitespace (tabs and space characters) at the end of the line when it grabs the filename. Is that (...) (19 years ago, 10-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) I'll do the same. (...) Hi Don, Nice post. GROUP commands are defined outside the LDraw spec, but I'd guess that the naming issues are the same. I just made a minor change to: 0 PLIST BEGIN SUB <file> // depricated 0 LPUB PLI BEGIN SUB <file> (...) (19 years ago, 10-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) Well, technically ldlite has been around since well before MLCad, and it supports the double quotes, but MLCad is more widely used. So I guess you could make that argument either way. (...) I only asked for a recommendation, not a requirement. (...) (19 years ago, 10-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) I used them until I got a VERY bizarre image of the 10016 tanker in L3p/PovRay. I promptly switched to using hyphens prefixed by the model id :) (19 years ago, 10-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) There are other possibilities too, for example: 7. You can exceed 8.3 but don't embed spaces or other sorts of whitespace 8. Limit filenames to only the character set legal for BrickShelf folders Not meant to be exhaustive, just to get (...) (19 years ago, 10-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Trouble creating building instructions using lpub and mpd file
|
|
(...) You could also define an escape character, to accept the character following (including spaces) as part of the string. However, as the standard allows both / and \ as directory separators, it would require some character other than \ (a common (...) (19 years ago, 11-Apr-05, to lugnet.cad, lugnet.cad.mlcad)
|
