 | | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) Call me paranoid, but long filenames make me nervous because of the other worms packaged along with them (like unicode or UTF-8, blech!). Sure your filenames might look great on Windows, but try to bring them over to another filesystem, or (...) (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) Or, we should start by introducing the new standard, use it in a few (relatively obscure) instances, and give the various software authors a chance to sort it out. Considering the general pace of parts releases, a long-named file would be on (...) (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) This suprises me. Can you elaborate on this? If we in the LSC are going to make an informed decision on this issue, understanding why this is the case with LPub/LSynth would help us greatly. I know all Win32 API calls work fine with long (...) (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) I'm personally undecided on the issue of long filenames. On the one hand Willy is entirely correct that we probably shouldn't disallow them purely because of ldraw.exe/ledit.exe. On the other hand, Kevin's post that LPub/LSynth would both have (...) (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Prefix character on meta commands?
|
|
(...) While I am a current member of the LSC, this hasn't been discussed there. It has always been my understanding that this format for meta commands was never intended to require existing meta commands (official or otherwise) to be changed. (...) (18 years ago, 28-Mar-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Prefix character on meta commands?
|
|
(...) As the author of the meta command section of the 1.0.0.0 spec, my intention wasn't to twist the arms of developers into adopting the "!" prefix or the program name requirement. For non-official LDraw.org programs, I meant for these rules to be (...) (18 years ago, 28-Mar-07, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) To elaborate: Suppose you have a part abcdefg.dat with loads of subparts (Too many to name with the 8.3 restriction). Just make a new subdirectory LDRAW/PARTS/S/abcdefg/ and put the numbered subparts in there (like (...) (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) Darn! In that case I'd suggest making a short filename preparer as a backwards compatibility measure. Perhaps it would bring all longfilename parts into an MPD (with shortened names) or something similar (eg. creates short name versions (...) (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) That's an interesting approach, but I don't know if it'll work for the subpart files that started this thread. I think mklist only handles files in the PARTS directory. The subpart filenames would be embedded in the part files that use them, (...) (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
| |
| | Re: Getting rif off the 8.3 nomenclature???
|
|
(...) Well I've just spent some time on another way. You can make a new version of mklist that works as follows: scan through the parts, if a filename is long then make a new copy of the file with a standardised short file name (possible assigned in (...) (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
