[Lazarus] Localization in toolkit like fpGUI

[Graeme Geldenhuys]

On 19/02/2008, ik <idokan at gmail.com> wrote:
>
> Well I don't like both ideas. Because when (?) fpGUI will support
> Bi-Directional and other Unicode rules, you will require to have some
> sort of code to find out what rule to apply on non direction and/or
> other invisible chars (unless we add it to each text line).

I have already noticed and thought of that.  Starting to changes some
of the dialogs to use the resourcestring constants.

eg:
    lblFontName.Text  := rsFont + ':';

For bi-directional languanges the ':' will be on the wrong end. ;)
Hell, I was hoping nobody would notice or that it would become
somebody else problem. :-)  Planning ahead is always the better
solution.  A quick solution for something like the above, is to
extract that (rsFont + ':') into a function so that in the future the
function can decide where the colon must be placed.

> executable. I also believe that if you'll make a library out of the
> GUI, you will give chance to other programming languages to use it as
> well.

That would be nice, but I have no idea what that would involve.

> So if you'll use the library way, gettext is the right solution, and
> you must also think also on the chars you wish your program to

But again with GetText the simplest little single executable program
in a non-english language is going to require a external language
file.  This it what I don't like about GetText for a toolkit.

Regards,
  - Graeme -


_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/