Re: i18n -vs- strings



On 25 Jan , raster@redhat.com wrote:
> On 25 Jan, Tom Tromey shouted:
> I've got another idea.. how about.. instead of people creating buttons:
> 
> button=gtk_button_new_with_label("Ok");
> lets have:
> button=gnome_gtk_button_new_standard("ok");
> 
> There is a list of standard strings for buttons (ok, cancel, retry,
> abort, help, etc....) and these map to text and/or pixmaps in buttons
> (so you could replace all "ok" buttons with green ticks, and all
> "cancel" buttons with red crosses, if the user so wants). so
> internationalisation of standard buttons could merely mean replacing
> the "OK" test with "Ja" or "Oui" or "Da" etc. - or just more generic
> icons like ticks, corsses etc. - dependant on the internationalisation/
> customisation options the user selects.
> 

I'm new to this list, but I would suggest that you replace common
system wide strings such as these with defined constants located in a
common header 


#ifdef ENGLISH

#define kACCEPT   "OK"
#define kABORT    "Cancel"
...

#elif DEUTCH

#define kACCEPT   "Ja"
#define kABORT    "Halt"
...

elif ...



-- 
Fred Bacon

==========================================================================
Aerodyne Research, Inc.                   Phone:   (978) 663-9500 ext. 273
45 Manning Rd.                              FAX:   (978) 663-4918
Billerica, MA  01821-3976                  http://www.aerodyne.com
==========================================================================
   "...the commercial world cannot win an evolutionary arms race with 
    free-software communities..."                       -- Eric S. Raymond



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]