Re: [fltk.development] [RFC] a new class to supportInternationalization
True, but not everything can be changed that way, e.g. file chooser, fatal errors... Ah, right - I thought that was covered too. Oh well, I always use the native file chooser these days anyway! Also fluid can't be translated and adopted to user specific locales. Yes, fluid is more problematic - though I was more focussed on the end user facing aspects of the lib; it does seem to me that the developer facing elements, such as fluid, might tolerate a lesser standard of i18n. Indeed, looking at the recent posts to the lists here, it looks as if *most* of the recent posters (apart from me!) are not native English speakers, and most are making a better job of it than I am! Cheers, -- Ian This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
Re: [fltk.development] [RFC] a new class to supportInternationalization
Hi Ian, True, but not everything can be changed that way, e.g. file chooser, fatal errors... Also fluid can't be translated and adopted to user specific locales. Sanel On 01/29/2013 10:19 PM, Ian MacArthur wrote: On 29 Jan 2013, at 17:35, Sanel Zukan wrote: Maybe question is why FLTK does not support (GNU) gettext across whole library? This way translation strings could be handled in more standard way and you will get for free a bunch of tools or services like Transifex. Hi Sanel, I'm not clear what you are proposing here: it doesn't seem to me that there are all that many strings in the library that are exposed in GUI elements, so I'm not sure what we would i18n here... What am I missing? There are a few places, e.g. in the fl_ask (and related) dialog boxes where strings are coded in, be ISTR that they are all accessible to be changed from user code at runtime? Other than that...? ___ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
