To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.dev.org.ldrawOpen lugnet.cad.dev.org.ldraw in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / Organizations / LDraw / *3491 (-20)
  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)
 
  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)
 
  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)
 
  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) ! 
 
  Re: Internationalization of the part library?
 
(...) Personally, I agree. That said, if the LSC decided that internationalization is not a goal then some consideration of how to proceed would be needed, but I would tend to want to follow their recommendation, it's their charter to own decisions (...) (20 years ago, 28-Feb-05, to lugnet.cad.dev.org.ldraw)
 
  Re: Internationalization of the part library?
 
(...) Personally I think this is well within the pervue of the LSC. I see no need for another organization. Kevin (20 years ago, 28-Feb-05, to lugnet.cad.dev.org.ldraw)
 
  Re: Internationalization of the part library?
 
(...) I feel it falls more to the LSC than any other group currently in existence. Although, the SteerCo could appoint a new i18n group... (...) I am picking my way through (URL) there another source of a good summary? From what I've read, this (...) (20 years ago, 28-Feb-05, to lugnet.cad.dev.org.ldraw)
 
  Re: No mention of scale in file format doc
 
(...) some links about this topic: (URL) I use paul's figures: 1 LDU = 0.015625 inch = 0.396875 mm (20 years ago, 28-Feb-05, to lugnet.cad.dev.org.ldraw)
 
  Re: No mention of scale in file format doc
 
(...) Thank you very much! Can you also add similar text under linetype 3? Steve (20 years ago, 28-Feb-05, to lugnet.cad.dev.org.ldraw)
 
  Re: No mention of scale in file format doc
 
(...) Hmm. Where did that figure come from? I've been using 1 LDU = .4mm for quite awhile now... (...) heh. Don't be *too* sure about that, I seem to remember seeing some early evidence about measurements in English units. But it's a vague memory, I (...) (20 years ago, 28-Feb-05, to lugnet.cad.dev.org.ldraw)


Next Page:  5 more | 10 more | 20 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR