On Mon, Aug 01, 2011 at 07:35:06PM +0000, corvid wrote:
Jorge wrote:
On Mon, Aug 01, 2011 at 07:19:37PM +0000, corvid wrote:
Jorge wrote:
On Mon, Aug 01, 2011 at 08:11:16PM +0200, SZERV?C Attila wrote:
Thx for work, pls gettextize (or i14e ;-)) Dillo - thx a lot!
That'd be good to have...
This intrigues me; I'll look into this unless someone who already knows their way around gettext wants to volunteer...?
AFAIR, the main issue here is handling resizes.
Can you elaborate? What I know about gettext is just about exactly zilch, being an English speaker and all...
In a nutshell, you can wrap the strings in the code: "Open" becomes _("open") and gettext does the job of providing the closest string given local settings [1]. On most toolkits widget resize is automatic, but with FLTK there's a need to articulate the resize "by hand". Imagine we have our "tools" button, and we use gettext with a spanish local: .-----. C / Tools '-----' "Tools" becomes "Herramientas", what happens with out button? .-----. C / Herra '-----' or .------------. C / Herramientas '------------' (FWIW, I don't know the answer). [1] http://en.wikipedia.org/wiki/Gettext -- Cheers Jorge.-