 | | 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)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) Devil's advocate for a sec, were those NAME changes or CATEGORY changes? (...) That was my thinking too, but I have no stats to back it up. (...) To Jacob's point about keeping changes in sync, which I agree is a valid concern and would need (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | 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)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) Thanks! Looking forward to it! I sort of don't follow the subtlety of the issue with lookup (GNU gettext?), but it seems to me from the outside that the part number ought to be the lookup key rather than one version of the part name. At least, (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | (murfl)
|
|
(murfl) (20 years ago, 1-Mar-05, to lugnet.announce, lugnet.admin.general, lugnet.cad, lugnet.org.it.itlug, lugnet.general) !!
|
| |
| | Re: Looking for parts
|
|
(...) (URL) (...) (2 URLs) (...) (URL) When you don't find parts from number (especially x.... numbers), make a keyword text search in (URL) part tracker list>. Before Ldraw certification of parts, Peeron and Ldraw temporary X... references are not (...) (20 years ago, 1-Mar-05, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Internationalization of the part library?
|
|
(...) It seems like there is general agreement that it would be a good idea, if the LSC creates a standard for i18n in LDraw parts names, so I will post a proposal to the LSC ASAP. Play well, Jacob (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Looking for parts
|
|
I can't find unofficial files for the following parts: 33299 Technic 1 x 3 with 2 Axleholes and Pin x873cx1 Technic Steering Arm with 4 Ball Joints (Complete Assembly with Black Base) x1029 Technic Steering CV Joint I know that there must be an (...) (20 years ago, 1-Mar-05, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: If I were a minifig......
|
|
(...) Unfortunately this scene is not possible to build in 'real' LEGO in the chosen colors. I spotted at least 4 parts not available in the chosen color. But that makes CAD so nice: all parts available in any color. It's a great scene with nice (...) (20 years ago, 1-Mar-05, to lugnet.cad.dat.models, FTX)
|
| |
| | 2005 LDraw Steering Committee Election is open
|
|
The 2005 LDraw.org Steering Committee election is now open. To vote, please visit (URL) and log in with your user account. Next, visit the announcement on LDraw.org here: (URL) the Ballot link. You may vote for up to five candidates. Please cast (...) (20 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw) !
|
| |
| | The Minifig Macro - walk that minifig
|
|
(URL) uses Anton Raves' POV-Ray library. You can create many minifigs with it, and best yet, you can walk them. Option one is to walk it in a straight line--boring. Option two, walk it on a spline. Very cool! There is an animation of a minifig (...) (20 years ago, 1-Mar-05, to lugnet.cad.ray, lugnet.animation, lugnet.announce)
|
| |
| | Re: Collinear vertices warning on very small triangels
|
|
(...) I based the error check code in LDDP on the L3P -check code you published a while ago. Since you have significantly updated this code are you planning on doing sharing again? If you you don't want to release this publically, would you consider (...) (20 years ago, 1-Mar-05, to lugnet.cad.dat.parts)
|
| |
| | Re: Collinear vertices warning on very small triangels
|
|
(...) Yes, reading and parsing files is common code. You can read more here: (URL) next version of L3P/L3Lab do accept your small triangles, see (URL) you set the warning level to 2 (-w2) you will see L3P's warnings (which should have been errors, (...) (20 years ago, 1-Mar-05, to lugnet.cad.dat.parts)
|
