 | | Re: No mention of scale in file format doc
|
|
(...) I beg to differ. The width of a 1x1 brick is not the same as the spacing between two stud centres. Bricks have a small gap between them, whereas studs are very accurately placed on any brick with more than 1 stud. The LDU unit should be (...) (20 years ago, 2-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: No mention of scale in file format doc
|
|
(...) Well, yes, and no. The bricks are not nearly as precise as the molds, but the dimensional tolerances for parts must certainly be a lot tighter than the difference between 1/64" and 0.4 mm. That difference is almost a full percent, so there is (...) (20 years ago, 2-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) They're just modified plate & brick: 6072 Plate 7 x 7 with cutouts and castle crenelations 6066 Brick 4 x 8 x 2 & 1/3 with cutouts and castle crenalations -John Van (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) OK, so I exaggerated a little bit. ;-) Only reason it sticks in my mind is because of that one release where it and the 2x2 radar dish shared the same name. (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) And Lego may change the number of that 2x2 from 3003 to 53456343, but it'd still be a 3003 to us, right? (...) Yes, true. (...) LDraw numbers are designed to be unambiguous. And that unambiguity is enforced by the fact that we store our data (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) Exactly. (...) Yes. (...) I wouldn't. But we would have to work around that problem anyway. (...) Exactly. Play well, Jacob (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) Both. The default for CATEGORY is the first word from the part title. Most parts have no explicit CATEGORY. I believe in all the examples given by William, the default CATEGORY is in effect. (...) I expect we'd work on updating translations in (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) a. I don't think gettext prevents you from using message codes in your code, it just allows you to use whatever text you want. b. Allowing embedded messages makes it easier for programmers, because they can read what's being output. c. (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) But the existing part names are the unique identifier *we* have control over. Lego may well start calling a 'Brick 2x2' 'OleKirk347' in the next version of the moulds, but it's still a 'Brick 2x2', right? There's also the value of at least a (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) Apparently my impression wasn't quite correct here. (...) Yes. But that would require the programs to be able to work directly on whatever translation format we decide to use. And it would inflate the parts library updates with approximately (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
