 | | | | | | |
| |
|
In lugnet.cad, Kevin L. Clague wrote:
> The only strike against double quotes is backward compatibility.
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.
> Isn't it too late to make this a requirement?
I only asked for a recommendation, not a requirement. But I would
like some sort of decision to move forward with. Also, I suspect
that filenames with embedded spaces are not all that widely used
at this point because of the lack of any kind of standard. If you
look, you'll see everytime someone has mentioned it, the suggestion
was not to use them.
Anyhow, how about if the Ldraw Standards Committee folks have a
round of emails and give some direction. I don't really care all
that much what gets picked, just pick something so we can code it
and expect other programs to read it. Here's some choices.
1. Everything to the end of line except trailing whitespace.
2. Accept filenames with surrounding quotes (and whitespace inside).
3. Both 1 and 2 are acceptable.
4. Same as 3, but prefer 1.
5. Same as 3, but prefer 2.
6. 8.3 filenames only. Curses upon you if you do anything else.
How about it? Enjoy,
Don
| | | | | | | | | | | | | | | |
> > Isn't it too late to make this a requirement?
>
> I only asked for a recommendation, not a requirement. But I would
> like some sort of decision to move forward with. Also, I suspect
> that filenames with embedded spaces are not all that widely used
> at this point because of the lack of any kind of standard. If you
> look, you'll see everytime someone has mentioned it, the suggestion
> was not to use them.
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 :)
--
Dean Earley, Dee (dean@earlsoft.co.uk)
irc: irc://irc.blitzed.org/
web: http://personal.earlsoft.co.uk
phone: +44 (0)780 8369596
| | | | | | | | | | | | | | | | | |
In lugnet.cad, Don Heyse wrote:
>
> 1. Everything to the end of line except trailing whitespace.
> 2. Accept filenames with surrounding quotes (and whitespace inside).
> 3. Both 1 and 2 are acceptable.
> 4. Same as 3, but prefer 1.
> 5. Same as 3, but prefer 2.
> 6. 8.3 filenames only. Curses upon you if you do anything else.
>
> How about it? Enjoy,
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 thinking going.
| | | | | | | | | | | | | | | | |
In lugnet.cad, Don Heyse wrote:
>
> 1. Everything to the end of line except trailing whitespace.
> 2. Accept filenames with surrounding quotes (and whitespace inside).
> 3. Both 1 and 2 are acceptable.
> 4. Same as 3, but prefer 1.
> 5. Same as 3, but prefer 2.
> 6. 8.3 filenames only. Curses upon you if you do anything else.
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 choice) to be used. But as long as you use a character that is currently
invalid, it would be backward compatible.
ROSCO
| | | | | | |
