|
|
 | | Re: CSV delimiters
|
| (...) I hate it too. IIRC, Excel uses "" instead of \" for an escaped " -- but I could be wrong. I just remember hating it once when I looked at it. :) One nice thing, though, is that Excel can import tab-delimited text, so that's it's saving grace. (...) (24 years ago, 23-Sep-00, to lugnet.admin.database, lugnet.off-topic.geek, lugnet.publish)
| | | | | RE: CSV delimiters
|
| (...) Sorry, I can't help. And I hate the way Excel outputs in plain text. But since it's 2:30 in the morning, I'll make useless comments. Sounds like you're working on the question I asked...augh, and I just entered all the sets manually. Oh well, (...) (24 years ago, 23-Sep-00, to lugnet.admin.database, lugnet.off-topic.geek, lugnet.publish)
| | | | | CSV delimiters
|
| Is there any "official" or "reasonably standardized format" for CSV (_C_omma _S_eparated _V_alue) data? I guess it's pretty obvious, mostly, but how are the delimiter characters typically encoded (specifically: comma, double-quote, and newline)? In (...) (24 years ago, 23-Sep-00, to lugnet.admin.database, lugnet.off-topic.geek, lugnet.publish)
| | | | | Re: compiled / searchable parts database with links to the set guide?
|
| (...) This is great! Todd: How about linking the element count in the set guide to the corresponding inventory page on dands site? KL (...) (24 years ago, 22-Sep-00, to lugnet.db.inv, lugnet.admin.database)
| | | | | Re: compiled / searchable parts database with links to the set guide?
|
| (...) the biggest thing everyone should agree on is the nameing convention... We used partsref and partid for ours, which seemed to be the most complete and easy to use convention... All the rest is really easy to transform, from one format to (...) (24 years ago, 22-Sep-00, to lugnet.db.inv, lugnet.admin.database)
|
|
