|
|
 | | Re: Color Names
|
| (...) All I mean by "own" (and the reason I keep using quotes) is that someone/some group is driving the process. And as I, and I believe Steve and Tim mentioned, the point I was making wasn't that anyone is told what to do, but that there is input (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
| | | | | Re: Color Names
|
| (...) This does apply to colors, albeit indirectly. A cross-reference would allow different sites/DBs to maintain different color names if they wished, and still translate between parts and colors. (...) Gaining cooperation for a cross-reference (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego)
| | | | | Re: Color Names
|
| (...) I'd suggest that we keep the LEGO names in the database, as another naming scheme. That way, when we want to look up the LEGO name for a color, just look it up in the database. Better yet, when an AFOL calls LEGO and refers to OUR name for (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego)
| | | | | Re: Color Names
|
| (...) Because unless TLC wholy converts over to using the same names that we do, it'd be nice to know what they're talking about when they start using a name that we don't. Also, it's nice to know what to ask for when you need to order a replacement (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
| | | | | Re: Color Names
|
| (...) While this has absolutly nothing to do with color names, it is a good idea that Steve and I have been kicking around for a couple of years now. I know Richard from BrikTrak has already built some translation tables between Peerl/LDraw and BL. (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego)
|
|
