 | | Re: Internationalization of the part library?
|
|
(...) If only we knew what to do with that lousy crenellated wall topper, we could get rid of the Castle group altogether... (...) FYI: the Boat Stud is now Dish 2 x 2 -- both Peeron and LDList will still match on Boat Stud. And it was officially (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) Mmmmm!!! Rock pieces (BURPs, LURPs, et al) recently became panels ... Castle walls also are in the process of becomming panels ... I no longer know where Boat Stud is as it moves so often ... And that's just the first three off the top of my (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) Done. :-) (now we just have to see what the rest of the LSC says to it) (...) I have worked both with code-based and with string-based lookup (not professionally, though) the last ten-fifteen years. Both methods have their benefits and (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) Peeron/LDraw/Partsref <-> BL isn't simple, because the part numbers are NOT consistant. AFAIK, the only way to actually resolve that is to build a proper translation table, which is what I think BrikTrak uses. (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) From a technical perspective I agree with Larry that the part number looks like the best key, and that the current part name is just one instance of an international language set of names. If we percieve peeron and and bricklink as countries, (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
