[LSC] Internationalisation (I18N) of the part library

[Travis Cobbs]

On 10/6/06, Travis Cobbs <tcobbs at gmail.com> wrote:
>
> I think using GNU gettext format for the translations might be a reallybad idea.  First of all, most ldraw tools don't run in *nix, so just using
> it might be a pain.  Secondly, gettext is GPL, and not LGPL, which means
> it can only be used by GPL-licensed tools.
>
> I haven't looked at the format of .pot and .po files, so it could be that
> they're easy for anyone to parse on their own.  If this is the case, then we
> can consider using the format anyway.  But it seems odd to use a file format
> designed to be used by a library that most ldraw software won't be using.
>
> Note: my program, LDView, is already licensed under GPL.  (The QT version
> has to be, since it uses QT GPL.)  But I know that there are a bunch of
> ldraw tools that aren't GPL (MLCad is probably at the top of the list).
>
> --Travis



My reply above was referring to the document linked to in William's second
post to this thread.  I realized after sending it that this wasn't clear.

In response to William's original post, here's my thinking:

Have one table with filename as the primary key that includes sub-keys for
name and description.
Have another table which is a simple string lookup to be used for categories
and keywords.  The primary key of this table is the English text found in
the files (space allowed).

We could fairly easily create a tool that scans the entire parts library and
generates an English version of the translation file.  Translators would
then just go through that file and translate the data.

--Travis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://five.pairlist.net/pipermail/lsc/attachments/20061006/deedcb70/attachment.htm