To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cadOpen lugnet.cad in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / *41465 (-20)
  Re: searching for tv-spots from TLC
 
(...) Here's a collection of YouTube links: (URL) Looking those up was way more fun than I expected. (18 years ago, 29-Mar-07, to lugnet.mediawatch, lugnet.cad)
 
  Re: Getting rif off the 8.3 nomenclature??? (scanf tricks)
 
(...) misparse file names with blanks or tabs in them. (...) will be backward compatible and not cause problems (at least not for (...) I have no idea whether this could be worked into your sscanf usage, but it is possible to read whitespace into (...) (18 years ago, 29-Mar-07, to lugnet.cad.dat.parts, lugnet.cad.dev, FTX)
 
  Re: Getting rif off the 8.3 nomenclature???
 
(...) OK, that makes a lot more sense. LDView had the same problem with whitespace in filenames until I specifically added support for that. (LDView now gives you a warning when it encounters whitespace in a filename.) --Travis (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
 
  Re: Getting rif off the 8.3 nomenclature???
 
(...) Sorry for posting to my own post. In particular if the "longer file names" cannot have blanks in the names, then there is no problem for LPub or LSynth. 20.3 would require no changes at to LPub or LSynth. Given that sscanf splits things up by (...) (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
 
  Re: Getting rif off the 8.3 nomenclature???
 
(...) Travis it has to do with parsing. For type 1 lines and 8.3 I can simply use sscanf. Kevin (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
 
  searching for tv-spots from TLC
 
I have some tv-spots from TLC. Does anybody has also some from other countries than germany. mikeheide (18 years ago, 28-Mar-07, to lugnet.mediawatch, lugnet.cad)
 
  Re: Getting rif off the 8.3 nomenclature???
 
(...) Well, I still do ocasionally, when I'm using my remote MS-DOS based platform. And on my other platform, running on a Windows NT operating system, (URL) this nomenclature test> failed on the second line. (Although I do not fully understand the (...) (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts, FTX)
 
  DATheader
 
I have just updated DATheader with some features. According to the actual discussion with long filenames I have tested long filenames also with spaces in the name and all worked fine. But keep in mind that this is only for windows systems. mikeheide (18 years ago, 28-Mar-07, to lugnet.cad)
 
  Re: Getting rif off the 8.3 nomenclature???
 
(...) We are talking about official files in the parts library here. They're not going to have Unicode or special characters. If this isn't already explicitly in the spec for library filenames, we can certainly add it. As a side note, UTF-8 and (...) (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
 
  Re: Getting rif off the 8.3 nomenclature???
 
(...) Couldn't that be dealt with by restricting the filenames to alphanumerics + the usual suspects (_ etc.)? My understanding was those were unchanged in any character set. Tim (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
 
  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)


Next Page:  5 more | 10 more | 20 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR