 | | Re: Standardized Inventory File Format?
|
|
(...) But not every major user wants to run Perl. Steve (27 years ago, 24-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) It doesn't do much good if the use of commas makes it so the columns don't line up. You want these inventory files to be easy to read by humans, and that means the columns need to line up! If we use commas as delimeters, we also need to add (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) Yes -- the way to do that type of transformation in a single operation is to replace the grep expression / +/ with /,/. Of course, if you don't have grep replace in your text editor, get a real text editor (-: Just kidding! Every major OS can (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) My parts database format is human-readable and well-suited to use by programs as well as humans, and solves your problem quite well. My inventory scripts use it. Look at: (URL) are some sample entries: ld2412, mr0055 Name: 1 x 2 tile with (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
Steve Bliss wrote in message <37ea300b.59491442@l...et.com>... (...) People may end up with multiple commas if there happens to be a gap of six or more spaces, then. Of course after replacing ' ' with ',', they could replace ',,' with ','. It might (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) Look at (URL) The LDraw numbers are included there, and there are links to Technica and Lutz Uhlman's parts list. Steve (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) Are there many programs that support multi-character delimiters in their import function? I'm fairly certain Excel and MS-Access do not. The point of making a standard format is to make the data more accessible to everyone. Not just coders. I (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
John Cromer wrote in message ... (...) I'd start at (URL) and try printing the Word version of the parts catalog. M$IE garbled the images and then crashed badly on me when I tried viewing the HTML version from the zip file. Forced a reboot (I made (...) (27 years ago, 23-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) This (...) Let's do it. 3 spaces between fields: count DATfilename Color Optional description Now, not being a CAD nut, where would I find the DATfilenames? And what do we put for parts without DATfilenames? as evah, John C. (27 years ago, 22-Sep-99, to lugnet.db.inv)
|
| |
| | Re: Standardized Inventory File Format?
|
|
(...) I solve that problem by using *3 or more spaces* as the delimiter. If you want to delimit the next field, you must always use at least 3 spaces in a row. This allows things like color names to include spaces and allows for a little human error (...) (27 years ago, 22-Sep-99, to lugnet.db.inv)
|
