Steve Underwood <[EMAIL PROTECTED]> writes:
> I hope one day that Glade will have facilities, like VC++ 4.0 and later,
> allowing translations to be conducted within the interface builder. VC++ has
> really screwed up the implementation of this, but the basic principal of
> integrating it is the right thing. When translations occur outside the
> interface builder, you have to keep going back into the interface builder to
> see if your new text fits in the available space - very inefficient.
Unlike VC++ we have sane geometry management, and can adapt to strings of different
lengths. This means, that it isn't necessary to constantly tweak your interface
for different languages - in general it will _just_work_.
That doesn't mean that user interfaces don't have to be checked to make sure
that everything does work, but it does mean that putting translations into
the GUI builder is simply a bad idea.
Instead of the translators being able to go linearly through a list of strings,
they would have to explore the interface and hope they found all the strings
that needed translation.
(OTOH, a po-file editor that allowed you quickly to see the string in the
context of the user interface might be useful.)
Regards,
Owen
+---------------------------------------------------------------------+
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the line "unsubscribe glade-devel" in the body of the message.
