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 / 3475
3474  |  3476
Subject: 
Re: Internationalization of the part library?
Newsgroups: 
lugnet.cad.dev.org.ldraw
Date: 
Mon, 28 Feb 2005 14:43:59 GMT
Viewed: 
7663 times
  
In lugnet.cad.dev.org.ldraw, Jacob Sparre Andersen wrote:
> Willy Tschager wrote:
> 
> > could you please work out a standard for the
> > internationalization of the part names.
> 
> I don't think it is really the task of the LSC to define a
> standard for internationalization (i18n) of part names

I feel it falls more to the LSC than any other group currently in existence.
Although, the SteerCo could appoint a new i18n group...

> here is a sketch of how I believe it should be handled:
> 
>  + The names found in LDraw files (parts and models) are
>    considered to be in the "POSIX" locale.
> 
>  + LDraw.org publishes a ".pot" file (translation template)
>    containing the names of all the parts files available
>    from LDraw.org (both official and unofficial).
> 
>  + Translators can submit translations (as ".po" files) back
>    to LDraw.org for distribution to users and developers.
> 
>  + Developers of applications using the LDraw.org parts
>    library are encouraged to use the translations of the
>    parts names available from LDraw.org to make the parts
>    names available to the users in their preferred
>    languages.

I am picking my way through
http://www.gnu.org/software/gettext/manual/html_node/gettext.html
Is there another source of a good summary?

From what I've read, this approach doesn't quite fit our needs, but would be
useable.  That is, we've got a good key (the part number) to use as a basis for
looking up translations, but gettext uses the original part title.

> Putting the translations in the parts files would mean that
> the parts library would have to be updated, every time
> somebody added a translation of the name of a part to one
> more language.

Nod, true.

> Using the (GNU) Gettext approach of keeping translations in
> separate files is in my opinion preferable.

I agree.

Steve



Message has 1 Reply:
  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 (22 years ago, 28-Feb-05, to lugnet.cad.dev.org.ldraw)

Message is in Reply To:
  Re: Internationalization of the part library?
 
(...) I don't think it is really the task of the LSC to define a standard for internationalization (i18n) of part names, but here is a sketch of how I believe it should be handled: + The names found in LDraw files (parts and models) are considered (...) (22 years ago, 28-Feb-05, to lugnet.cad.dev.org.ldraw)

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
    

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