Talk:Gettext

message: This page seems to be only about GNU gettext, but has a generic gettext title.  It should at least mention that gettext originated at Sun, and is still used by Sun's software and OS.  The portable environment variable is named LANG, not LANGUAGE, the latter being a GNU extension with certain additional features.
:I changed it to GNU gettext for now.  If a generic gettext page is later made, this can be merged back in. Superm401 - Talk 00:01, 8 September 2008 (UTC)
replies: text:   This is now a generic page and not only GNU specific. The article has been renamed to gettext. Wget (talk) 22:01, 25 June 2016 (UTC)
thread_title: Only about GNU gettext

message: It reads on this article that gettext isn't thread safe! But it is locales that aren't thread safe! I'm removing the whole sentence. 80.244.73.230 22:47, 21 October 2007 (UTC)
thread_title:  Thread safe 

message: Some articles link to this one for a discription of PO = portable object, but PO is not mentioned here. Maybe it should be. --LA2 (talk) 02:18, 7 January 2008 (UTC)
thread_title:  Portable Object 

message: Any objections to merging the content from msgfmt into this article and leaving that as a redirect to here? That article has forever been only a 2-sentence stub and almost could be deletable for lack of asserted notability. Is there anything major to say about that utility, and is it so important on its own vs just being a component of the gettext system? DMacks (talk) 19:44, 4 July 2008 (UTC)
thread_title:  Merger from [[msgfmt]] 

message: It should be interesting to present not only how to create, but also how to update a .po file.  http://live.gnome.org/TranslationProject/SvnHowTo shows these steps: intltool-update xy ; vi xy.po ; msgfmt -cv -o /dev/null xy.po  —Preceding unsigned comment added by 82.238.108.175 (talk) 17:03, 25 February 2009 (UTC)
thread_title:  How to update a .po file 

message: I'm just starting with gettext and the like, but I've noticed that if I run gettext with the options given in the example, i.e. run "xgettext --add-comments=/", then the pot (and po) content will include the leading '/' used as the comment tag. I.e. I get:
 #. / TRANSLATORS: Please leave %s as it is, because it is needed by the program.
 #. / Thank you for contributing to this project.
 #: src/name.c:36
 msgid "My name is %s.\n"
 msgstr ""
I have no idea if this is an error here in the article, or if this behaviour may occur for some version(s) of gettext.
It's also the case that, in the case of a continuous set of single-line comments, the tag is only needed on the first single-line, and not on the subsequent lines. Logical, of course, and this means that it's not necessary to add the tag to each line, as in the example (which could imply that it's necessary). You could have:
 /// TRANSLATORS: Please leave %s as it is, because it is needed by the program.
 // Thank you for contributing to this project.
 printf(_("My name is %s.\n"), my_name);
..for an output of:
 #. / TRANSLATORS: Please leave %s as it is, because it is needed by the program.
 #. Thank you for contributing to this project.
 #: src/name.c:36
 msgid "My name is %s.\n"
 msgstr ""
Phylasnier (talk) 17:57, 22 August 2014 (UTC)
thread_title:  Incorrect output for example given 

message: The infobox claims it was 1990, its reference suggests it was 1987, the History-section says “Sun Microsystems implemented the first gettext in 1993.”. --MüffelSchnüffel (talk) 03:23, 7 March 2020 (UTC)
thread_title:  When was the first release?