Subject:
|
Re: Internationalization of the part library?
|
Newsgroups:
|
lugnet.cad.dev.org.ldraw
|
Date:
|
Tue, 1 Mar 2005 16:14:45 GMT
|
Viewed:
|
1586 times
|
| |
|
|
In lugnet.cad.dev.org.ldraw, Jacob Sparre Andersen wrote:
> 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.
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, when I've done i18n stuff in
my real job, (NLS, (National Language Support) we called it) we always had a
code that was then replaced by a returned lookup value depending on the local
language.
The parts files already have "one" replacement value in them, the text form of
the part name, but that's not a good choice necessarily for an unambiguous key,
nor is it as stable as the part number itself, right? (or is it... do names
change as often as part numbers do? and even if they do not, are they the right
key from a theoretical standpoint? part numbers are designed to be unambiguous,
names are not necessarily so, although usually are)
|
|
Message has 4 Replies:
 | | 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, (...) (19 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 (...) (19 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 (...) (19 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. (...) (19 years ago, 1-Mar-05, to lugnet.cad.dev.org.ldraw)
|
Message is in Reply To:
22 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
