Misplaced Pages

gettext

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
GNU internationalization and localization software
This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Gettext" – news · newspapers · books · scholar · JSTOR (August 2008) (Learn how and when to remove this message)
This article is written like a manual or guide. Please help rewrite this article and remove advice or instruction. (May 2009)
(Learn how and when to remove this message)

gettext
Original author(s)Sun Microsystems
Developer(s)various
Initial release1990; 34 years ago (1990)
Stable release0.23 Edit this on Wikidata / 1 December 2024; 27 days ago (1 December 2024)
Repositoryvarious based on OpenSolaris and GNU gettext
Operating systemCross-platform
TypeInternationalization and localization
LicenseVarious free software licenses
Websitewww.gnu.org/software/gettext/ Edit this on Wikidata

In computing, gettext is an internationalization and localization (i18n and l10n) system commonly used for writing multilingual programs on Unix-like computer operating systems. One of the main benefits of gettext is that it separates programming from translating. The most commonly used implementation of gettext is GNU gettext, released by the GNU Project in 1995. The runtime library is libintl. gettext provides an option to use different strings for any number of plural forms of nouns, but this feature has no support for grammatical gender. The main filename extensions used by this system are .POT (Portable Object Template), .PO (Portable Object) and .MO (Machine Object).

History

Initially, POSIX provided no means of localizing messages. Two proposals were raised in the late 1980s, the 1988 Uniforum gettext and the 1989 X/Open catgets (XPG-3 § 5). Sun Microsystems implemented the first gettext in 1993. The Unix and POSIX developers never really agreed on what kind of interface to use (the other option is the X/Open catgets), so many C libraries, including glibc, implemented both. As of August 2019, whether gettext should be part of POSIX was still a point of debate in the Austin Group, despite the fact that its old foe has already fallen out of use. Concerns cited included its dependence on the system-set locale (a global variable subject to multithreading problems) and its support for newer C-language extensions involving wide strings.

The GNU Project decided that the message-as-key approach of gettext is simpler and more friendly. (Most other systems, including catgets, requires the developer to come up with "key" names for every string.) They released GNU gettext, a free software implementation of the system in 1995. Gettext, GNU or not, has since been ported to many programming languages. The simplicity of po and widespread editor support even lead to its adoption in non-program contexts for text documents or as an intermediate between other localization formats, with converters like po4a (po for anything) and Translate Toolkit emerging to provide such a bridge.

Operation

Programming

Typical gettext workflow. The de.po instance on the left shows a "renewing" of translations via msgmerge.

The basic interface of gettext is the gettext(const char*) function, which accepts a string that the user will see in the original language, usually English. To save typing time and reduce code clutter, this function is commonly aliased to _: 

printf(gettext("My name is %s.\n"), my_name);
printf(_("My name is %s.\n"), my_name); // same, but shorter

gettext() then uses the supplied strings as keys for looking up translations, and will return the original string when no translation is available. This is in contrast to POSIX catgets(), AmigaOS GetString(), or Microsoft Windows LoadString() where a programmatic ID (often an integer) is used. To handle the case where the same original-language text can have different meanings, gettext has functions like cgettext() that accept an additional "context" string.

xgettext is run on the sources to produce a .pot (Portable Object Template) file, which contains a list of all the translatable strings extracted from the sources. Comments starting with /// are used to give translators hints, although other prefixes are also configurable to further limit the scope. One such common prefix is TRANSLATORS:.

For example, an input file with a comment might look like: 

/// TRANSLATORS: %s contains the user's name as specified in Preferences
printf(_("My name is %s.\n"), my_name);

xgettext is run using the command: 

xgettext -c /

The resultant .pot file looks like this with the comment (note that xgettext recognizes the string as a C-language printf format string): 

#. TRANSLATORS: %s contains the user's name as specified in Preferences
#, c-format
#: src/name.c:36
msgid "My name is %s.\n"
msgstr ""

In POSIX shell script, gettext provides a gettext.sh library one can include that provides the many same functions gettext provides in similar languages. GNU bash also has a simplified construct $"msgid" for the simple gettext function, although it depends on the C library to provide a gettext() function.

Translating

The translator derives a .po (Portable Object) file from the template using the msginit program, then fills out the translations. msginit initializes the translations so, for instance, for a French language translation, the command to run would be: 

msginit --locale=fr --input=name.pot

This will create fr.po. The translator then edits the resultant file, either by hand or with a translation tool like Poedit, or Emacs with its editing mode for .po files. An edited entry will look like: 

#: src/name.c:36
msgid "My name is %s.\n"
msgstr "Je m'appelle %s.\n"

Finally, the .po files are compiled with msgfmt into binary .mo (Machine Object) files. GNU gettext may use its own file name extension .gmo on systems with another gettext implementation. These are now ready for distribution with the software package.

GNU msgfmt can also perform some checks relevant to the format string used by the programming language. It also allows for outputting to language-specific formats other than MO; the X/Open equivalent is gencat.

In later phases of the developmental workflow, msgmerge can be used to "update" an old translation to a newer template. There is also msgunfmt for reverse-compiling .mo files, and many other utilities for batch processing.

Running

The user, on Unix-type systems, sets the environment variable LC_MESSAGES, and the program will display strings in the selected language, if there is an .mo file for it.

Users on GNU variants can also use the environment variable LANGUAGE instead. Its main difference from the Unix variable is that it supports multiple languages, separated with a colon, for fallback.

