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

RE: gettext functions



> > gettext, dgettext, dcgettext
> > ngettext, dngettext, dcngettext
> > textdomain, bindtextdomain
> > (there may be more missing)
> > 
> > Of those, I only find gettext, dcgettext,
> > textdomain and bindtextdomain

> gettext is an "LSB" standard
> 
> http://linuxbase.alt.org/dbadmin/browse/interface.php?cmd=disp
> lay-letter&prefix=gettext&Display=Display
> 
> where the others are not
> 
> http://linuxbase.alt.org/dbadmin/browse/interface.php?cmd=disp
> lay-letter&prefix=dgettext&Display=Display

Actually, dcgettext too.  I don't quite understand
this database output... why are there six entries
for gettext, for example: three listed as "All"
and three as "IA32" for Architecture.


Anyway, further research turned up that one set was
earlier than the other.  These have GLIBC_2.0
symbol versions:

gettext, dgettext, dcgettext, textdomain, bindtextdomain

The other four have GLIBC_2.2 symbol versions.
Ummm, okay, THREE, plus the one I didn't list,
bind_textdomain_codeset

I see no reason why the first set should not be
complete, if we've got gettext and dcgettext,
we should have dgettext.  All well documented
in the glibc manpages, dgettext is gettext with
an extra argument, a pointer to the message
domain (in gettext this is suplied by a previous
call to textdomain, instead of an explicit
argument).


-- 
To UNSUBSCRIBE, email to lsb-spec-request@lists.linuxbase.org
with subject of "unsubscribe". Trouble? Email listmaster@lists.linuxbase.org



Reply to: