 | | 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 (21 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Bye, bye LUGNET
|
|
(...) I was thinking about the 'various ways' that people could get around the built-in filter (if there was one). Then I started thinking that if the filter turns specific words into #%##$, and people know that, so they type S P A C E D words to (...) (21 years ago, 1-Mar-05, to lugnet.general)
|
| |
| | 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 (...) (21 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. (...) (21 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 (...) (21 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
