Re: libglade-1.99.1



James Henstridge <james daa com au> writes: 
> At the moment, you pass the translation domain as the third argument to
> glade_xml_new (or pass NULL for the default domain).  The alternative
> would be to specify the translation domain as part of the glade file
> itself (maybe as an attribute of the toplevel element).  This option would
> still require some setup in the C code (a call to bindtextdomain() to set
> the directory where translations are found).
> 
> Which option sounds better?

For most apps I can think of, the domain is defined by a preprocessor
macro, so having it specified in the code is probably better.

Havoc





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