Plural form

The ngettext() interface accounts for the count of a noun in the string. As with the convention of gettext(), it is often aliased to N_ in practical use. Consider the code sample: 

// parameters: english singular, english plural, integer count
printf(ngettext("%d translated message", "%d translated messages", n), n);

A header in the "" (empty string) entry of the PO file stores some metadata, one of which is the plural form that the language uses, usually specified using a C-style ternary operator. Suppose we want to translate for the Slovene language: 

msgid ""
msgstr ""
"..."
"Language: sl\n"
"Plural-Forms: nplurals=4; plural=(n%100==1 ? 1 : n%100==2 ? 2 : n%100==3 || n%100==4 ? 3 : 0);\n"

Since now there are four plural forms, the final po would look like: 

#: src/msgfmt.c:876
#, c-format
msgid "%d translated message"
msgid_plural "%d translated messages"
msgstr "%d prevedenih sporočil"
msgstr "%d prevedeno sporočilo"
msgstr "%d prevedeni sporočili"
msgstr "%d prevedena sporočila"

Reference plural rules for languages are provided by the Unicode consortium. msginit also prefills the appropriate rule when creating a file for one specific language.

Implementations

In addition to C, gettext has the following implementations: C# for both ASP.NET and for WPF, Perl, PHP, Python, R, Scala, and Node.js.

GNU gettext has native support for Objective-C, but there is no support for the Swift programming language yet. A commonly used gettext implementation on these Cocoa platforms is POLocalizedString. The Microsoft Outlook for iOS team also provides a LocalizedStringsKit library with a gettext-like API.

See also

References

  1. ^ "About gettext". gnu.org. Retrieved 9 May 2024.
  2. ^ "History of gettext() et al? - comp.unix.solaris". Compgroups.net. Archived from the original on 23 March 2012. Retrieved 3 April 2016.
  3. Bruno Haible (1 December 2024). "gettext-0.23 released [stable]". Retrieved 1 December 2024.
  4. Martindale, Linda (1 November 2002). "Bridging the Digital Divide in South Africa | Linux Journal". linuxjournal.com. Linux Journal. Archived from the original on 17 September 2019. Retrieved 17 September 2019.
  5. Tykhomyrov, Olexiy Ye (1 November 2002). "Introduction to Internationalization Programming | Linux Journal". linuxjournal.com. Linux Journal. Archived from the original on 17 September 2019. Retrieved 17 September 2019.
  6. ^ "How to Translate With GetText PO and POT Files". Icanlocalize.com. Retrieved 3 April 2016.
  7. "Message Translation". The GNU C Library.
  8. "0001122: POSIX should include gettext() and friends - Austin Group Defect Tracker". Austin Group Defect Tracker.
  9. "The Programmer's View". gettext 0.10.35. 30 April 1998.
  10. "GNU gettext utilities: List of Programming Languages".
  11. "po4a". po4a.org.
  12. "The essential toolkit for localization engineers". Translate Toolkit.
  13. "GNU gettext utilities: How Marks Appear in Sources". www.gnu.org. Archived from the original on 25 March 2024. Retrieved 3 April 2024.
  14. "About catgets". gnu.org. Retrieved 24 October 2017.
  15. "AmigaOS Manual: Python Modules and Packages - AmigaOS Documentation Wiki". wiki.amigaos.net. Retrieved 9 July 2023.
  16. "GNU gettext utilities: sh".
  17. "GNU gettext utilities: bash".
  18. ^ "GNU gettext utilities: PO Files". Gnu.org. Retrieved 3 April 2016.
  19. "Files Conveying Translations". Gnu.org. Retrieved 22 April 2014.
  20. "msgfmt Invocation". GNU gettext utilities.
  21. "GNU gettext utilities: Locale Environment Variables". Gnu.org. Retrieved 3 April 2016.
  22. "Language Plural Rules". unicode.org.
  23. "Google Code Archive - Long-term storage for Google Code Project Hosting". Code.google.com. Retrieved 3 April 2016.
  24. "turquoiseowl/i18n: Smart internationalization for ASP.NET". GitHub.com. Retrieved 3 April 2016.
  25. "NGettext.Wpf - Proper internationalization support for WPF (via NGettext)". GitHub. 16 August 2019.
  26. "libintl-perl - An Internationalization Library for Perl That Aims To Be Compatible With the Uniforum Message Translations System as Implemented For Example in GNU Gettext". github.com. Retrieved 14 September 2017.
  27. "Gettext". php.net. Retrieved 24 October 2017.
  28. "gettext – Multilingual internationalization services – Python 3.7.0 documentation". docs.python.org. Retrieved 21 September 2018.
  29. "gettext: Translate Text Messages". rdrr.io. Retrieved 13 November 2021.
  30. "makkarpov/scalingua: A simple gettext-like internationalization library for Scala". github.com. Retrieved 28 April 2016.
  31. "DanielBaulig/node-gettext: An adaption of Joshua I. Miller's Javascript Gettext library for node.js". GitHub.com. Retrieved 3 April 2016.
  32. "hulab/POLocalizedString: gettext for iOS/OS X/watchOS/tvOS". GitHub. hulab. 19 September 2019.
  33. "microsoft/LocalizedStringKit: Generate .strings files directly from your code". GitHub. Microsoft. 12 February 2020.

External links

Categories: