[LSC] Internationalisation (I18N) of the part library

[Travis Cobbs]

I don't know for sure, but I'm guessing MLCad uses standard Windows stuff
for i18n.  In other words, all the work is done by translating the resource
file.

In LDView, I go that way for the dialog boxes, but since much of the other
text will be shared between Windows, Linux, etc. versions, I just created a
small class that reads in a string table from a file in ini format.  That
was fairly quick and easy.

Personally, for the parts library, I think we'd be best off coming up with
something simple.  I did a quick glance at the gettext stuff, and it looks
to me like the "key" for lookups is the text in the original language.  I
may have misinterpreted that, though.

--Travis

On 10/8/06, Lars C. Hassing <lars at hassings.dk> wrote:
>
> William Howard wrote:
> > How about opening the implementation discussion up to the programmers by
> > posting on Lugnet?
>
> Good idea.
> It would be nice to hear an opinion from anyone who would actually support
> I18N,
> e.g. Michael Lachmann.
> /Lars
>
> _______________________________________________
> LSC mailing list
> LSC at ldraw.org
> http://five.pairlist.net/mailman/listinfo/lsc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://five.pairlist.net/pipermail/lsc/attachments/20061009/e411724f/attachment.html