{ "mode": "info", "parameter": "gettext", "section": "", "url": "https://www.chedong.com/phpMan.php/info/gettext/json", "generated": "2026-06-08T15:59:03Z", "sections": { "GNU 'gettext' utilities": { "content": "This manual documents the GNU gettext tools and the GNU libintl\nlibrary, version 0.21.\n\n* Menu:\n\n* Introduction:: Introduction\n* Users:: The User's View\n* PO Files:: The Format of PO Files\n* Sources:: Preparing Program Sources\n* Template:: Making the PO Template File\n* Creating:: Creating a New PO File\n* Updating:: Updating Existing PO Files\n* Editing:: Editing PO Files\n* Manipulating:: Manipulating PO Files\n* Binaries:: Producing Binary MO Files\n* Programmers:: The Programmer's View\n* Translators:: The Translator's View\n* Maintainers:: The Maintainer's View\n* Installers:: The Installer's and Distributor's View\n* Programming Languages:: Other Programming Languages\n* Data Formats:: Other Data Formats\n* Conclusion:: Concluding Remarks\n\n* Language Codes:: ISO 639 language codes\n* Country Codes:: ISO 3166 country codes\n* Licenses:: Licenses\n\n* Program Index:: Index of Programs\n* Option Index:: Index of Command-Line Options\n* Variable Index:: Index of Environment Variables\n* PO Mode Index:: Index of Emacs PO Mode Commands\n* Autoconf Macro Index:: Index of Autoconf Macros\n* Index:: General Index\n\n-- The Detailed Node Listing --\n\nIntroduction\n\n* Why:: The Purpose of GNU 'gettext'\n* Concepts:: I18n, L10n, and Such\n* Aspects:: Aspects in Native Language Support\n* Files:: Files Conveying Translations\n* Overview:: Overview of GNU 'gettext'\n\nThe User's View\n\n* System Installation:: Questions During Operating System Installation\n* Setting the GUI Locale:: How to Specify the Locale Used by GUI Programs\n* Setting the POSIX Locale:: How to Specify the Locale According to POSIX\n* Working in a Windows console:: Obtaining good output in a Windows console\n* Installing Localizations:: How to Install Additional Translations\n\nSetting the Locale through Environment Variables\n\n* Locale Names:: How a Locale Specification Looks Like\n* Locale Environment Variables:: Which Environment Variable Specfies What\n* The LANGUAGE variable:: How to Specify a Priority List of Languages\n\nPreparing Program Sources\n\n* Importing:: Importing the 'gettext' declaration\n* Triggering:: Triggering 'gettext' Operations\n* Preparing Strings:: Preparing Translatable Strings\n* Mark Keywords:: How Marks Appear in Sources\n* Marking:: Marking Translatable Strings\n* c-format Flag:: Telling something about the following string\n* Special cases:: Special Cases of Translatable Strings\n* Bug Report Address:: Letting Users Report Translation Bugs\n* Names:: Marking Proper Names for Translation\n* Libraries:: Preparing Library Sources\n\nMaking the PO Template File\n\n* xgettext Invocation:: Invoking the 'xgettext' Program\n\nCreating a New PO File\n\n* msginit Invocation:: Invoking the 'msginit' Program\n* Header Entry:: Filling in the Header Entry\n\nUpdating Existing PO Files\n\n* msgmerge Invocation:: Invoking the 'msgmerge' Program\n\nEditing PO Files\n\n* KBabel:: KDE's PO File Editor\n* Gtranslator:: GNOME's PO File Editor\n* PO Mode:: Emacs's PO File Editor\n* Compendium:: Using Translation Compendia\n\nEmacs's PO File Editor\n\n* Installation:: Completing GNU 'gettext' Installation\n* Main PO Commands:: Main Commands\n* Entry Positioning:: Entry Positioning\n* Normalizing:: Normalizing Strings in Entries\n* Translated Entries:: Translated Entries\n* Fuzzy Entries:: Fuzzy Entries\n* Untranslated Entries:: Untranslated Entries\n* Obsolete Entries:: Obsolete Entries\n* Modifying Translations:: Modifying Translations\n* Modifying Comments:: Modifying Comments\n* Subedit:: Mode for Editing Translations\n* C Sources Context:: C Sources Context\n* Auxiliary:: Consulting Auxiliary PO Files\n\nUsing Translation Compendia\n\n* Creating Compendia:: Merging translations for later use\n* Using Compendia:: Using older translations if they fit\n\nManipulating PO Files\n\n* msgcat Invocation:: Invoking the 'msgcat' Program\n* msgconv Invocation:: Invoking the 'msgconv' Program\n* msggrep Invocation:: Invoking the 'msggrep' Program\n* msgfilter Invocation:: Invoking the 'msgfilter' Program\n* msguniq Invocation:: Invoking the 'msguniq' Program\n* msgcomm Invocation:: Invoking the 'msgcomm' Program\n* msgcmp Invocation:: Invoking the 'msgcmp' Program\n* msgattrib Invocation:: Invoking the 'msgattrib' Program\n* msgen Invocation:: Invoking the 'msgen' Program\n* msgexec Invocation:: Invoking the 'msgexec' Program\n* Colorizing:: Highlighting parts of PO files\n* Other tools:: Other tools for manipulating PO files\n* libgettextpo:: Writing your own programs that process PO files\n\nHighlighting parts of PO files\n\n* The --color option:: Triggering colorized output\n* The TERM variable:: The environment variable 'TERM'\n* The --style option:: The '--style' option\n* Style rules:: Style rules for PO files\n* Customizing less:: Customizing 'less' for viewing PO files\n\nProducing Binary MO Files\n\n* msgfmt Invocation:: Invoking the 'msgfmt' Program\n* msgunfmt Invocation:: Invoking the 'msgunfmt' Program\n* MO Files:: The Format of GNU MO Files\n\nThe Programmer's View\n\n* catgets:: About 'catgets'\n* gettext:: About 'gettext'\n* Comparison:: Comparing the two interfaces\n* Using libintl.a:: Using libintl.a in own programs\n* gettext grok:: Being a 'gettext' grok\n* Temp Programmers:: Temporary Notes for the Programmers Chapter\n\nAbout 'catgets'\n\n* Interface to catgets:: The interface\n* Problems with catgets:: Problems with the 'catgets' interface?!\n\nAbout 'gettext'\n\n* Interface to gettext:: The interface\n* Ambiguities:: Solving ambiguities\n* Locating Catalogs:: Locating message catalog files\n* Charset conversion:: How to request conversion to Unicode\n* Contexts:: Solving ambiguities in GUI programs\n* Plural forms:: Additional functions for handling plurals\n* Optimized gettext:: Optimization of the *gettext functions\n\nTemporary Notes for the Programmers Chapter\n\n* Temp Implementations:: Temporary - Two Possible Implementations\n* Temp catgets:: Temporary - About 'catgets'\n* Temp WSI:: Temporary - Why a single implementation\n* Temp Notes:: Temporary - Notes\n\nThe Translator's View\n\n* Trans Intro 0:: Introduction 0\n* Trans Intro 1:: Introduction 1\n* Discussions:: Discussions\n* Organization:: Organization\n* Information Flow:: Information Flow\n* Translating plural forms:: How to fill in 'msgstr[0]', 'msgstr[1]'\n* Prioritizing messages:: How to find which messages to translate first\n\nOrganization\n\n* Central Coordination:: Central Coordination\n* National Teams:: National Teams\n* Mailing Lists:: Mailing Lists\n\nNational Teams\n\n* Sub-Cultures:: Sub-Cultures\n* Organizational Ideas:: Organizational Ideas\n\nThe Maintainer's View\n\n* Flat and Non-Flat:: Flat or Non-Flat Directory Structures\n* Prerequisites:: Prerequisite Works\n* gettextize Invocation:: Invoking the 'gettextize' Program\n* Adjusting Files:: Files You Must Create or Alter\n* autoconf macros:: Autoconf macros for use in 'configure.ac'\n* Version Control Issues::\n* Release Management:: Creating a Distribution Tarball\n\nFiles You Must Create or Alter\n\n* po/POTFILES.in:: 'POTFILES.in' in 'po/'\n* po/LINGUAS:: 'LINGUAS' in 'po/'\n* po/Makevars:: 'Makevars' in 'po/'\n* po/Rules-*:: Extending 'Makefile' in 'po/'\n* configure.ac:: 'configure.ac' at top level\n* config.guess:: 'config.guess', 'config.sub' at top level\n* mkinstalldirs:: 'mkinstalldirs' at top level\n* aclocal:: 'aclocal.m4' at top level\n* config.h.in:: 'config.h.in' at top level\n* Makefile:: 'Makefile.in' at top level\n* src/Makefile:: 'Makefile.in' in 'src/'\n* lib/gettext.h:: 'gettext.h' in 'lib/'\n\nAutoconf macros for use in 'configure.ac'\n\n* AMGNUGETTEXT:: AMGNUGETTEXT in 'gettext.m4'\n* AMGNUGETTEXTVERSION:: AMGNUGETTEXTVERSION in 'gettext.m4'\n* AMGNUGETTEXTNEED:: AMGNUGETTEXTNEED in 'gettext.m4'\n* AMPOSUBDIRS:: AMPOSUBDIRS in 'po.m4'\n* AMXGETTEXTOPTION:: AMXGETTEXTOPTION in 'po.m4'\n* AMICONV:: AMICONV in 'iconv.m4'\n\nIntegrating with Version Control Systems\n\n* Distributed Development:: Avoiding version mismatch in distributed development\n* Files under Version Control:: Files to put under version control\n* Translations under Version Control:: Put PO Files under Version Control\n* autopoint Invocation:: Invoking the 'autopoint' Program\n\nOther Programming Languages\n\n* Language Implementors:: The Language Implementor's View\n* Programmers for other Languages:: The Programmer's View\n* Translators for other Languages:: The Translator's View\n* Maintainers for other Languages:: The Maintainer's View\n* List of Programming Languages:: Individual Programming Languages\n\nThe Translator's View\n\n* c-format:: C Format Strings\n* objc-format:: Objective C Format Strings\n* python-format:: Python Format Strings\n* java-format:: Java Format Strings\n* csharp-format:: C# Format Strings\n* javascript-format:: JavaScript Format Strings\n* scheme-format:: Scheme Format Strings\n* lisp-format:: Lisp Format Strings\n* elisp-format:: Emacs Lisp Format Strings\n* librep-format:: librep Format Strings\n* ruby-format:: Ruby Format Strings\n* sh-format:: Shell Format Strings\n* awk-format:: awk Format Strings\n* lua-format:: Lua Format Strings\n* object-pascal-format:: Object Pascal Format Strings\n* smalltalk-format:: Smalltalk Format Strings\n* qt-format:: Qt Format Strings\n* qt-plural-format:: Qt Plural Format Strings\n* kde-format:: KDE Format Strings\n* kde-kuit-format:: KUIT Format Strings\n* boost-format:: Boost Format Strings\n* tcl-format:: Tcl Format Strings\n* perl-format:: Perl Format Strings\n* php-format:: PHP Format Strings\n* gcc-internal-format:: GCC internal Format Strings\n* gfc-internal-format:: GFC internal Format Strings\n* ycp-format:: YCP Format Strings\n\nIndividual Programming Languages\n\n* C:: C, C++, Objective C\n* Python:: Python\n* Java:: Java\n* C#:: C#\n* JavaScript:: JavaScript\n* Scheme:: GNU guile - Scheme\n* Common Lisp:: GNU clisp - Common Lisp\n* clisp C:: GNU clisp C sources\n* Emacs Lisp:: Emacs Lisp\n* librep:: librep\n* Ruby:: Ruby\n* sh:: sh - Shell Script\n* bash:: bash - Bourne-Again Shell Script\n* gawk:: GNU awk\n* Lua:: Lua\n* Pascal:: Pascal - Free Pascal Compiler\n* Smalltalk:: GNU Smalltalk\n* Vala:: Vala\n* wxWidgets:: wxWidgets library\n* Tcl:: Tcl - Tk's scripting language\n* Perl:: Perl\n* PHP:: PHP Hypertext Preprocessor\n* Pike:: Pike\n* GCC-source:: GNU Compiler Collection sources\n* YCP:: YCP - YaST2 scripting language\n\nsh - Shell Script\n\n* Preparing Shell Scripts:: Preparing Shell Scripts for Internationalization\n* gettext.sh:: Contents of 'gettext.sh'\n* gettext Invocation:: Invoking the 'gettext' program\n* ngettext Invocation:: Invoking the 'ngettext' program\n* envsubst Invocation:: Invoking the 'envsubst' program\n* evalgettext Invocation:: Invoking the 'evalgettext' function\n* evalngettext Invocation:: Invoking the 'evalngettext' function\n* evalpgettext Invocation:: Invoking the 'evalpgettext' function\n* evalnpgettext Invocation:: Invoking the 'evalnpgettext' function\n\nPerl\n\n* General Problems:: General Problems Parsing Perl Code\n* Default Keywords:: Which Keywords Will xgettext Look For?\n* Special Keywords:: How to Extract Hash Keys\n* Quote-like Expressions:: What are Strings And Quote-like Expressions?\n* Interpolation I:: Invalid String Interpolation\n* Interpolation II:: Valid String Interpolation\n* Parentheses:: When To Use Parentheses\n* Long Lines:: How To Grok with Long Lines\n* Perl Pitfalls:: Bugs, Pitfalls, and Things That Do Not Work\n\nOther Data Formats\n\n* Internationalizable Data:: Internationalizable Data Formats\n* Localized Data:: Localized Data Formats\n\nInternationalizable Data Formats\n\n* POT:: POT - Portable Object Template\n* RST:: Resource String Table\n* Glade:: Glade - GNOME user interface description\n* GSettings:: GSettings - GNOME user configuration schema\n* AppData:: AppData - freedesktop.org application description\n* Preparing ITS Rules:: Preparing Rules for XML Internationalization\n\nLocalized Data Formats\n\n* Editable Message Catalogs:: Editable Message Catalogs\n* Compiled Message Catalogs:: Compiled Message Catalogs\n* Desktop Entry:: Desktop Entry files\n* XML:: XML files\n\nEditable Message Catalogs\n\n* PO:: PO - Portable Object\n* Java .properties:: Java .properties\n* GNUstep .strings:: NeXTstep/GNUstep .strings\n\nCompiled Message Catalogs\n\n* MO:: MO - Machine Object\n* Java ResourceBundle:: Java ResourceBundle\n* C# Satellite Assembly:: C# Satellite Assembly\n* C# Resource:: C# Resource\n* Tcl message catalog:: Tcl message catalog\n* Qt message catalog:: Qt message catalog\n\nConcluding Remarks\n\n* History:: History of GNU 'gettext'\n* The original ABOUT-NLS:: Historical introduction\n* References:: Related Readings\n\nLanguage Codes\n\n* Usual Language Codes:: Two-letter ISO 639 language codes\n* Rare Language Codes:: Three-letter ISO 639 language codes\n\nLicenses\n\n* GNU GPL:: GNU General Public License\n* GNU LGPL:: GNU Lesser General Public License\n* GNU FDL:: GNU Free Documentation License\n\n\nFile: gettext.info, Node: Introduction, Next: Users, Prev: Top, Up: Top\n", "subsections": [] }, "1 Introduction": { "content": "This chapter explains the goals sought in the creation of GNU\n'gettext' and the free Translation Project. Then, it explains a few\nbroad concepts around Native Language Support, and positions message\ntranslation with regard to other aspects of national and cultural\nvariance, as they apply to programs. It also surveys those files used\nto convey the translations. It explains how the various tools interact\nin the initial generation of these files, and later, how the maintenance\ncycle should usually operate.\n\nIn this manual, we use he when speaking of the programmer or\nmaintainer, she when speaking of the translator, and they when\nspeaking of the installers or end users of the translated program. This\nis only a convenience for clarifying the documentation. It is\nabsolutely not meant to imply that some roles are more appropriate to\nmales or females. Besides, as you might guess, GNU 'gettext' is meant\nto be useful for people using computers, whatever their sex, race,\nreligion or nationality!\n\nPlease submit suggestions and corrections\n* either in the bug tracker at\n\n* or by email to 'bug-gettext@gnu.org'.\n\nPlease include the manual's edition number and update date in your\nmessages.\n\n* Menu:\n\n* Why:: The Purpose of GNU 'gettext'\n* Concepts:: I18n, L10n, and Such\n* Aspects:: Aspects in Native Language Support\n* Files:: Files Conveying Translations\n* Overview:: Overview of GNU 'gettext'\n\nFile: gettext.info, Node: Why, Next: Concepts, Up: Introduction\n", "subsections": [ { "name": "1.1 The Purpose of GNU 'gettext'", "content": "Usually, programs are written and documented in English, and use\nEnglish at execution time to interact with users. This is true not only\nof GNU software, but also of a great deal of proprietary and free\nsoftware. Using a common language is quite handy for communication\nbetween developers, maintainers and users from all countries. On the\nother hand, most people are less comfortable with English than with\ntheir own native language, and would prefer to use their mother tongue\nfor day to day's work, as far as possible. Many would simply love to\nsee their computer screen showing a lot less of English, and far more of\ntheir own language.\n\nHowever, to many people, this dream might appear so far fetched that\nthey may believe it is not even worth spending time thinking about it.\nThey have no confidence at all that the dream might ever become true.\nYet some have not lost hope, and have organized themselves. The\nTranslation Project is a formalization of this hope into a workable\nstructure, which has a good chance to get all of us nearer the\nachievement of a truly multi-lingual set of programs.\n\nGNU 'gettext' is an important step for the Translation Project, as it\nis an asset on which we may build many other steps. This package offers\nto programmers, translators and even users, a well integrated set of\ntools and documentation. Specifically, the GNU 'gettext' utilities are\na set of tools that provides a framework within which other free\npackages may produce multi-lingual messages. These tools include\n\n* A set of conventions about how programs should be written to\nsupport message catalogs.\n\n* A directory and file naming organization for the message catalogs\nthemselves.\n\n* A runtime library supporting the retrieval of translated messages.\n\n* A few stand-alone programs to massage in various ways the sets of\ntranslatable strings, or already translated strings.\n\n* A library supporting the parsing and creation of files containing\ntranslated messages.\n\n* A special mode for Emacs(1) which helps preparing these sets and\nbringing them up to date.\n\nGNU 'gettext' is designed to minimize the impact of\ninternationalization on program sources, keeping this impact as small\nand hardly noticeable as possible. Internationalization has better\nchances of succeeding if it is very light weighted, or at least, appear\nto be so, when looking at program sources.\n\nThe Translation Project also uses the GNU 'gettext' distribution as a\nvehicle for documenting its structure and methods. This goes beyond the\nstrict technicalities of documenting the GNU 'gettext' proper. By so\ndoing, translators will find in a single place, as far as possible, all\nthey need to know for properly doing their translating work. Also, this\nsupplemental documentation might also help programmers, and even curious\nusers, in understanding how GNU 'gettext' is related to the remainder of\nthe Translation Project, and consequently, have a glimpse at the big\npicture.\n\n---------- Footnotes ----------\n\n(1) In this manual, all mentions of Emacs refers to either GNU Emacs\nor to XEmacs, which people sometimes call FSF Emacs and Lucid Emacs,\nrespectively.\n\nFile: gettext.info, Node: Concepts, Next: Aspects, Prev: Why, Up: Introduction\n" }, { "name": "1.2 I18n, L10n, and Such", "content": "Two long words appear all the time when we discuss support of native\nlanguage in programs, and these words have a precise meaning, worth\nbeing explained here, once and for all in this document. The words are\ninternationalization and localization. Many people, tired of\nwriting these long words over and over again, took the habit of writing\n\"i18n\" and \"l10n\" instead, quoting the first and last letter of each\nword, and replacing the run of intermediate letters by a number merely\ntelling how many such letters there are. But in this manual, in the\nsake of clarity, we will patiently write the names in full, each time...\n\nBy \"internationalization\", one refers to the operation by which a\nprogram, or a set of programs turned into a package, is made aware of\nand able to support multiple languages. This is a generalization\nprocess, by which the programs are untied from calling only English\nstrings or other English specific habits, and connected to generic ways\nof doing the same, instead. Program developers may use various\ntechniques to internationalize their programs. Some of these have been\nstandardized. GNU 'gettext' offers one of these standards. *Note\nProgrammers::.\n\nBy \"localization\", one means the operation by which, in a set of\nprograms already internationalized, one gives the program all needed\ninformation so that it can adapt itself to handle its input and output\nin a fashion which is correct for some native language and cultural\nhabits. This is a particularisation process, by which generic methods\nalready implemented in an internationalized program are used in specific\nways. The programming environment puts several functions to the\nprogrammers disposal which allow this runtime configuration. The formal\ndescription of specific set of cultural habits for some country,\ntogether with all associated translations targeted to the same native\nlanguage, is called the \"locale\" for this language or country. Users\nachieve localization of programs by setting proper values to special\nenvironment variables, prior to executing those programs, identifying\nwhich locale should be used.\n\nIn fact, locale message support is only one component of the cultural\ndata that makes up a particular locale. There are a whole host of\nroutines and functions provided to aid programmers in developing\ninternationalized software and which allow them to access the data\nstored in a particular locale. When someone presently refers to a\nparticular locale, they are obviously referring to the data stored\nwithin that particular locale. Similarly, if a programmer is referring\nto \"accessing the locale routines\", they are referring to the complete\nsuite of routines that access all of the locale's information.\n\nOne uses the expression \"Native Language Support\", or merely NLS, for\nspeaking of the overall activity or feature encompassing both\ninternationalization and localization, allowing for multi-lingual\ninteractions in a program. In a nutshell, one could say that\ninternationalization is the operation by which further localizations are\nmade possible.\n\nAlso, very roughly said, when it comes to multi-lingual messages,\ninternationalization is usually taken care of by programmers, and\nlocalization is usually taken care of by translators.\n\nFile: gettext.info, Node: Aspects, Next: Files, Prev: Concepts, Up: Introduction\n" }, { "name": "1.3 Aspects in Native Language Support", "content": "For a totally multi-lingual distribution, there are many things to\ntranslate beyond output messages.\n\n* As of today, GNU 'gettext' offers a complete toolset for\ntranslating messages output by C programs. Perl scripts and shell\nscripts will also need to be translated. Even if there are today\nsome hooks by which this can be done, these hooks are not\nintegrated as well as they should be.\n\n* Some programs, like 'autoconf' or 'bison', are able to produce\nother programs (or scripts). Even if the generating programs\nthemselves are internationalized, the generated programs they\nproduce may need internationalization on their own, and this\nindirect internationalization could be automated right from the\ngenerating program. In fact, quite usually, generating and\ngenerated programs could be internationalized independently, as the\neffort needed is fairly orthogonal.\n\n* A few programs include textual tables which might need translation\nthemselves, independently of the strings contained in the program\nitself. For example, RFC 1345 gives an English description for\neach character which the 'recode' program is able to reconstruct at\nexecution. Since these descriptions are extracted from the RFC by\nmechanical means, translating them properly would require a prior\ntranslation of the RFC itself.\n\n* Almost all programs accept options, which are often worded out so\nto be descriptive for the English readers; one might want to\nconsider offering translated versions for program options as well.\n\n* Many programs read, interpret, compile, or are somewhat driven by\ninput files which are texts containing keywords, identifiers, or\nreplies which are inherently translatable. For example, one may\nwant 'gcc' to allow diacriticized characters in identifiers or use\ntranslated keywords; 'rm -i' might accept something else than 'y'\nor 'n' for replies, etc. Even if the program will eventually make\nmost of its output in the foreign languages, one has to decide\nwhether the input syntax, option values, etc., are to be localized\nor not.\n\n* The manual accompanying a package, as well as all documentation\nfiles in the distribution, could surely be translated, too.\nTranslating a manual, with the intent of later keeping up with\nupdates, is a major undertaking in itself, generally.\n\nAs we already stressed, translation is only one aspect of locales.\nOther internationalization aspects are system services and are handled\nin GNU 'libc'. There are many attributes that are needed to define a\ncountry's cultural conventions. These attributes include beside the\ncountry's native language, the formatting of the date and time, the\nrepresentation of numbers, the symbols for currency, etc. These local\n\"rules\" are termed the country's locale. The locale represents the\nknowledge needed to support the country's native attributes.\n\nThere are a few major areas which may vary between countries and\nhence, define what a locale must describe. The following list helps\nputting multi-lingual messages into the proper context of other tasks\nrelated to locales. See the GNU 'libc' manual for details.\n\nCharacters and Codesets\n\nThe codeset most commonly used through out the USA and most English\nspeaking parts of the world is the ASCII codeset. However, there\nare many characters needed by various locales that are not found\nwithin this codeset. The 8-bit ISO 8859-1 code set has most of the\nspecial characters needed to handle the major European languages.\nHowever, in many cases, choosing ISO 8859-1 is nevertheless not\nadequate: it doesn't even handle the major European currency.\nHence each locale will need to specify which codeset they need to\nuse and will need to have the appropriate character handling\nroutines to cope with the codeset.\n\nCurrency\n\nThe symbols used vary from country to country as does the position\nused by the symbol. Software needs to be able to transparently\ndisplay currency figures in the native mode for each locale.\n\nDates\n\nThe format of date varies between locales. For example, Christmas\nday in 1994 is written as 12/25/94 in the USA and as 25/12/94 in\nAustralia. Other countries might use ISO 8601 dates, etc.\n\nTime of the day may be noted as HH:MM, HH.MM, or otherwise. Some\nlocales require time to be specified in 24-hour mode rather than as\nAM or PM. Further, the nature and yearly extent of the Daylight\nSaving correction vary widely between countries.\n\nNumbers\n\nNumbers can be represented differently in different locales. For\nexample, the following numbers are all written correctly for their\nrespective locales:\n\n12,345.67 English\n12.345,67 German\n12345,67 French\n1,2345.67 Asia\n\nSome programs could go further and use different unit systems, like\nEnglish units or Metric units, or even take into account variants\nabout how numbers are spelled in full.\n\nMessages\n\nThe most obvious area is the language support within a locale.\nThis is where GNU 'gettext' provides the means for developers and\nusers to easily change the language that the software uses to\ncommunicate to the user.\n\nThese areas of cultural conventions are called locale categories.\nIt is an unfortunate term; locale aspects or locale feature\ncategories would be a better term, because each \"locale category\"\ndescribes an area or task that requires localization. The concrete data\nthat describes the cultural conventions for such an area and for a\nparticular culture is also called a locale category. In this sense, a\nlocale is composed of several locale categories: the locale category\ndescribing the codeset, the locale category describing the formatting of\nnumbers, the locale category containing the translated messages, and so\non.\n\nComponents of locale outside of message handling are standardized in\nthe ISO C standard and the POSIX:2001 standard (also known as the SUSV3\nspecification). GNU 'libc' fully implements this, and most other modern\nsystems provide a more or less reasonable support for at least some of\nthe missing components.\n\nFile: gettext.info, Node: Files, Next: Overview, Prev: Aspects, Up: Introduction\n" }, { "name": "1.4 Files Conveying Translations", "content": "The letters PO in '.po' files means Portable Object, to distinguish\nit from '.mo' files, where MO stands for Machine Object. This paradigm,\nas well as the PO file format, is inspired by the NLS standard developed\nby Uniforum, and first implemented by Sun in their Solaris system.\n\nPO files are meant to be read and edited by humans, and associate\neach original, translatable string of a given package with its\ntranslation in a particular target language. A single PO file is\ndedicated to a single target language. If a package supports many\nlanguages, there is one such PO file per language supported, and each\npackage has its own set of PO files. These PO files are best created by\nthe 'xgettext' program, and later updated or refreshed through the\n'msgmerge' program. Program 'xgettext' extracts all marked messages\nfrom a set of C files and initializes a PO file with empty translations.\nProgram 'msgmerge' takes care of adjusting PO files between releases of\nthe corresponding sources, commenting obsolete entries, initializing new\nones, and updating all source line references. Files ending with '.pot'\nare kind of base translation files found in distributions, in PO file\nformat.\n\nMO files are meant to be read by programs, and are binary in nature.\nA few systems already offer tools for creating and handling MO files as\npart of the Native Language Support coming with the system, but the\nformat of these MO files is often different from system to system, and\nnon-portable. The tools already provided with these systems don't\nsupport all the features of GNU 'gettext'. Therefore GNU 'gettext' uses\nits own format for MO files. Files ending with '.gmo' are really MO\nfiles, when it is known that these files use the GNU format.\n\nFile: gettext.info, Node: Overview, Prev: Files, Up: Introduction\n" }, { "name": "1.5 Overview of GNU 'gettext'", "content": "The following diagram summarizes the relation between the files\nhandled by GNU 'gettext' and the tools acting on these files. It is\nfollowed by somewhat detailed explanations, which you should read while\nkeeping an eye on the diagram. Having a clear understanding of these\ninterrelations will surely help programmers, translators and\nmaintainers.\n\nOriginal C Sources ---> Preparation ---> Marked C Sources ---.\n|\n.---------<--- GNU gettext Library |\n.--- make <---+ |\n| `---------<--------------------+---------------'\n| |\n| .-----<--- PACKAGE.pot <--- xgettext <---' .---<--- PO Compendium\n| | | ^\n| | `---. |\n| `---. +---> PO editor ---.\n| +----> msgmerge ------> LANG.po ---->--------' |\n| .---' |\n| | |\n| `-------------<---------------. |\n| +--- New LANG.po <--------------------'\n| .--- LANG.gmo <--- msgfmt <---'\n| |\n| `---> install ---> /.../LANG/PACKAGE.mo ---.\n| +---> \"Hello world!\"\n`-------> install ---> /.../bin/PROGRAM -------'\n\nAs a programmer, the first step to bringing GNU 'gettext' into your\npackage is identifying, right in the C sources, those strings which are\nmeant to be translatable, and those which are untranslatable. This\ntedious job can be done a little more comfortably using emacs PO mode,\nbut you can use any means familiar to you for modifying your C sources.\nBeside this some other simple, standard changes are needed to properly\ninitialize the translation library. *Note Sources::, for more\ninformation about all this.\n\nFor newly written software the strings of course can and should be\nmarked while writing it. The 'gettext' approach makes this very easy.\nSimply put the following lines at the beginning of each file or in a\ncentral header file:\n\n#define (String) (String)\n#define N(String) String\n#define textdomain(Domain)\n#define bindtextdomain(Package, Directory)\n\nDoing this allows you to prepare the sources for internationalization.\nLater when you feel ready for the step to use the 'gettext' library\nsimply replace these definitions by the following:\n\n#include \n#define (String) gettext (String)\n#define gettextnoop(String) String\n#define N(String) gettextnoop (String)\n\nand link against 'libintl.a' or 'libintl.so'. Note that on GNU systems,\nyou don't need to link with 'libintl' because the 'gettext' library\nfunctions are already contained in GNU libc. That is all you have to\nchange.\n\nOnce the C sources have been modified, the 'xgettext' program is used\nto find and extract all translatable strings, and create a PO template\nfile out of all these. This 'PACKAGE.pot' file contains all original\nprogram strings. It has sets of pointers to exactly where in C sources\neach string is used. All translations are set to empty. The letter 't'\nin '.pot' marks this as a Template PO file, not yet oriented towards any\nparticular language. *Note xgettext Invocation::, for more details\nabout how one calls the 'xgettext' program. If you are really lazy,\nyou might be interested at working a lot more right away, and preparing\nthe whole distribution setup (*note Maintainers::). By doing so, you\nspare yourself typing the 'xgettext' command, as 'make' should now\ngenerate the proper things automatically for you!\n\nThe first time through, there is no 'LANG.po' yet, so the 'msgmerge'\nstep may be skipped and replaced by a mere copy of 'PACKAGE.pot' to\n'LANG.po', where LANG represents the target language. See *note\nCreating:: for details.\n\nThen comes the initial translation of messages. Translation in\nitself is a whole matter, still exclusively meant for humans, and whose\ncomplexity far overwhelms the level of this manual. Nevertheless, a few\nhints are given in some other chapter of this manual (*note\nTranslators::). You will also find there indications about how to\ncontact translating teams, or becoming part of them, for sharing your\ntranslating concerns with others who target the same native language.\n\nWhile adding the translated messages into the 'LANG.po' PO file, if\nyou are not using one of the dedicated PO file editors (*note\nEditing::), you are on your own for ensuring that your efforts fully\nrespect the PO file format, and quoting conventions (*note PO Files::).\nThis is surely not an impossible task, as this is the way many people\nhave handled PO files around 1995. On the other hand, by using a PO\nfile editor, most details of PO file format are taken care of for you,\nbut you have to acquire some familiarity with PO file editor itself.\n\nIf some common translations have already been saved into a compendium\nPO file, translators may use PO mode for initializing untranslated\nentries from the compendium, and also save selected translations into\nthe compendium, updating it (*note Compendium::). Compendium files are\nmeant to be exchanged between members of a given translation team.\n\nPrograms, or packages of programs, are dynamic in nature: users write\nbug reports and suggestion for improvements, maintainers react by\nmodifying programs in various ways. The fact that a package has already\nbeen internationalized should not make maintainers shy of adding new\nstrings, or modifying strings already translated. They just do their\njob the best they can. For the Translation Project to work smoothly, it\nis important that maintainers do not carry translation concerns on their\nalready loaded shoulders, and that translators be kept as free as\npossible of programming concerns.\n\nThe only concern maintainers should have is carefully marking new\nstrings as translatable, when they should be, and do not otherwise worry\nabout them being translated, as this will come in proper time.\nConsequently, when programs and their strings are adjusted in various\nways by maintainers, and for matters usually unrelated to translation,\n'xgettext' would construct 'PACKAGE.pot' files which are evolving over\ntime, so the translations carried by 'LANG.po' are slowly fading out of\ndate.\n\nIt is important for translators (and even maintainers) to understand\nthat package translation is a continuous process in the lifetime of a\npackage, and not something which is done once and for all at the start.\nAfter an initial burst of translation activity for a given package,\ninterventions are needed once in a while, because here and there,\ntranslated entries become obsolete, and new untranslated entries appear,\nneeding translation.\n\nThe 'msgmerge' program has the purpose of refreshing an already\nexisting 'LANG.po' file, by comparing it with a newer 'PACKAGE.pot'\ntemplate file, extracted by 'xgettext' out of recent C sources. The\nrefreshing operation adjusts all references to C source locations for\nstrings, since these strings move as programs are modified. Also,\n'msgmerge' comments out as obsolete, in 'LANG.po', those already\ntranslated entries which are no longer used in the program sources\n(*note Obsolete Entries::). It finally discovers new strings and\ninserts them in the resulting PO file as untranslated entries (*note\nUntranslated Entries::). *Note msgmerge Invocation::, for more\ninformation about what 'msgmerge' really does.\n\nWhatever route or means taken, the goal is to obtain an updated\n'LANG.po' file offering translations for all strings.\n\nThe temporal mobility, or fluidity of PO files, is an integral part\nof the translation game, and should be well understood, and accepted.\nPeople resisting it will have a hard time participating in the\nTranslation Project, or will give a hard time to other participants! In\nparticular, maintainers should relax and include all available official\nPO files in their distributions, even if these have not recently been\nupdated, without exerting pressure on the translator teams to get the\njob done. The pressure should rather come from the community of users\nspeaking a particular language, and maintainers should consider\nthemselves fairly relieved of any concern about the adequacy of\ntranslation files. On the other hand, translators should reasonably try\nupdating the PO files they are responsible for, while the package is\nundergoing pretest, prior to an official distribution.\n\nOnce the PO file is complete and dependable, the 'msgfmt' program is\nused for turning the PO file into a machine-oriented format, which may\nyield efficient retrieval of translations by the programs of the\npackage, whenever needed at runtime (*note MO Files::). *Note msgfmt\nInvocation::, for more information about all modes of execution for the\n'msgfmt' program.\n\nFinally, the modified and marked C sources are compiled and linked\nwith the GNU 'gettext' library, usually through the operation of 'make',\ngiven a suitable 'Makefile' exists for the project, and the resulting\nexecutable is installed somewhere users will find it. The MO files\nthemselves should also be properly installed. Given the appropriate\nenvironment variables are set (*note Setting the POSIX Locale::), the\nprogram should localize itself automatically, whenever it executes.\n\nThe remainder of this manual has the purpose of explaining in depth\nthe various steps outlined above.\n\nFile: gettext.info, Node: Users, Next: PO Files, Prev: Introduction, Up: Top\n" } ] }, "2 The User's View": { "content": "Nowadays, when users log into a computer, they usually find that all\ntheir programs show messages in their native language - at least for\nusers of languages with an active free software community, like French\nor German; to a lesser extent for languages with a smaller participation\nin free software and the GNU project, like Hindi and Filipino.\n\nHow does this work? How can the user influence the language that is\nused by the programs? This chapter will answer it.\n\n* Menu:\n\n* System Installation:: Questions During Operating System Installation\n* Setting the GUI Locale:: How to Specify the Locale Used by GUI Programs\n* Setting the POSIX Locale:: How to Specify the Locale According to POSIX\n* Working in a Windows console:: Obtaining good output in a Windows console\n* Installing Localizations:: How to Install Additional Translations\n\nFile: gettext.info, Node: System Installation, Next: Setting the GUI Locale, Up: Users\n", "subsections": [ { "name": "2.1 Operating System Installation", "content": "The default language is often already specified during operating\nsystem installation. When the operating system is installed, the\ninstaller typically asks for the language used for the installation\nprocess and, separately, for the language to use in the installed\nsystem. Some OS installers only ask for the language once.\n\nThis determines the system-wide default language for all users. But\nthe installers often give the possibility to install extra localizations\nfor additional languages. For example, the localizations of KDE (the K\nDesktop Environment) and OpenOffice.org are often bundled separately, as\none installable package per language.\n\nAt this point it is good to consider the intended use of the machine:\nIf it is a machine designated for personal use, additional localizations\nare probably not necessary. If, however, the machine is in use in an\norganization or company that has international relationships, one can\nconsider the needs of guest users. If you have a guest from abroad, for\na week, what could be his preferred locales? It may be worth installing\nthese additional localizations ahead of time, since they cost only a bit\nof disk space at this point.\n\nThe system-wide default language is the locale configuration that is\nused when a new user account is created. But the user can have his own\nlocale configuration that is different from the one of the other users\nof the same machine. He can specify it, typically after the first\nlogin, as described in the next section.\n\nFile: gettext.info, Node: Setting the GUI Locale, Next: Setting the POSIX Locale, Prev: System Installation, Up: Users\n" }, { "name": "2.2 Setting the Locale Used by GUI Programs", "content": "The immediately available programs in a user's desktop come from a\ngroup of programs called a \"desktop environment\"; it usually includes\nthe window manager, a web browser, a text editor, and more. The most\ncommon free desktop environments are KDE, GNOME, and Xfce.\n\nThe locale used by GUI programs of the desktop environment can be\nspecified in a configuration screen called \"control center\", \"language\nsettings\" or \"country settings\".\n\nIndividual GUI programs that are not part of the desktop environment\ncan have their locale specified either in a settings panel, or through\nenvironment variables.\n\nFor some programs, it is possible to specify the locale through\nenvironment variables, possibly even to a different locale than the\ndesktop's locale. This means, instead of starting a program through a\nmenu or from the file system, you can start it from the command-line,\nafter having set some environment variables. The environment variables\ncan be those specified in the next section (*note Setting the POSIX\nLocale::); for some versions of KDE, however, the locale is specified\nthrough a variable 'KDELANG', rather than 'LANG' or 'LCALL'.\n\nFile: gettext.info, Node: Setting the POSIX Locale, Next: Working in a Windows console, Prev: Setting the GUI Locale, Up: Users\n" }, { "name": "2.3 Setting the Locale through Environment Variables", "content": "As a user, if your language has been installed for this package, in\nthe simplest case, you only have to set the 'LANG' environment variable\nto the appropriate 'LLCC' combination. For example, let's suppose that\nyou speak German and live in Germany. At the shell prompt, merely\nexecute 'setenv LANG deDE' (in 'csh'), 'export LANG; LANG=deDE' (in\n'sh') or 'export LANG=deDE' (in 'bash'). This can be done from your\n'.login' or '.profile' file, once and for all.\n\n* Menu:\n\n* Locale Names:: How a Locale Specification Looks Like\n* Locale Environment Variables:: Which Environment Variable Specfies What\n* The LANGUAGE variable:: How to Specify a Priority List of Languages\n\nFile: gettext.info, Node: Locale Names, Next: Locale Environment Variables, Up: Setting the POSIX Locale\n\n\nA locale name usually has the form 'LLCC'. Here 'LL' is an ISO 639\ntwo-letter language code, and 'CC' is an ISO 3166 two-letter country\ncode. For example, for German in Germany, LL is 'de', and CC is 'DE'.\nYou find a list of the language codes in appendix *note Language Codes::\nand a list of the country codes in appendix *note Country Codes::.\n\nYou might think that the country code specification is redundant.\nBut in fact, some languages have dialects in different countries. For\nexample, 'deAT' is used for Austria, and 'ptBR' for Brazil. The\ncountry code serves to distinguish the dialects.\n\nMany locale names have an extended syntax 'LLCC.ENCODING' that also\nspecifies the character encoding. These are in use because between 2000\nand 2005, most users have switched to locales in UTF-8 encoding. For\nexample, the German locale on glibc systems is nowadays 'deDE.UTF-8'.\nThe older name 'deDE' still refers to the German locale as of 2000 that\nstores characters in ISO-8859-1 encoding - a text encoding that cannot\neven accommodate the Euro currency sign.\n\nSome locale names use 'LLCC@VARIANT' instead of 'LLCC'. The\n'@VARIANT' can denote any kind of characteristics that is not already\nimplied by the language LL and the country CC. It can denote a\nparticular monetary unit. For example, on glibc systems, 'deDE@euro'\ndenotes the locale that uses the Euro currency, in contrast to the older\nlocale 'deDE' which implies the use of the currency before 2002. It\ncan also denote a dialect of the language, or the script used to write\ntext (for example, 'srRS@latin' uses the Latin script, whereas 'srRS'\nuses the Cyrillic script to write Serbian), or the orthography rules, or\nsimilar.\n\nOn other systems, some variations of this scheme are used, such as\n'LL'. You can get the list of locales supported by your system for your\nlanguage by running the command 'locale -a | grep '^LL''.\n\nThere is also a special locale, called 'C'. When it is used, it\ndisables all localization: in this locale, all programs standardized by\nPOSIX use English messages and an unspecified character encoding (often\nUS-ASCII, but sometimes also ISO-8859-1 or UTF-8, depending on the\noperating system).\n\nFile: gettext.info, Node: Locale Environment Variables, Next: The LANGUAGE variable, Prev: Locale Names, Up: Setting the POSIX Locale\n\n\nA locale is composed of several locale categories, see *note\nAspects::. When a program looks up locale dependent values, it does\nthis according to the following environment variables, in priority\norder:\n\n1. 'LANGUAGE'\n2. 'LCALL'\n3. 'LCxxx', according to selected locale category: 'LCCTYPE',\n'LCNUMERIC', 'LCTIME', 'LCCOLLATE', 'LCMONETARY',\n'LCMESSAGES', ...\n4. 'LANG'\n\nVariables whose value is set but is empty are ignored in this lookup.\n\n'LANG' is the normal environment variable for specifying a locale.\nAs a user, you normally set this variable (unless some of the other\nvariables have already been set by the system, in '/etc/profile' or\nsimilar initialization files).\n\n'LCCTYPE', 'LCNUMERIC', 'LCTIME', 'LCCOLLATE', 'LCMONETARY',\n'LCMESSAGES', and so on, are the environment variables meant to\noverride 'LANG' and affecting a single locale category only. For\nexample, assume you are a Swedish user in Spain, and you want your\nprograms to handle numbers and dates according to Spanish conventions,\nand only the messages should be in Swedish. Then you could create a\nlocale named 'svES' or 'svES.UTF-8' by use of the 'localedef' program.\nBut it is simpler, and achieves the same effect, to set the 'LANG'\nvariable to 'esES.UTF-8' and the 'LCMESSAGES' variable to\n'svSE.UTF-8'; these two locales come already preinstalled with the\noperating system.\n\n'LCALL' is an environment variable that overrides all of these. It\nis typically used in scripts that run particular programs. For example,\n'configure' scripts generated by GNU autoconf use 'LCALL' to make sure\nthat the configuration tests don't operate in locale dependent ways.\n\nSome systems, unfortunately, set 'LCALL' in '/etc/profile' or in\nsimilar initialization files. As a user, you therefore have to unset\nthis variable if you want to set 'LANG' and optionally some of the other\n'LCxxx' variables.\n\nThe 'LANGUAGE' variable is described in the next subsection.\n\nFile: gettext.info, Node: The LANGUAGE variable, Prev: Locale Environment Variables, Up: Setting the POSIX Locale\n\n\nNot all programs have translations for all languages. By default, an\nEnglish message is shown in place of a nonexistent translation. If you\nunderstand other languages, you can set up a priority list of languages.\nThis is done through a different environment variable, called\n'LANGUAGE'. GNU 'gettext' gives preference to 'LANGUAGE' over 'LCALL'\nand 'LANG' for the purpose of message handling, but you still need to\nhave 'LANG' (or 'LCALL') set to the primary language; this is required\nby other parts of the system libraries. For example, some Swedish users\nwho would rather read translations in German than English for when\nSwedish is not available, set 'LANGUAGE' to 'sv:de' while leaving 'LANG'\nto 'svSE'.\n\nSpecial advice for Norwegian users: The language code for Norwegian\nbokm??l changed from 'no' to 'nb' recently (in 2003). During the\ntransition period, while some message catalogs for this language are\ninstalled under 'nb' and some older ones under 'no', it is recommended\nfor Norwegian users to set 'LANGUAGE' to 'nb:no' so that both newer and\nolder translations are used.\n\nIn the 'LANGUAGE' environment variable, but not in the other\nenvironment variables, 'LLCC' combinations can be abbreviated as 'LL'\nto denote the language's main dialect. For example, 'de' is equivalent\nto 'deDE' (German as spoken in Germany), and 'pt' to 'ptPT'\n(Portuguese as spoken in Portugal) in this context.\n\nNote: The variable 'LANGUAGE' is ignored if the locale is set to 'C'.\nIn other words, you have to first enable localization, by setting 'LANG'\n(or 'LCALL') to a value other than 'C', before you can use a language\npriority list through the 'LANGUAGE' variable.\n\nFile: gettext.info, Node: Working in a Windows console, Next: Installing Localizations, Prev: Setting the POSIX Locale, Up: Users\n" }, { "name": "2.4 Obtaining good output in a Windows console", "content": "On Windows, consoles such as the one started by the 'cmd.exe' program\ndo input and output in an encoding, called \"OEM code page\", that is\ndifferent from the encoding that text-mode programs usually use, called\n\"ANSI code page\". (Note: This problem does not exist for Cygwin\nconsoles; these consoles do input and output in the UTF-8 encoding.) As\na workaround, you may request that the programs produce output in this\n\"OEM\" encoding. To do so, set the environment variable 'OUTPUTCHARSET'\nto the \"OEM\" encoding, through a command such as\nset OUTPUTCHARSET=CP850\nNote: This has an effect only on strings looked up in message\ncatalogs; other categories of text are usually not affected by this\nsetting. Note also that this environment variable also affects output\nsent to a file or to a pipe; output to a file is most often expected to\nbe in the \"ANSI\" or in the UTF-8 encoding.\n\nHere are examples of the \"ANSI\" and \"OEM\" code pages:\n\nTerritories ANSI encoding OEM encoding\n\n---------------------------------------------------------------------------\nWestern Europe CP1252 CP850\nSlavic countries (Latin 2) CP1250 CP852\nBaltic countries CP1257 CP775\nRussia CP1251 CP866\n\nFile: gettext.info, Node: Installing Localizations, Prev: Working in a Windows console, Up: Users\n" }, { "name": "2.5 Installing Translations for Particular Programs", "content": "Languages are not equally well supported in all packages using GNU\n'gettext', and more translations are added over time. Usually, you use\nthe translations that are shipped with the operating system or with\nparticular packages that you install afterwards. But you can also\ninstall newer localizations directly. For doing this, you will need an\nunderstanding where each localization file is stored on the file system.\n\nFor programs that participate in the Translation Project, you can\nstart looking for translations here:\n.\n\nFor programs that are part of the KDE project, the starting point is:\n.\n\nFor programs that are part of the GNOME project, the starting point\nis: .\n\nFor other programs, you may check whether the program's source code\npackage contains some 'LL.po' files; often they are kept together in a\ndirectory called 'po/'. Each 'LL.po' file contains the message\ntranslations for the language whose abbreviation of LL.\n\nFile: gettext.info, Node: PO Files, Next: Sources, Prev: Users, Up: Top\n" } ] }, "3 The Format of PO Files": { "content": "The GNU 'gettext' toolset helps programmers and translators at\nproducing, updating and using translation files, mainly those PO files\nwhich are textual, editable files. This chapter explains the format of\nPO files.\n\nA PO file is made up of many entries, each entry holding the relation\nbetween an original untranslated string and its corresponding\ntranslation. All entries in a given PO file usually pertain to a single\nproject, and all translations are expressed in a single target language.\nOne PO file \"entry\" has the following schematic structure:\n\nWHITE-SPACE\n# TRANSLATOR-COMMENTS\n#. EXTRACTED-COMMENTS\n#: REFERENCE...\n#, FLAG...\n#| msgid PREVIOUS-UNTRANSLATED-STRING\nmsgid UNTRANSLATED-STRING\nmsgstr TRANSLATED-STRING\n\nThe general structure of a PO file should be well understood by the\ntranslator. When using PO mode, very little has to be known about the\nformat details, as PO mode takes care of them for her.\n\nA simple entry can look like this:\n\n#: lib/error.c:116\nmsgid \"Unknown system error\"\nmsgstr \"Error desconegut del sistema\"\n\nEntries begin with some optional white space. Usually, when\ngenerated through GNU 'gettext' tools, there is exactly one blank line\nbetween entries. Then comments follow, on lines all starting with the\ncharacter '#'. There are two kinds of comments: those which have some\nwhite space immediately following the '#' - the TRANSLATOR COMMENTS -,\nwhich comments are created and maintained exclusively by the translator,\nand those which have some non-white character just after the '#' - the\nAUTOMATIC COMMENTS -, which comments are created and maintained\nautomatically by GNU 'gettext' tools. Comment lines starting with '#.'\ncontain comments given by the programmer, directed at the translator;\nthese comments are called EXTRACTED COMMENTS because the 'xgettext'\nprogram extracts them from the program's source code. Comment lines\nstarting with '#:' contain references to the program's source code.\nComment lines starting with '#,' contain flags; more about these below.\nComment lines starting with '#|' contain the previous untranslated\nstring for which the translator gave a translation.\n\nAll comments, of either kind, are optional.\n\nAfter white space and comments, entries show two strings, namely\nfirst the untranslated string as it appears in the original program\nsources, and then, the translation of this string. The original string\nis introduced by the keyword 'msgid', and the translation, by 'msgstr'.\nThe two strings, untranslated and translated, are quoted in various ways\nin the PO file, using '\"' delimiters and '\\' escapes, but the translator\ndoes not really have to pay attention to the precise quoting format, as\nPO mode fully takes care of quoting for her.\n\nThe 'msgid' strings, as well as automatic comments, are produced and\nmanaged by other GNU 'gettext' tools, and PO mode does not provide means\nfor the translator to alter these. The most she can do is merely\ndeleting them, and only by deleting the whole entry. On the other hand,\nthe 'msgstr' string, as well as translator comments, are really meant\nfor the translator, and PO mode gives her the full control she needs.\n\nThe comment lines beginning with '#,' are special because they are\nnot completely ignored by the programs as comments generally are. The\ncomma separated list of FLAGs is used by the 'msgfmt' program to give\nthe user some better diagnostic messages. Currently there are two forms\nof flags defined:\n\n'fuzzy'\nThis flag can be generated by the 'msgmerge' program or it can be\ninserted by the translator herself. It shows that the 'msgstr'\nstring might not be a correct translation (anymore). Only the\ntranslator can judge if the translation requires further\nmodification, or is acceptable as is. Once satisfied with the\ntranslation, she then removes this 'fuzzy' attribute. The\n'msgmerge' program inserts this when it combined the 'msgid' and\n'msgstr' entries after fuzzy search only. *Note Fuzzy Entries::.\n\n'c-format'\n'no-c-format'\nThese flags should not be added by a human. Instead only the\n'xgettext' program adds them. In an automated PO file processing\nsystem as proposed here, the user's changes would be thrown away\nagain as soon as the 'xgettext' program generates a new template\nfile.\n\nThe 'c-format' flag indicates that the untranslated string and the\ntranslation are supposed to be C format strings. The 'no-c-format'\nflag indicates that they are not C format strings, even though the\nuntranslated string happens to look like a C format string (with\n'%' directives).\n\nWhen the 'c-format' flag is given for a string the 'msgfmt' program\ndoes some more tests to check the validity of the translation.\n*Note msgfmt Invocation::, *note c-format Flag:: and *note\nc-format::.\n\n'objc-format'\n'no-objc-format'\nLikewise for Objective C, see *note objc-format::.\n\n'python-format'\n'no-python-format'\nLikewise for Python, see *note python-format::.\n\n'python-brace-format'\n'no-python-brace-format'\nLikewise for Python brace, see *note python-format::.\n\n'java-format'\n'no-java-format'\nLikewise for Java 'MessageFormat' format strings, see *note\njava-format::.\n\n'java-printf-format'\n'no-java-printf-format'\nLikewise for Java 'printf' format strings, see *note java-format::.\n\n'csharp-format'\n'no-csharp-format'\nLikewise for C#, see *note csharp-format::.\n\n'javascript-format'\n'no-javascript-format'\nLikewise for JavaScript, see *note javascript-format::.\n\n'scheme-format'\n'no-scheme-format'\nLikewise for Scheme, see *note scheme-format::.\n\n'lisp-format'\n'no-lisp-format'\nLikewise for Lisp, see *note lisp-format::.\n\n'elisp-format'\n'no-elisp-format'\nLikewise for Emacs Lisp, see *note elisp-format::.\n\n'librep-format'\n'no-librep-format'\nLikewise for librep, see *note librep-format::.\n\n'ruby-format'\n'no-ruby-format'\nLikewise for Ruby, see *note ruby-format::.\n\n'sh-format'\n'no-sh-format'\nLikewise for Shell, see *note sh-format::.\n\n'awk-format'\n'no-awk-format'\nLikewise for awk, see *note awk-format::.\n\n'lua-format'\n'no-lua-format'\nLikewise for Lua, see *note lua-format::.\n\n'object-pascal-format'\n'no-object-pascal-format'\nLikewise for Object Pascal, see *note object-pascal-format::.\n\n'smalltalk-format'\n'no-smalltalk-format'\nLikewise for Smalltalk, see *note smalltalk-format::.\n\n'qt-format'\n'no-qt-format'\nLikewise for Qt, see *note qt-format::.\n\n'qt-plural-format'\n'no-qt-plural-format'\nLikewise for Qt plural forms, see *note qt-plural-format::.\n\n'kde-format'\n'no-kde-format'\nLikewise for KDE, see *note kde-format::.\n\n'boost-format'\n'no-boost-format'\nLikewise for Boost, see *note boost-format::.\n\n'tcl-format'\n'no-tcl-format'\nLikewise for Tcl, see *note tcl-format::.\n\n'perl-format'\n'no-perl-format'\nLikewise for Perl, see *note perl-format::.\n\n'perl-brace-format'\n'no-perl-brace-format'\nLikewise for Perl brace, see *note perl-format::.\n\n'php-format'\n'no-php-format'\nLikewise for PHP, see *note php-format::.\n\n'gcc-internal-format'\n'no-gcc-internal-format'\nLikewise for the GCC sources, see *note gcc-internal-format::.\n\n'gfc-internal-format'\n'no-gfc-internal-format'\nLikewise for the GNU Fortran Compiler sources, see *note\ngfc-internal-format::.\n\n'ycp-format'\n'no-ycp-format'\nLikewise for YCP, see *note ycp-format::.\n\nIt is also possible to have entries with a context specifier. They\nlook like this:\n\nWHITE-SPACE\n# TRANSLATOR-COMMENTS\n#. EXTRACTED-COMMENTS\n#: REFERENCE...\n#, FLAG...\n#| msgctxt PREVIOUS-CONTEXT\n#| msgid PREVIOUS-UNTRANSLATED-STRING\nmsgctxt CONTEXT\nmsgid UNTRANSLATED-STRING\nmsgstr TRANSLATED-STRING\n\nThe context serves to disambiguate messages with the same\nUNTRANSLATED-STRING. It is possible to have several entries with the\nsame UNTRANSLATED-STRING in a PO file, provided that they each have a\ndifferent CONTEXT. Note that an empty CONTEXT string and an absent\n'msgctxt' line do not mean the same thing.\n\nA different kind of entries is used for translations which involve\nplural forms.\n\nWHITE-SPACE\n# TRANSLATOR-COMMENTS\n#. EXTRACTED-COMMENTS\n#: REFERENCE...\n#, FLAG...\n#| msgid PREVIOUS-UNTRANSLATED-STRING-SINGULAR\n#| msgidplural PREVIOUS-UNTRANSLATED-STRING-PLURAL\nmsgid UNTRANSLATED-STRING-SINGULAR\nmsgidplural UNTRANSLATED-STRING-PLURAL\nmsgstr[0] TRANSLATED-STRING-CASE-0\n...\nmsgstr[N] TRANSLATED-STRING-CASE-N\n\nSuch an entry can look like this:\n\n#: src/msgcmp.c:338 src/po-lex.c:699\n#, c-format\nmsgid \"found %d fatal error\"\nmsgidplural \"found %d fatal errors\"\nmsgstr[0] \"s'ha trobat %d error fatal\"\nmsgstr[1] \"s'han trobat %d errors fatals\"\n\nHere also, a 'msgctxt' context can be specified before 'msgid', like\nabove.\n\nHere, additional kinds of flags can be used:\n\n'range:'\nThis flag is followed by a range of non-negative numbers, using the\nsyntax 'range: MINIMUM-VALUE..MAXIMUM-VALUE'. It designates the\npossible values that the numeric parameter of the message can take.\nIn some languages, translators may produce slightly better\ntranslations if they know that the value can only take on values\nbetween 0 and 10, for example.\n\nThe PREVIOUS-UNTRANSLATED-STRING is optionally inserted by the\n'msgmerge' program, at the same time when it marks a message fuzzy. It\nhelps the translator to see which changes were done by the developers on\nthe UNTRANSLATED-STRING.\n\nIt happens that some lines, usually whitespace or comments, follow\nthe very last entry of a PO file. Such lines are not part of any entry,\nand will be dropped when the PO file is processed by the tools, or may\ndisturb some PO file editors.\n\nThe remainder of this section may be safely skipped by those using a\nPO file editor, yet it may be interesting for everybody to have a better\nidea of the precise format of a PO file. On the other hand, those\nwishing to modify PO files by hand should carefully continue reading on.\n\nAn empty UNTRANSLATED-STRING is reserved to contain the header entry\nwith the meta information (*note Header Entry::). This header entry\nshould be the first entry of the file. The empty UNTRANSLATED-STRING is\nreserved for this purpose and must not be used anywhere else.\n\nEach of UNTRANSLATED-STRING and TRANSLATED-STRING respects the C\nsyntax for a character string, including the surrounding quotes and\nembedded backslashed escape sequences. When the time comes to write\nmulti-line strings, one should not use escaped newlines. Instead, a\nclosing quote should follow the last character on the line to be\ncontinued, and an opening quote should resume the string at the\nbeginning of the following PO file line. For example:\n\nmsgid \"\"\n\"Here is an example of how one might continue a very long string\\n\"\n\"for the common case the string represents multi-line output.\\n\"\n\nIn this example, the empty string is used on the first line, to allow\nbetter alignment of the 'H' from the word 'Here' over the 'f' from the\nword 'for'. In this example, the 'msgid' keyword is followed by three\nstrings, which are meant to be concatenated. Concatenating the empty\nstring does not change the resulting overall string, but it is a way for\nus to comply with the necessity of 'msgid' to be followed by a string on\nthe same line, while keeping the multi-line presentation left-justified,\nas we find this to be a cleaner disposition. The empty string could\nhave been omitted, but only if the string starting with 'Here' was\npromoted on the first line, right after 'msgid'.(1) It was not really\nnecessary either to switch between the two last quoted strings\nimmediately after the newline '\\n', the switch could have occurred after\nany other character, we just did it this way because it is neater.\n\nOne should carefully distinguish between end of lines marked as '\\n'\ninside quotes, which are part of the represented string, and end of\nlines in the PO file itself, outside string quotes, which have no\nincidence on the represented string.\n\nOutside strings, white lines and comments may be used freely.\nComments start at the beginning of a line with '#' and extend until the\nend of the PO file line. Comments written by translators should have\nthe initial '#' immediately followed by some white space. If the '#' is\nnot immediately followed by white space, this comment is most likely\ngenerated and managed by specialized GNU tools, and might disappear or\nbe replaced unexpectedly when the PO file is given to 'msgmerge'.\n\n---------- Footnotes ----------\n\n(1) This limitation is not imposed by GNU 'gettext', but is for\ncompatibility with the 'msgfmt' implementation on Solaris.\n\nFile: gettext.info, Node: Sources, Next: Template, Prev: PO Files, Up: Top\n", "subsections": [] }, "4 Preparing Program Sources": { "content": "For the programmer, changes to the C source code fall into three\ncategories. First, you have to make the localization functions known to\nall modules needing message translation. Second, you should properly\ntrigger the operation of GNU 'gettext' when the program initializes,\nusually from the 'main' function. Last, you should identify, adjust and\nmark all constant strings in your program needing translation.\n\n* Menu:\n\n* Importing:: Importing the 'gettext' declaration\n* Triggering:: Triggering 'gettext' Operations\n* Preparing Strings:: Preparing Translatable Strings\n* Mark Keywords:: How Marks Appear in Sources\n* Marking:: Marking Translatable Strings\n* c-format Flag:: Telling something about the following string\n* Special cases:: Special Cases of Translatable Strings\n* Bug Report Address:: Letting Users Report Translation Bugs\n* Names:: Marking Proper Names for Translation\n* Libraries:: Preparing Library Sources\n\nFile: gettext.info, Node: Importing, Next: Triggering, Up: Sources\n", "subsections": [ { "name": "4.1 Importing the 'gettext' declaration", "content": "Presuming that your set of programs, or package, has been adjusted so\nall needed GNU 'gettext' files are available, and your 'Makefile' files\nare adjusted (*note Maintainers::), each C module having translated C\nstrings should contain the line:\n\n#include \n\nSimilarly, each C module containing 'printf()'/'fprintf()'/... calls\nwith a format string that could be a translated C string (even if the C\nstring comes from a different C module) should contain the line:\n\n#include \n\nFile: gettext.info, Node: Triggering, Next: Preparing Strings, Prev: Importing, Up: Sources\n" }, { "name": "4.2 Triggering 'gettext' Operations", "content": "The initialization of locale data should be done with more or less\nthe same code in every program, as demonstrated below:\n\nint\nmain (int argc, char *argv[])\n{\n...\nsetlocale (LCALL, \"\");\nbindtextdomain (PACKAGE, LOCALEDIR);\ntextdomain (PACKAGE);\n...\n}\n\nPACKAGE and LOCALEDIR should be provided either by 'config.h' or by\nthe Makefile. For now consult the 'gettext' or 'hello' sources for more\ninformation.\n\nThe use of 'LCALL' might not be appropriate for you. 'LCALL'\nincludes all locale categories and especially 'LCCTYPE'. This latter\ncategory is responsible for determining character classes with the\n'isalnum' etc. functions from 'ctype.h' which could especially for\nprograms, which process some kind of input language, be wrong. For\nexample this would mean that a source code using the c, (c-cedilla\ncharacter) is runnable in France but not in the U.S.\n\nSome systems also have problems with parsing numbers using the\n'scanf' functions if an other but the 'LCALL' locale category is used.\nThe standards say that additional formats but the one known in the '\"C\"'\nlocale might be recognized. But some systems seem to reject numbers in\nthe '\"C\"' locale format. In some situation, it might also be a problem\nwith the notation itself which makes it impossible to recognize whether\nthe number is in the '\"C\"' locale or the local format. This can happen\nif thousands separator characters are used. Some locales define this\ncharacter according to the national conventions to ''.'' which is the\nsame character used in the '\"C\"' locale to denote the decimal point.\n\nSo it is sometimes necessary to replace the 'LCALL' line in the code\nabove by a sequence of 'setlocale' lines\n\n{\n...\nsetlocale (LCCTYPE, \"\");\nsetlocale (LCMESSAGES, \"\");\n...\n}\n\nOn all POSIX conformant systems the locale categories 'LCCTYPE',\n'LCMESSAGES', 'LCCOLLATE', 'LCMONETARY', 'LCNUMERIC', and 'LCTIME'\nare available. On some systems which are only ISO C compliant,\n'LCMESSAGES' is missing, but a substitute for it is defined in GNU\ngettext's '' and in GNU gnulib's ''.\n\nNote that changing the 'LCCTYPE' also affects the functions declared\nin the '' standard header and some functions declared in the\n'' and '' standard headers. If this is not\ndesirable in your application (for example in a compiler's parser), you\ncan use a set of substitute functions which hardwire the C locale, such\nas found in the modules 'c-ctype', 'c-strcase', 'c-strcasestr',\n'c-strtod', 'c-strtold' in the GNU gnulib source distribution.\n\nIt is also possible to switch the locale forth and back between the\nenvironment dependent locale and the C locale, but this approach is\nnormally avoided because a 'setlocale' call is expensive, because it is\ntedious to determine the places where a locale switch is needed in a\nlarge program's source, and because switching a locale is not\nmultithread-safe.\n\nFile: gettext.info, Node: Preparing Strings, Next: Mark Keywords, Prev: Triggering, Up: Sources\n" }, { "name": "4.3 Preparing Translatable Strings", "content": "Before strings can be marked for translations, they sometimes need to\nbe adjusted. Usually preparing a string for translation is done right\nbefore marking it, during the marking phase which is described in the\nnext sections. What you have to keep in mind while doing that is the\nfollowing.\n\n* Decent English style.\n\n* Entire sentences.\n\n* Split at paragraphs.\n\n* Use format strings instead of string concatenation.\n\n* Use placeholders in format strings instead of embedded URLs.\n\n* Avoid unusual markup and unusual control characters.\n\nLet's look at some examples of these guidelines.\n\n\nTranslatable strings should be in good English style. If slang\nlanguage with abbreviations and shortcuts is used, often translators\nwill not understand the message and will produce very inappropriate\ntranslations.\n\n\"%s: is parameter\\n\"\n\nThis is nearly untranslatable: Is the displayed item a parameter or\nthe parameter?\n\n\"No match\"\n\nThe ambiguity in this message makes it unintelligible: Is the program\nattempting to set something on fire? Does it mean \"The given object\ndoes not match the template\"? Does it mean \"The template does not fit\nfor any of the objects\"?\n\nIn both cases, adding more words to the message will help both the\ntranslator and the English speaking user.\n\n\nTranslatable strings should be entire sentences. It is often not\npossible to translate single verbs or adjectives in a substitutable way.\n\nprintf (\"File %s is %s protected\", filename, rw ? \"write\" : \"read\");\n\nMost translators will not look at the source and will thus only see the\nstring '\"File %s is %s protected\"', which is unintelligible. Change\nthis to\n\nprintf (rw ? \"File %s is write protected\" : \"File %s is read protected\",\nfilename);\n\nThis way the translator will not only understand the message, she will\nalso be able to find the appropriate grammatical construction. A French\ntranslator for example translates \"write protected\" like \"protected\nagainst writing\".\n\nEntire sentences are also important because in many languages, the\ndeclination of some word in a sentence depends on the gender or the\nnumber (singular/plural) of another part of the sentence. There are\nusually more interdependencies between words than in English. The\nconsequence is that asking a translator to translate two half-sentences\nand then combining these two half-sentences through dumb string\nconcatenation will not work, for many languages, even though it would\nwork for English. That's why translators need to handle entire\nsentences.\n\nOften sentences don't fit into a single line. If a sentence is\noutput using two subsequent 'printf' statements, like this\n\nprintf (\"Locale charset \\\"%s\\\" is different from\\n\", lcharset);\nprintf (\"input file charset \\\"%s\\\".\\n\", fcharset);\n\nthe translator would have to translate two half sentences, but nothing\nin the POT file would tell her that the two half sentences belong\ntogether. It is necessary to merge the two 'printf' statements so that\nthe translator can handle the entire sentence at once and decide at\nwhich place to insert a line break in the translation (if at all):\n\nprintf (\"Locale charset \\\"%s\\\" is different from\\n\\\ninput file charset \\\"%s\\\".\\n\", lcharset, fcharset);\n\nYou may now ask: how about two or more adjacent sentences? Like in\nthis case:\n\nputs (\"Apollo 13 scenario: Stack overflow handling failed.\");\nputs (\"On the next stack overflow we will crash!!!\");\n\nShould these two statements merged into a single one? I would recommend\nto merge them if the two sentences are related to each other, because\nthen it makes it easier for the translator to understand and translate\nboth. On the other hand, if one of the two messages is a stereotypic\none, occurring in other places as well, you will do a favour to the\ntranslator by not merging the two. (Identical messages occurring in\nseveral places are combined by xgettext, so the translator has to handle\nthem once only.)\n\n\nTranslatable strings should be limited to one paragraph; don't let a\nsingle message be longer than ten lines. The reason is that when the\ntranslatable string changes, the translator is faced with the task of\nupdating the entire translated string. Maybe only a single word will\nhave changed in the English string, but the translator doesn't see that\n(with the current translation tools), therefore she has to proofread the\nentire message.\n\nMany GNU programs have a '--help' output that extends over several\nscreen pages. It is a courtesy towards the translators to split such a\nmessage into several ones of five to ten lines each. While doing that,\nyou can also attempt to split the documented options into groups, such\nas the input options, the output options, and the informative output\noptions. This will help every user to find the option he is looking\nfor.\n\n\nHardcoded string concatenation is sometimes used to construct English\nstrings:\n\nstrcpy (s, \"Replace \");\nstrcat (s, object1);\nstrcat (s, \" with \");\nstrcat (s, object2);\nstrcat (s, \"?\");\n\nIn order to present to the translator only entire sentences, and also\nbecause in some languages the translator might want to swap the order of\n'object1' and 'object2', it is necessary to change this to use a format\nstring:\n\nsprintf (s, \"Replace %s with %s?\", object1, object2);\n\nA similar case is compile time concatenation of strings. The ISO C\n99 include file '' contains a macro 'PRId64' that can be\nused as a formatting directive for outputting an 'int64t' integer\nthrough 'printf'. It expands to a constant string, usually \"d\" or \"ld\"\nor \"lld\" or something like this, depending on the platform. Assume you\nhave code like\n\nprintf (\"The amount is %0\" PRId64 \"\\n\", number);\n\nThe 'gettext' tools and library have special support for these\n'' macros. You can therefore simply write\n\nprintf (gettext (\"The amount is %0\" PRId64 \"\\n\"), number);\n\nThe PO file will contain the string \"The amount is %0\\n\". The\ntranslators will provide a translation containing \"%0\" as well,\nand at runtime the 'gettext' function's result will contain the\nappropriate constant string, \"d\" or \"ld\" or \"lld\".\n\nThis works only for the predefined '' macros. If you\nhave defined your own similar macros, let's say 'MYPRId64', that are not\nknown to 'xgettext', the solution for this problem is to change the code\nlike this:\n\nchar buf1[100];\nsprintf (buf1, \"%0\" MYPRId64, number);\nprintf (gettext (\"The amount is %s\\n\"), buf1);\n\nThis means, you put the platform dependent code in one statement, and\nthe internationalization code in a different statement. Note that a\nbuffer length of 100 is safe, because all available hardware integer\ntypes are limited to 128 bits, and to print a 128 bit integer one needs\nat most 54 characters, regardless whether in decimal, octal or\nhexadecimal.\n\nAll this applies to other programming languages as well. For\nexample, in Java and C#, string concatenation is very frequently used,\nbecause it is a compiler built-in operator. Like in C, in Java, you\nwould change\n\nSystem.out.println(\"Replace \"+object1+\" with \"+object2+\"?\");\n\ninto a statement involving a format string:\n\nSystem.out.println(\nMessageFormat.format(\"Replace {0} with {1}?\",\nnew Object[] { object1, object2 }));\n\nSimilarly, in C#, you would change\n\nConsole.WriteLine(\"Replace \"+object1+\" with \"+object2+\"?\");\n\ninto a statement involving a format string:\n\nConsole.WriteLine(\nString.Format(\"Replace {0} with {1}?\", object1, object2));\n\n\nIt is good to not embed URLs in translatable strings, for several\nreasons:\n* It avoids possible mistakes during copy and paste.\n* Translators cannot translate the URLs or, by mistake, use the URLs\nfrom other packages that are present in their compendium.\n* When the URLs change, translators don't need to revisit the\ntranslation of the string.\n\nThe same holds for email addresses.\n\nSo, you would change\n\nfputs ((\"GNU GPL version 3 \\n\"),\nstream);\n\nto\n\nfprintf (stream, (\"GNU GPL version 3 <%s>\\n\"),\n\"https://gnu.org/licenses/gpl.html\");\n\n\nUnusual markup or control characters should not be used in\ntranslatable strings. Translators will likely not understand the\nparticular meaning of the markup or control characters.\n\nFor example, if you have a convention that '|' delimits the left-hand\nand right-hand part of some GUI elements, translators will often not\nunderstand it without specific comments. It might be better to have the\ntranslator translate the left-hand and right-hand part separately.\n\nAnother example is the 'argp' convention to use a single '\\v'\n(vertical tab) control character to delimit two sections inside a\nstring. This is flawed. Some translators may convert it to a simple\nnewline, some to blank lines. With some PO file editors it may not be\neasy to even enter a vertical tab control character. So, you cannot be\nsure that the translation will contain a '\\v' character, at the\ncorresponding position. The solution is, again, to let the translator\ntranslate two separate strings and combine at run-time the two\ntranslated strings with the '\\v' required by the convention.\n\nHTML markup, however, is common enough that it's probably ok to use\nin translatable strings. But please bear in mind that the GNU gettext\ntools don't verify that the translations are well-formed HTML.\n\nFile: gettext.info, Node: Mark Keywords, Next: Marking, Prev: Preparing Strings, Up: Sources\n" }, { "name": "4.4 How Marks Appear in Sources", "content": "All strings requiring translation should be marked in the C sources.\nMarking is done in such a way that each translatable string appears to\nbe the sole argument of some function or preprocessor macro. There are\nonly a few such possible functions or macros meant for translation, and\ntheir names are said to be marking keywords. The marking is attached to\nstrings themselves, rather than to what we do with them. This approach\nhas more uses. A blatant example is an error message produced by\nformatting. The format string needs translation, as well as some\nstrings inserted through some '%s' specification in the format, while\nthe result from 'sprintf' may have so many different instances that it\nis impractical to list them all in some 'errorstringout()' routine,\nsay.\n\nThis marking operation has two goals. The first goal of marking is\nfor triggering the retrieval of the translation, at run time. The\nkeyword is possibly resolved into a routine able to dynamically return\nthe proper translation, as far as possible or wanted, for the argument\nstring. Most localizable strings are found in executable positions,\nthat is, attached to variables or given as parameters to functions. But\nthis is not universal usage, and some translatable strings appear in\nstructured initializations. *Note Special cases::.\n\nThe second goal of the marking operation is to help 'xgettext' at\nproperly extracting all translatable strings when it scans a set of\nprogram sources and produces PO file templates.\n\nThe canonical keyword for marking translatable strings is 'gettext',\nit gave its name to the whole GNU 'gettext' package. For packages\nmaking only light use of the 'gettext' keyword, macro or function, it is\neasily used as is. However, for packages using the 'gettext'\ninterface more heavily, it is usually more convenient to give the main\nkeyword a shorter, less obtrusive name. Indeed, the keyword might\nappear on a lot of strings all over the package, and programmers usually\ndo not want nor need their program sources to remind them forcefully,\nall the time, that they are internationalized. Further, a long keyword\nhas the disadvantage of using more horizontal space, forcing more\nindentation work on sources for those trying to keep them within 79 or\n80 columns.\n\nMany packages use '' (a simple underline) as a keyword, and write\n'(\"Translatable string\")' instead of 'gettext (\"Translatable string\")'.\nFurther, the coding rule, from GNU standards, wanting that there is a\nspace between the keyword and the opening parenthesis is relaxed, in\npractice, for this particular usage. So, the textual overhead per\ntranslatable string is reduced to only three characters: the underline\nand the two parentheses. However, even if GNU 'gettext' uses this\nconvention internally, it does not offer it officially. The real,\ngenuine keyword is truly 'gettext' indeed. It is fairly easy for those\nwanting to use '' instead of 'gettext' to declare:\n\n#include \n#define (String) gettext (String)\n\ninstead of merely using '#include '.\n\nThe marking keywords 'gettext' and '' take the translatable string\nas sole argument. It is also possible to define marking functions that\ntake it at another argument position. It is even possible to make the\nmarked argument position depend on the total number of arguments of the\nfunction call; this is useful in C++. All this is achieved using\n'xgettext''s '--keyword' option. How to pass such an option to\n'xgettext', assuming that 'gettextize' is used, is described in *note\npo/Makevars:: and *note AMXGETTEXTOPTION::.\n\nNote also that long strings can be split across lines, into multiple\nadjacent string tokens. Automatic string concatenation is performed at\ncompile time according to ISO C and ISO C++; 'xgettext' also supports\nthis syntax.\n\nLater on, the maintenance is relatively easy. If, as a programmer,\nyou add or modify a string, you will have to ask yourself if the new or\naltered string requires translation, and include it within '()' if you\nthink it should be translated. For example, '\"%s\"' is an example of\nstring not requiring translation. But '\"%s: %d\"' does require\ntranslation, because in French, unlike in English, it's customary to put\na space before a colon.\n\nFile: gettext.info, Node: Marking, Next: c-format Flag, Prev: Mark Keywords, Up: Sources\n" }, { "name": "4.5 Marking Translatable Strings", "content": "In PO mode, one set of features is meant more for the programmer than\nfor the translator, and allows him to interactively mark which strings,\nin a set of program sources, are translatable, and which are not. Even\nif it is a fairly easy job for a programmer to find and mark such\nstrings by other means, using any editor of his choice, PO mode makes\nthis work more comfortable. Further, this gives translators who feel a\nlittle like programmers, or programmers who feel a little like\ntranslators, a tool letting them work at marking translatable strings in\nthe program sources, while simultaneously producing a set of translation\nin some language, for the package being internationalized.\n\nThe set of program sources, targeted by the PO mode commands describe\nhere, should have an Emacs tags table constructed for your project,\nprior to using these PO file commands. This is easy to do. In any\nshell window, change the directory to the root of your project, then\nexecute a command resembling:\n\netags src/*.[hc] lib/*.[hc]\n\npresuming here you want to process all '.h' and '.c' files from the\n'src/' and 'lib/' directories. This command will explore all said files\nand create a 'TAGS' file in your root directory, somewhat summarizing\nthe contents using a special file format Emacs can understand.\n\nFor packages following the GNU coding standards, there is a make goal\n'tags' or 'TAGS' which constructs the tag files in all directories and\nfor all files containing source code.\n\nOnce your 'TAGS' file is ready, the following commands assist the\nprogrammer at marking translatable strings in his set of sources. But\nthese commands are necessarily driven from within a PO file window, and\nit is likely that you do not even have such a PO file yet. This is not\na problem at all, as you may safely open a new, empty PO file, mainly\nfor using these commands. This empty PO file will slowly fill in while\nyou mark strings as translatable in your program sources.\n\n','\nSearch through program sources for a string which looks like a\ncandidate for translation ('po-tags-search').\n\n'M-,'\nMark the last string found with '()' ('po-mark-translatable').\n\n'M-.'\nMark the last string found with a keyword taken from a set of\npossible keywords. This command with a prefix allows some\nmanagement of these keywords ('po-select-mark-and-mark').\n\nThe ',' ('po-tags-search') command searches for the next occurrence\nof a string which looks like a possible candidate for translation, and\ndisplays the program source in another Emacs window, positioned in such\na way that the string is near the top of this other window. If the\nstring is too big to fit whole in this window, it is positioned so only\nits end is shown. In any case, the cursor is left in the PO file\nwindow. If the shown string would be better presented differently in\ndifferent native languages, you may mark it using 'M-,' or 'M-.'.\nOtherwise, you might rather ignore it and skip to the next string by\nmerely repeating the ',' command.\n\nA string is a good candidate for translation if it contains a\nsequence of three or more letters. A string containing at most two\nletters in a row will be considered as a candidate if it has more\nletters than non-letters. The command disregards strings containing no\nletters, or isolated letters only. It also disregards strings within\ncomments, or strings already marked with some keyword PO mode knows (see\nbelow).\n\nIf you have never told Emacs about some 'TAGS' file to use, the\ncommand will request that you specify one from the minibuffer, the first\ntime you use the command. You may later change your 'TAGS' file by\nusing the regular Emacs command 'M-x visit-tags-table', which will ask\nyou to name the precise 'TAGS' file you want to use. *Note Tag Tables:\n(emacs)Tags.\n\nEach time you use the ',' command, the search resumes from where it\nwas left by the previous search, and goes through all program sources,\nobeying the 'TAGS' file, until all sources have been processed.\nHowever, by giving a prefix argument to the command ('C-u ,'), you may\nrequest that the search be restarted all over again from the first\nprogram source; but in this case, strings that you recently marked as\ntranslatable will be automatically skipped.\n\nUsing this ',' command does not prevent using of other regular Emacs\ntags commands. For example, regular 'tags-search' or\n'tags-query-replace' commands may be used without disrupting the\nindependent ',' search sequence. However, as implemented, the initial\n',' command (or the ',' command is used with a prefix) might also\nreinitialize the regular Emacs tags searching to the first tags file,\nthis reinitialization might be considered spurious.\n\nThe 'M-,' ('po-mark-translatable') command will mark the recently\nfound string with the '' keyword. The 'M-.'\n('po-select-mark-and-mark') command will request that you type one\nkeyword from the minibuffer and use that keyword for marking the string.\nBoth commands will automatically create a new PO file untranslated entry\nfor the string being marked, and make it the current entry (making it\neasy for you to immediately proceed to its translation, if you feel like\ndoing it right away). It is possible that the modifications made to the\nprogram source by 'M-,' or 'M-.' render some source line longer than 80\ncolumns, forcing you to break and re-indent this line differently. You\nmay use the 'O' command from PO mode, or any other window changing\ncommand from Emacs, to break out into the program source window, and do\nany needed adjustments. You will have to use some regular Emacs command\nto return the cursor to the PO file window, if you want command ',' for\nthe next string, say.\n\nThe 'M-.' command has a few built-in speedups, so you do not have to\nexplicitly type all keywords all the time. The first such speedup is\nthat you are presented with a preferred keyword, which you may accept\nby merely typing '' at the prompt. The second speedup is that you\nmay type any non-ambiguous prefix of the keyword you really mean, and\nthe command will complete it automatically for you. This also means\nthat PO mode has to know all your possible keywords, and that it will\nnot accept mistyped keywords.\n\nIf you reply '?' to the keyword request, the command gives a list of\nall known keywords, from which you may choose. When the command is\nprefixed by an argument ('C-u M-.'), it inhibits updating any program\nsource or PO file buffer, and does some simple keyword management\ninstead. In this case, the command asks for a keyword, written in full,\nwhich becomes a new allowed keyword for later 'M-.' commands. Moreover,\nthis new keyword automatically becomes the preferred keyword for later\ncommands. By typing an already known keyword in response to 'C-u M-.',\none merely changes the preferred keyword and does nothing more.\n\nAll keywords known for 'M-.' are recognized by the ',' command when\nscanning for strings, and strings already marked by any of those known\nkeywords are automatically skipped. If many PO files are opened\nsimultaneously, each one has its own independent set of known keywords.\nThere is no provision in PO mode, currently, for deleting a known\nkeyword, you have to quit the file (maybe using 'q') and reopen it\nafresh. When a PO file is newly brought up in an Emacs window, only\n'gettext' and '' are known as keywords, and 'gettext' is preferred for\nthe 'M-.' command. In fact, this is not useful to prefer '', as this\none is already built in the 'M-,' command.\n\nFile: gettext.info, Node: c-format Flag, Next: Special cases, Prev: Marking, Up: Sources\n" }, { "name": "4.6 Special Comments preceding Keywords", "content": "In C programs strings are often used within calls of functions from\nthe 'printf' family. The special thing about these format strings is\nthat they can contain format specifiers introduced with '%'. Assume we\nhave the code\n\nprintf (gettext (\"String `%s' has %d characters\\n\"), s, strlen (s));\n\nA possible German translation for the above string might be:\n\n\"%d Zeichen lang ist die Zeichenkette `%s'\"\n\nA C programmer, even if he cannot speak German, will recognize that\nthere is something wrong here. The order of the two format specifiers\nis changed but of course the arguments in the 'printf' don't have. This\nwill most probably lead to problems because now the length of the string\nis regarded as the address.\n\nTo prevent errors at runtime caused by translations, the 'msgfmt'\ntool can check statically whether the arguments in the original and the\ntranslation string match in type and number. If this is not the case\nand the '-c' option has been passed to 'msgfmt', 'msgfmt' will give an\nerror and refuse to produce a MO file. Thus consistent use of 'msgfmt\n-c' will catch the error, so that it cannot cause problems at runtime.\n\nIf the word order in the above German translation would be correct one\nwould have to write\n\n\"%2$d Zeichen lang ist die Zeichenkette `%1$s'\"\n\nThe routines in 'msgfmt' know about this special notation.\n\nBecause not all strings in a program will be format strings, it is\nnot useful for 'msgfmt' to test all the strings in the '.po' file. This\nmight cause problems because the string might contain what looks like a\nformat specifier, but the string is not used in 'printf'.\n\nTherefore 'xgettext' adds a special tag to those messages it thinks\nmight be a format string. There is no absolute rule for this, only a\nheuristic. In the '.po' file the entry is marked using the 'c-format'\nflag in the '#,' comment line (*note PO Files::).\n\nThe careful reader now might say that this again can cause problems.\nThe heuristic might guess it wrong. This is true and therefore\n'xgettext' knows about a special kind of comment which lets the\nprogrammer take over the decision. If in the same line as or the\nimmediately preceding line to the 'gettext' keyword the 'xgettext'\nprogram finds a comment containing the words 'xgettext:c-format', it\nwill mark the string in any case with the 'c-format' flag. This kind of\ncomment should be used when 'xgettext' does not recognize the string as\na format string but it really is one and it should be tested. Please\nnote that when the comment is in the same line as the 'gettext' keyword,\nit must be before the string to be translated.\n\nThis situation happens quite often. The 'printf' function is often\ncalled with strings which do not contain a format specifier. Of course\none would normally use 'fputs' but it does happen. In this case\n'xgettext' does not recognize this as a format string but what happens\nif the translation introduces a valid format specifier? The 'printf'\nfunction will try to access one of the parameters but none exists\nbecause the original code does not pass any parameters.\n\n'xgettext' of course could make a wrong decision the other way round,\ni.e. a string marked as a format string actually is not a format string.\nIn this case the 'msgfmt' might give too many warnings and would prevent\ntranslating the '.po' file. The method to prevent this wrong decision\nis similar to the one used above, only the comment to use must contain\nthe string 'xgettext:no-c-format'.\n\nIf a string is marked with 'c-format' and this is not correct the\nuser can find out who is responsible for the decision. See *note\nxgettext Invocation:: to see how the '--debug' option can be used for\nsolving this problem.\n\nFile: gettext.info, Node: Special cases, Next: Bug Report Address, Prev: c-format Flag, Up: Sources\n" }, { "name": "4.7 Special Cases of Translatable Strings", "content": "The attentive reader might now point out that it is not always\npossible to mark translatable string with 'gettext' or something like\nthis. Consider the following case:\n\n{\nstatic const char *messages[] = {\n\"some very meaningful message\",\n\"and another one\"\n};\nconst char *string;\n...\nstring\n= index > 1 ? \"a default message\" : messages[index];\n\nfputs (string);\n...\n}\n\nWhile it is no problem to mark the string '\"a default message\"' it is\nnot possible to mark the string initializers for 'messages'. What is to\nbe done? We have to fulfill two tasks. First we have to mark the\nstrings so that the 'xgettext' program (*note xgettext Invocation::) can\nfind them, and second we have to translate the string at runtime before\nprinting them.\n\nThe first task can be fulfilled by creating a new keyword, which\nnames a no-op. For the second we have to mark all access points to a\nstring from the array. So one solution can look like this:\n\n#define gettextnoop(String) String\n\n{\nstatic const char *messages[] = {\ngettextnoop (\"some very meaningful message\"),\ngettextnoop (\"and another one\")\n};\nconst char *string;\n...\nstring\n= index > 1 ? gettext (\"a default message\") : gettext (messages[index]);\n\nfputs (string);\n...\n}\n\nPlease convince yourself that the string which is written by 'fputs'\nis translated in any case. How to get 'xgettext' know the additional\nkeyword 'gettextnoop' is explained in *note xgettext Invocation::.\n\nThe above is of course not the only solution. You could also come\nalong with the following one:\n\n#define gettextnoop(String) String\n\n{\nstatic const char *messages[] = {\ngettextnoop (\"some very meaningful message\"),\ngettextnoop (\"and another one\")\n};\nconst char *string;\n...\nstring\n= index > 1 ? gettextnoop (\"a default message\") : messages[index];\n\nfputs (gettext (string));\n...\n}\n\nBut this has a drawback. The programmer has to take care that he\nuses 'gettextnoop' for the string '\"a default message\"'. A use of\n'gettext' could have in rare cases unpredictable results.\n\nOne advantage is that you need not make control flow analysis to make\nsure the output is really translated in any case. But this analysis is\ngenerally not very difficult. If it should be in any situation you can\nuse this second method in this situation.\n\nFile: gettext.info, Node: Bug Report Address, Next: Names, Prev: Special cases, Up: Sources\n" }, { "name": "4.8 Letting Users Report Translation Bugs", "content": "Code sometimes has bugs, but translations sometimes have bugs too.\nThe users need to be able to report them. Reporting translation bugs to\nthe programmer or maintainer of a package is not very useful, since the\nmaintainer must never change a translation, except on behalf of the\ntranslator. Hence the translation bugs must be reported to the\ntranslators.\n\nHere is a way to organize this so that the maintainer does not need\nto forward translation bug reports, nor even keep a list of the\naddresses of the translators or their translation teams.\n\nEvery program has a place where is shows the bug report address. For\nGNU programs, it is the code which handles the \"-help\" option, typically\nin a function called \"usage\". In this place, instruct the translator to\nadd her own bug reporting address. For example, if that code has a\nstatement\n\nprintf ((\"Report bugs to <%s>.\\n\"), PACKAGEBUGREPORT);\n\nyou can add some translator instructions like this:\n\n/* TRANSLATORS: The placeholder indicates the bug-reporting address\nfor this package. Please add another line saying\n\"Report translation bugs to <...>\\n\" with the address for translation\nbugs (typically your translation team's web or email address). */\nprintf ((\"Report bugs to <%s>.\\n\"), PACKAGEBUGREPORT);\n\nThese will be extracted by 'xgettext', leading to a .pot file that\ncontains this:\n\n#. TRANSLATORS: The placeholder indicates the bug-reporting address\n#. for this package. Please add another line saying\n#. \"Report translation bugs to <...>\\n\" with the address for translation\n#. bugs (typically your translation team's web or email address).\n#: src/hello.c:178\n#, c-format\nmsgid \"Report bugs to <%s>.\\n\"\nmsgstr \"\"\n\nFile: gettext.info, Node: Names, Next: Libraries, Prev: Bug Report Address, Up: Sources\n" }, { "name": "4.9 Marking Proper Names for Translation", "content": "Should names of persons, cities, locations etc. be marked for\ntranslation or not? People who only know languages that can be written\nwith Latin letters (English, Spanish, French, German, etc.) are tempted\nto say \"no\", because names usually do not change when transported\nbetween these languages. However, in general when translating from one\nscript to another, names are translated too, usually phonetically or by\ntransliteration. For example, Russian or Greek names are converted to\nthe Latin alphabet when being translated to English, and English or\nFrench names are converted to the Katakana script when being translated\nto Japanese. This is necessary because the speakers of the target\nlanguage in general cannot read the script the name is originally\nwritten in.\n\nAs a programmer, you should therefore make sure that names are marked\nfor translation, with a special comment telling the translators that it\nis a proper name and how to pronounce it. In its simple form, it looks\nlike this:\n\nprintf ((\"Written by %s.\\n\"),\n/* TRANSLATORS: This is a proper name. See the gettext\nmanual, section Names. Note this is actually a non-ASCII\nname: The first name is (with Unicode escapes)\n\"Fran\\u00e7ois\" or (with HTML entities) \"François\".\nPronunciation is like \"fraa-swa pee-nar\". */\n(\"Francois Pinard\"));\n\nThe GNU gnulib library offers a module 'propername'\n()\nwhich takes care to automatically append the original name, in\nparentheses, to the translated name. For names that cannot be written\nin ASCII, it also frees the translator from the task of entering the\nappropriate non-ASCII characters if no script change is needed. In this\nmore comfortable form, it looks like this:\n\nprintf ((\"Written by %s and %s.\\n\"),\npropername (\"Ulrich Drepper\"),\n/* TRANSLATORS: This is a proper name. See the gettext\nmanual, section Names. Note this is actually a non-ASCII\nname: The first name is (with Unicode escapes)\n\"Fran\\u00e7ois\" or (with HTML entities) \"François\".\nPronunciation is like \"fraa-swa pee-nar\". */\npropernameutf8 (\"Francois Pinard\", \"Fran\\303\\247ois Pinard\"));\n\nYou can also write the original name directly in Unicode (rather than\nwith Unicode escapes or HTML entities) and denote the pronunciation\nusing the International Phonetic Alphabet (see\n).\n\nAs a translator, you should use some care when translating names,\nbecause it is frustrating if people see their names mutilated or\ndistorted.\n\nIf your language uses the Latin script, all you need to do is to\nreproduce the name as perfectly as you can within the usual character\nset of your language. In this particular case, this means to provide a\ntranslation containing the c-cedilla character. If your language uses a\ndifferent script and the people speaking it don't usually read Latin\nwords, it means transliteration. If the programmer used the simple\ncase, you should still give, in parentheses, the original writing of the\nname - for the sake of the people that do read the Latin script. If the\nprogrammer used the 'propername' module mentioned above, you don't need\nto give the original writing of the name in parentheses, because the\nprogram will already do so. Here is an example, using Greek as the\ntarget script:\n\n#. This is a proper name. See the gettext\n#. manual, section Names. Note this is actually a non-ASCII\n#. name: The first name is (with Unicode escapes)\n#. \"Fran\\u00e7ois\" or (with HTML entities) \"François\".\n#. Pronunciation is like \"fraa-swa pee-nar\".\nmsgid \"Francois Pinard\"\nmsgstr \"\\phi\\rho\\alpha\\sigma\\omicron\\alpha \\pi\\iota\\nu\\alpha\\rho\"\n\" (Francois Pinard)\"\n\nBecause translation of names is such a sensitive domain, it is a good\nidea to test your translation before submitting it.\n\nFile: gettext.info, Node: Libraries, Prev: Names, Up: Sources\n" }, { "name": "4.10 Preparing Library Sources", "content": "When you are preparing a library, not a program, for the use of\n'gettext', only a few details are different. Here we assume that the\nlibrary has a translation domain and a POT file of its own. (If it uses\nthe translation domain and POT file of the main program, then the\nprevious sections apply without changes.)\n\n1. The library code doesn't call 'setlocale (LCALL, \"\")'. It's the\nresponsibility of the main program to set the locale. The\nlibrary's documentation should mention this fact, so that\ndevelopers of programs using the library are aware of it.\n\n2. The library code doesn't call 'textdomain (PACKAGE)', because it\nwould interfere with the text domain set by the main program.\n\n3. The initialization code for a program was\n\nsetlocale (LCALL, \"\");\nbindtextdomain (PACKAGE, LOCALEDIR);\ntextdomain (PACKAGE);\n\nFor a library it is reduced to\n\nbindtextdomain (PACKAGE, LOCALEDIR);\n\nIf your library's API doesn't already have an initialization\nfunction, you need to create one, containing at least the\n'bindtextdomain' invocation. However, you usually don't need to\nexport and document this initialization function: It is sufficient\nthat all entry points of the library call the initialization\nfunction if it hasn't been called before. The typical idiom used\nto achieve this is a static boolean variable that indicates whether\nthe initialization function has been called. Like this:\n\nstatic bool libfooinitialized;\n\nstatic void\nlibfooinitialize (void)\n{\nbindtextdomain (PACKAGE, LOCALEDIR);\nlibfooinitialized = true;\n}\n\n/* This function is part of the exported API. */\nstruct foo *\ncreatefoo (...)\n{\n/* Must ensure the initialization is performed. */\nif (!libfooinitialized)\nlibfooinitialize ();\n...\n}\n\n/* This function is part of the exported API. The argument must be\nnon-NULL and have been created through createfoo(). */\nint\nfoorefcount (struct foo *argument)\n{\n/* No need to invoke the initialization function here, because\ncreatefoo() must already have been called before. */\n...\n}\n\n4. The usual declaration of the '' macro in each source file was\n\n#include \n#define (String) gettext (String)\n\nfor a program. For a library, which has its own translation\ndomain, it reads like this:\n\n#include \n#define (String) dgettext (PACKAGE, String)\n\nIn other words, 'dgettext' is used instead of 'gettext'.\nSimilarly, the 'dngettext' function should be used in place of the\n'ngettext' function.\n\nFile: gettext.info, Node: Template, Next: Creating, Prev: Sources, Up: Top\n" } ] }, "5 Making the PO Template File": { "content": "After preparing the sources, the programmer creates a PO template\nfile. This section explains how to use 'xgettext' for this purpose.\n\n'xgettext' creates a file named 'DOMAINNAME.po'. You should then\nrename it to 'DOMAINNAME.pot'. (Why doesn't 'xgettext' create it under\nthe name 'DOMAINNAME.pot' right away? The answer is: for historical\nreasons. When 'xgettext' was specified, the distinction between a PO\nfile and PO file template was fuzzy, and the suffix '.pot' wasn't in use\nat that time.)\n\n* Menu:\n\n* xgettext Invocation:: Invoking the 'xgettext' Program\n\nFile: gettext.info, Node: xgettext Invocation, Up: Template\n", "subsections": [ { "name": "5.1 Invoking the 'xgettext' Program", "content": "xgettext [OPTION] [INPUTFILE] ...\n\nThe 'xgettext' program extracts translatable strings from given input\nfiles.\n\n\n'INPUTFILE ...'\nInput files.\n\n'-f FILE'\n'--files-from=FILE'\nRead the names of the input files from FILE instead of getting them\nfrom the command line.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting '.po'\nfile will be written relative to the current directory, though.\n\nIf INPUTFILE is '-', standard input is read.\n\n\n'-d NAME'\n'--default-domain=NAME'\nUse 'NAME.po' for output (instead of 'messages.po').\n\n'-o FILE'\n'--output=FILE'\nWrite output to specified file (instead of 'NAME.po' or\n'messages.po').\n\n'-p DIR'\n'--output-dir=DIR'\nOutput files will be placed in directory DIR.\n\nIf the output FILE is '-' or '/dev/stdout', the output is written to\nstandard output.\n\n\n'-L NAME'\n'--language=NAME'\nSpecifies the language of the input files. The supported languages\nare 'C', 'C++', 'ObjectiveC', 'PO', 'Shell', 'Python', 'Lisp',\n'EmacsLisp', 'librep', 'Scheme', 'Smalltalk', 'Java',\n'JavaProperties', 'C#', 'awk', 'YCP', 'Tcl', 'Perl', 'PHP', 'Ruby',\n'GCC-source', 'NXStringTable', 'RST', 'RSJ', 'Glade', 'Lua',\n'JavaScript', 'Vala', 'GSettings', 'Desktop'.\n\n'-C'\n'--c++'\nThis is a shorthand for '--language=C++'.\n\nBy default the language is guessed depending on the input file name\nextension.\n\n\n'--from-code=NAME'\nSpecifies the encoding of the input files. This option is needed\nonly if some untranslated message strings or their corresponding\ncomments contain non-ASCII characters. Note that Tcl and Glade\ninput files are always assumed to be in UTF-8, regardless of this\noption.\n\nBy default the input files are assumed to be in ASCII.\n\n\n'-j'\n'--join-existing'\nJoin messages with existing file.\n\n'-x FILE'\n'--exclude-file=FILE'\nEntries from FILE are not extracted. FILE should be a PO or POT\nfile.\n\n'-c[TAG]'\n'--add-comments[=TAG]'\nPlace comment blocks starting with TAG and preceding keyword lines\nin the output file. Without a TAG, the option means to put all\ncomment blocks preceding keyword lines in the output file.\n\nNote that comment blocks supposed to be extracted must be adjacent\nto keyword lines. For example, in the following C source code:\n\n/* This is the first comment. */\ngettext (\"foo\");\n\n/* This is the second comment: not extracted */\ngettext (\n\"bar\");\n\ngettext (\n/* This is the third comment. */\n\"baz\");\n\nThe second comment line will not be extracted, because there is one\nblank line between the comment line and the keyword.\n\n'--check[=CHECK]'\nPerform a syntax check on msgid and msgidplural. The supported\nchecks are:\n\n'ellipsis-unicode'\nPrefer Unicode ellipsis character over ASCII '...'\n\n'space-ellipsis'\nProhibit whitespace before an ellipsis character\n\n'quote-unicode'\nPrefer Unicode quotation marks over ASCII '\"'`'\n\n'bullet-unicode'\nPrefer Unicode bullet character over ASCII '*' or '-'\n\nThe option has an effect on all input files. To enable or disable\nchecks for a certain string, you can mark it with an 'xgettext:'\nspecial comment in the source file. For example, if you specify\nthe '--check=space-ellipsis' option, but want to suppress the check\non a particular string, add the following comment:\n\n/* xgettext: no-space-ellipsis-check */\ngettext (\"We really want a space before ellipsis here ...\");\n\nThe 'xgettext:' comment can be followed by flags separated with a\ncomma. The possible flags are of the form '[no-]NAME-check', where\nNAME is the name of a valid syntax check. If a flag is prefixed by\n'no-', the meaning is negated.\n\nSome tests apply the checks to each sentence within the msgid,\nrather than the whole string. xgettext detects the end of sentence\nby performing a pattern match, which usually looks for a period\nfollowed by a certain number of spaces. The number is specified\nwith the '--sentence-end' option.\n\n'--sentence-end[=TYPE]'\nThe supported values are:\n\n'single-space'\nExpect at least one whitespace after a period\n\n'double-space'\nExpect at least two whitespaces after a period\n\n\n'-a'\n'--extract-all'\nExtract all strings.\n\nThis option has an effect with most languages, namely C, C++,\nObjectiveC, Shell, Python, Lisp, EmacsLisp, librep, Java, C#, awk,\nTcl, Perl, PHP, GCC-source, Glade, Lua, JavaScript, Vala,\nGSettings.\n\n'-k[KEYWORDSPEC]'\n'--keyword[=KEYWORDSPEC]'\nSpecify KEYWORDSPEC as an additional keyword to be looked for.\nWithout a KEYWORDSPEC, the option means to not use default\nkeywords.\n\nIf KEYWORDSPEC is a C identifier ID, 'xgettext' looks for strings\nin the first argument of each call to the function or macro ID. If\nKEYWORDSPEC is of the form 'ID:ARGNUM', 'xgettext' looks for\nstrings in the ARGNUMth argument of the call. If KEYWORDSPEC is of\nthe form 'ID:ARGNUM1,ARGNUM2', 'xgettext' looks for strings in the\nARGNUM1st argument and in the ARGNUM2nd argument of the call, and\ntreats them as singular/plural variants for a message with plural\nhandling. Also, if KEYWORDSPEC is of the form\n'ID:CONTEXTARGNUMc,ARGNUM' or 'ID:ARGNUM,CONTEXTARGNUMc',\n'xgettext' treats strings in the CONTEXTARGNUMth argument as a\ncontext specifier. And, as a special-purpose support for GNOME, if\nKEYWORDSPEC is of the form 'ID:ARGNUMg', 'xgettext' recognizes the\nARGNUMth argument as a string with context, using the GNOME 'glib'\nsyntax '\"msgctxt|msgid\"'.\nFurthermore, if KEYWORDSPEC is of the form 'ID:...,TOTALNUMARGSt',\n'xgettext' recognizes this argument specification only if the\nnumber of actual arguments is equal to TOTALNUMARGS. This is\nuseful for disambiguating overloaded function calls in C++.\nFinally, if KEYWORDSPEC is of the form 'ID:ARGNUM...,\"XCOMMENT\"',\n'xgettext', when extracting a message from the specified argument\nstrings, adds an extracted comment XCOMMENT to the message. Note\nthat when used through a normal shell command line, the\ndouble-quotes around the XCOMMENT need to be escaped.\n\nThis option has an effect with most languages, namely C, C++,\nObjectiveC, Shell, Python, Lisp, EmacsLisp, librep, Java, C#, awk,\nTcl, Perl, PHP, GCC-source, Glade, Lua, JavaScript, Vala,\nGSettings, Desktop.\n\nThe default keyword specifications, which are always looked for if\nnot explicitly disabled, are language dependent. They are:\n\n* For C, C++, and GCC-source: 'gettext', 'dgettext:2',\n'dcgettext:2', 'ngettext:1,2', 'dngettext:2,3',\n'dcngettext:2,3', 'gettextnoop', and 'pgettext:1c,2',\n'dpgettext:2c,3', 'dcpgettext:2c,3', 'npgettext:1c,2,3',\n'dnpgettext:2c,3,4', 'dcnpgettext:2c,3,4'.\n\n* For Objective C: Like for C, and also 'NSLocalizedString',\n'', 'NSLocalizedStaticString', ''.\n\n* For Shell scripts: 'gettext', 'ngettext:1,2', 'evalgettext',\n'evalngettext:1,2', 'evalpgettext:1c,2',\n'evalnpgettext:1c,2,3'.\n\n* For Python: 'gettext', 'ugettext', 'dgettext:2',\n'ngettext:1,2', 'ungettext:1,2', 'dngettext:2,3', ''.\n\n* For Lisp: 'gettext', 'ngettext:1,2', 'gettext-noop'.\n\n* For EmacsLisp: ''.\n\n* For librep: ''.\n\n* For Scheme: 'gettext', 'ngettext:1,2', 'gettext-noop'.\n\n* For Java: 'GettextResource.gettext:2',\n'GettextResource.ngettext:2,3',\n'GettextResource.pgettext:2c,3',\n'GettextResource.npgettext:2c,3,4', 'gettext', 'ngettext:1,2',\n'pgettext:1c,2', 'npgettext:1c,2,3', 'getString'.\n\n* For C#: 'GetString', 'GetPluralString:1,2',\n'GetParticularString:1c,2',\n'GetParticularPluralString:1c,2,3'.\n\n* For awk: 'dcgettext', 'dcngettext:1,2'.\n\n* For Tcl: '::msgcat::mc'.\n\n* For Perl: 'gettext', '%gettext', '$gettext', 'dgettext:2',\n'dcgettext:2', 'ngettext:1,2', 'dngettext:2,3',\n'dcngettext:2,3', 'gettextnoop'.\n\n* For PHP: '', 'gettext', 'dgettext:2', 'dcgettext:2',\n'ngettext:1,2', 'dngettext:2,3', 'dcngettext:2,3'.\n\n* For Glade 1: 'label', 'title', 'text', 'format', 'copyright',\n'comments', 'previewtext', 'tooltip'.\n\n* For Lua: '', 'gettext.gettext', 'gettext.dgettext:2',\n'gettext.dcgettext:2', 'gettext.ngettext:1,2',\n'gettext.dngettext:2,3', 'gettext.dcngettext:2,3'.\n\n* For JavaScript: '', 'gettext', 'dgettext:2', 'dcgettext:2',\n'ngettext:1,2', 'dngettext:2,3', 'pgettext:1c,2',\n'dpgettext:2c,3'.\n\n* For Vala: '', 'Q', 'N', 'NC', 'dgettext:2', 'dcgettext:2',\n'ngettext:1,2', 'dngettext:2,3', 'dpgettext:2c,3',\n'dpgettext2:2c,3'.\n\n* For Desktop: 'Name', 'GenericName', 'Comment', 'Keywords'.\n\nTo disable the default keyword specifications, the option '-k' or\n'--keyword' or '--keyword=', without a KEYWORDSPEC, can be used.\n\n'--flag=WORD:ARG:FLAG'\nSpecifies additional flags for strings occurring as part of the\nARGth argument of the function WORD. The possible flags are the\npossible format string indicators, such as 'c-format', and their\nnegations, such as 'no-c-format', possibly prefixed with 'pass-'.\nThe meaning of '--flag=FUNCTION:ARG:LANG-format' is that in\nlanguage LANG, the specified FUNCTION expects as ARGth argument a\nformat string. (For those of you familiar with GCC function\nattributes, '--flag=FUNCTION:ARG:c-format' is roughly equivalent to\nthe declaration 'attribute ((format (printf, ARG,\n...)))' attached to FUNCTION in a C source file.) For example, if\nyou use the 'error' function from GNU libc, you can specify its\nbehaviour through '--flag=error:3:c-format'. The effect of this\nspecification is that 'xgettext' will mark as format strings all\n'gettext' invocations that occur as ARGth argument of FUNCTION.\nThis is useful when such strings contain no format string\ndirectives: together with the checks done by 'msgfmt -c' it will\nensure that translators cannot accidentally use format string\ndirectives that would lead to a crash at runtime.\nThe meaning of '--flag=FUNCTION:ARG:pass-LANG-format' is that in\nlanguage LANG, if the FUNCTION call occurs in a position that must\nyield a format string, then its ARGth argument must yield a format\nstring of the same type as well. (If you know GCC function\nattributes, the '--flag=FUNCTION:ARG:pass-c-format' option is\nroughly equivalent to the declaration 'attribute\n((formatarg (ARG)))' attached to FUNCTION in a C source file.)\nFor example, if you use the '' shortcut for the 'gettext'\nfunction, you should use '--flag=:1:pass-c-format'. The effect of\nthis specification is that 'xgettext' will propagate a format\nstring requirement for a '(\"string\")' call to its first argument,\nthe literal '\"string\"', and thus mark it as a format string. This\nis useful when such strings contain no format string directives:\ntogether with the checks done by 'msgfmt -c' it will ensure that\ntranslators cannot accidentally use format string directives that\nwould lead to a crash at runtime.\nThis option has an effect with most languages, namely C, C++,\nObjectiveC, Shell, Python, Lisp, EmacsLisp, librep, Scheme, Java,\nC#, awk, YCP, Tcl, Perl, PHP, GCC-source, Lua, JavaScript, Vala.\n\n'-T'\n'--trigraphs'\nUnderstand ANSI C trigraphs for input.\nThis option has an effect only with the languages C, C++,\nObjectiveC.\n\n'--qt'\nRecognize Qt format strings.\nThis option has an effect only with the language C++.\n\n'--kde'\nRecognize KDE 4 format strings.\nThis option has an effect only with the language C++.\n\n'--boost'\nRecognize Boost format strings.\nThis option has an effect only with the language C++.\n\n'--debug'\nUse the flags 'c-format' and 'possible-c-format' to show who was\nresponsible for marking a message as a format string. The latter\nform is used if the 'xgettext' program decided, the former form is\nused if the programmer prescribed it.\n\nBy default only the 'c-format' form is used. The translator should\nnot have to care about these details.\n\nThis implementation of 'xgettext' is able to process a few awkward\ncases, like strings in preprocessor macros, ANSI concatenation of\nadjacent strings, and escaped end of lines for continued strings.\n\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'--force-po'\nAlways write an output file even if no message is defined.\n\n'-i'\n'--indent'\nWrite the .po file using indented style.\n\n'--no-location'\nDo not write '#: FILENAME:LINE' lines. Note that using this option\nmakes it harder for technically skilled translators to understand\neach message's context.\n\n'-n'\n'--add-location=TYPE'\nGenerate '#: FILENAME:LINE' lines (default).\n\nThe optional TYPE can be either 'full', 'file', or 'never'. If it\nis not given or 'full', it generates the lines with both file name\nand line number. If it is 'file', the line number part is omitted.\nIf it is 'never', it completely suppresses the lines (same as\n'--no-location').\n\n'--strict'\nWrite out a strict Uniforum conforming PO file. Note that this\nUniforum format should be avoided because it doesn't support the\nGNU extensions.\n\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'--its=FILE'\nUse ITS rules defined in FILE. Note that this is only effective\nwith XML files.\n\n'--itstool'\nWrite out comments recognized by itstool ().\nNote that this is only effective with XML files.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n'-s'\n'--sort-output'\nGenerate sorted output. Note that using this option makes it much\nharder for the translator to understand each message's context.\n\n'-F'\n'--sort-by-file'\nSort output by file location.\n\n'--omit-header'\nDon't write header with 'msgid \"\"' entry.\n\nThis is useful for testing purposes because it eliminates a source\nof variance for generated '.gmo' files. With '--omit-header', two\ninvocations of 'xgettext' on the same files with the same options\nat different times are guaranteed to produce the same results.\n\nNote that using this option will lead to an error if the resulting\nfile would not entirely be in ASCII.\n\n'--copyright-holder=STRING'\nSet the copyright holder in the output. STRING should be the\ncopyright holder of the surrounding package. (Note that the msgstr\nstrings, extracted from the package's sources, belong to the\ncopyright holder of the package.) Translators are expected to\ntransfer or disclaim the copyright for their translations, so that\npackage maintainers can distribute them without legal risk. If\nSTRING is empty, the output files are marked as being in the public\ndomain; in this case, the translators are expected to disclaim\ntheir copyright, again so that package maintainers can distribute\nthem without legal risk.\n\nThe default value for STRING is the Free Software Foundation, Inc.,\nsimply because 'xgettext' was first used in the GNU project.\n\n'--foreign-user'\nOmit FSF copyright in output. This option is equivalent to\n'--copyright-holder='''. It can be useful for packages outside the\nGNU project that want their translations to be in the public\ndomain.\n\n'--package-name=PACKAGE'\nSet the package name in the header of the output.\n\n'--package-version=VERSION'\nSet the package version in the header of the output. This option\nhas an effect only if the '--package-name' option is also used.\n\n'--msgid-bugs-address=EMAIL@ADDRESS'\nSet the reporting address for msgid bugs. This is the email\naddress or URL to which the translators shall report bugs in the\nuntranslated strings:\n\n- Strings which are not entire sentences; see the maintainer\nguidelines in *note Preparing Strings::.\n- Strings which use unclear terms or require additional context\nto be understood.\n- Strings which make invalid assumptions about notation of date,\ntime or money.\n- Pluralisation problems.\n- Incorrect English spelling.\n- Incorrect formatting.\n\nIt can be your email address, or a mailing list address where\ntranslators can write to without being subscribed, or the URL of a\nweb page through which the translators can contact you.\n\nThe default value is empty, which means that translators will be\nclueless! Don't forget to specify this option.\n\n'-m[STRING]'\n'--msgstr-prefix[=STRING]'\nUse STRING (or \"\" if not specified) as prefix for msgstr values.\n\n'-M[STRING]'\n'--msgstr-suffix[=STRING]'\nUse STRING (or \"\" if not specified) as suffix for msgstr values.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\n'-v'\n'--verbose'\nIncrease verbosity level.\n\nFile: gettext.info, Node: Creating, Next: Updating, Prev: Template, Up: Top\n" } ] }, "6 Creating a New PO File": { "content": "When starting a new translation, the translator creates a file called\n'LANG.po', as a copy of the 'PACKAGE.pot' template file with\nmodifications in the initial comments (at the beginning of the file) and\nin the header entry (the first entry, near the beginning of the file).\n\nThe easiest way to do so is by use of the 'msginit' program. For\nexample:\n\n$ cd PACKAGE-VERSION\n$ cd po\n$ msginit\n\nThe alternative way is to do the copy and modifications by hand. To\ndo so, the translator copies 'PACKAGE.pot' to 'LANG.po'. Then she\nmodifies the initial comments and the header entry of this file.\n\n* Menu:\n\n* msginit Invocation:: Invoking the 'msginit' Program\n* Header Entry:: Filling in the Header Entry\n\nFile: gettext.info, Node: msginit Invocation, Next: Header Entry, Up: Creating\n", "subsections": [ { "name": "6.1 Invoking the 'msginit' Program", "content": "msginit [OPTION]\n\nThe 'msginit' program creates a new PO file, initializing the meta\ninformation with values from the user's environment.\n\nHere are more details. The following header fields of a PO file are\nautomatically filled, when possible.\n\n'Project-Id-Version'\nThe value is guessed from the 'configure' script or any other files\nin the current directory.\n\n'PO-Revision-Date'\nThe value is taken from the 'PO-Creation-Data' in the input POT\nfile, or the current date is used.\n\n'Last-Translator'\nThe value is taken from user's password file entry and the mailer\nconfiguration files.\n\n'Language-Team, Language'\nThese values are set according to the current locale and the\npredefined list of translation teams.\n\n'MIME-Version, Content-Type, Content-Transfer-Encoding'\nThese values are set according to the content of the POT file and\nthe current locale. If the POT file contains charset=UTF-8, it\nmeans that the POT file contains non-ASCII characters, and we keep\nthe UTF-8 encoding. Otherwise, when the POT file is plain ASCII,\nwe use the locale's encoding.\n\n'Plural-Forms'\nThe value is first looked up from the embedded table.\n\nAs an experimental feature, you can instruct 'msginit' to use the\ninformation from Unicode CLDR, by setting the 'GETTEXTCLDRDIR'\nenvironment variable. The program will look for a file named\n'common/supplemental/plurals.xml' under that directory. You can\nget the CLDR data from .\n\n\n'-i INPUTFILE'\n'--input=INPUTFILE'\nInput POT file.\n\nIf no INPUTFILE is given, the current directory is searched for the\nPOT file. If it is '-', standard input is read.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified PO file.\n\nIf no output file is given, it depends on the '--locale' option or\nthe user's locale setting. If it is '-', the results are written to\nstandard output.\n\n\n'-P'\n'--properties-input'\nAssume the input file is a Java ResourceBundle in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input file is a NeXTstep/GNUstep localized resource file\nin '.strings' syntax, not in PO file syntax.\n\n\n'-l LLCC[.ENCODING]'\n'--locale=LLCC[.ENCODING]'\nSet target locale. LL should be a language code, and CC should be\na country code. The optional part .ENCODING specifies the encoding\nof the locale; most often this part is '.UTF-8'. The command\n'locale -a' can be used to output a list of all installed locales.\nThe default is the user's locale setting.\n\n'--no-translator'\nDeclares that the PO file will not have a human translator and is\ninstead automatically generated.\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'-p'\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\nFile: gettext.info, Node: Header Entry, Prev: msginit Invocation, Up: Creating\n" }, { "name": "6.2 Filling in the Header Entry", "content": "The initial comments \"SOME DESCRIPTIVE TITLE\", \"YEAR\" and \"FIRST\nAUTHOR , YEAR\" ought to be replaced by sensible\ninformation. This can be done in any text editor; if Emacs is used and\nit switched to PO mode automatically (because it has recognized the\nfile's suffix), you can disable it by typing 'M-x fundamental-mode'.\n\nModifying the header entry can already be done using PO mode: in\nEmacs, type 'M-x po-mode RET' and then 'RET' again to start editing the\nentry. You should fill in the following fields.\n\nProject-Id-Version\nThis is the name and version of the package. Fill it in if it has\nnot already been filled in by 'xgettext'.\n\nReport-Msgid-Bugs-To\nThis has already been filled in by 'xgettext'. It contains an\nemail address or URL where you can report bugs in the untranslated\nstrings:\n\n- Strings which are not entire sentences, see the maintainer\nguidelines in *note Preparing Strings::.\n- Strings which use unclear terms or require additional context\nto be understood.\n- Strings which make invalid assumptions about notation of date,\ntime or money.\n- Pluralisation problems.\n- Incorrect English spelling.\n- Incorrect formatting.\n\nPOT-Creation-Date\nThis has already been filled in by 'xgettext'.\n\nPO-Revision-Date\nYou don't need to fill this in. It will be filled by the PO file\neditor when you save the file.\n\nLast-Translator\nFill in your name and email address (without double quotes).\n\nLanguage-Team\nFill in the English name of the language, and the email address or\nhomepage URL of the language team you are part of.\n\nBefore starting a translation, it is a good idea to get in touch\nwith your translation team, not only to make sure you don't do\nduplicated work, but also to coordinate difficult linguistic\nissues.\n\nIn the Free Translation Project, each translation team has its own\nmailing list. The up-to-date list of teams can be found at the\nFree Translation Project's homepage,\n, in the \"Teams\" area.\n\nLanguage\nFill in the language code of the language. This can be in one of\nthree forms:\n\n- 'LL', an ISO 639 two-letter language code (lowercase). See\n*note Language Codes:: for the list of codes.\n\n- 'LLCC', where 'LL' is an ISO 639 two-letter language code\n(lowercase) and 'CC' is an ISO 3166 two-letter country code\n(uppercase). The country code specification is not redundant:\nSome languages have dialects in different countries. For\nexample, 'deAT' is used for Austria, and 'ptBR' for Brazil.\nThe country code serves to distinguish the dialects. See\n*note Language Codes:: and *note Country Codes:: for the lists\nof codes.\n\n- 'LLCC@VARIANT', where 'LL' is an ISO 639 two-letter language\ncode (lowercase), 'CC' is an ISO 3166 two-letter country code\n(uppercase), and 'VARIANT' is a variant designator. The\nvariant designator (lowercase) can be a script designator,\nsuch as 'latin' or 'cyrillic'.\n\nThe naming convention 'LLCC' is also the way locales are named on\nsystems based on GNU libc. But there are three important\ndifferences:\n\n* In this PO file field, but not in locale names, 'LLCC'\ncombinations denoting a language's main dialect are\nabbreviated as 'LL'. For example, 'de' is equivalent to\n'deDE' (German as spoken in Germany), and 'pt' to 'ptPT'\n(Portuguese as spoken in Portugal) in this context.\n\n* In this PO file field, suffixes like '.ENCODING' are not used.\n\n* In this PO file field, variant designators that are not\nrelevant to message translation, such as '@euro', are not\nused.\n\nSo, if your locale name is 'deDE.UTF-8', the language\nspecification in PO files is just 'de'.\n\nContent-Type\nReplace 'CHARSET' with the character encoding used for your\nlanguage, in your locale, or UTF-8. This field is needed for\ncorrect operation of the 'msgmerge' and 'msgfmt' programs, as well\nas for users whose locale's character encoding differs from yours\n(see *note Charset conversion::).\n\nYou get the character encoding of your locale by running the shell\ncommand 'locale charmap'. If the result is 'C' or\n'ANSIX3.4-1968', which is equivalent to 'ASCII' (= 'US-ASCII'), it\nmeans that your locale is not correctly configured. In this case,\nask your translation team which charset to use. 'ASCII' is not\nusable for any language except Latin.\n\nBecause the PO files must be portable to operating systems with\nless advanced internationalization facilities, the character\nencodings that can be used are limited to those supported by both\nGNU 'libc' and GNU 'libiconv'. These are: 'ASCII', 'ISO-8859-1',\n'ISO-8859-2', 'ISO-8859-3', 'ISO-8859-4', 'ISO-8859-5',\n'ISO-8859-6', 'ISO-8859-7', 'ISO-8859-8', 'ISO-8859-9',\n'ISO-8859-13', 'ISO-8859-14', 'ISO-8859-15', 'KOI8-R', 'KOI8-U',\n'KOI8-T', 'CP850', 'CP866', 'CP874', 'CP932', 'CP949', 'CP950',\n'CP1250', 'CP1251', 'CP1252', 'CP1253', 'CP1254', 'CP1255',\n'CP1256', 'CP1257', 'GB2312', 'EUC-JP', 'EUC-KR', 'EUC-TW', 'BIG5',\n'BIG5-HKSCS', 'GBK', 'GB18030', 'SHIFTJIS', 'JOHAB', 'TIS-620',\n'VISCII', 'GEORGIAN-PS', 'UTF-8'.\n\nIn the GNU system, the following encodings are frequently used for\nthe corresponding languages.\n\n* 'ISO-8859-1' for Afrikaans, Albanian, Basque, Breton, Catalan,\nCornish, Danish, Dutch, English, Estonian, Faroese, Finnish,\nFrench, Galician, German, Greenlandic, Icelandic, Indonesian,\nIrish, Italian, Malay, Manx, Norwegian, Occitan, Portuguese,\nSpanish, Swedish, Tagalog, Uzbek, Walloon,\n* 'ISO-8859-2' for Bosnian, Croatian, Czech, Hungarian, Polish,\nRomanian, Serbian, Slovak, Slovenian,\n* 'ISO-8859-3' for Maltese,\n* 'ISO-8859-5' for Macedonian, Serbian,\n* 'ISO-8859-6' for Arabic,\n* 'ISO-8859-7' for Greek,\n* 'ISO-8859-8' for Hebrew,\n* 'ISO-8859-9' for Turkish,\n* 'ISO-8859-13' for Latvian, Lithuanian, Maori,\n* 'ISO-8859-14' for Welsh,\n* 'ISO-8859-15' for Basque, Catalan, Dutch, English, Finnish,\nFrench, Galician, German, Irish, Italian, Portuguese, Spanish,\nSwedish, Walloon,\n* 'KOI8-R' for Russian,\n* 'KOI8-U' for Ukrainian,\n* 'KOI8-T' for Tajik,\n* 'CP1251' for Bulgarian, Belarusian,\n* 'GB2312', 'GBK', 'GB18030' for simplified writing of Chinese,\n* 'BIG5', 'BIG5-HKSCS' for traditional writing of Chinese,\n* 'EUC-JP' for Japanese,\n* 'EUC-KR' for Korean,\n* 'TIS-620' for Thai,\n* 'GEORGIAN-PS' for Georgian,\n* 'UTF-8' for any language, including those listed above.\n\nWhen single quote characters or double quote characters are used in\ntranslations for your language, and your locale's encoding is one\nof the ISO-8859-* charsets, it is best if you create your PO files\nin UTF-8 encoding, instead of your locale's encoding. This is\nbecause in UTF-8 the real quote characters can be represented\n(single quote characters: U+2018, U+2019, double quote characters:\nU+201C, U+201D), whereas none of ISO-8859-* charsets has them all.\nUsers in UTF-8 locales will see the real quote characters, whereas\nusers in ISO-8859-* locales will see the vertical apostrophe and\nthe vertical double quote instead (because that's what the\ncharacter set conversion will transliterate them to).\n\nTo enter such quote characters under X11, you can change your\nkeyboard mapping using the 'xmodmap' program. The X11 names of the\nquote characters are \"leftsinglequotemark\", \"rightsinglequotemark\",\n\"leftdoublequotemark\", \"rightdoublequotemark\",\n\"singlelowquotemark\", \"doublelowquotemark\".\n\nNote that only recent versions of GNU Emacs support the UTF-8\nencoding: Emacs 20 with Mule-UCS, and Emacs 21. As of January\n2001, XEmacs doesn't support the UTF-8 encoding.\n\nThe character encoding name can be written in either upper or lower\ncase. Usually upper case is preferred.\n\nContent-Transfer-Encoding\nSet this to '8bit'.\n\nPlural-Forms\nThis field is optional. It is only needed if the PO file has\nplural forms. You can find them by searching for the\n'msgidplural' keyword. The format of the plural forms field is\ndescribed in *note Plural forms:: and *note Translating plural\nforms::.\n\nFile: gettext.info, Node: Updating, Next: Editing, Prev: Creating, Up: Top\n" } ] }, "7 Updating Existing PO Files": { "content": "* Menu:\n\n* msgmerge Invocation:: Invoking the 'msgmerge' Program\n\nFile: gettext.info, Node: msgmerge Invocation, Up: Updating\n", "subsections": [ { "name": "7.1 Invoking the 'msgmerge' Program", "content": "msgmerge [OPTION] DEF.po REF.pot\n\nThe 'msgmerge' program merges two Uniforum style .po files together.\nThe DEF.po file is an existing PO file with translations which will be\ntaken over to the newly created file as long as they still match;\ncomments will be preserved, but extracted comments and file positions\nwill be discarded. The REF.pot file is the last created PO file with\nup-to-date source references but old translations, or a PO Template file\n(generally created by 'xgettext'); any translations or comments in the\nfile will be discarded, however dot comments and file positions will be\npreserved. Where an exact match cannot be found, fuzzy matching is used\nto produce better results.\n\n\n'DEF.po'\nTranslations referring to old sources.\n\n'REF.pot'\nReferences to the new sources.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting '.po'\nfile will be written relative to the current directory, though.\n\n'-C FILE'\n'--compendium=FILE'\nSpecify an additional library of message translations. *Note\nCompendium::. This option may be specified more than once.\n\n\n'-U'\n'--update'\nUpdate DEF.po. Do nothing if DEF.po is already up to date.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified file.\n\nThe results are written to standard output if no output file is\nspecified or if it is '-'.\n\n\nThe result is written back to DEF.po.\n\n'--backup=CONTROL'\nMake a backup of DEF.po\n\n'--suffix=SUFFIX'\nOverride the usual backup suffix.\n\nThe version control method may be selected via the '--backup' option\nor through the 'VERSIONCONTROL' environment variable. Here are the\nvalues:\n\n'none'\n'off'\nNever make backups (even if '--backup' is given).\n\n'numbered'\n't'\nMake numbered backups.\n\n'existing'\n'nil'\nMake numbered backups if numbered backups for this file already\nexist, otherwise make simple backups.\n\n'simple'\n'never'\nAlways make simple backups.\n\nThe backup suffix is '~', unless set with '--suffix' or the\n'SIMPLEBACKUPSUFFIX' environment variable.\n\n\n'-m'\n'--multi-domain'\nApply REF.pot to each of the domains in DEF.po.\n\n'--for-msgfmt'\nProduce a PO file meant for 'msgfmt' only, not for a translator.\nThis option omits untranslated messages, fuzzy messages (except the\nheader entry), and obsolete messages from the output. Also, it\nomits translator comments and '#: FILENAME:LINE' lines from the\noutput. In particular, this option implies '--no-fuzzy-matching'.\n\n'-N'\n'--no-fuzzy-matching'\nDo not use fuzzy matching when an exact match is not found. This\nmay speed up the operation considerably.\n\n'--previous'\nKeep the previous msgids of translated messages, marked with '#|',\nwhen adding the fuzzy marker to such messages.\n\n\n'-P'\n'--properties-input'\nAssume the input files are Java ResourceBundles in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input files are NeXTstep/GNUstep localized resource\nfiles in '.strings' syntax, not in PO file syntax.\n\n\n'--lang=CATALOGNAME'\nSpecify the 'Language' field to be used in the header entry. See\n*note Header Entry:: for the meaning of this field. Note: The\n'Language-Team' and 'Plural-Forms' fields are left unchanged. If\nthis option is not specified, the 'Language' field is inferred, as\nbest as possible, from the 'Language-Team' field.\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'--force-po'\nAlways write an output file even if it contains no message.\n\n'-i'\n'--indent'\nWrite the .po file using indented style.\n\n'--no-location'\nDo not write '#: FILENAME:LINE' lines.\n\n'-n'\n'--add-location=TYPE'\nGenerate '#: FILENAME:LINE' lines (default).\n\nThe optional TYPE can be either 'full', 'file', or 'never'. If it\nis not given or 'full', it generates the lines with both file name\nand line number. If it is 'file', the line number part is omitted.\nIf it is 'never', it completely suppresses the lines (same as\n'--no-location').\n\n'--strict'\nWrite out a strict Uniforum conforming PO file. Note that this\nUniforum format should be avoided because it doesn't support the\nGNU extensions.\n\n'-p'\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n'-s'\n'--sort-output'\nGenerate sorted output. Note that using this option makes it much\nharder for the translator to understand each message's context.\n\n'-F'\n'--sort-by-file'\nSort output by file location.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\n'-v'\n'--verbose'\nIncrease verbosity level.\n\n'-q'\n'--quiet'\n'--silent'\nSuppress progress indicators.\n\nFile: gettext.info, Node: Editing, Next: Manipulating, Prev: Updating, Up: Top\n" } ] }, "8 Editing PO Files": { "content": "* Menu:\n\n* KBabel:: KDE's PO File Editor\n* Gtranslator:: GNOME's PO File Editor\n* PO Mode:: Emacs's PO File Editor\n* Compendium:: Using Translation Compendia\n\nFile: gettext.info, Node: KBabel, Next: Gtranslator, Up: Editing\n", "subsections": [ { "name": "8.1 KDE's PO File Editor", "content": "File: gettext.info, Node: Gtranslator, Next: PO Mode, Prev: KBabel, Up: Editing\n" }, { "name": "8.2 GNOME's PO File Editor", "content": "File: gettext.info, Node: PO Mode, Next: Compendium, Prev: Gtranslator, Up: Editing\n" }, { "name": "8.3 Emacs's PO File Editor", "content": "For those of you being the lucky users of Emacs, PO mode has been\nspecifically created for providing a cozy environment for editing or\nmodifying PO files. While editing a PO file, PO mode allows for the\neasy browsing of auxiliary and compendium PO files, as well as for\nfollowing references into the set of C program sources from which PO\nfiles have been derived. It has a few special features, among which are\nthe interactive marking of program strings as translatable, and the\nvalidation of PO files with easy repositioning to PO file lines showing\nerrors.\n\nFor the beginning, besides main PO mode commands (*note Main PO\nCommands::), you should know how to move between entries (*note Entry\nPositioning::), and how to handle untranslated entries (*note\nUntranslated Entries::).\n\n* Menu:\n\n* Installation:: Completing GNU 'gettext' Installation\n* Main PO Commands:: Main Commands\n* Entry Positioning:: Entry Positioning\n* Normalizing:: Normalizing Strings in Entries\n* Translated Entries:: Translated Entries\n* Fuzzy Entries:: Fuzzy Entries\n* Untranslated Entries:: Untranslated Entries\n* Obsolete Entries:: Obsolete Entries\n* Modifying Translations:: Modifying Translations\n* Modifying Comments:: Modifying Comments\n* Subedit:: Mode for Editing Translations\n* C Sources Context:: C Sources Context\n* Auxiliary:: Consulting Auxiliary PO Files\n\nFile: gettext.info, Node: Installation, Next: Main PO Commands, Up: PO Mode\n\n\nOnce you have received, unpacked, configured and compiled the GNU\n'gettext' distribution, the 'make install' command puts in place the\nprograms 'xgettext', 'msgfmt', 'gettext', and 'msgmerge', as well as\ntheir available message catalogs. To top off a comfortable\ninstallation, you might also want to make the PO mode available to your\nEmacs users.\n\nDuring the installation of the PO mode, you might want to modify your\nfile '.emacs', once and for all, so it contains a few lines looking\nlike:\n\n(setq auto-mode-alist\n(cons '(\"\\\\.po\\\\'\\\\|\\\\.po\\\\.\" . po-mode) auto-mode-alist))\n(autoload 'po-mode \"po-mode\" \"Major mode for translators to edit PO files\" t)\n\nLater, whenever you edit some '.po' file, or any file having the\nstring '.po.' within its name, Emacs loads 'po-mode.elc' (or\n'po-mode.el') as needed, and automatically activates PO mode commands\nfor the associated buffer. The string PO appears in the mode line for\nany buffer for which PO mode is active. Many PO files may be active at\nonce in a single Emacs session.\n\nIf you are using Emacs version 20 or newer, and have already\ninstalled the appropriate international fonts on your system, you may\nalso tell Emacs how to determine automatically the coding system of\nevery PO file. This will often (but not always) cause the necessary\nfonts to be loaded and used for displaying the translations on your\nEmacs screen. For this to happen, add the lines:\n\n(modify-coding-system-alist 'file \"\\\\.po\\\\'\\\\|\\\\.po\\\\.\"\n'po-find-file-coding-system)\n(autoload 'po-find-file-coding-system \"po-mode\")\n\nto your '.emacs' file. If, with this, you still see boxes instead of\ninternational characters, try a different font set (via Shift Mouse\nbutton 1).\n\nFile: gettext.info, Node: Main PO Commands, Next: Entry Positioning, Prev: Installation, Up: PO Mode\n\n\nAfter setting up Emacs with something similar to the lines in *note\nInstallation::, PO mode is activated for a window when Emacs finds a PO\nfile in that window. This puts the window read-only and establishes a\npo-mode-map, which is a genuine Emacs mode, in a way that is not derived\nfrom text mode in any way. Functions found on 'po-mode-hook', if any,\nwill be executed.\n\nWhen PO mode is active in a window, the letters 'PO' appear in the\nmode line for that window. The mode line also displays how many entries\nof each kind are held in the PO file. For example, the string\n'132t+3f+10u+2o' would tell the translator that the PO mode contains 132\ntranslated entries (*note Translated Entries::, 3 fuzzy entries (*note\nFuzzy Entries::), 10 untranslated entries (*note Untranslated Entries::)\nand 2 obsolete entries (*note Obsolete Entries::). Zero-coefficients\nitems are not shown. So, in this example, if the fuzzy entries were\nunfuzzied, the untranslated entries were translated and the obsolete\nentries were deleted, the mode line would merely display '145t' for the\ncounters.\n\nThe main PO commands are those which do not fit into the other\ncategories of subsequent sections. These allow for quitting PO mode or\nfor managing windows in special ways.\n\n''\nUndo last modification to the PO file ('po-undo').\n\n'Q'\nQuit processing and save the PO file ('po-quit').\n\n'q'\nQuit processing, possibly after confirmation\n('po-confirm-and-quit').\n\n'0'\nTemporary leave the PO file window ('po-other-window').\n\n'?'\n'h'\nShow help about PO mode ('po-help').\n\n'='\nGive some PO file statistics ('po-statistics').\n\n'V'\nBatch validate the format of the whole PO file ('po-validate').\n\nThe command '' ('po-undo') interfaces to the Emacs undo facility.\n*Note Undoing Changes: (emacs)Undo. Each time '' is typed,\nmodifications which the translator did to the PO file are undone a\nlittle more. For the purpose of undoing, each PO mode command is\natomic. This is especially true for the '' command: the whole\nedition made by using a single use of this command is undone at once,\neven if the edition itself implied several actions. However, while in\nthe editing window, one can undo the edition work quite parsimoniously.\n\nThe commands 'Q' ('po-quit') and 'q' ('po-confirm-and-quit') are used\nwhen the translator is done with the PO file. The former is a bit less\nverbose than the latter. If the file has been modified, it is saved to\ndisk first. In both cases, and prior to all this, the commands check if\nany untranslated messages remain in the PO file and, if so, the\ntranslator is asked if she really wants to leave off working with this\nPO file. This is the preferred way of getting rid of an Emacs PO file\nbuffer. Merely killing it through the usual command 'C-x k'\n('kill-buffer') is not the tidiest way to proceed.\n\nThe command '0' ('po-other-window') is another, softer way, to leave\nPO mode, temporarily. It just moves the cursor to some other Emacs\nwindow, and pops one if necessary. For example, if the translator just\ngot PO mode to show some source context in some other, she might\ndiscover some apparent bug in the program source that needs correction.\nThis command allows the translator to change sex, become a programmer,\nand have the cursor right into the window containing the program she (or\nrather he) wants to modify. By later getting the cursor back in the\nPO file window, or by asking Emacs to edit this file once again, PO mode\nis then recovered.\n\nThe command 'h' ('po-help') displays a summary of all available PO\nmode commands. The translator should then type any character to resume\nnormal PO mode operations. The command '?' has the same effect as 'h'.\n\nThe command '=' ('po-statistics') computes the total number of\nentries in the PO file, the ordinal of the current entry (counted from\n1), the number of untranslated entries, the number of obsolete entries,\nand displays all these numbers.\n\nThe command 'V' ('po-validate') launches 'msgfmt' in checking and\nverbose mode over the current PO file. This command first offers to\nsave the current PO file on disk. The 'msgfmt' tool, from GNU\n'gettext', has the purpose of creating a MO file out of a PO file, and\nPO mode uses the features of this program for checking the overall\nformat of a PO file, as well as all individual entries.\n\nThe program 'msgfmt' runs asynchronously with Emacs, so the\ntranslator regains control immediately while her PO file is being\nstudied. Error output is collected in the Emacs '*compilation*' buffer,\ndisplayed in another window. The regular Emacs command 'C-x`'\n('next-error'), as well as other usual compile commands, allow the\ntranslator to reposition quickly to the offending parts of the PO file.\nOnce the cursor is on the line in error, the translator may decide on\nany PO mode action which would help correcting the error.\n\nFile: gettext.info, Node: Entry Positioning, Next: Normalizing, Prev: Main PO Commands, Up: PO Mode\n\n\nThe cursor in a PO file window is almost always part of an entry.\nThe only exceptions are the special case when the cursor is after the\nlast entry in the file, or when the PO file is empty. The entry where\nthe cursor is found to be is said to be the current entry. Many PO mode\ncommands operate on the current entry, so moving the cursor does more\nthan allowing the translator to browse the PO file, this also selects on\nwhich entry commands operate.\n\nSome PO mode commands alter the position of the cursor in a\nspecialized way. A few of those special purpose positioning are\ndescribed here, the others are described in following sections (for a\ncomplete list try 'C-h m'):\n\n'.'\nRedisplay the current entry ('po-current-entry').\n\n'n'\nSelect the entry after the current one ('po-next-entry').\n\n'p'\nSelect the entry before the current one ('po-previous-entry').\n\n'<'\nSelect the first entry in the PO file ('po-first-entry').\n\n'>'\nSelect the last entry in the PO file ('po-last-entry').\n\n'm'\nRecord the location of the current entry for later use\n('po-push-location').\n\n'r'\nReturn to a previously saved entry location ('po-pop-location').\n\n'x'\nExchange the current entry location with the previously saved one\n('po-exchange-location').\n\nAny Emacs command able to reposition the cursor may be used to select\nthe current entry in PO mode, including commands which move by\ncharacters, lines, paragraphs, screens or pages, and search commands.\nHowever, there is a kind of standard way to display the current entry in\nPO mode, which usual Emacs commands moving the cursor do not especially\ntry to enforce. The command '.' ('po-current-entry') has the sole\npurpose of redisplaying the current entry properly, after the current\nentry has been changed by means external to PO mode, or the Emacs screen\notherwise altered.\n\nIt is yet to be decided if PO mode helps the translator, or otherwise\nirritates her, by forcing a rigid window disposition while she is doing\nher work. We originally had quite precise ideas about how windows\nshould behave, but on the other hand, anyone used to Emacs is often\nhappy to keep full control. Maybe a fixed window disposition might be\noffered as a PO mode option that the translator might activate or\ndeactivate at will, so it could be offered on an experimental basis. If\nnobody feels a real need for using it, or a compulsion for writing it,\nwe should drop this whole idea. The incentive for doing it should come\nfrom translators rather than programmers, as opinions from an\nexperienced translator are surely more worth to me than opinions from\nprogrammers thinking about how others should do translation.\n\nThe commands 'n' ('po-next-entry') and 'p' ('po-previous-entry') move\nthe cursor the entry following, or preceding, the current one. If 'n'\nis given while the cursor is on the last entry of the PO file, or if 'p'\nis given while the cursor is on the first entry, no move is done.\n\nThe commands '<' ('po-first-entry') and '>' ('po-last-entry') move\nthe cursor to the first entry, or last entry, of the PO file. When the\ncursor is located past the last entry in a PO file, most PO mode\ncommands will return an error saying 'After last entry'. Moreover, the\ncommands '<' and '>' have the special property of being able to work\neven when the cursor is not into some PO file entry, and one may use\nthem for nicely correcting this situation. But even these commands will\nfail on a truly empty PO file. There are development plans for the PO\nmode for it to interactively fill an empty PO file from sources. *Note\nMarking::.\n\nThe translator may decide, before working at the translation of a\nparticular entry, that she needs to browse the remainder of the PO file,\nmaybe for finding the terminology or phraseology used in related\nentries. She can of course use the standard Emacs idioms for saving the\ncurrent cursor location in some register, and use that register for\ngetting back, or else, use the location ring.\n\nPO mode offers another approach, by which cursor locations may be\nsaved onto a special stack. The command 'm' ('po-push-location') merely\nadds the location of current entry to the stack, pushing the already\nsaved locations under the new one. The command 'r' ('po-pop-location')\nconsumes the top stack element and repositions the cursor to the entry\nassociated with that top element. This position is then lost, for the\nnext 'r' will move the cursor to the previously saved location, and so\non until no locations remain on the stack.\n\nIf the translator wants the position to be kept on the location\nstack, maybe for taking a look at the entry associated with the top\nelement, then go elsewhere with the intent of getting back later, she\nought to use 'm' immediately after 'r'.\n\nThe command 'x' ('po-exchange-location') simultaneously repositions\nthe cursor to the entry associated with the top element of the stack of\nsaved locations, and replaces that top element with the location of the\ncurrent entry before the move. Consequently, repeating the 'x' command\ntoggles alternatively between two entries. For achieving this, the\ntranslator will position the cursor on the first entry, use 'm', then\nposition to the second entry, and merely use 'x' for making the switch.\n\nFile: gettext.info, Node: Normalizing, Next: Translated Entries, Prev: Entry Positioning, Up: PO Mode\n\n\nThere are many different ways for encoding a particular string into a\nPO file entry, because there are so many different ways to split and\nquote multi-line strings, and even, to represent special characters by\nbackslashed escaped sequences. Some features of PO mode rely on the\nability for PO mode to scan an already existing PO file for a particular\nstring encoded into the 'msgid' field of some entry. Even if PO mode\nhas internally all the built-in machinery for implementing this\nrecognition easily, doing it fast is technically difficult. To\nfacilitate a solution to this efficiency problem, we decided on a\ncanonical representation for strings.\n\nA conventional representation of strings in a PO file is currently\nunder discussion, and PO mode experiments with a canonical\nrepresentation. Having both 'xgettext' and PO mode converging towards a\nuniform way of representing equivalent strings would be useful, as the\ninternal normalization needed by PO mode could be automatically\nsatisfied when using 'xgettext' from GNU 'gettext'. An explicit PO mode\nnormalization should then be only necessary for PO files imported from\nelsewhere, or for when the convention itself evolves.\n\nSo, for achieving normalization of at least the strings of a given PO\nfile needing a canonical representation, the following PO mode command\nis available:\n\n'M-x po-normalize'\nTidy the whole PO file by making entries more uniform.\n\nThe special command 'M-x po-normalize', which has no associated keys,\nrevises all entries, ensuring that strings of both original and\ntranslated entries use uniform internal quoting in the PO file. It also\nremoves any crumb after the last entry. This command may be useful for\nPO files freshly imported from elsewhere, or if we ever improve on the\ncanonical quoting format we use. This canonical format is not only\nmeant for getting cleaner PO files, but also for greatly speeding up\n'msgid' string lookup for some other PO mode commands.\n\n'M-x po-normalize' presently makes three passes over the entries.\nThe first implements heuristics for converting PO files for GNU\n'gettext' 0.6 and earlier, in which 'msgid' and 'msgstr' fields were\nusing K&R style C string syntax for multi-line strings. These\nheuristics may fail for comments not related to obsolete entries and\nending with a backslash; they also depend on subsequent passes for\nfinalizing the proper commenting of continued lines for obsolete\nentries. This first pass might disappear once all oldish PO files would\nhave been adjusted. The second and third pass normalize all 'msgid' and\n'msgstr' strings respectively. They also clean out those trailing\nbackslashes used by XView's 'msgfmt' for continued lines.\n\nHaving such an explicit normalizing command allows for importing PO\nfiles from other sources, but also eases the evolution of the current\nconvention, evolution driven mostly by aesthetic concerns, as of now.\nIt is easy to make suggested adjustments at a later time, as the\nnormalizing command and eventually, other GNU 'gettext' tools should\ngreatly automate conformance. A description of the canonical string\nformat is given below, for the particular benefit of those not having\nEmacs handy, and who would nevertheless want to handcraft their PO files\nin nice ways.\n\nRight now, in PO mode, strings are single line or multi-line. A\nstring goes multi-line if and only if it has embedded newlines, that\nis, if it matches '[^\\n]\\n+[^\\n]'. So, we would have:\n\nmsgstr \"\\n\\nHello, world!\\n\\n\\n\"\n\nbut, replacing the space by a newline, this becomes:\n\nmsgstr \"\"\n\"\\n\"\n\"\\n\"\n\"Hello,\\n\"\n\"world!\\n\"\n\"\\n\"\n\"\\n\"\n\nWe are deliberately using a caricatural example, here, to make the\npoint clearer. Usually, multi-lines are not that bad looking. It is\nprobable that we will implement the following suggestion. We might lump\ntogether all initial newlines into the empty string, and also all\nnewlines introducing empty lines (that is, for N > 1, the N-1'th last\nnewlines would go together on a separate string), so making the previous\nexample appear:\n\nmsgstr \"\\n\\n\"\n\"Hello,\\n\"\n\"world!\\n\"\n\"\\n\\n\"\n\nThere are a few yet undecided little points about string\nnormalization, to be documented in this manual, once these questions\nsettle.\n\nFile: gettext.info, Node: Translated Entries, Next: Fuzzy Entries, Prev: Normalizing, Up: PO Mode\n\n\nEach PO file entry for which the 'msgstr' field has been filled with\na translation, and which is not marked as fuzzy (*note Fuzzy Entries::),\nis said to be a \"translated\" entry. Only translated entries will later\nbe compiled by GNU 'msgfmt' and become usable in programs. Other entry\ntypes will be excluded; translation will not occur for them.\n\nSome commands are more specifically related to translated entry\nprocessing.\n\n't'\nFind the next translated entry ('po-next-translated-entry').\n\n'T'\nFind the previous translated entry\n('po-previous-translated-entry').\n\nThe commands 't' ('po-next-translated-entry') and 'T'\n('po-previous-translated-entry') move forwards or backwards, chasing for\nan translated entry. If none is found, the search is extended and wraps\naround in the PO file buffer.\n\nTranslated entries usually result from the translator having edited\nin a translation for them, *note Modifying Translations::. However, if\nthe variable 'po-auto-fuzzy-on-edit' is not 'nil', the entry having\nreceived a new translation first becomes a fuzzy entry, which ought to\nbe later unfuzzied before becoming an official, genuine translated\nentry. *Note Fuzzy Entries::.\n\nFile: gettext.info, Node: Fuzzy Entries, Next: Untranslated Entries, Prev: Translated Entries, Up: PO Mode\n\n\nEach PO file entry may have a set of \"attributes\", which are\nqualities given a name and explicitly associated with the translation,\nusing a special system comment. One of these attributes has the name\n'fuzzy', and entries having this attribute are said to have a fuzzy\ntranslation. They are called fuzzy entries, for short.\n\nFuzzy entries, even if they account for translated entries for most\nother purposes, usually call for revision by the translator. Those may\nbe produced by applying the program 'msgmerge' to update an older\ntranslated PO files according to a new PO template file, when this tool\nhypothesises that some new 'msgid' has been modified only slightly out\nof an older one, and chooses to pair what it thinks to be the old\ntranslation for the new modified entry. The slight alteration in the\noriginal string (the 'msgid' string) should often be reflected in the\ntranslated string, and this requires the intervention of the translator.\nFor this reason, 'msgmerge' might mark some entries as being fuzzy.\n\nAlso, the translator may decide herself to mark an entry as fuzzy for\nher own convenience, when she wants to remember that the entry has to be\nlater revisited. So, some commands are more specifically related to\nfuzzy entry processing.\n\n'f'\nFind the next fuzzy entry ('po-next-fuzzy-entry').\n\n'F'\nFind the previous fuzzy entry ('po-previous-fuzzy-entry').\n\n''\nRemove the fuzzy attribute of the current entry ('po-unfuzzy').\n\nThe commands 'f' ('po-next-fuzzy-entry') and 'F'\n('po-previous-fuzzy-entry') move forwards or backwards, chasing for a\nfuzzy entry. If none is found, the search is extended and wraps around\nin the PO file buffer.\n\nThe command '' ('po-unfuzzy') removes the fuzzy attribute\nassociated with an entry, usually leaving it translated. Further, if\nthe variable 'po-auto-select-on-unfuzzy' has not the 'nil' value, the\n'' command will automatically chase for another interesting entry\nto work on. The initial value of 'po-auto-select-on-unfuzzy' is 'nil'.\n\nThe initial value of 'po-auto-fuzzy-on-edit' is 'nil'. However, if\nthe variable 'po-auto-fuzzy-on-edit' is set to 't', any entry edited\nthrough the '' command is marked fuzzy, as a way to ensure some\nkind of double check, later. In this case, the usual paradigm is that\nan entry becomes fuzzy (if not already) whenever the translator modifies\nit. If she is satisfied with the translation, she then uses '' to\npick another entry to work on, clearing the fuzzy attribute on the same\nblow. If she is not satisfied yet, she merely uses '' to chase\nanother entry, leaving the entry fuzzy.\n\nThe translator may also use the '' command ('po-fade-out-entry')\nover any translated entry to mark it as being fuzzy, when she wants to\neasily leave a trace she wants to later return working at this entry.\n\nAlso, when time comes to quit working on a PO file buffer with the\n'q' command, the translator is asked for confirmation, if fuzzy string\nstill exists.\n\nFile: gettext.info, Node: Untranslated Entries, Next: Obsolete Entries, Prev: Fuzzy Entries, Up: PO Mode\n\n\nWhen 'xgettext' originally creates a PO file, unless told otherwise,\nit initializes the 'msgid' field with the untranslated string, and\nleaves the 'msgstr' string to be empty. Such entries, having an empty\ntranslation, are said to be \"untranslated\" entries. Later, when the\nprogrammer slightly modifies some string right in the program, this\nchange is later reflected in the PO file by the appearance of a new\nuntranslated entry for the modified string.\n\nThe usual commands moving from entry to entry consider untranslated\nentries on the same level as active entries. Untranslated entries are\neasily recognizable by the fact they end with 'msgstr \"\"'.\n\nThe work of the translator might be (quite naively) seen as the\nprocess of seeking for an untranslated entry, editing a translation for\nit, and repeating these actions until no untranslated entries remain.\nSome commands are more specifically related to untranslated entry\nprocessing.\n\n'u'\nFind the next untranslated entry ('po-next-untranslated-entry').\n\n'U'\nFind the previous untranslated entry\n('po-previous-untransted-entry').\n\n'k'\nTurn the current entry into an untranslated one ('po-kill-msgstr').\n\nThe commands 'u' ('po-next-untranslated-entry') and 'U'\n('po-previous-untransted-entry') move forwards or backwards, chasing for\nan untranslated entry. If none is found, the search is extended and\nwraps around in the PO file buffer.\n\nAn entry can be turned back into an untranslated entry by merely\nemptying its translation, using the command 'k' ('po-kill-msgstr').\n*Note Modifying Translations::.\n\nAlso, when time comes to quit working on a PO file buffer with the\n'q' command, the translator is asked for confirmation, if some\nuntranslated string still exists.\n\nFile: gettext.info, Node: Obsolete Entries, Next: Modifying Translations, Prev: Untranslated Entries, Up: PO Mode\n\n\nBy \"obsolete\" PO file entries, we mean those entries which are\ncommented out, usually by 'msgmerge' when it found that the translation\nis not needed anymore by the package being localized.\n\nThe usual commands moving from entry to entry consider obsolete\nentries on the same level as active entries. Obsolete entries are\neasily recognizable by the fact that all their lines start with '#',\neven those lines containing 'msgid' or 'msgstr'.\n\nCommands exist for emptying the translation or reinitializing it to\nthe original untranslated string. Commands interfacing with the kill\nring may force some previously saved text into the translation. The\nuser may interactively edit the translation. All these commands may\napply to obsolete entries, carefully leaving the entry obsolete after\nthe fact.\n\nMoreover, some commands are more specifically related to obsolete\nentry processing.\n\n'o'\nFind the next obsolete entry ('po-next-obsolete-entry').\n\n'O'\nFind the previous obsolete entry ('po-previous-obsolete-entry').\n\n''\nMake an active entry obsolete, or zap out an obsolete entry\n('po-fade-out-entry').\n\nThe commands 'o' ('po-next-obsolete-entry') and 'O'\n('po-previous-obsolete-entry') move forwards or backwards, chasing for\nan obsolete entry. If none is found, the search is extended and wraps\naround in the PO file buffer.\n\nPO mode does not provide ways for un-commenting an obsolete entry and\nmaking it active, because this would reintroduce an original\nuntranslated string which does not correspond to any marked string in\nthe program sources. This goes with the philosophy of never introducing\nuseless 'msgid' values.\n\nHowever, it is possible to comment out an active entry, so making it\nobsolete. GNU 'gettext' utilities will later react to the disappearance\nof a translation by using the untranslated string. The command ''\n('po-fade-out-entry') pushes the current entry a little further towards\nannihilation. If the entry is active (it is a translated entry), then\nit is first made fuzzy. If it is already fuzzy, then the entry is\nmerely commented out, with confirmation. If the entry is already\nobsolete, then it is completely deleted from the PO file. It is easy to\nrecycle the translation so deleted into some other PO file entry,\nusually one which is untranslated. *Note Modifying Translations::.\n\nHere is a quite interesting problem to solve for later development of\nPO mode, for those nights you are not sleepy. The idea would be that PO\nmode might become bright enough, one of these days, to make good guesses\nat retrieving the most probable candidate, among all obsolete entries,\nfor initializing the translation of a newly appeared string. I think it\nmight be a quite hard problem to do this algorithmically, as we have to\ndevelop good and efficient measures of string similarity. Right now, PO\nmode completely lets the decision to the translator, when the time comes\nto find the adequate obsolete translation, it merely tries to provide\nhandy tools for helping her to do so.\n\nFile: gettext.info, Node: Modifying Translations, Next: Modifying Comments, Prev: Obsolete Entries, Up: PO Mode\n\n\nPO mode prevents direct modification of the PO file, by the usual\nmeans Emacs gives for altering a buffer's contents. By doing so, it\npretends helping the translator to avoid little clerical errors about\nthe overall file format, or the proper quoting of strings, as those\nerrors would be easily made. Other kinds of errors are still possible,\nbut some may be caught and diagnosed by the batch validation process,\nwhich the translator may always trigger by the 'V' command. For all\nother errors, the translator has to rely on her own judgment, and also\non the linguistic reports submitted to her by the users of the\ntranslated package, having the same mother tongue.\n\nWhen the time comes to create a translation, correct an error\ndiagnosed mechanically or reported by a user, the translators have to\nresort to using the following commands for modifying the translations.\n\n''\nInteractively edit the translation ('po-edit-msgstr').\n\n''\n'C-j'\nReinitialize the translation with the original, untranslated string\n('po-msgid-to-msgstr').\n\n'k'\nSave the translation on the kill ring, and delete it\n('po-kill-msgstr').\n\n'w'\nSave the translation on the kill ring, without deleting it\n('po-kill-ring-save-msgstr').\n\n'y'\nReplace the translation, taking the new from the kill ring\n('po-yank-msgstr').\n\nThe command '' ('po-edit-msgstr') opens a new Emacs window meant\nto edit in a new translation, or to modify an already existing\ntranslation. The new window contains a copy of the translation taken\nfrom the current PO file entry, all ready for edition, expunged of all\nquoting marks, fully modifiable and with the complete extent of Emacs\nmodifying commands. When the translator is done with her modifications,\nshe may use 'C-c C-c' to close the subedit window with the automatically\nrequoted results, or 'C-c C-k' to abort her modifications. *Note\nSubedit::, for more information.\n\nThe command '' ('po-msgid-to-msgstr') initializes, or\nreinitializes the translation with the original string. This command is\nnormally used when the translator wants to redo a fresh translation of\nthe original string, disregarding any previous work.\n\nIt is possible to arrange so, whenever editing an untranslated entry,\nthe '' command be automatically executed. If you set\n'po-auto-edit-with-msgid' to 't', the translation gets initialised with\nthe original string, in case none exists already. The default value for\n'po-auto-edit-with-msgid' is 'nil'.\n\nIn fact, whether it is best to start a translation with an empty\nstring, or rather with a copy of the original string, is a matter of\ntaste or habit. Sometimes, the source language and the target language\nare so different that is simply best to start writing on an empty page.\nAt other times, the source and target languages are so close that it\nwould be a waste to retype a number of words already being written in\nthe original string. A translator may also like having the original\nstring right under her eyes, as she will progressively overwrite the\noriginal text with the translation, even if this requires some extra\nediting work to get rid of the original.\n\nThe command 'k' ('po-kill-msgstr') merely empties the translation\nstring, so turning the entry into an untranslated one. But while doing\nso, its previous contents is put apart in a special place, known as the\nkill ring. The command 'w' ('po-kill-ring-save-msgstr') has also the\neffect of taking a copy of the translation onto the kill ring, but it\notherwise leaves the entry alone, and does not remove the translation\nfrom the entry. Both commands use exactly the Emacs kill ring, which is\nshared between buffers, and which is well known already to Emacs lovers.\n\nThe translator may use 'k' or 'w' many times in the course of her\nwork, as the kill ring may hold several saved translations. From the\nkill ring, strings may later be reinserted in various Emacs buffers. In\nparticular, the kill ring may be used for moving translation strings\nbetween different entries of a single PO file buffer, or if the\ntranslator is handling many such buffers at once, even between PO files.\n\nTo facilitate exchanges with buffers which are not in PO mode, the\ntranslation string put on the kill ring by the 'k' command is fully\nunquoted before being saved: external quotes are removed, multi-line\nstrings are concatenated, and backslash escaped sequences are turned\ninto their corresponding characters. In the special case of obsolete\nentries, the translation is also uncommented prior to saving.\n\nThe command 'y' ('po-yank-msgstr') completely replaces the\ntranslation of the current entry by a string taken from the kill ring.\nFollowing Emacs terminology, we then say that the replacement string is\n\"yanked\" into the PO file buffer. *Note (emacs)Yanking::. The first\ntime 'y' is used, the translation receives the value of the most recent\naddition to the kill ring. If 'y' is typed once again, immediately,\nwithout intervening keystrokes, the translation just inserted is taken\naway and replaced by the second most recent addition to the kill ring.\nBy repeating 'y' many times in a row, the translator may travel along\nthe kill ring for saved strings, until she finds the string she really\nwanted.\n\nWhen a string is yanked into a PO file entry, it is fully and\nautomatically requoted for complying with the format PO files should\nhave. Further, if the entry is obsolete, PO mode then appropriately\npush the inserted string inside comments. Once again, translators\nshould not burden themselves with quoting considerations besides, of\ncourse, the necessity of the translated string itself respective to the\nprogram using it.\n\nNote that 'k' or 'w' are not the only commands pushing strings on the\nkill ring, as almost any PO mode command replacing translation strings\n(or the translator comments) automatically saves the old string on the\nkill ring. The main exceptions to this general rule are the yanking\ncommands themselves.\n\nTo better illustrate the operation of killing and yanking, let's use\nan actual example, taken from a common situation. When the programmer\nslightly modifies some string right in the program, his change is later\nreflected in the PO file by the appearance of a new untranslated entry\nfor the modified string, and the fact that the entry translating the\noriginal or unmodified string becomes obsolete. In many cases, the\ntranslator might spare herself some work by retrieving the unmodified\ntranslation from the obsolete entry, then initializing the untranslated\nentry 'msgstr' field with this retrieved translation. Once this done,\nthe obsolete entry is not wanted anymore, and may be safely deleted.\n\nWhen the translator finds an untranslated entry and suspects that a\nslight variant of the translation exists, she immediately uses 'm' to\nmark the current entry location, then starts chasing obsolete entries\nwith 'o', hoping to find some translation corresponding to the\nunmodified string. Once found, she uses the '' command for\ndeleting the obsolete entry, knowing that '' also kills the\ntranslation, that is, pushes the translation on the kill ring. Then,\n'r' returns to the initial untranslated entry, and 'y' then yanks the\nsaved translation right into the 'msgstr' field. The translator is then\nfree to use '' for fine tuning the translation contents, and maybe\nto later use 'u', then 'm' again, for going on with the next\nuntranslated string.\n\nWhen some sequence of keys has to be typed over and over again, the\ntranslator may find it useful to become better acquainted with the Emacs\ncapability of learning these sequences and playing them back under\nrequest. *Note (emacs)Keyboard Macros::.\n\nFile: gettext.info, Node: Modifying Comments, Next: Subedit, Prev: Modifying Translations, Up: PO Mode\n\n\nAny translation work done seriously will raise many linguistic\ndifficulties, for which decisions have to be made, and the choices\nfurther documented. These documents may be saved within the PO file in\nform of translator comments, which the translator is free to create,\ndelete, or modify at will. These comments may be useful to herself when\nshe returns to this PO file after a while.\n\nComments not having whitespace after the initial '#', for example,\nthose beginning with '#.' or '#:', are not translator comments, they\nare exclusively created by other 'gettext' tools. So, the commands\nbelow will never alter such system added comments, they are not meant\nfor the translator to modify. *Note PO Files::.\n\nThe following commands are somewhat similar to those modifying\ntranslations, so the general indications given for those apply here.\n*Note Modifying Translations::.\n\n'#'\nInteractively edit the translator comments ('po-edit-comment').\n\n'K'\nSave the translator comments on the kill ring, and delete it\n('po-kill-comment').\n\n'W'\nSave the translator comments on the kill ring, without deleting it\n('po-kill-ring-save-comment').\n\n'Y'\nReplace the translator comments, taking the new from the kill ring\n('po-yank-comment').\n\nThese commands parallel PO mode commands for modifying the\ntranslation strings, and behave much the same way as they do, except\nthat they handle this part of PO file comments meant for translator\nusage, rather than the translation strings. So, if the descriptions\ngiven below are slightly succinct, it is because the full details have\nalready been given. *Note Modifying Translations::.\n\nThe command '#' ('po-edit-comment') opens a new Emacs window\ncontaining a copy of the translator comments on the current PO file\nentry. If there are no such comments, PO mode understands that the\ntranslator wants to add a comment to the entry, and she is presented\nwith an empty screen. Comment marks ('#') and the space following them\nare automatically removed before edition, and reinstated after. For\ntranslator comments pertaining to obsolete entries, the uncommenting and\nrecommenting operations are done twice. Once in the editing window, the\nkeys 'C-c C-c' allow the translator to tell she is finished with editing\nthe comment. *Note Subedit::, for further details.\n\nFunctions found on 'po-subedit-mode-hook', if any, are executed after\nthe string has been inserted in the edit buffer.\n\nThe command 'K' ('po-kill-comment') gets rid of all translator\ncomments, while saving those comments on the kill ring. The command 'W'\n('po-kill-ring-save-comment') takes a copy of the translator comments on\nthe kill ring, but leaves them undisturbed in the current entry. The\ncommand 'Y' ('po-yank-comment') completely replaces the translator\ncomments by a string taken at the front of the kill ring. When this\ncommand is immediately repeated, the comments just inserted are\nwithdrawn, and replaced by other strings taken along the kill ring.\n\nOn the kill ring, all strings have the same nature. There is no\ndistinction between translation strings and translator comments\nstrings. So, for example, let's presume the translator has just\nfinished editing a translation, and wants to create a new translator\ncomment to document why the previous translation was not good, just to\nremember what was the problem. Foreseeing that she will do that in her\ndocumentation, the translator may want to quote the previous translation\nin her translator comments. To do so, she may initialize the translator\ncomments with the previous translation, still at the head of the kill\nring. Because editing already pushed the previous translation on the\nkill ring, she merely has to type 'M-w' prior to '#', and the previous\ntranslation will be right there, all ready for being introduced by some\nexplanatory text.\n\nOn the other hand, presume there are some translator comments already\nand that the translator wants to add to those comments, instead of\nwholly replacing them. Then, she should edit the comment right away\nwith '#'. Once inside the editing window, she can use the regular Emacs\ncommands 'C-y' ('yank') and 'M-y' ('yank-pop') to get the previous\ntranslation where she likes.\n\nFile: gettext.info, Node: Subedit, Next: C Sources Context, Prev: Modifying Comments, Up: PO Mode\n\n\nThe PO subedit minor mode has a few peculiarities worth being\ndescribed in fuller detail. It installs a few commands over the usual\nediting set of Emacs, which are described below.\n\n'C-c C-c'\nComplete edition ('po-subedit-exit').\n\n'C-c C-k'\nAbort edition ('po-subedit-abort').\n\n'C-c C-a'\nConsult auxiliary PO files ('po-subedit-cycle-auxiliary').\n\nThe window's contents represents a translation for a given message,\nor a translator comment. The translator may modify this window to her\nheart's content. Once this is done, the command 'C-c C-c'\n('po-subedit-exit') may be used to return the edited translation into\nthe PO file, replacing the original translation, even if it moved out of\nsight or if buffers were switched.\n\nIf the translator becomes unsatisfied with her translation or\ncomment, to the extent she prefers keeping what was existent prior to\nthe '' or '#' command, she may use the command 'C-c C-k'\n('po-subedit-abort') to merely get rid of edition, while preserving the\noriginal translation or comment. Another way would be for her to exit\nnormally with 'C-c C-c', then type 'U' once for undoing the whole effect\nof last edition.\n\nThe command 'C-c C-a' ('po-subedit-cycle-auxiliary') allows for\nglancing through translations already achieved in other languages,\ndirectly while editing the current translation. This may be quite\nconvenient when the translator is fluent at many languages, but of\ncourse, only makes sense when such completed auxiliary PO files are\nalready available to her (*note Auxiliary::).\n\nFunctions found on 'po-subedit-mode-hook', if any, are executed after\nthe string has been inserted in the edit buffer.\n\nWhile editing her translation, the translator should pay attention to\nnot inserting unwanted '' (newline) characters at the end of the\ntranslated string if those are not meant to be there, or to removing\nsuch characters when they are required. Since these characters are not\nvisible in the editing buffer, they are easily introduced by mistake.\nTo help her, '' automatically puts the character '<' at the end of\nthe string being edited, but this '<' is not really part of the string.\nOn exiting the editing window with 'C-c C-c', PO mode automatically\nremoves such '<' and all whitespace added after it. If the translator\nadds characters after the terminating '<', it looses its delimiting\nproperty and integrally becomes part of the string. If she removes the\ndelimiting '<', then the edited string is taken as is, with all\ntrailing newlines, even if invisible. Also, if the translated string\nought to end itself with a genuine '<', then the delimiting '<' may not\nbe removed; so the string should appear, in the editing window, as\nending with two '<' in a row.\n\nWhen a translation (or a comment) is being edited, the translator may\nmove the cursor back into the PO file buffer and freely move to other\nentries, browsing at will. If, with an edition pending, the translator\nwanders in the PO file buffer, she may decide to start modifying another\nentry. Each entry being edited has its own subedit buffer. It is\npossible to simultaneously edit the translation and the comment of a\nsingle entry, or to edit entries in different PO files, all at once.\nTyping '' on a field already being edited merely resumes that\nparticular edit. Yet, the translator should better be comfortable at\nhandling many Emacs windows!\n\nPending subedits may be completed or aborted in any order, regardless\nof how or when they were started. When many subedits are pending and\nthe translator asks for quitting the PO file (with the 'q' command),\nsubedits are automatically resumed one at a time, so she may decide for\neach of them.\n\nFile: gettext.info, Node: C Sources Context, Next: Auxiliary, Prev: Subedit, Up: PO Mode\n\n\nPO mode is particularly powerful when used with PO files created\nthrough GNU 'gettext' utilities, as those utilities insert special\ncomments in the PO files they generate. Some of these special comments\nrelate the PO file entry to exactly where the untranslated string\nappears in the program sources.\n\nWhen the translator gets to an untranslated entry, she is fairly\noften faced with an original string which is not as informative as it\nnormally should be, being succinct, cryptic, or otherwise ambiguous.\nBefore choosing how to translate the string, she needs to understand\nbetter what the string really means and how tight the translation has to\nbe. Most of the time, when problems arise, the only way left to make\nher judgment is looking at the true program sources from where this\nstring originated, searching for surrounding comments the programmer\nmight have put in there, and looking around for helping clues of any\nkind.\n\nSurely, when looking at program sources, the translator will receive\nmore help if she is a fluent programmer. However, even if she is not\nversed in programming and feels a little lost in C code, the translator\nshould not be shy at taking a look, once in a while. It is most\nprobable that she will still be able to find some of the hints she\nneeds. She will learn quickly to not feel uncomfortable in program\ncode, paying more attention to programmer's comments, variable and\nfunction names (if he dared choosing them well), and overall\norganization, than to the program code itself.\n\nThe following commands are meant to help the translator at getting\nprogram source context for a PO file entry.\n\n's'\nResume the display of a program source context, or cycle through\nthem ('po-cycle-source-reference').\n\n'M-s'\nDisplay of a program source context selected by menu\n('po-select-source-reference').\n\n'S'\nAdd a directory to the search path for source files\n('po-consider-source-path').\n\n'M-S'\nDelete a directory from the search path for source files\n('po-ignore-source-path').\n\nThe commands 's' ('po-cycle-source-reference') and 'M-s'\n('po-select-source-reference') both open another window displaying some\nsource program file, and already positioned in such a way that it shows\nan actual use of the string to be translated. By doing so, the command\ngives source program context for the string. But if the entry has no\nsource context references, or if all references are unresolved along the\nsearch path for program sources, then the command diagnoses this as an\nerror.\n\nEven if 's' (or 'M-s') opens a new window, the cursor stays in the PO\nfile window. If the translator really wants to get into the program\nsource window, she ought to do it explicitly, maybe by using command\n'O'.\n\nWhen 's' is typed for the first time, or for a PO file entry which is\ndifferent of the last one used for getting source context, then the\ncommand reacts by giving the first context available for this entry, if\nany. If some context has already been recently displayed for the\ncurrent PO file entry, and the translator wandered off to do other\nthings, typing 's' again will merely resume, in another window, the\ncontext last displayed. In particular, if the translator moved the\ncursor away from the context in the source file, the command will bring\nthe cursor back to the context. By using 's' many times in a row, with\nno other commands intervening, PO mode will cycle to the next available\ncontexts for this particular entry, getting back to the first context\nonce the last has been shown.\n\nThe command 'M-s' behaves differently. Instead of cycling through\nreferences, it lets the translator choose a particular reference among\nmany, and displays that reference. It is best used with completion, if\nthe translator types '' immediately after 'M-s', in response to the\nquestion, she will be offered a menu of all possible references, as a\nreminder of which are the acceptable answers. This command is useful\nonly where there are really many contexts available for a single string\nto translate.\n\nProgram source files are usually found relative to where the PO file\nstands. As a special provision, when this fails, the file is also\nlooked for, but relative to the directory immediately above it. Those\ntwo cases take proper care of most PO files. However, it might happen\nthat a PO file has been moved, or is edited in a different place than\nits normal location. When this happens, the translator should tell PO\nmode in which directory normally sits the genuine PO file. Many such\ndirectories may be specified, and all together, they constitute what is\ncalled the \"search path\" for program sources. The command 'S'\n('po-consider-source-path') is used to interactively enter a new\ndirectory at the front of the search path, and the command 'M-S'\n('po-ignore-source-path') is used to select, with completion, one of the\ndirectories she does not want anymore on the search path.\n\nFile: gettext.info, Node: Auxiliary, Prev: C Sources Context, Up: PO Mode\n\n\nPO mode is able to help the knowledgeable translator, being fluent in\nmany languages, at taking advantage of translations already achieved in\nother languages she just happens to know. It provides these other\nlanguage translations as additional context for her own work. Moreover,\nit has features to ease the production of translations for many\nlanguages at once, for translators preferring to work in this way.\n\nAn \"auxiliary\" PO file is an existing PO file meant for the same\npackage the translator is working on, but targeted to a different mother\ntongue language. Commands exist for declaring and handling auxiliary PO\nfiles, and also for showing contexts for the entry under work.\n\nHere are the auxiliary file commands available in PO mode.\n\n'a'\nSeek auxiliary files for another translation for the same entry\n('po-cycle-auxiliary').\n\n'C-c C-a'\nSwitch to a particular auxiliary file ('po-select-auxiliary').\n\n'A'\nDeclare this PO file as an auxiliary file\n('po-consider-as-auxiliary').\n\n'M-A'\nRemove this PO file from the list of auxiliary files\n('po-ignore-as-auxiliary').\n\nCommand 'A' ('po-consider-as-auxiliary') adds the current PO file to\nthe list of auxiliary files, while command 'M-A'\n('po-ignore-as-auxiliary' just removes it.\n\nThe command 'a' ('po-cycle-auxiliary') seeks all auxiliary PO files,\nround-robin, searching for a translated entry in some other language\nhaving an 'msgid' field identical as the one for the current entry. The\nfound PO file, if any, takes the place of the current PO file in the\ndisplay (its window gets on top). Before doing so, the current PO file\nis also made into an auxiliary file, if not already. So, 'a' in this\nnewly displayed PO file will seek another PO file, and so on, so\nrepeating 'a' will eventually yield back the original PO file.\n\nThe command 'C-c C-a' ('po-select-auxiliary') asks the translator for\nher choice of a particular auxiliary file, with completion, and then\nswitches to that selected PO file. The command also checks if the\nselected file has an 'msgid' field identical as the one for the current\nentry, and if yes, this entry becomes current. Otherwise, the cursor of\nthe selected file is left undisturbed.\n\nFor all this to work fully, auxiliary PO files will have to be\nnormalized, in that way that 'msgid' fields should be written exactly\nthe same way. It is possible to write 'msgid' fields in various ways\nfor representing the same string, different writing would break the\nproper behaviour of the auxiliary file commands of PO mode. This is not\nexpected to be much a problem in practice, as most existing PO files\nhave their 'msgid' entries written by the same GNU 'gettext' tools.\n\nHowever, PO files initially created by PO mode itself, while marking\nstrings in source files, are normalised differently. So are PO files\nresulting of the 'M-x normalize' command. Until these discrepancies\nbetween PO mode and other GNU 'gettext' tools get fully resolved, the\ntranslator should stay aware of normalisation issues.\n\nFile: gettext.info, Node: Compendium, Prev: PO Mode, Up: Editing\n" }, { "name": "8.4 Using Translation Compendia", "content": "A \"compendium\" is a special PO file containing a set of translations\nrecurring in many different packages. The translator can use gettext\ntools to build a new compendium, to add entries to her compendium, and\nto initialize untranslated entries, or to update already translated\nentries, from translations kept in the compendium.\n\n* Menu:\n\n* Creating Compendia:: Merging translations for later use\n* Using Compendia:: Using older translations if they fit\n\nFile: gettext.info, Node: Creating Compendia, Next: Using Compendia, Up: Compendium\n\n\nBasically every PO file consisting of translated entries only can be\ndeclared as a valid compendium. Often the translator wants to have\nspecial compendia; let's consider two cases: 'concatenating PO files'\nand 'extracting a message subset from a PO file'.\n\n8.4.1.1 Concatenate PO Files\n............................\n\nTo concatenate several valid PO files into one compendium file you\ncan use 'msgcomm' or 'msgcat' (the latter preferred):\n\nmsgcat -o compendium.po file1.po file2.po\n\nBy default, 'msgcat' will accumulate divergent translations for the\nsame string. Those occurrences will be marked as 'fuzzy' and highly\nvisible decorated; calling 'msgcat' on 'file1.po':\n\n#: src/hello.c:200\n#, c-format\nmsgid \"Report bugs to <%s>.\\n\"\nmsgstr \"Comunicar `bugs' a <%s>.\\n\"\n\nand 'file2.po':\n\n#: src/bye.c:100\n#, c-format\nmsgid \"Report bugs to <%s>.\\n\"\nmsgstr \"Comunicar \\\"bugs\\\" a <%s>.\\n\"\n\nwill result in:\n\n#: src/hello.c:200 src/bye.c:100\n#, fuzzy, c-format\nmsgid \"Report bugs to <%s>.\\n\"\nmsgstr \"\"\n\"#-#-#-#-# file1.po #-#-#-#-#\\n\"\n\"Comunicar `bugs' a <%s>.\\n\"\n\"#-#-#-#-# file2.po #-#-#-#-#\\n\"\n\"Comunicar \\\"bugs\\\" a <%s>.\\n\"\n\nThe translator will have to resolve this \"conflict\" manually; she has to\ndecide whether the first or the second version is appropriate (or\nprovide a new translation), to delete the \"marker lines\", and finally to\nremove the 'fuzzy' mark.\n\nIf the translator knows in advance the first found translation of a\nmessage is always the best translation she can make use to the\n'--use-first' switch:\n\nmsgcat --use-first -o compendium.po file1.po file2.po\n\nA good compendium file must not contain 'fuzzy' or untranslated\nentries. If input files are \"dirty\" you must preprocess the input files\nor postprocess the result using 'msgattrib --translated --no-fuzzy'.\n\n8.4.1.2 Extract a Message Subset from a PO File\n...............................................\n\nNobody wants to translate the same messages again and again; thus you\nmay wish to have a compendium file containing 'getopt.c' messages.\n\nTo extract a message subset (e.g., all 'getopt.c' messages) from an\nexisting PO file into one compendium file you can use 'msggrep':\n\nmsggrep --location src/getopt.c -o compendium.po file.po\n\nFile: gettext.info, Node: Using Compendia, Prev: Creating Compendia, Up: Compendium\n\n\nYou can use a compendium file to initialize a translation from\nscratch or to update an already existing translation.\n\n8.4.2.1 Initialize a New Translation File\n.........................................\n\nSince a PO file with translations does not exist the translator can\nmerely use '/dev/null' to fake the \"old\" translation file.\n\nmsgmerge --compendium compendium.po -o file.po /dev/null file.pot\n\n8.4.2.2 Update an Existing Translation File\n...........................................\n\nConcatenate the compendium file(s) and the existing PO, merge the\nresult with the POT file and remove the obsolete entries (optional, here\ndone using 'msgattrib'):\n\nmsgcat --use-first -o update.po compendium1.po compendium2.po file.po\nmsgmerge update.po file.pot | msgattrib --no-obsolete > file.po\n\nFile: gettext.info, Node: Manipulating, Next: Binaries, Prev: Editing, Up: Top\n" } ] }, "9 Manipulating PO Files": { "content": "Sometimes it is necessary to manipulate PO files in a way that is\nbetter performed automatically than by hand. GNU 'gettext' includes a\ncomplete set of tools for this purpose.\n\nWhen merging two packages into a single package, the resulting POT\nfile will be the concatenation of the two packages' POT files. Thus the\nmaintainer must concatenate the two existing package translations into a\nsingle translation catalog, for each language. This is best performed\nusing 'msgcat'. It is then the translators' duty to deal with any\npossible conflicts that arose during the merge.\n\nWhen a translator takes over the translation job from another\ntranslator, but she uses a different character encoding in her locale,\nshe will convert the catalog to her character encoding. This is best\ndone through the 'msgconv' program.\n\nWhen a maintainer takes a source file with tagged messages from\nanother package, he should also take the existing translations for this\nsource file (and not let the translators do the same job twice). One\nway to do this is through 'msggrep', another is to create a POT file for\nthat source file and use 'msgmerge'.\n\nWhen a translator wants to adjust some translation catalog for a\nspecial dialect or orthography -- for example, German as written in\nSwitzerland versus German as written in Germany -- she needs to apply\nsome text processing to every message in the catalog. The tool for\ndoing this is 'msgfilter'.\n\nAnother use of 'msgfilter' is to produce approximately the POT file\nfor which a given PO file was made. This can be done through a filter\ncommand like 'msgfilter sed -e d | sed -e '/^# /d''. Note that the\noriginal POT file may have had different comments and different plural\nmessage counts, that's why it's better to use the original POT file if\navailable.\n\nWhen a translator wants to check her translations, for example\naccording to orthography rules or using a non-interactive spell checker,\nshe can do so using the 'msgexec' program.\n\nWhen third party tools create PO or POT files, sometimes duplicates\ncannot be avoided. But the GNU 'gettext' tools give an error when they\nencounter duplicate msgids in the same file and in the same domain. To\nmerge duplicates, the 'msguniq' program can be used.\n\n'msgcomm' is a more general tool for keeping or throwing away\nduplicates, occurring in different files.\n\n'msgcmp' can be used to check whether a translation catalog is\ncompletely translated.\n\n'msgattrib' can be used to select and extract only the fuzzy or\nuntranslated messages of a translation catalog.\n\n'msgen' is useful as a first step for preparing English translation\ncatalogs. It copies each message's msgid to its msgstr.\n\nFinally, for those applications where all these various programs are\nnot sufficient, a library 'libgettextpo' is provided that can be used to\nwrite other specialized programs that process PO files.\n\n* Menu:\n\n* msgcat Invocation:: Invoking the 'msgcat' Program\n* msgconv Invocation:: Invoking the 'msgconv' Program\n* msggrep Invocation:: Invoking the 'msggrep' Program\n* msgfilter Invocation:: Invoking the 'msgfilter' Program\n* msguniq Invocation:: Invoking the 'msguniq' Program\n* msgcomm Invocation:: Invoking the 'msgcomm' Program\n* msgcmp Invocation:: Invoking the 'msgcmp' Program\n* msgattrib Invocation:: Invoking the 'msgattrib' Program\n* msgen Invocation:: Invoking the 'msgen' Program\n* msgexec Invocation:: Invoking the 'msgexec' Program\n* Colorizing:: Highlighting parts of PO files\n* Other tools:: Other tools for manipulating PO files\n* libgettextpo:: Writing your own programs that process PO files\n\nFile: gettext.info, Node: msgcat Invocation, Next: msgconv Invocation, Up: Manipulating\n", "subsections": [ { "name": "9.1 Invoking the 'msgcat' Program", "content": "msgcat [OPTION] [INPUTFILE]...\n\nThe 'msgcat' program concatenates and merges the specified PO files.\nIt finds messages which are common to two or more of the specified PO\nfiles. By using the '--more-than' option, greater commonality may be\nrequested before messages are printed. Conversely, the '--less-than'\noption may be used to specify less commonality before messages are\nprinted (i.e. '--less-than=2' will only print the unique messages).\nTranslations, comments, extracted comments, and file positions will be\ncumulated, except that if '--use-first' is specified, they will be taken\nfrom the first PO file to define them.\n\nTo concatenate POT files, better use 'xgettext', not 'msgcat',\nbecause 'msgcat' would choke on the undefined charsets in the specified\nPOT files.\n\n\n'INPUTFILE ...'\nInput files.\n\n'-f FILE'\n'--files-from=FILE'\nRead the names of the input files from FILE instead of getting them\nfrom the command line.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting '.po'\nfile will be written relative to the current directory, though.\n\nIf INPUTFILE is '-', standard input is read.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified file.\n\nThe results are written to standard output if no output file is\nspecified or if it is '-'.\n\n\n'-< NUMBER'\n'--less-than=NUMBER'\nPrint messages with less than NUMBER definitions, defaults to\ninfinite if not set.\n\n'-> NUMBER'\n'--more-than=NUMBER'\nPrint messages with more than NUMBER definitions, defaults to 0 if\nnot set.\n\n'-u'\n'--unique'\nShorthand for '--less-than=2'. Requests that only unique messages\nbe printed.\n\n\n'-P'\n'--properties-input'\nAssume the input files are Java ResourceBundles in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input files are NeXTstep/GNUstep localized resource\nfiles in '.strings' syntax, not in PO file syntax.\n\n\n'-t'\n'--to-code=NAME'\nSpecify encoding for output.\n\n'--use-first'\nUse first available translation for each message. Don't merge\nseveral translations into one.\n\n'--lang=CATALOGNAME'\nSpecify the 'Language' field to be used in the header entry. See\n*note Header Entry:: for the meaning of this field. Note: The\n'Language-Team' and 'Plural-Forms' fields are left unchanged.\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'--force-po'\nAlways write an output file even if it contains no message.\n\n'-i'\n'--indent'\nWrite the .po file using indented style.\n\n'--no-location'\nDo not write '#: FILENAME:LINE' lines.\n\n'-n'\n'--add-location=TYPE'\nGenerate '#: FILENAME:LINE' lines (default).\n\nThe optional TYPE can be either 'full', 'file', or 'never'. If it\nis not given or 'full', it generates the lines with both file name\nand line number. If it is 'file', the line number part is omitted.\nIf it is 'never', it completely suppresses the lines (same as\n'--no-location').\n\n'--strict'\nWrite out a strict Uniforum conforming PO file. Note that this\nUniforum format should be avoided because it doesn't support the\nGNU extensions.\n\n'-p'\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n'-s'\n'--sort-output'\nGenerate sorted output. Note that using this option makes it much\nharder for the translator to understand each message's context.\n\n'-F'\n'--sort-by-file'\nSort output by file location.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\nFile: gettext.info, Node: msgconv Invocation, Next: msggrep Invocation, Prev: msgcat Invocation, Up: Manipulating\n" }, { "name": "9.2 Invoking the 'msgconv' Program", "content": "msgconv [OPTION] [INPUTFILE]\n\nThe 'msgconv' program converts a translation catalog to a different\ncharacter encoding.\n\n\n'INPUTFILE'\nInput PO file.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting '.po'\nfile will be written relative to the current directory, though.\n\nIf no INPUTFILE is given or if it is '-', standard input is read.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified file.\n\nThe results are written to standard output if no output file is\nspecified or if it is '-'.\n\n\n'-t'\n'--to-code=NAME'\nSpecify encoding for output.\n\nThe default encoding is the current locale's encoding.\n\n\n'-P'\n'--properties-input'\nAssume the input file is a Java ResourceBundle in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input file is a NeXTstep/GNUstep localized resource file\nin '.strings' syntax, not in PO file syntax.\n\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'--force-po'\nAlways write an output file even if it contains no message.\n\n'-i'\n'--indent'\nWrite the .po file using indented style.\n\n'--no-location'\nDo not write '#: FILENAME:LINE' lines.\n\n'-n'\n'--add-location=TYPE'\nGenerate '#: FILENAME:LINE' lines (default).\n\nThe optional TYPE can be either 'full', 'file', or 'never'. If it\nis not given or 'full', it generates the lines with both file name\nand line number. If it is 'file', the line number part is omitted.\nIf it is 'never', it completely suppresses the lines (same as\n'--no-location').\n\n'--strict'\nWrite out a strict Uniforum conforming PO file. Note that this\nUniforum format should be avoided because it doesn't support the\nGNU extensions.\n\n'-p'\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n'-s'\n'--sort-output'\nGenerate sorted output. Note that using this option makes it much\nharder for the translator to understand each message's context.\n\n'-F'\n'--sort-by-file'\nSort output by file location.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\nFile: gettext.info, Node: msggrep Invocation, Next: msgfilter Invocation, Prev: msgconv Invocation, Up: Manipulating\n" }, { "name": "9.3 Invoking the 'msggrep' Program", "content": "msggrep [OPTION] [INPUTFILE]\n\nThe 'msggrep' program extracts all messages of a translation catalog\nthat match a given pattern or belong to some given source files.\n\n\n'INPUTFILE'\nInput PO file.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting '.po'\nfile will be written relative to the current directory, though.\n\nIf no INPUTFILE is given or if it is '-', standard input is read.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified file.\n\nThe results are written to standard output if no output file is\nspecified or if it is '-'.\n\n\n[-N SOURCEFILE]... [-M DOMAINNAME]...\n[-J MSGCTXT-PATTERN] [-K MSGID-PATTERN] [-T MSGSTR-PATTERN]\n[-C COMMENT-PATTERN]\n\nA message is selected if\n* it comes from one of the specified source files,\n* or if it comes from one of the specified domains,\n* or if '-J' is given and its context (msgctxt) matches\nMSGCTXT-PATTERN,\n* or if '-K' is given and its key (msgid or msgidplural) matches\nMSGID-PATTERN,\n* or if '-T' is given and its translation (msgstr) matches\nMSGSTR-PATTERN,\n* or if '-C' is given and the translator's comment matches\nCOMMENT-PATTERN.\n\nWhen more than one selection criterion is specified, the set of\nselected messages is the union of the selected messages of each\ncriterion.\n\nMSGCTXT-PATTERN or MSGID-PATTERN or MSGSTR-PATTERN syntax:\n[-E | -F] [-e PATTERN | -f FILE]...\nPATTERNs are basic regular expressions by default, or extended\nregular expressions if -E is given, or fixed strings if -F is given.\n\n'-N SOURCEFILE'\n'--location=SOURCEFILE'\nSelect messages extracted from SOURCEFILE. SOURCEFILE can be\neither a literal file name or a wildcard pattern.\n\n'-M DOMAINNAME'\n'--domain=DOMAINNAME'\nSelect messages belonging to domain DOMAINNAME.\n\n'-J'\n'--msgctxt'\nStart of patterns for the msgctxt.\n\n'-K'\n'--msgid'\nStart of patterns for the msgid.\n\n'-T'\n'--msgstr'\nStart of patterns for the msgstr.\n\n'-C'\n'--comment'\nStart of patterns for the translator's comment.\n\n'-X'\n'--extracted-comment'\nStart of patterns for the extracted comments.\n\n'-E'\n'--extended-regexp'\nSpecify that PATTERN is an extended regular expression.\n\n'-F'\n'--fixed-strings'\nSpecify that PATTERN is a set of newline-separated strings.\n\n'-e PATTERN'\n'--regexp=PATTERN'\nUse PATTERN as a regular expression.\n\n'-f FILE'\n'--file=FILE'\nObtain PATTERN from FILE.\n\n'-i'\n'--ignore-case'\nIgnore case distinctions.\n\n'-v'\n'--invert-match'\nOutput only the messages that do not match any selection criterion,\ninstead of the messages that match a selection criterion.\n\n\n'-P'\n'--properties-input'\nAssume the input file is a Java ResourceBundle in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input file is a NeXTstep/GNUstep localized resource file\nin '.strings' syntax, not in PO file syntax.\n\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'--force-po'\nAlways write an output file even if it contains no message.\n\n'--indent'\nWrite the .po file using indented style.\n\n'--no-location'\nDo not write '#: FILENAME:LINE' lines.\n\n'-n'\n'--add-location=TYPE'\nGenerate '#: FILENAME:LINE' lines (default).\n\nThe optional TYPE can be either 'full', 'file', or 'never'. If it\nis not given or 'full', it generates the lines with both file name\nand line number. If it is 'file', the line number part is omitted.\nIf it is 'never', it completely suppresses the lines (same as\n'--no-location').\n\n'--strict'\nWrite out a strict Uniforum conforming PO file. Note that this\nUniforum format should be avoided because it doesn't support the\nGNU extensions.\n\n'-p'\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n'--sort-output'\nGenerate sorted output. Note that using this option makes it much\nharder for the translator to understand each message's context.\n\n'--sort-by-file'\nSort output by file location.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\n\nTo extract the messages that come from the source files\n'gnulib-lib/error.c' and 'gnulib-lib/getopt.c':\n\nmsggrep -N gnulib-lib/error.c -N gnulib-lib/getopt.c input.po\n\nTo extract the messages that contain the string \"Please specify\" in\nthe original string:\n\nmsggrep --msgid -F -e 'Please specify' input.po\n\nTo extract the messages that have a context specifier of either\n\"Menu>File\" or \"Menu>Edit\" or a submenu of them:\n\nmsggrep --msgctxt -E -e '^Menu>(File|Edit)' input.po\n\nTo extract the messages whose translation contains one of the strings\nin the file 'wordlist.txt':\n\nmsggrep --msgstr -F -f wordlist.txt input.po\n\nFile: gettext.info, Node: msgfilter Invocation, Next: msguniq Invocation, Prev: msggrep Invocation, Up: Manipulating\n" }, { "name": "9.4 Invoking the 'msgfilter' Program", "content": "msgfilter [OPTION] FILTER [FILTER-OPTION]\n\nThe 'msgfilter' program applies a filter to all translations of a\ntranslation catalog.\n\nDuring each FILTER invocation, the environment variable\n'MSGFILTERMSGID' is bound to the message's msgid, and the environment\nvariable 'MSGFILTERLOCATION' is bound to the location in the PO file of\nthe message. If the message has a context, the environment variable\n'MSGFILTERMSGCTXT' is bound to the message's msgctxt, otherwise it is\nunbound. If the message has a plural form, environment variable\n'MSGFILTERMSGIDPLURAL' is bound to the message's msgidplural and\n'MSGFILTERPLURALFORM' is bound to the order number of the plural\nactually processed (starting with 0), otherwise both are unbound. If\nthe message has a previous msgid (added by 'msgmerge'), environment\nvariable 'MSGFILTERPREVMSGCTXT' is bound to the message's previous\nmsgctxt, 'MSGFILTERPREVMSGID' is bound to the previous msgid, and\n'MSGFILTERPREVMSGIDPLURAL' is bound to the previous msgidplural.\n\n\n'-i INPUTFILE'\n'--input=INPUTFILE'\nInput PO file.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting '.po'\nfile will be written relative to the current directory, though.\n\nIf no INPUTFILE is given or if it is '-', standard input is read.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified file.\n\nThe results are written to standard output if no output file is\nspecified or if it is '-'.\n\n\nThe FILTER can be any program that reads a translation from standard\ninput and writes a modified translation to standard output. A\nfrequently used filter is 'sed'. A few particular built-in filters are\nalso recognized.\n\n'--newline'\nAdd newline at the end of each input line and also strip the ending\nnewline from the output line.\n\nNote: If the filter is not a built-in filter, you have to care about\nencodings: It is your responsibility to ensure that the FILTER can cope\nwith input encoded in the translation catalog's encoding. If the FILTER\nwants input in a particular encoding, you can in a first step convert\nthe translation catalog to that encoding using the 'msgconv' program,\nbefore invoking 'msgfilter'. If the FILTER wants input in the locale's\nencoding, but you want to avoid the locale's encoding, then you can\nfirst convert the translation catalog to UTF-8 using the 'msgconv'\nprogram and then make 'msgfilter' work in an UTF-8 locale, by using the\n'LCALL' environment variable.\n\nNote: Most translations in a translation catalog don't end with a\nnewline character. For this reason, unless the '--newline' option is\nused, it is important that the FILTER recognizes its last input line\neven if it ends without a newline, and that it doesn't add an undesired\ntrailing newline at the end. The 'sed' program on some platforms is\nknown to ignore the last line of input if it is not terminated with a\nnewline. You can use GNU 'sed' instead; it does not have this\nlimitation.\n\n\n'-e SCRIPT'\n'--expression=SCRIPT'\nAdd SCRIPT to the commands to be executed.\n\n'-f SCRIPTFILE'\n'--file=SCRIPTFILE'\nAdd the contents of SCRIPTFILE to the commands to be executed.\n\n'-n'\n'--quiet'\n'--silent'\nSuppress automatic printing of pattern space.\n\n\nThe filter 'recode-sr-latin' is recognized as a built-in filter. The\ncommand 'recode-sr-latin' converts Serbian text, written in the Cyrillic\nscript, to the Latin script. The command 'msgfilter recode-sr-latin'\napplies this conversion to the translations of a PO file. Thus, it can\nbe used to convert an 'sr.po' file to an 'sr@latin.po' file.\n\nThe filter 'quot' is recognized as a built-in filter. The command\n'msgfilter quot' converts any quotations surrounded by a pair of '\"',\n''', and '`'.\n\nThe filter 'boldquot' is recognized as a built-in filter. The\ncommand 'msgfilter boldquot' converts any quotations surrounded by a\npair of '\"', ''', and '`', also adding the VT100 escape sequences to the\ntext to decorate it as bold.\n\nThe use of built-in filters is not sensitive to the current locale's\nencoding. Moreover, when used with a built-in filter, 'msgfilter' can\nautomatically convert the message catalog to the UTF-8 encoding when\nneeded.\n\n\n'-P'\n'--properties-input'\nAssume the input file is a Java ResourceBundle in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input file is a NeXTstep/GNUstep localized resource file\nin '.strings' syntax, not in PO file syntax.\n\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'--force-po'\nAlways write an output file even if it contains no message.\n\n'--indent'\nWrite the .po file using indented style.\n\n'--keep-header'\nKeep the header entry, i.e. the message with 'msgid \"\"',\nunmodified, instead of filtering it. By default, the header entry\nis subject to filtering like any other message.\n\n'--no-location'\nDo not write '#: FILENAME:LINE' lines.\n\n'-n'\n'--add-location=TYPE'\nGenerate '#: FILENAME:LINE' lines (default).\n\nThe optional TYPE can be either 'full', 'file', or 'never'. If it\nis not given or 'full', it generates the lines with both file name\nand line number. If it is 'file', the line number part is omitted.\nIf it is 'never', it completely suppresses the lines (same as\n'--no-location').\n\n'--strict'\nWrite out a strict Uniforum conforming PO file. Note that this\nUniforum format should be avoided because it doesn't support the\nGNU extensions.\n\n'-p'\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n'-s'\n'--sort-output'\nGenerate sorted output. Note that using this option makes it much\nharder for the translator to understand each message's context.\n\n'-F'\n'--sort-by-file'\nSort output by file location.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\n\nTo convert German translations to Swiss orthography (in an UTF-8\nlocale):\n\nmsgconv -t UTF-8 de.po | msgfilter sed -e 's/ss/ss/g'\n\nTo convert Serbian translations in Cyrillic script to Latin script:\n\nmsgfilter recode-sr-latin < sr.po\n\nFile: gettext.info, Node: msguniq Invocation, Next: msgcomm Invocation, Prev: msgfilter Invocation, Up: Manipulating\n" }, { "name": "9.5 Invoking the 'msguniq' Program", "content": "msguniq [OPTION] [INPUTFILE]\n\nThe 'msguniq' program unifies duplicate translations in a translation\ncatalog. It finds duplicate translations of the same message ID. Such\nduplicates are invalid input for other programs like 'msgfmt',\n'msgmerge' or 'msgcat'. By default, duplicates are merged together.\nWhen using the '--repeated' option, only duplicates are output, and all\nother messages are discarded. Comments and extracted comments will be\ncumulated, except that if '--use-first' is specified, they will be taken\nfrom the first translation. File positions will be cumulated. When\nusing the '--unique' option, duplicates are discarded.\n\n\n'INPUTFILE'\nInput PO file.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting '.po'\nfile will be written relative to the current directory, though.\n\nIf no INPUTFILE is given or if it is '-', standard input is read.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified file.\n\nThe results are written to standard output if no output file is\nspecified or if it is '-'.\n\n\n'-d'\n'--repeated'\nPrint only duplicates.\n\n'-u'\n'--unique'\nPrint only unique messages, discard duplicates.\n\n\n'-P'\n'--properties-input'\nAssume the input file is a Java ResourceBundle in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input file is a NeXTstep/GNUstep localized resource file\nin '.strings' syntax, not in PO file syntax.\n\n\n'-t'\n'--to-code=NAME'\nSpecify encoding for output.\n\n'--use-first'\nUse first available translation for each message. Don't merge\nseveral translations into one.\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'--force-po'\nAlways write an output file even if it contains no message.\n\n'-i'\n'--indent'\nWrite the .po file using indented style.\n\n'--no-location'\nDo not write '#: FILENAME:LINE' lines.\n\n'-n'\n'--add-location=TYPE'\nGenerate '#: FILENAME:LINE' lines (default).\n\nThe optional TYPE can be either 'full', 'file', or 'never'. If it\nis not given or 'full', it generates the lines with both file name\nand line number. If it is 'file', the line number part is omitted.\nIf it is 'never', it completely suppresses the lines (same as\n'--no-location').\n\n'--strict'\nWrite out a strict Uniforum conforming PO file. Note that this\nUniforum format should be avoided because it doesn't support the\nGNU extensions.\n\n'-p'\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n'-s'\n'--sort-output'\nGenerate sorted output. Note that using this option makes it much\nharder for the translator to understand each message's context.\n\n'-F'\n'--sort-by-file'\nSort output by file location.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\nFile: gettext.info, Node: msgcomm Invocation, Next: msgcmp Invocation, Prev: msguniq Invocation, Up: Manipulating\n" }, { "name": "9.6 Invoking the 'msgcomm' Program", "content": "msgcomm [OPTION] [INPUTFILE]...\n\nThe 'msgcomm' program finds messages which are common to two or more\nof the specified PO files. By using the '--more-than' option, greater\ncommonality may be requested before messages are printed. Conversely,\nthe '--less-than' option may be used to specify less commonality before\nmessages are printed (i.e. '--less-than=2' will only print the unique\nmessages). Translations, comments and extracted comments will be\npreserved, but only from the first PO file to define them. File\npositions from all PO files will be cumulated.\n\n\n'INPUTFILE ...'\nInput files.\n\n'-f FILE'\n'--files-from=FILE'\nRead the names of the input files from FILE instead of getting them\nfrom the command line.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting '.po'\nfile will be written relative to the current directory, though.\n\nIf INPUTFILE is '-', standard input is read.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified file.\n\nThe results are written to standard output if no output file is\nspecified or if it is '-'.\n\n\n'-< NUMBER'\n'--less-than=NUMBER'\nPrint messages with less than NUMBER definitions, defaults to\ninfinite if not set.\n\n'-> NUMBER'\n'--more-than=NUMBER'\nPrint messages with more than NUMBER definitions, defaults to 1 if\nnot set.\n\n'-u'\n'--unique'\nShorthand for '--less-than=2'. Requests that only unique messages\nbe printed.\n\n\n'-P'\n'--properties-input'\nAssume the input files are Java ResourceBundles in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input files are NeXTstep/GNUstep localized resource\nfiles in '.strings' syntax, not in PO file syntax.\n\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'--force-po'\nAlways write an output file even if it contains no message.\n\n'-i'\n'--indent'\nWrite the .po file using indented style.\n\n'--no-location'\nDo not write '#: FILENAME:LINE' lines.\n\n'-n'\n'--add-location=TYPE'\nGenerate '#: FILENAME:LINE' lines (default).\n\nThe optional TYPE can be either 'full', 'file', or 'never'. If it\nis not given or 'full', it generates the lines with both file name\nand line number. If it is 'file', the line number part is omitted.\nIf it is 'never', it completely suppresses the lines (same as\n'--no-location').\n\n'--strict'\nWrite out a strict Uniforum conforming PO file. Note that this\nUniforum format should be avoided because it doesn't support the\nGNU extensions.\n\n'-p'\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n'-s'\n'--sort-output'\nGenerate sorted output. Note that using this option makes it much\nharder for the translator to understand each message's context.\n\n'-F'\n'--sort-by-file'\nSort output by file location.\n\n'--omit-header'\nDon't write header with 'msgid \"\"' entry.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\nFile: gettext.info, Node: msgcmp Invocation, Next: msgattrib Invocation, Prev: msgcomm Invocation, Up: Manipulating\n" }, { "name": "9.7 Invoking the 'msgcmp' Program", "content": "msgcmp [OPTION] DEF.po REF.pot\n\nThe 'msgcmp' program compares two Uniforum style .po files to check\nthat both contain the same set of msgid strings. The DEF.po file is an\nexisting PO file with the translations. The REF.pot file is the last\ncreated PO file, or a PO Template file (generally created by\n'xgettext'). This is useful for checking that you have translated each\nand every message in your program. Where an exact match cannot be\nfound, fuzzy matching is used to produce better diagnostics.\n\n\n'DEF.po'\nTranslations.\n\n'REF.pot'\nReferences to the sources.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories.\n\n\n'-m'\n'--multi-domain'\nApply REF.pot to each of the domains in DEF.po.\n\n'-N'\n'--no-fuzzy-matching'\nDo not use fuzzy matching when an exact match is not found. This\nmay speed up the operation considerably.\n\n'--use-fuzzy'\nConsider fuzzy messages in the DEF.po file like translated\nmessages. Note that using this option is usually wrong, because\nfuzzy messages are exactly those which have not been validated by a\nhuman translator.\n\n'--use-untranslated'\nConsider untranslated messages in the DEF.po file like translated\nmessages. Note that using this option is usually wrong.\n\n\n'-P'\n'--properties-input'\nAssume the input files are Java ResourceBundles in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input files are NeXTstep/GNUstep localized resource\nfiles in '.strings' syntax, not in PO file syntax.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\nFile: gettext.info, Node: msgattrib Invocation, Next: msgen Invocation, Prev: msgcmp Invocation, Up: Manipulating\n" }, { "name": "9.8 Invoking the 'msgattrib' Program", "content": "msgattrib [OPTION] [INPUTFILE]\n\nThe 'msgattrib' program filters the messages of a translation catalog\naccording to their attributes, and manipulates the attributes.\n\n\n'INPUTFILE'\nInput PO file.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting '.po'\nfile will be written relative to the current directory, though.\n\nIf no INPUTFILE is given or if it is '-', standard input is read.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified file.\n\nThe results are written to standard output if no output file is\nspecified or if it is '-'.\n\n\n'--translated'\nKeep translated messages, remove untranslated messages.\n\n'--untranslated'\nKeep untranslated messages, remove translated messages.\n\n'--no-fuzzy'\nRemove 'fuzzy' marked messages.\n\n'--only-fuzzy'\nKeep 'fuzzy' marked messages, remove all other messages.\n\n'--no-obsolete'\nRemove obsolete #~ messages.\n\n'--only-obsolete'\nKeep obsolete #~ messages, remove all other messages.\n\n\nAttributes are modified after the message selection/removal has been\nperformed. If the '--only-file' or '--ignore-file' option is specified,\nthe attribute modification is applied only to those messages that are\nlisted in the ONLY-FILE and not listed in the IGNORE-FILE.\n\n'--set-fuzzy'\nSet all messages 'fuzzy'.\n\n'--clear-fuzzy'\nSet all messages non-'fuzzy'.\n\n'--set-obsolete'\nSet all messages obsolete.\n\n'--clear-obsolete'\nSet all messages non-obsolete.\n\n'--previous'\nWhen setting 'fuzzy' mark, keep \"previous msgid\" of translated\nmessages.\n\n'--clear-previous'\nRemove the \"previous msgid\" ('#|') comments from all messages.\n\n'--empty'\nWhen removing 'fuzzy' mark, also set msgstr empty.\n\n'--only-file=FILE'\nLimit the attribute changes to entries that are listed in FILE.\nFILE should be a PO or POT file.\n\n'--ignore-file=FILE'\nLimit the attribute changes to entries that are not listed in FILE.\nFILE should be a PO or POT file.\n\n'--fuzzy'\nSynonym for '--only-fuzzy --clear-fuzzy': It keeps only the fuzzy\nmessages and removes their 'fuzzy' mark.\n\n'--obsolete'\nSynonym for '--only-obsolete --clear-obsolete': It keeps only the\nobsolete messages and makes them non-obsolete.\n\n\n'-P'\n'--properties-input'\nAssume the input file is a Java ResourceBundle in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input file is a NeXTstep/GNUstep localized resource file\nin '.strings' syntax, not in PO file syntax.\n\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'--force-po'\nAlways write an output file even if it contains no message.\n\n'-i'\n'--indent'\nWrite the .po file using indented style.\n\n'--no-location'\nDo not write '#: FILENAME:LINE' lines.\n\n'-n'\n'--add-location=TYPE'\nGenerate '#: FILENAME:LINE' lines (default).\n\nThe optional TYPE can be either 'full', 'file', or 'never'. If it\nis not given or 'full', it generates the lines with both file name\nand line number. If it is 'file', the line number part is omitted.\nIf it is 'never', it completely suppresses the lines (same as\n'--no-location').\n\n'--strict'\nWrite out a strict Uniforum conforming PO file. Note that this\nUniforum format should be avoided because it doesn't support the\nGNU extensions.\n\n'-p'\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n'-s'\n'--sort-output'\nGenerate sorted output. Note that using this option makes it much\nharder for the translator to understand each message's context.\n\n'-F'\n'--sort-by-file'\nSort output by file location.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\nFile: gettext.info, Node: msgen Invocation, Next: msgexec Invocation, Prev: msgattrib Invocation, Up: Manipulating\n" }, { "name": "9.9 Invoking the 'msgen' Program", "content": "msgen [OPTION] INPUTFILE\n\nThe 'msgen' program creates an English translation catalog. The\ninput file is the last created English PO file, or a PO Template file\n(generally created by xgettext). Untranslated entries are assigned a\ntranslation that is identical to the msgid.\n\nNote: 'msginit --no-translator --locale=en' performs a very similar\ntask. The main difference is that 'msginit' cares specially about the\nheader entry, whereas 'msgen' doesn't.\n\n\n'INPUTFILE'\nInput PO or POT file.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting '.po'\nfile will be written relative to the current directory, though.\n\nIf INPUTFILE is '-', standard input is read.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified file.\n\nThe results are written to standard output if no output file is\nspecified or if it is '-'.\n\n\n'-P'\n'--properties-input'\nAssume the input file is a Java ResourceBundle in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input file is a NeXTstep/GNUstep localized resource file\nin '.strings' syntax, not in PO file syntax.\n\n\n'--lang=CATALOGNAME'\nSpecify the 'Language' field to be used in the header entry. See\n*note Header Entry:: for the meaning of this field. Note: The\n'Language-Team' and 'Plural-Forms' fields are not set by this\noption.\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'--force-po'\nAlways write an output file even if it contains no message.\n\n'-i'\n'--indent'\nWrite the .po file using indented style.\n\n'--no-location'\nDo not write '#: FILENAME:LINE' lines.\n\n'-n'\n'--add-location=TYPE'\nGenerate '#: FILENAME:LINE' lines (default).\n\nThe optional TYPE can be either 'full', 'file', or 'never'. If it\nis not given or 'full', it generates the lines with both file name\nand line number. If it is 'file', the line number part is omitted.\nIf it is 'never', it completely suppresses the lines (same as\n'--no-location').\n\n'--strict'\nWrite out a strict Uniforum conforming PO file. Note that this\nUniforum format should be avoided because it doesn't support the\nGNU extensions.\n\n'-p'\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n'-s'\n'--sort-output'\nGenerate sorted output. Note that using this option makes it much\nharder for the translator to understand each message's context.\n\n'-F'\n'--sort-by-file'\nSort output by file location.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\nFile: gettext.info, Node: msgexec Invocation, Next: Colorizing, Prev: msgen Invocation, Up: Manipulating\n" }, { "name": "9.10 Invoking the 'msgexec' Program", "content": "msgexec [OPTION] COMMAND [COMMAND-OPTION]\n\nThe 'msgexec' program applies a command to all translations of a\ntranslation catalog. The COMMAND can be any program that reads a\ntranslation from standard input. It is invoked once for each\ntranslation. Its output becomes msgexec's output. 'msgexec''s return\ncode is the maximum return code across all invocations.\n\nA special builtin command called '0' outputs the translation,\nfollowed by a null byte. The output of 'msgexec 0' is suitable as input\nfor 'xargs -0'.\n\n'--newline'\nAdd newline at the end of each input line.\n\nDuring each COMMAND invocation, the environment variable\n'MSGEXECMSGID' is bound to the message's msgid, and the environment\nvariable 'MSGEXECLOCATION' is bound to the location in the PO file of\nthe message. If the message has a context, the environment variable\n'MSGEXECMSGCTXT' is bound to the message's msgctxt, otherwise it is\nunbound. If the message has a plural form, environment variable\n'MSGEXECMSGIDPLURAL' is bound to the message's msgidplural and\n'MSGEXECPLURALFORM' is bound to the order number of the plural\nactually processed (starting with 0), otherwise both are unbound. If\nthe message has a previous msgid (added by 'msgmerge'), environment\nvariable 'MSGEXECPREVMSGCTXT' is bound to the message's previous\nmsgctxt, 'MSGEXECPREVMSGID' is bound to the previous msgid, and\n'MSGEXECPREVMSGIDPLURAL' is bound to the previous msgidplural.\n\nNote: It is your responsibility to ensure that the COMMAND can cope\nwith input encoded in the translation catalog's encoding. If the\nCOMMAND wants input in a particular encoding, you can in a first step\nconvert the translation catalog to that encoding using the 'msgconv'\nprogram, before invoking 'msgexec'. If the COMMAND wants input in the\nlocale's encoding, but you want to avoid the locale's encoding, then you\ncan first convert the translation catalog to UTF-8 using the 'msgconv'\nprogram and then make 'msgexec' work in an UTF-8 locale, by using the\n'LCALL' environment variable.\n\n\n'-i INPUTFILE'\n'--input=INPUTFILE'\nInput PO file.\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting '.po'\nfile will be written relative to the current directory, though.\n\nIf no INPUTFILE is given or if it is '-', standard input is read.\n\n\n'-P'\n'--properties-input'\nAssume the input file is a Java ResourceBundle in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input file is a NeXTstep/GNUstep localized resource file\nin '.strings' syntax, not in PO file syntax.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\nFile: gettext.info, Node: Colorizing, Next: Other tools, Prev: msgexec Invocation, Up: Manipulating\n" }, { "name": "9.11 Highlighting parts of PO files", "content": "Translators are usually only interested in seeing the untranslated\nand fuzzy messages of a PO file. Also, when a message is set fuzzy\nbecause the msgid changed, they want to see the differences between the\nprevious msgid and the current one (especially if the msgid is long and\nonly few words in it have changed). Finally, it's always welcome to\nhighlight the different sections of a message in a PO file (comments,\nmsgid, msgstr, etc.).\n\nSuch highlighting is possible through the options '--color' and\n'--style'. They are supported by all the programs that produce a PO\nfile on standard output, such as 'msgcat', 'msgmerge', and 'msgunfmt'.\n\n* Menu:\n\n* The --color option:: Triggering colorized output\n* The TERM variable:: The environment variable 'TERM'\n* The --style option:: The '--style' option\n* Style rules:: Style rules for PO files\n* Customizing less:: Customizing 'less' for viewing PO files\n\nFile: gettext.info, Node: The --color option, Next: The TERM variable, Up: Colorizing\n\n\nThe '--color=WHEN' option specifies under which conditions colorized\noutput should be generated. The WHEN part can be one of the following:\n\n'always'\n'yes'\nThe output will be colorized.\n\n'never'\n'no'\nThe output will not be colorized.\n\n'auto'\n'tty'\nThe output will be colorized if the output device is a tty, i.e.\nwhen the output goes directly to a text screen or terminal emulator\nwindow.\n\n'html'\nThe output will be colorized and be in HTML format.\n\n'test'\nThis is a special value, understood only by the 'msgcat' program.\nIt is explained in the next section (*note The TERM variable::).\n\n'--color' is equivalent to '--color=yes'. The default is\n'--color=auto'.\n\nThus, a command like 'msgcat vi.po' will produce colorized output\nwhen called by itself in a command window. Whereas in a pipe, such as\n'msgcat vi.po | less -R', it will not produce colorized output. To get\ncolorized output in this situation nevertheless, use the command 'msgcat\n--color vi.po | less -R'.\n\nThe '--color=html' option will produce output that can be viewed in a\nbrowser. This can be useful, for example, for Indic languages, because\nthe renderic of Indic scripts in browsers is usually better than in\nterminal emulators.\n\nNote that the output produced with the '--color' option is not a\nvalid PO file in itself. It contains additional terminal-specific\nescape sequences or HTML tags. A PO file reader will give a syntax\nerror when confronted with such content. Except for the '--color=html'\ncase, you therefore normally don't need to save output produced with the\n'--color' option in a file.\n\nFile: gettext.info, Node: The TERM variable, Next: The --style option, Prev: The --color option, Up: Colorizing\n\n\nThe environment variable 'TERM' contains a identifier for the text\nwindow's capabilities. You can get a detailed list of these\ncababilities by using the 'infocmp' command, using 'man 5 terminfo' as a\nreference.\n\nWhen producing text with embedded color directives, 'msgcat' looks at\nthe 'TERM' variable. Text windows today typically support at least 8\ncolors. Often, however, the text window supports 16 or more colors,\neven though the 'TERM' variable is set to a identifier denoting only 8\nsupported colors. It can be worth setting the 'TERM' variable to a\ndifferent value in these cases:\n\n'xterm'\n'xterm' is in most cases built with support for 16 colors. It can\nalso be built with support for 88 or 256 colors (but not both).\nYou can try to set 'TERM' to either 'xterm-16color',\n'xterm-88color', or 'xterm-256color'.\n\n'rxvt'\n'rxvt' is often built with support for 16 colors. You can try to\nset 'TERM' to 'rxvt-16color'.\n\n'konsole'\n'konsole' too is often built with support for 16 colors. You can\ntry to set 'TERM' to 'konsole-16color' or 'xterm-16color'.\n\nAfter setting 'TERM', you can verify it by invoking 'msgcat\n--color=test' and seeing whether the output looks like a reasonable\ncolor map.\n\nFile: gettext.info, Node: The --style option, Next: Style rules, Prev: The TERM variable, Up: Colorizing\n\n\nThe '--style=STYLEFILE' option specifies the style file to use when\ncolorizing. It has an effect only when the '--color' option is\neffective.\n\nIf the '--style' option is not specified, the environment variable\n'POSTYLE' is considered. It is meant to point to the user's preferred\nstyle for PO files.\n\nThe default style file is\n'$prefix/share/gettext/styles/po-default.css', where '$prefix' is the\ninstallation location.\n\nA few style files are predefined:\n'po-vim.css'\nThis style imitates the look used by vim 7.\n\n'po-emacs-x.css'\nThis style imitates the look used by GNU Emacs 21 and 22 in an X11\nwindow.\n\n'po-emacs-xterm.css'\n'po-emacs-xterm16.css'\n'po-emacs-xterm256.css'\nThis style imitates the look used by GNU Emacs 22 in a terminal of\ntype 'xterm' (8 colors) or 'xterm-16color' (16 colors) or\n'xterm-256color' (256 colors), respectively.\n\nYou can use these styles without specifying a directory. They are\nactually located in '$prefix/share/gettext/styles/', where '$prefix' is\nthe installation location.\n\nYou can also design your own styles. This is described in the next\nsection.\n\nFile: gettext.info, Node: Style rules, Next: Customizing less, Prev: The --style option, Up: Colorizing\n\n\nThe same style file can be used for styling of a PO file, for\nterminal output and for HTML output. It is written in CSS (Cascading\nStyle Sheet) syntax. See for a\nformal definition of CSS. Many HTML authoring tutorials also contain\nexplanations of CSS.\n\nIn the case of HTML output, the style file is embedded in the HTML\noutput. In the case of text output, the style file is interpreted by\nthe 'msgcat' program. This means, in particular, that when '@import' is\nused with relative file names, the file names are\n\n- relative to the resulting HTML file, in the case of HTML output,\n\n- relative to the style sheet containing the '@import', in the case\nof text output. (Actually, '@import's are not yet supported in\nthis case, due to a limitation in 'libcroco'.)\n\nCSS rules are built up from selectors and declarations. The\ndeclarations specify graphical properties; the selectors specify when\nthey apply.\n\nIn PO files, the following simple selectors (based on \"CSS classes\",\nsee the CSS2 spec, section 5.8.3) are supported.\n\n* Selectors that apply to entire messages:\n\n'.header'\nThis matches the header entry of a PO file.\n\n'.translated'\nThis matches a translated message.\n\n'.untranslated'\nThis matches an untranslated message (i.e. a message with\nempty translation).\n\n'.fuzzy'\nThis matches a fuzzy message (i.e. a message which has a\ntranslation that needs review by the translator).\n\n'.obsolete'\nThis matches an obsolete message (i.e. a message that was\ntranslated but is not needed by the current POT file any\nmore).\n\n* Selectors that apply to parts of a message in PO syntax. Recall\nthe general structure of a message in PO syntax:\n\nWHITE-SPACE\n# TRANSLATOR-COMMENTS\n#. EXTRACTED-COMMENTS\n#: REFERENCE...\n#, FLAG...\n#| msgid PREVIOUS-UNTRANSLATED-STRING\nmsgid UNTRANSLATED-STRING\nmsgstr TRANSLATED-STRING\n\n'.comment'\nThis matches all comments (translator comments, extracted\ncomments, source file reference comments, flag comments,\nprevious message comments, as well as the entire obsolete\nmessages).\n\n'.translator-comment'\nThis matches the translator comments.\n\n'.extracted-comment'\nThis matches the extracted comments, i.e. the comments placed\nby the programmer at the attention of the translator.\n\n'.reference-comment'\nThis matches the source file reference comments (entire\nlines).\n\n'.reference'\nThis matches the individual source file references inside the\nsource file reference comment lines.\n\n'.flag-comment'\nThis matches the flag comment lines (entire lines).\n\n'.flag'\nThis matches the individual flags inside flag comment lines.\n\n'.fuzzy-flag'\nThis matches the 'fuzzy' flag inside flag comment lines.\n\n'.previous-comment'\nThis matches the comments containing the previous untranslated\nstring (entire lines).\n\n'.previous'\nThis matches the previous untranslated string including the\nstring delimiters, the associated keywords ('msgid' etc.) and\nthe spaces between them.\n\n'.msgid'\nThis matches the untranslated string including the string\ndelimiters, the associated keywords ('msgid' etc.) and the\nspaces between them.\n\n'.msgstr'\nThis matches the translated string including the string\ndelimiters, the associated keywords ('msgstr' etc.) and the\nspaces between them.\n\n'.keyword'\nThis matches the keywords ('msgid', 'msgstr', etc.).\n\n'.string'\nThis matches strings, including the string delimiters (double\nquotes).\n\n* Selectors that apply to parts of strings:\n\n'.text'\nThis matches the entire contents of a string (excluding the\nstring delimiters, i.e. the double quotes).\n\n'.escape-sequence'\nThis matches an escape sequence (starting with a backslash).\n\n'.format-directive'\nThis matches a format string directive (starting with a '%'\nsign in the case of most programming languages, with a '{' in\nthe case of 'java-format' and 'csharp-format', with a '~' in\nthe case of 'lisp-format' and 'scheme-format', or with '$' in\nthe case of 'sh-format').\n\n'.invalid-format-directive'\nThis matches an invalid format string directive.\n\n'.added'\nIn an untranslated string, this matches a part of the string\nthat was not present in the previous untranslated string.\n(Not yet implemented in this release.)\n\n'.changed'\nIn an untranslated string or in a previous untranslated\nstring, this matches a part of the string that is changed or\nreplaced. (Not yet implemented in this release.)\n\n'.removed'\nIn a previous untranslated string, this matches a part of the\nstring that is not present in the current untranslated string.\n(Not yet implemented in this release.)\n\nThese selectors can be combined to hierarchical selectors. For\nexample,\n\n.msgstr .invalid-format-directive { color: red; }\n\nwill highlight the invalid format directives in the translated strings.\n\nIn text mode, pseudo-classes (CSS2 spec, section 5.11) and\npseudo-elements (CSS2 spec, section 5.12) are not supported.\n\nThe declarations in HTML mode are not limited; any graphical\nattribute supported by the browsers can be used.\n\nThe declarations in text mode are limited to the following\nproperties. Other properties will be silently ignored.\n\n'color' (CSS2 spec, section 14.1)\n'background-color' (CSS2 spec, section 14.2.1)\nThese properties is supported. Colors will be adjusted to match\nthe terminal's capabilities. Note that many terminals support only\n8 colors.\n\n'font-weight' (CSS2 spec, section 15.2.3)\nThis property is supported, but most terminals can only render two\ndifferent weights: 'normal' and 'bold'. Values >= 600 are rendered\nas 'bold'.\n\n'font-style' (CSS2 spec, section 15.2.3)\nThis property is supported. The values 'italic' and 'oblique' are\nrendered the same way.\n\n'text-decoration' (CSS2 spec, section 16.3.1)\nThis property is supported, limited to the values 'none' and\n'underline'.\n\nFile: gettext.info, Node: Customizing less, Prev: Style rules, Up: Colorizing\n\n\nThe 'less' program is a popular text file browser for use in a text\nscreen or terminal emulator. It also supports text with embedded escape\nsequences for colors and text decorations.\n\nYou can use 'less' to view a PO file like this (assuming an UTF-8\nenvironment):\n\nmsgcat --to-code=UTF-8 --color xyz.po | less -R\n\nYou can simplify this to this simple command:\n\nless xyz.po\n\nafter these three preparations:\n\n1. Add the options '-R' and '-f' to the 'LESS' environment variable.\nIn sh shells:\n$ LESS=\"$LESS -R -f\"\n$ export LESS\n\n2. If your system does not already have the 'lessopen.sh' and\n'lessclose.sh' scripts, create them and set the 'LESSOPEN' and\n'LESSCLOSE' environment variables, as indicated in the manual page\n('man less').\n\n3. Add to 'lessopen.sh' a piece of script that recognizes PO files\nthrough their file extension and invokes 'msgcat' on them,\nproducing a temporary file. Like this:\n\ncase \"$1\" in\n*.po)\ntmpfile=`mktemp \"${TMPDIR-/tmp}/less.XXXXXX\"`\nmsgcat --to-code=UTF-8 --color \"$1\" > \"$tmpfile\"\necho \"$tmpfile\"\nexit 0\n;;\nesac\n\nFile: gettext.info, Node: Other tools, Next: libgettextpo, Prev: Colorizing, Up: Manipulating\n" }, { "name": "9.12 Other tools for manipulating PO files", "content": "The \"Pology\" package is a Free Software package for manipulating PO\nfiles. It features, in particular:\n\n* Examination and in-place modification of collections of PO files.\n* Format-aware diffing and patching of PO files.\n* Handling of version-control branches.\n* Fine-grained asynchronous review workflow.\n* Custom translation validation.\n* Language and project specific support.\n\nIts home page is at .\n\nFile: gettext.info, Node: libgettextpo, Prev: Other tools, Up: Manipulating\n" }, { "name": "9.13 Writing your own programs that process PO files", "content": "For the tasks for which a combination of 'msgattrib', 'msgcat' etc.\nis not sufficient, a set of C functions is provided in a library, to\nmake it possible to process PO files in your own programs. When you use\nthis library, you don't need to write routines to parse the PO file;\ninstead, you retrieve a pointer in memory to each of messages contained\nin the PO file. Functions for writing those memory structures to a file\nafter working with them are provided too.\n\nThe functions are declared in the header file '', and\nare defined in a library called 'libgettextpo'.\n\n* Menu:\n\n* Error Handling:: Error handling functions\n* pofilet API:: File management\n* pomessageiteratort API:: Message iteration\n* pomessaget API:: The basic units of the file\n* PO Header Entry API:: Meta information of the file\n* pofilepost API:: References to the sources\n* Format Type API:: Supported format types\n* Checking API:: Enforcing constraints\n\nThe following example shows code how these functions can be used.\nError handling code is omitted, as its implementation is delegated to\nthe user provided functions.\n\nstruct poxerrorhandler handler =\n{\n.xerror = ...,\n.xerror2 = ...\n};\nconst char *filename = ...;\n/* Read the file into memory. */\npofilet file = pofileread (filename, &handler);\n\n{\nconst char * const *domains = pofiledomains (file);\nconst char * const *domainp;\n\n/* Iterate the domains contained in the file. */\nfor (domainp = domains; *domainp; domainp++)\n{\npomessaget *message;\nconst char *domain = *domainp;\npomessageiteratort iterator = pomessageiterator (file, domain);\n\n/* Iterate each message inside the domain. */\nwhile ((message = ponextmessage (iterator)) != NULL)\n{\n/* Read data from the message ... */\nconst char *msgid = pomessagemsgid (message);\nconst char *msgstr = pomessagemsgstr (message);\n\n...\n\n/* Modify its contents ... */\nif (performsometests (msgid, msgstr))\npomessagesetfuzzy (message, 1);\n\n...\n}\n/* Always release returned pomessageiteratort. */\npomessageiteratorfree (iterator);\n}\n\n/* Write back the result. */\npofilet result = pofilewrite (file, filename, &handler);\n}\n\n/* Always release the returned pofilet. */\npofilefree (file);\n\nFile: gettext.info, Node: Error Handling, Next: pofilet API, Up: libgettextpo\n\n\nError management is performed through callbacks provided by the user\nof the library. They are provided through a parameter with the\nfollowing type:\n\n-- Data Type: struct poxerrorhandler\nIts pointer is defined as 'poxerrorhandlert'. Contains two\nfields, 'xerror' and 'xerror2', with the following function\nsignatures.\n\n-- Function: void xerror (int SEVERITY, pomessaget MESSAGE,\nconst char *FILENAME, sizet LINENO, sizet COLUMN,\nint MULTILINEP, const char *MESSAGETEXT)\n\nThis function is called to signal a problem of the given SEVERITY.\nIt must not return if SEVERITY is 'POSEVERITYFATALERROR'.\n\nMESSAGETEXT is the problem description. When MULTILINEP is true,\nit can contain multiple lines of text, each terminated with a\nnewline, otherwise a single line.\n\nMESSAGE and/or FILENAME and LINENO indicate where the problem\noccurred:\n\n* If FILENAME is 'NULL', FILENAME and LINENO and COLUMN should\nbe ignored.\n\n* If LINENO is '(sizet)(-1)', LINENO and COLUMN should be\nignored.\n\n* If COLUMN is '(sizet)(-1)', it should be ignored.\n\n-- Function: void xerror2 (int SEVERITY, pomessaget MESSAGE1,\nconst char *FILENAME1, sizet LINENO1, sizet COLUMN1,\nint MULTILINEP1, const char *MESSAGETEXT1,\npomessaget MESSAGE2, const char *FILENAME2, sizet LINENO2,\nsizet COLUMN2, int MULTILINEP2, const char *MESSAGETEXT2)\n\nThis function is called to signal a problem of the given SEVERITY\nthat refers to two messages. It must not return if SEVERITY is\n'POSEVERITYFATALERROR'.\n\nIt is similar to two calls to xerror. If possible, an ellipsis can\nbe appended to MESSAGETEXT1 and prepended to MESSAGETEXT2.\n\nFile: gettext.info, Node: pofilet API, Next: pomessageiteratort API, Prev: Error Handling, Up: libgettextpo\n\n\n-- Data Type: pofilet\nThis is a pointer type that refers to the contents of a PO file,\nafter it has been read into memory.\n\n-- Function: pofilet pofilecreate ()\nThe 'pofilecreate' function creates an empty PO file\nrepresentation in memory.\n\n-- Function: pofilet pofileread (const char *FILENAME,\nstruct poxerrorhandler *HANDLER)\nThe 'pofileread' function reads a PO file into memory. The file\nname is given as argument. The return value is a handle to the PO\nfile's contents, valid until 'pofilefree' is called on it. In\ncase of error, the functions from HANDLER are called to signal it.\n\nThis function is exported as 'pofilereadv3' at ABI level, but is\ndefined as 'pofileread' in C code after the inclusion of\n''.\n\n-- Function: pofilet pofilewrite (pofilet FILE,\nconst char *FILENAME, struct poxerrorhandler *HANDLER)\nThe 'pofilewrite' function writes the contents of the memory\nstructure FILE the FILENAME given. The return value is FILE after\na successful operation. In case of error, the functions from\nHANDLER are called to signal it.\n\nThis function is exported as 'pofilewritev2' at ABI level, but\nis defined as 'pofilewrite' in C code after the inclusion of\n''.\n\n-- Function: void pofilefree (pofilet FILE)\nThe 'pofilefree' function frees a PO file's contents from memory,\nincluding all messages that are only implicitly accessible through\niterators.\n\n-- Function: const char * const * pofiledomains (pofilet FILE)\nThe 'pofiledomains' function returns the domains for which the\ngiven PO file has messages. The return value is a 'NULL'\nterminated array which is valid as long as the FILE handle is\nvalid. For PO files which contain no 'domain' directive, the\nreturn value contains only one domain, namely the default domain\n'\"messages\"'.\n\nFile: gettext.info, Node: pomessageiteratort API, Next: pomessaget API, Prev: pofilet API, Up: libgettextpo\n\n\n-- Data Type: pomessageiteratort\nThis is a pointer type that refers to an iterator that produces a\nsequence of messages.\n\n-- Function: pomessageiteratort pomessageiterator (pofilet FILE,\nconst char *DOMAIN)\nThe 'pomessageiterator' returns an iterator that will produce the\nmessages of FILE that belong to the given DOMAIN. If DOMAIN is\n'NULL', the default domain is used instead. To list the messages,\nuse the function 'ponextmessage' repeatedly.\n\n-- Function: void pomessageiteratorfree\n(pomessageiteratort ITERATOR)\nThe 'pomessageiteratorfree' function frees an iterator\npreviously allocated through the 'pomessageiterator' function.\n\n-- Function: pomessaget ponextmessage\n(pomessageiteratort ITERATOR)\nThe 'ponextmessage' function returns the next message from\nITERATOR and advances the iterator. It returns 'NULL' when the\niterator has reached the end of its message list.\n\nFile: gettext.info, Node: pomessaget API, Next: PO Header Entry API, Prev: pomessageiteratort API, Up: libgettextpo\n\n\n-- Data Type: pomessaget\nThis is a pointer type that refers to a message of a PO file,\nincluding its translation.\n\n-- Function: pomessaget pomessagecreate (void)\nReturns a freshly constructed message. To finish initializing the\nmessage, you must set the 'msgid' and 'msgstr'. It must be\ninserted into a file to manage its memory, as there is no\n'pomessagefree' available to the user of the library.\n\nThe following functions access details of a 'pomessaget'. Recall\nthat the results are valid as long as the FILE handle is valid.\n\n-- Function: const char * pomessagemsgctxt (pomessaget MESSAGE)\nThe 'pomessagemsgctxt' function returns the 'msgctxt', the\ncontext of MESSAGE. Returns 'NULL' for a message not restricted to\na context.\n\n-- Function: void pomessagesetmsgctxt (pomessaget MESSAGE,\nconst char *MSGCTXT)\nThe 'pomessagesetmsgctxt' function changes the 'msgctxt', the\ncontext of the message, to the value provided through MSGCTXT. The\nvalue 'NULL' removes the restriction.\n\n-- Function: const char * pomessagemsgid (pomessaget MESSAGE)\nThe 'pomessagemsgid' function returns the 'msgid' (untranslated\nEnglish string) of MESSAGE. This is guaranteed to be non-'NULL'.\n\n-- Function: void pomessagesetmsgid (pomessaget MESSAGE,\nconst char *MSGID)\nThe 'pomessagesetmsgid' function changes the 'msgid'\n(untranslated English string) of MESSAGE to the value provided\nthrough MSGID, a non-'NULL' string.\n\n-- Function: const char * pomessagemsgidplural\n(pomessaget MESSAGE)\nThe 'pomessagemsgidplural' function returns the 'msgidplural'\n(untranslated English plural string) of MESSAGE, a message with\nplurals, or 'NULL' for a message without plural.\n\n-- Function: void pomessagesetmsgidplural (pomessaget MESSAGE,\nconst char *MSGIDPLURAL)\nThe 'pomessagesetmsgidplural' function changes the\n'msgidplural' (untranslated English plural string) of a message to\nthe value provided through MSGIDPLURAL, or removes the plurals if\n'NULL' is provided as MSGIDPLURAL.\n\n-- Function: const char * pomessagemsgstr (pomessaget MESSAGE)\nThe 'pomessagemsgstr' function returns the 'msgstr' (translation)\nof MESSAGE. For an untranslated message, the return value is an\nempty string.\n\n-- Function: void pomessagesetmsgstr (pomessaget MESSAGE,\nconst char *MSGSTR)\nThe 'pomessagesetmsgstr' function changes the 'msgstr'\n(translation) of MESSAGE to the value provided through MSGSTR, a\nnon-'NULL' string.\n\n-- Function: const char * pomessagemsgstrplural\n(pomessaget MESSAGE, int INDEX)\nThe 'pomessagemsgstrplural' function returns the 'msgstr[INDEX]'\nof MESSAGE, a message with plurals, or 'NULL' when the INDEX is out\nof range or for a message without plural.\n\n-- Function: void pomessagesetmsgstrplural (pomessaget MESSAGE,\nint INDEX, const char *MSGSTRPLURAL)\nThe 'pomessagesetmsgstrplural' function changes the\n'msgstr[INDEX]' of MESSAGE, a message with plurals, to the value\nprovided through MSGSTRPLURAL. MESSAGE must be a message with\nplurals. Use 'NULL' as the value of MSGSTRPLURAL with INDEX\npointing to the last element to reduce the number of plural forms.\n\n-- Function: const char * pomessagecomments (pomessaget MESSAGE)\nThe 'pomessagecomments' function returns the comments of MESSAGE,\na multiline string, ending in a newline, or a non-'NULL' empty\nstring.\n\n-- Function: void pomessagesetcomments (pomessaget MESSAGE,\nconst char *COMMENTS)\nThe 'pomessagesetcomments' function changes the comments of\nMESSAGE to the value COMMENTS, a multiline string, ending in a\nnewline, or a non-'NULL' empty string.\n\n-- Function: const char * pomessageextractedcomments\n(pomessaget MESSAGE)\nThe 'pomessageextractedcomments' function returns the extracted\ncomments of MESSAGE, a multiline string, ending in a newline, or a\nnon-'NULL' empty string.\n\n-- Function: void pomessagesetextractedcomments\n(pomessaget MESSAGE, const char *EXTRACTEDCOMMENTS)\nThe 'pomessagesetextractedcomments' function changes the\ncomments of MESSAGE to the value EXTRACTEDCOMMENTS, a multiline\nstring, ending in a newline, or a non-'NULL' empty string.\n\n-- Function: const char * pomessageprevmsgctxt\n(pomessaget MESSAGE)\nThe 'pomessageprevmsgctxt' function returns the previous\n'msgctxt', the previous context of MESSAGE. Return 'NULL' for a\nmessage that does not have a previous context.\n\n-- Function: void pomessagesetprevmsgctxt (pomessaget MESSAGE,\nconst char *PREVMSGCTXT)\nThe 'pomessagesetprevmsgctxt' function changes the previous\n'msgctxt', the context of the message, to the value provided\nthrough PREVMSGCTXT. The value 'NULL' removes the stored previous\nmsgctxt.\n\n-- Function: const char * pomessageprevmsgid (pomessaget MESSAGE)\nThe 'pomessageprevmsgid' function returns the previous 'msgid'\n(untranslated English string) of MESSAGE, or 'NULL' if there is no\nprevious 'msgid' stored.\n\n-- Function: void pomessagesetprevmsgid (pomessaget MESSAGE,\nconst char *PREVMSGID)\nThe 'pomessagesetprevmsgid' function changes the previous\n'msgid' (untranslated English string) of MESSAGE to the value\nprovided through PREVMSGID, or removes the message when it is\n'NULL'.\n\n-- Function: const char * pomessageprevmsgidplural\n(pomessaget MESSAGE)\nThe 'pomessageprevmsgidplural' function returns the previous\n'msgidplural' (untranslated English plural string) of MESSAGE, a\nmessage with plurals, or 'NULL' for a message without plural\nwithout any stored previous 'msgidplural'.\n\n-- Function: void pomessagesetprevmsgidplural\n(pomessaget MESSAGE, const char *PREVMSGIDPLURAL)\nThe 'pomessagesetprevmsgidplural' function changes the\nprevious 'msgidplural' (untranslated English plural string) of a\nmessage to the value provided through PREVMSGIDPLURAL, or removes\nthe stored previous 'msgidplural' if 'NULL' is provided as\nPREVMSGIDPLURAL.\n\n-- Function: int pomessageisobsolete (pomessaget MESSAGE)\nThe 'pomessageisobsolete' function returns true when MESSAGE is\nmarked as obsolete.\n\n-- Function: void pomessagesetobsolete (pomessaget MESSAGE,\nint OBSOLETE)\nThe 'pomessagesetobsolete' function changes the obsolete mark of\nMESSAGE.\n\n-- Function: int pomessageisfuzzy (pomessaget MESSAGE)\nThe 'pomessageisfuzzy' function returns true when MESSAGE is\nmarked as fuzzy.\n\n-- Function: void pomessagesetfuzzy (pomessaget MESSAGE,\nint FUZZY)\nThe 'pomessagesetfuzzy' function changes the fuzzy mark of\nMESSAGE.\n\n-- Function: int pomessageisformat (pomessaget MESSAGE,\nconst char *FORMATTYPE)\nThe 'pomessageisformat' function returns true when the message\nis marked as being a format string of FORMATTYPE.\n\n-- Function: void pomessagesetformat (pomessaget MESSAGE,\nconst char *FORMATTYPE, int VALUE)\nThe 'pomessagesetfuzzy' function changes the format mark of the\nmessage for the FORMATTYPE provided.\n\n-- Function: int pomessageisrange (pomessaget MESSAGE, int *MINP,\nint *MAXP)\nThe 'pomessageisrange' function returns true when the message\nhas a numeric range set, and stores the minimum and maximum value\nin the locations pointed by MINP and MAXP respectively.\n\n-- Function: void pomessagesetrange (pomessaget MESSAGE, int MIN,\nint MAX)\nThe 'pomessagesetrange' function changes the numeric range of\nthe message. MIN and MAX must be non-negative, with MIN < MAX.\nUse MIN and MAX with value '-1' to remove the numeric range of\nMESSAGE.\n\nFile: gettext.info, Node: PO Header Entry API, Next: pofilepost API, Prev: pomessaget API, Up: libgettextpo\n\n\nThe following functions provide an interface to extract and\nmanipulate the header entry (*note Header Entry::) from a file loaded in\nmemory. The meta information must be written back into the domain\nmessage with the empty string as 'msgid'.\n\n-- Function: const char * pofiledomainheader (pofilet FILE,\nconst char *DOMAIN)\nReturns the header entry of a domain from FILE, a PO file loaded in\nmemory. The value 'NULL' provided as DOMAIN denotes the default\ndomain. Returns 'NULL' if there is no header entry.\n\n-- Function: char * poheaderfield (const char *HEADER,\nconst char *FIELD)\nReturns the value of FIELD in the HEADER entry. The return value\nis either a freshly allocated string, to be freed by the caller, or\n'NULL'.\n\n-- Function: char * poheadersetfield (const char *HEADER,\nconst char *FIELD, const char *VALUE)\nReturns a freshly allocated string which contains the entry from\nHEADER with FIELD set to VALUE. The field is added if necessary.\n\nFile: gettext.info, Node: pofilepost API, Next: Format Type API, Prev: PO Header Entry API, Up: libgettextpo\n\n\n-- Data Type: pofilepost\nThis is a pointer type that refers to a string's position within a\nsource file.\n\nThe following functions provide an interface to extract and\nmanipulate these references.\n\n-- Function: pofilepost pomessagefilepos (pomessaget MESSAGE,\nint INDEX)\nReturns the file reference in position INDEX from the message. If\nINDEX is out of range, returns 'NULL'.\n\n-- Function: void pomessageremovefilepos (pomessaget MESSAGE,\nint INDEX)\nRemoves the file reference in position INDEX from the message. It\nmoves all references following INDEX one position backwards.\n\n-- Function: void pomessageaddfilepos (pomessaget MESSAGE,\nconst char *FILE, sizet STARTLINE)\nAdds a reference to the string from FILE starting at STARTLINE, if\nit is not already present for the message. The value\n'(sizet)(-1)' for STARTLINE denotes that the line number is not\navailable.\n\nFile: gettext.info, Node: Format Type API, Next: Checking API, Prev: pofilepost API, Up: libgettextpo\n\n\n-- Function: const char * const * poformatlist (void)\nReturns a 'NULL' terminated array of the supported format types.\n\n-- Function: const char * poformatprettyname\n(const char *FORMATTYPE)\nReturns the pretty name associated with FORMATTYPE. For example,\nit returns \"C#\" when FORMATTYPE is \"csharpformat\". Return 'NULL'\nif FORMATTYPE is not a supported format type.\n\nFile: gettext.info, Node: Checking API, Prev: Format Type API, Up: libgettextpo\n\n\n-- Function: void pofilecheckall (pofilet FILE,\npoxerrorhandlert HANDLER)\nTests whether the entire FILE is valid, like 'msgfmt' does it. If\nit is invalid, passes the reasons to HANDLER.\n\n-- Function: void pomessagecheckall (pomessaget MESSAGE,\npomessageiteratort ITERATOR, poxerrorhandlert HANDLER)\nTests MESSAGE, to be inserted at ITERATOR in a PO file in memory,\nlike 'msgfmt' does it. If it is invalid, passes the reasons to\nHANDLER. ITERATOR is not modified by this call; it only specifies\nthe file and the domain.\n\n-- Function: void pomessagecheckformat (pomessaget MESSAGE,\npoxerrorhandlert HANDLER)\nTests whether the message translation from MESSAGE is a valid\nformat string if the message is marked as being a format string.\nIf it is invalid, passes the reasons to HANDLER.\n\nThis function is exported as 'pomessagecheckformatv2' at ABI\nlevel, but is defined as 'pomessagecheckformat' in C code after\nthe inclusion of ''.\n\nFile: gettext.info, Node: Binaries, Next: Programmers, Prev: Manipulating, Up: Top\n" } ] }, "10 Producing Binary MO Files": { "content": "* Menu:\n\n* msgfmt Invocation:: Invoking the 'msgfmt' Program\n* msgunfmt Invocation:: Invoking the 'msgunfmt' Program\n* MO Files:: The Format of GNU MO Files\n\nFile: gettext.info, Node: msgfmt Invocation, Next: msgunfmt Invocation, Up: Binaries\n", "subsections": [ { "name": "10.1 Invoking the 'msgfmt' Program", "content": "msgfmt [OPTION] FILENAME.po ...\n\nThe 'msgfmt' programs generates a binary message catalog from a\ntextual translation description.\n\n\n'FILENAME.po ...'\n\n'-D DIRECTORY'\n'--directory=DIRECTORY'\nAdd DIRECTORY to the list of directories. Source files are\nsearched relative to this list of directories. The resulting\nbinary file will be written relative to the current directory,\nthough.\n\nIf an input file is '-', standard input is read.\n\n\n'-j'\n'--java'\nJava mode: generate a Java 'ResourceBundle' class.\n\n'--java2'\nLike -java, and assume Java2 (JDK 1.2 or higher).\n\n'--csharp'\nC# mode: generate a .NET .dll file containing a subclass of\n'GettextResourceSet'.\n\n'--csharp-resources'\nC# resources mode: generate a .NET '.resources' file.\n\n'--tcl'\nTcl mode: generate a tcl/msgcat '.msg' file.\n\n'--qt'\nQt mode: generate a Qt '.qm' file.\n\n'--desktop'\nDesktop Entry mode: generate a '.desktop' file.\n\n'--xml'\nXML mode: generate an XML file.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified file.\n\n'--strict'\nDirect the program to work strictly following the Uniforum/Sun\nimplementation. Currently this only affects the naming of the\noutput file. If this option is not given the name of the output\nfile is the same as the domain name. If the strict Uniforum mode\nis enabled the suffix '.mo' is added to the file name if it is not\nalready present.\n\nWe find this behaviour of Sun's implementation rather silly and so\nby default this mode is not selected.\n\nIf the output FILE is '-', output is written to standard output.\n\n\n'-r RESOURCE'\n'--resource=RESOURCE'\nSpecify the resource name.\n\n'-l LOCALE'\n'--locale=LOCALE'\nSpecify the locale name, either a language specification of the\nform LL or a combined language and country specification of the\nform LLCC.\n\n'-d DIRECTORY'\nSpecify the base directory of classes directory hierarchy.\n\n'--source'\nProduce a .java source file, instead of a compiled .class file.\n\nThe class name is determined by appending the locale name to the\nresource name, separated with an underscore. The '-d' option is\nmandatory. The class is written under the specified directory.\n\n\n'-r RESOURCE'\n'--resource=RESOURCE'\nSpecify the resource name.\n\n'-l LOCALE'\n'--locale=LOCALE'\nSpecify the locale name, either a language specification of the\nform LL or a combined language and country specification of the\nform LLCC.\n\n'-d DIRECTORY'\nSpecify the base directory for locale dependent '.dll' files.\n\nThe '-l' and '-d' options are mandatory. The '.dll' file is written\nin a subdirectory of the specified directory whose name depends on the\nlocale.\n\n\n'-l LOCALE'\n'--locale=LOCALE'\nSpecify the locale name, either a language specification of the\nform LL or a combined language and country specification of the\nform LLCC.\n\n'-d DIRECTORY'\nSpecify the base directory of '.msg' message catalogs.\n\nThe '-l' and '-d' options are mandatory. The '.msg' file is written\nin the specified directory.\n\n\n'--template=TEMPLATE'\nSpecify a .desktop file used as a template.\n\n'-k[KEYWORDSPEC]'\n'--keyword[=KEYWORDSPEC]'\nSpecify KEYWORDSPEC as an additional keyword to be looked for.\nWithout a KEYWORDSPEC, the option means to not use default\nkeywords.\n\n'-l LOCALE'\n'--locale=LOCALE'\nSpecify the locale name, either a language specification of the\nform LL or a combined language and country specification of the\nform LLCC.\n\n'-d DIRECTORY'\nSpecify the directory where PO files are read. The directory must\ncontain the 'LINGUAS' file.\n\nTo generate a '.desktop' file for a single locale, you can use it as\nfollows.\n\nmsgfmt --desktop --template=TEMPLATE --locale=LOCALE \\\n-o FILE FILENAME.po ...\n\nmsgfmt provides a special \"bulk\" operation mode to process multiple\n'.po' files at a time.\n\nmsgfmt --desktop --template=TEMPLATE -d DIRECTORY -o FILE\n\nmsgfmt first reads the 'LINGUAS' file under DIRECTORY, and then\nprocesses all '.po' files listed there. You can also limit the locales\nto a subset, through the 'LINGUAS' environment variable.\n\nFor either operation modes, the '-o' and '--template' options are\nmandatory.\n\n\n'--template=TEMPLATE'\nSpecify an XML file used as a template.\n\n'-L NAME'\n'--language=NAME'\nSpecifies the language of the input files.\n\n'-l LOCALE'\n'--locale=LOCALE'\nSpecify the locale name, either a language specification of the\nform LL or a combined language and country specification of the\nform LLCC.\n\n'-d DIRECTORY'\nSpecify the base directory of '.po' message catalogs.\n\nTo generate an XML file for a single locale, you can use it as\nfollows.\n\nmsgfmt --xml --template=TEMPLATE --locale=LOCALE \\\n-o FILE FILENAME.po ...\n\nmsgfmt provides a special \"bulk\" operation mode to process multiple\n'.po' files at a time.\n\nmsgfmt --xml --template=TEMPLATE -d DIRECTORY -o FILE\n\nmsgfmt first reads the 'LINGUAS' file under DIRECTORY, and then\nprocesses all '.po' files listed there. You can also limit the locales\nto a subset, through the 'LINGUAS' environment variable.\n\nFor either operation modes, the '-o' and '--template' options are\nmandatory.\n\n\n'-P'\n'--properties-input'\nAssume the input files are Java ResourceBundles in Java\n'.properties' syntax, not in PO file syntax.\n\n'--stringtable-input'\nAssume the input files are NeXTstep/GNUstep localized resource\nfiles in '.strings' syntax, not in PO file syntax.\n\n\n'-c'\n'--check'\nPerform all the checks implied by '--check-format',\n'--check-header', '--check-domain'.\n\n'--check-format'\nCheck language dependent format strings.\n\nIf the string represents a format string used in a 'printf'-like\nfunction both strings should have the same number of '%' format\nspecifiers, with matching types. If the flag 'c-format' or\n'possible-c-format' appears in the special comment <#,> for this\nentry a check is performed. For example, the check will diagnose\nusing '%.*s' against '%s', or '%d' against '%s', or '%d' against\n'%x'. It can even handle positional parameters.\n\nNormally the 'xgettext' program automatically decides whether a\nstring is a format string or not. This algorithm is not perfect,\nthough. It might regard a string as a format string though it is\nnot used in a 'printf'-like function and so 'msgfmt' might report\nerrors where there are none.\n\nTo solve this problem the programmer can dictate the decision to\nthe 'xgettext' program (*note c-format::). The translator should\nnot consider removing the flag from the <#,> line. This \"fix\"\nwould be reversed again as soon as 'msgmerge' is called the next\ntime.\n\n'--check-header'\nVerify presence and contents of the header entry. *Note Header\nEntry::, for a description of the various fields in the header\nentry.\n\n'--check-domain'\nCheck for conflicts between domain directives and the\n'--output-file' option\n\n'-C'\n'--check-compatibility'\nCheck that GNU msgfmt behaves like X/Open msgfmt. This will give\nan error when attempting to use the GNU extensions.\n\n'--check-accelerators[=CHAR]'\nCheck presence of keyboard accelerators for menu items. This is\nbased on the convention used in some GUIs that a keyboard\naccelerator in a menu item string is designated by an immediately\npreceding '&' character. Sometimes a keyboard accelerator is also\ncalled \"keyboard mnemonic\". This check verifies that if the\nuntranslated string has exactly one '&' character, the translated\nstring has exactly one '&' as well. If this option is given with a\nCHAR argument, this CHAR should be a non-alphanumeric character and\nis used as keyboard accelerator mark instead of '&'.\n\n'-f'\n'--use-fuzzy'\nUse fuzzy entries in output. Note that using this option is\nusually wrong, because fuzzy messages are exactly those which have\nnot been validated by a human translator.\n\n\n'-a NUMBER'\n'--alignment=NUMBER'\nAlign strings to NUMBER bytes (default: 1).\n\n'--endianness=BYTEORDER'\nWrite out 32-bit numbers in the given byte order. The possible\nvalues are 'big' and 'little'. The default is 'little'.\n\nMO files of any endianness can be used on any platform. When a MO\nfile has an endianness other than the platform's one, the 32-bit\nnumbers from the MO file are swapped at runtime. The performance\nimpact is negligible.\n\nThis option can be useful to produce MO files that are optimized\nfor one platform.\n\n'--no-hash'\nDon't include a hash table in the binary file. Lookup will be more\nexpensive at run time (binary search instead of hash table lookup).\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\n'--statistics'\nPrint statistics about translations. When the option '--verbose'\nis used in combination with '--statistics', the input file name is\nprinted in front of the statistics line.\n\n'-v'\n'--verbose'\nIncrease verbosity level.\n\nFile: gettext.info, Node: msgunfmt Invocation, Next: MO Files, Prev: msgfmt Invocation, Up: Binaries\n" }, { "name": "10.2 Invoking the 'msgunfmt' Program", "content": "msgunfmt [OPTION] [FILE]...\n\nThe 'msgunfmt' program converts a binary message catalog to a\nUniforum style .po file.\n\n\n'-j'\n'--java'\nJava mode: input is a Java 'ResourceBundle' class.\n\n'--csharp'\nC# mode: input is a .NET .dll file containing a subclass of\n'GettextResourceSet'.\n\n'--csharp-resources'\nC# resources mode: input is a .NET '.resources' file.\n\n'--tcl'\nTcl mode: input is a tcl/msgcat '.msg' file.\n\n\n'FILE ...'\nInput .mo files.\n\nIf no input FILE is given or if it is '-', standard input is read.\n\n\n'-r RESOURCE'\n'--resource=RESOURCE'\nSpecify the resource name.\n\n'-l LOCALE'\n'--locale=LOCALE'\nSpecify the locale name, either a language specification of the\nform LL or a combined language and country specification of the\nform LLCC.\n\nThe class name is determined by appending the locale name to the\nresource name, separated with an underscore. The class is located using\nthe 'CLASSPATH'.\n\n\n'-r RESOURCE'\n'--resource=RESOURCE'\nSpecify the resource name.\n\n'-l LOCALE'\n'--locale=LOCALE'\nSpecify the locale name, either a language specification of the\nform LL or a combined language and country specification of the\nform LLCC.\n\n'-d DIRECTORY'\nSpecify the base directory for locale dependent '.dll' files.\n\nThe '-l' and '-d' options are mandatory. The '.msg' file is located\nin a subdirectory of the specified directory whose name depends on the\nlocale.\n\n\n'-l LOCALE'\n'--locale=LOCALE'\nSpecify the locale name, either a language specification of the\nform LL or a combined language and country specification of the\nform LLCC.\n\n'-d DIRECTORY'\nSpecify the base directory of '.msg' message catalogs.\n\nThe '-l' and '-d' options are mandatory. The '.msg' file is located\nin the specified directory.\n\n\n'-o FILE'\n'--output-file=FILE'\nWrite output to specified file.\n\nThe results are written to standard output if no output file is\nspecified or if it is '-'.\n\n\n'--color'\n'--color=WHEN'\nSpecify whether or when to use colors and other text attributes.\nSee *note The --color option:: for details.\n\n'--style=STYLEFILE'\nSpecify the CSS style rule file to use for '--color'. See *note\nThe --style option:: for details.\n\n'--force-po'\nAlways write an output file even if it contains no message.\n\n'-i'\n'--indent'\nWrite the .po file using indented style.\n\n'--strict'\nWrite out a strict Uniforum conforming PO file. Note that this\nUniforum format should be avoided because it doesn't support the\nGNU extensions.\n\n'-p'\n'--properties-output'\nWrite out a Java ResourceBundle in Java '.properties' syntax. Note\nthat this file format doesn't support plural forms and silently\ndrops obsolete messages.\n\n'--stringtable-output'\nWrite out a NeXTstep/GNUstep localized resource file in '.strings'\nsyntax. Note that this file format doesn't support plural forms.\n\n'-w NUMBER'\n'--width=NUMBER'\nSet the output page width. Long strings in the output files will\nbe split across multiple lines in order to ensure that each line's\nwidth (= number of screen columns) is less or equal to the given\nNUMBER.\n\n'--no-wrap'\nDo not break long message lines. Message lines whose width exceeds\nthe output page width will not be split into several lines. Only\nfile reference lines which are wider than the output page width\nwill be split.\n\n'-s'\n'--sort-output'\nGenerate sorted output. Note that using this option makes it much\nharder for the translator to understand each message's context.\n\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\n'-v'\n'--verbose'\nIncrease verbosity level.\n\nFile: gettext.info, Node: MO Files, Prev: msgunfmt Invocation, Up: Binaries\n" }, { "name": "10.3 The Format of GNU MO Files", "content": "The format of the generated MO files is best described by a picture,\nwhich appears below.\n\nThe first two words serve the identification of the file. The magic\nnumber will always signal GNU MO files. The number is stored in the\nbyte order used when the MO file was generated, so the magic number\nreally is two numbers: '0x950412de' and '0xde120495'.\n\nThe second word describes the current revision of the file format,\ncomposed of a major and a minor revision number. The revision numbers\nensure that the readers of MO files can distinguish new formats from old\nones and handle their contents, as far as possible. For now the major\nrevision is 0 or 1, and the minor revision is also 0 or 1. More\nrevisions might be added in the future. A program seeing an unexpected\nmajor revision number should stop reading the MO file entirely; whereas\nan unexpected minor revision number means that the file can be read but\nwill not reveal its full contents, when parsed by a program that\nsupports only smaller minor revision numbers.\n\nThe version is kept separate from the magic number, instead of using\ndifferent magic numbers for different formats, mainly because\n'/etc/magic' is not updated often.\n\nFollow a number of pointers to later tables in the file, allowing for\nthe extension of the prefix part of MO files without having to recompile\nprograms reading them. This might become useful for later inserting a\nfew flag bits, indication about the charset used, new tables, or other\nthings.\n\nThen, at offset O and offset T in the picture, two tables of string\ndescriptors can be found. In both tables, each string descriptor uses\ntwo 32 bits integers, one for the string length, another for the offset\nof the string in the MO file, counting in bytes from the start of the\nfile. The first table contains descriptors for the original strings,\nand is sorted so the original strings are in increasing lexicographical\norder. The second table contains descriptors for the translated\nstrings, and is parallel to the first table: to find the corresponding\ntranslation one has to access the array slot in the second array with\nthe same index.\n\nHaving the original strings sorted enables the use of simple binary\nsearch, for when the MO file does not contain an hashing table, or for\nwhen it is not practical to use the hashing table provided in the MO\nfile. This also has another advantage, as the empty string in a PO file\nGNU 'gettext' is usually translated into some system information\nattached to that particular MO file, and the empty string necessarily\nbecomes the first in both the original and translated tables, making the\nsystem information very easy to find.\n\nThe size S of the hash table can be zero. In this case, the hash\ntable itself is not contained in the MO file. Some people might prefer\nthis because a precomputed hashing table takes disk space, and does not\nwin that much speed. The hash table contains indices to the sorted\narray of strings in the MO file. Conflict resolution is done by double\nhashing. The precise hashing algorithm used is fairly dependent on GNU\n'gettext' code, and is not documented here.\n\nAs for the strings themselves, they follow the hash file, and each is\nterminated with a , and this is not counted in the length\nwhich appears in the string descriptor. The 'msgfmt' program has an\noption selecting the alignment for MO file strings. With this option,\neach string is separately aligned so it starts at an offset which is a\nmultiple of the alignment value. On some RISC machines, a correct\nalignment will speed things up.\n\nContexts are stored by storing the concatenation of the context, a\n byte, and the original string, instead of the original string.\n\nPlural forms are stored by letting the plural of the original string\nfollow the singular of the original string, separated through a \nbyte. The length which appears in the string descriptor includes both.\nHowever, only the singular of the original string takes part in the hash\ntable lookup. The plural variants of the translation are all stored\nconsecutively, separated through a byte. Here also, the length in\nthe string descriptor includes all of them.\n\nNothing prevents a MO file from having embedded s in strings.\nHowever, the program interface currently used already presumes that\nstrings are terminated, so embedded s are somewhat useless.\nBut the MO file format is general enough so other interfaces would be\nlater possible, if for example, we ever want to implement wide\ncharacters right in MO files, where bytes may accidentally appear.\n(No, we don't want to have wide characters in MO files. They would make\nthe file unnecessarily large, and the 'wchart' type being platform\ndependent, MO files would be platform dependent as well.)\n\nThis particular issue has been strongly debated in the GNU 'gettext'\ndevelopment forum, and it is expectable that MO file format will evolve\nor change over time. It is even possible that many formats may later be\nsupported concurrently. But surely, we have to start somewhere, and the\nMO file format described here is a good start. Nothing is cast in\nconcrete, and the format may later evolve fairly easily, so we should\nfeel comfortable with the current approach.\n\nbyte\n+------------------------------------------+\n0 | magic number = 0x950412de |\n| |\n4 | file format revision = 0 |\n| |\n8 | number of strings | == N\n| |\n12 | offset of table with original strings | == O\n| |\n16 | offset of table with translation strings | == T\n| |\n20 | size of hashing table | == S\n| |\n24 | offset of hashing table | == H\n| |\n. .\n. (possibly more entries later) .\n. .\n| |\nO | length & offset 0th string ----------------.\nO + 8 | length & offset 1st string ------------------.\n... ... | |\nO + ((N-1)*8)| length & offset (N-1)th string | | |\n| | | |\nT | length & offset 0th translation ---------------.\nT + 8 | length & offset 1st translation -----------------.\n... ... | | | |\nT + ((N-1)*8)| length & offset (N-1)th translation | | | | |\n| | | | | |\nH | start hash table | | | | |\n... ... | | | |\nH + S * 4 | end hash table | | | | |\n| | | | | |\n| NUL terminated 0th string <----------------' | | |\n| | | | |\n| NUL terminated 1st string <------------------' | |\n| | | |\n... ... | |\n| | | |\n| NUL terminated 0th translation <---------------' |\n| | |\n| NUL terminated 1st translation <-----------------'\n| |\n... ...\n| |\n+------------------------------------------+\n\nFile: gettext.info, Node: Programmers, Next: Translators, Prev: Binaries, Up: Top\n" } ] }, "11 The Programmer's View": { "content": "One aim of the current message catalog implementation provided by GNU\n'gettext' was to use the system's message catalog handling, if the\ninstaller wishes to do so. So we perhaps should first take a look at\nthe solutions we know about. The people in the POSIX committee did not\nmanage to agree on one of the semi-official standards which we'll\ndescribe below. In fact they couldn't agree on anything, so they\ndecided only to include an example of an interface. The major Unix\nvendors are split in the usage of the two most important specifications:\nX/Open's catgets vs. Uniforum's gettext interface. We'll describe them\nboth and later explain our solution of this dilemma.\n\n* Menu:\n\n* catgets:: About 'catgets'\n* gettext:: About 'gettext'\n* Comparison:: Comparing the two interfaces\n* Using libintl.a:: Using libintl.a in own programs\n* gettext grok:: Being a 'gettext' grok\n* Temp Programmers:: Temporary Notes for the Programmers Chapter\n\nFile: gettext.info, Node: catgets, Next: gettext, Up: Programmers\n", "subsections": [ { "name": "11.1 About 'catgets'", "content": "The 'catgets' implementation is defined in the X/Open Portability\nGuide, Volume 3, XSI Supplementary Definitions, Chapter 5. But the\nprocess of creating this standard seemed to be too slow for some of the\nUnix vendors so they created their implementations on preliminary\nversions of the standard. Of course this leads again to problems while\nwriting platform independent programs: even the usage of 'catgets' does\nnot guarantee a unique interface.\n\nAnother, personal comment on this that only a bunch of committee\nmembers could have made this interface. They never really tried to\nprogram using this interface. It is a fast, memory-saving\nimplementation, an user can happily live with it. But programmers hate\nit (at least I and some others do...)\n\nBut we must not forget one point: after all the trouble with\ntransferring the rights on Unix they at last came to X/Open, the very\nsame who published this specification. This leads me to making the\nprediction that this interface will be in future Unix standards (e.g.\nSpec1170) and therefore part of all Unix implementation\n(implementations, which are allowed to wear this name).\n\n* Menu:\n\n* Interface to catgets:: The interface\n* Problems with catgets:: Problems with the 'catgets' interface?!\n\nFile: gettext.info, Node: Interface to catgets, Next: Problems with catgets, Up: catgets\n\n\nThe interface to the 'catgets' implementation consists of three\nfunctions which correspond to those used in file access: 'catopen' to\nopen the catalog for using, 'catgets' for accessing the message tables,\nand 'catclose' for closing after work is done. Prototypes for the\nfunctions and the needed definitions are in the '' header\nfile.\n\n'catopen' is used like in this:\n\nnlcatd catd = catopen (\"catalogname\", 0);\n\nThe function takes as the argument the name of the catalog. This\nusual refers to the name of the program or the package. The second\nparameter is not further specified in the standard. I don't even know\nwhether it is implemented consistently among various systems. So the\ncommon advice is to use '0' as the value. The return value is a handle\nto the message catalog, equivalent to handles to file returned by\n'open'.\n\nThis handle is of course used in the 'catgets' function which can be\nused like this:\n\nchar *translation = catgets (catd, setno, msgid, \"original string\");\n\nThe first parameter is this catalog descriptor. The second parameter\nspecifies the set of messages in this catalog, in which the message\ndescribed by 'msgid' is obtained. 'catgets' therefore uses a\nthree-stage addressing:\n\ncatalog name => set number => message ID => translation\n\nThe fourth argument is not used to address the translation. It is\ngiven as a default value in case when one of the addressing stages fail.\nOne important thing to remember is that although the return type of\ncatgets is 'char *' the resulting string must not be changed. It\nshould better be 'const char *', but the standard is published in 1988,\none year before ANSI C.\n\nThe last of these functions is used and behaves as expected:\n\ncatclose (catd);\n\nAfter this no 'catgets' call using the descriptor is legal anymore.\n\nFile: gettext.info, Node: Problems with catgets, Prev: Interface to catgets, Up: catgets\n\n\nNow that this description seemed to be really easy -- where are the\nproblems we speak of? In fact the interface could be used in a\nreasonable way, but constructing the message catalogs is a pain. The\nreason for this lies in the third argument of 'catgets': the unique\nmessage ID. This has to be a numeric value for all messages in a single\nset. Perhaps you could imagine the problems keeping such a list while\nchanging the source code. Add a new message here, remove one there. Of\ncourse there have been developed a lot of tools helping to organize this\nchaos but one as the other fails in one aspect or the other. We don't\nwant to say that the other approach has no problems but they are far\nmore easy to manage.\n\nFile: gettext.info, Node: gettext, Next: Comparison, Prev: catgets, Up: Programmers\n" }, { "name": "11.2 About 'gettext'", "content": "The definition of the 'gettext' interface comes from a Uniforum\nproposal. It was submitted there by Sun, who had implemented the\n'gettext' function in SunOS 4, around 1990. Nowadays, the 'gettext'\ninterface is specified by the OpenI18N standard.\n\nThe main point about this solution is that it does not follow the\nmethod of normal file handling (open-use-close) and that it does not\nburden the programmer with so many tasks, especially the unique key\nhandling. Of course here also a unique key is needed, but this key is\nthe message itself (how long or short it is). See *note Comparison::\nfor a more detailed comparison of the two methods.\n\nThe following section contains a rather detailed description of the\ninterface. We make it that detailed because this is the interface we\nchose for the GNU 'gettext' Library. Programmers interested in using\nthis library will be interested in this description.\n\n* Menu:\n\n* Interface to gettext:: The interface\n* Ambiguities:: Solving ambiguities\n* Locating Catalogs:: Locating message catalog files\n* Charset conversion:: How to request conversion to Unicode\n* Contexts:: Solving ambiguities in GUI programs\n* Plural forms:: Additional functions for handling plurals\n* Optimized gettext:: Optimization of the *gettext functions\n\nFile: gettext.info, Node: Interface to gettext, Next: Ambiguities, Up: gettext\n\n\nThe minimal functionality an interface must have is a) to select a\ndomain the strings are coming from (a single domain for all programs is\nnot reasonable because its construction and maintenance is difficult,\nperhaps impossible) and b) to access a string in a selected domain.\n\nThis is principally the description of the 'gettext' interface. It\nhas a global domain which unqualified usages reference. Of course this\ndomain is selectable by the user.\n\nchar *textdomain (const char *domainname);\n\nThis provides the possibility to change or query the current status\nof the current global domain of the 'LCMESSAGE' category. The argument\nis a null-terminated string, whose characters must be legal in the use\nin filenames. If the DOMAINNAME argument is 'NULL', the function\nreturns the current value. If no value has been set before, the name of\nthe default domain is returned: messages. Please note that although\nthe return value of 'textdomain' is of type 'char *' no changing is\nallowed. It is also important to know that no checks of the\navailability are made. If the name is not available you will see this\nby the fact that no translations are provided.\n\nTo use a domain set by 'textdomain' the function\n\nchar *gettext (const char *msgid);\n\nis to be used. This is the simplest reasonable form one can imagine.\nThe translation of the string MSGID is returned if it is available in\nthe current domain. If it is not available, the argument itself is\nreturned. If the argument is 'NULL' the result is undefined.\n\nOne thing which should come into mind is that no explicit dependency\nto the used domain is given. The current value of the domain is used.\nIf this changes between two executions of the same 'gettext' call in the\nprogram, both calls reference a different message catalog.\n\nFor the easiest case, which is normally used in internationalized\npackages, once at the beginning of execution a call to 'textdomain' is\nissued, setting the domain to a unique name, normally the package name.\nIn the following code all strings which have to be translated are\nfiltered through the gettext function. That's all, the package speaks\nyour language.\n\nFile: gettext.info, Node: Ambiguities, Next: Locating Catalogs, Prev: Interface to gettext, Up: gettext\n\n\nWhile this single name domain works well for most applications there\nmight be the need to get translations from more than one domain. Of\ncourse one could switch between different domains with calls to\n'textdomain', but this is really not convenient nor is it fast. A\npossible situation could be one case subject to discussion during this\nwriting: all error messages of functions in the set of common used\nfunctions should go into a separate domain 'error'. By this mean we\nwould only need to translate them once. Another case are messages from\na library, as these have to be independent of the current domain set\nby the application.\n\nFor this reasons there are two more functions to retrieve strings:\n\nchar *dgettext (const char *domainname, const char *msgid);\nchar *dcgettext (const char *domainname, const char *msgid,\nint category);\n\nBoth take an additional argument at the first place, which\ncorresponds to the argument of 'textdomain'. The third argument of\n'dcgettext' allows to use another locale category but 'LCMESSAGES'.\nBut I really don't know where this can be useful. If the DOMAINNAME is\n'NULL' or CATEGORY has an value beside the known ones, the result is\nundefined. It should also be noted that this function is not part of\nthe second known implementation of this function family, the one found\nin Solaris.\n\nA second ambiguity can arise by the fact, that perhaps more than one\ndomain has the same name. This can be solved by specifying where the\nneeded message catalog files can be found.\n\nchar *bindtextdomain (const char *domainname,\nconst char *dirname);\n\nCalling this function binds the given domain to a file in the\nspecified directory (how this file is determined follows below).\nEspecially a file in the systems default place is not favored against\nthe specified file anymore (as it would be by solely using\n'textdomain'). A 'NULL' pointer for the DIRNAME parameter returns the\nbinding associated with DOMAINNAME. If DOMAINNAME itself is 'NULL'\nnothing happens and a 'NULL' pointer is returned. Here again as for all\nthe other functions is true that none of the return value must be\nchanged!\n\nIt is important to remember that relative path names for the DIRNAME\nparameter can be trouble. Since the path is always computed relative to\nthe current directory different results will be achieved when the\nprogram executes a 'chdir' command. Relative paths should always be\navoided to avoid dependencies and unreliabilities.\n\nwchart *wbindtextdomain (const char *domainname,\nconst wchart *dirname);\n\nThis function is provided only on native Windows platforms. It is\nlike 'bindtextdomain', except that the DIRNAME parameter is a wide\nstring (in UTF-16 encoding, as usual on Windows).\n\nFile: gettext.info, Node: Locating Catalogs, Next: Charset conversion, Prev: Ambiguities, Up: gettext\n\n\nBecause many different languages for many different packages have to\nbe stored we need some way to add these information to file message\ncatalog files. The way usually used in Unix environments is have this\nencoding in the file name. This is also done here. The directory name\ngiven in 'bindtextdomain's second argument (or the default directory),\nfollowed by the name of the locale, the locale category, and the domain\nname are concatenated:\n\nDIRNAME/LOCALE/LCCATEGORY/DOMAINNAME.mo\n\nThe default value for DIRNAME is system specific. For the GNU\nlibrary, and for packages adhering to its conventions, it's:\n/usr/local/share/locale\n\nLOCALE is the name of the locale category which is designated by\n'LCCATEGORY'. For 'gettext' and 'dgettext' this 'LCCATEGORY' is\nalways 'LCMESSAGES'.(1) The name of the locale category is determined\nthrough 'setlocale (LCCATEGORY, NULL)'. (2) When using the function\n'dcgettext', you can specify the locale category through the third\nargument.\n\n---------- Footnotes ----------\n\n(1) Some system, e.g. mingw, don't have 'LCMESSAGES'. Here we use a\nmore or less arbitrary value for it, namely 1729, the smallest positive\ninteger which can be represented in two different ways as the sum of two\ncubes.\n\n(2) When the system does not support 'setlocale' its behavior in\nsetting the locale values is simulated by looking at the environment\nvariables.\n\nFile: gettext.info, Node: Charset conversion, Next: Contexts, Prev: Locating Catalogs, Up: gettext\n\n\n'gettext' not only looks up a translation in a message catalog. It\nalso converts the translation on the fly to the desired output character\nset. This is useful if the user is working in a different character set\nthan the translator who created the message catalog, because it avoids\ndistributing variants of message catalogs which differ only in the\ncharacter set.\n\nThe output character set is, by default, the value of 'nllanginfo\n(CODESET)', which depends on the 'LCCTYPE' part of the current locale.\nBut programs which store strings in a locale independent way (e.g.\nUTF-8) can request that 'gettext' and related functions return the\ntranslations in that encoding, by use of the 'bindtextdomaincodeset'\nfunction.\n\nNote that the MSGID argument to 'gettext' is not subject to character\nset conversion. Also, when 'gettext' does not find a translation for\nMSGID, it returns MSGID unchanged - independently of the current output\ncharacter set. It is therefore recommended that all MSGIDs be US-ASCII\nstrings.\n\n-- Function: char * bindtextdomaincodeset (const char *DOMAINNAME,\nconst char *CODESET)\nThe 'bindtextdomaincodeset' function can be used to specify the\noutput character set for message catalogs for domain DOMAINNAME.\nThe CODESET argument must be a valid codeset name which can be used\nfor the 'iconvopen' function, or a null pointer.\n\nIf the CODESET parameter is the null pointer,\n'bindtextdomaincodeset' returns the currently selected codeset\nfor the domain with the name DOMAINNAME. It returns 'NULL' if no\ncodeset has yet been selected.\n\nThe 'bindtextdomaincodeset' function can be used several times.\nIf used multiple times with the same DOMAINNAME argument, the later\ncall overrides the settings made by the earlier one.\n\nThe 'bindtextdomaincodeset' function returns a pointer to a\nstring containing the name of the selected codeset. The string is\nallocated internally in the function and must not be changed by the\nuser. If the system went out of core during the execution of\n'bindtextdomaincodeset', the return value is 'NULL' and the\nglobal variable ERRNO is set accordingly.\n\nFile: gettext.info, Node: Contexts, Next: Plural forms, Prev: Charset conversion, Up: gettext\n\n\nOne place where the 'gettext' functions, if used normally, have big\nproblems is within programs with graphical user interfaces (GUIs). The\nproblem is that many of the strings which have to be translated are very\nshort. They have to appear in pull-down menus which restricts the\nlength. But strings which are not containing entire sentences or at\nleast large fragments of a sentence may appear in more than one\nsituation in the program but might have different translations. This is\nespecially true for the one-word strings which are frequently used in\nGUI programs.\n\nAs a consequence many people say that the 'gettext' approach is wrong\nand instead 'catgets' should be used which indeed does not have this\nproblem. But there is a very simple and powerful method to handle this\nkind of problems with the 'gettext' functions.\n\nContexts can be added to strings to be translated. A context\ndependent translation lookup is when a translation for a given string is\nsearched, that is limited to a given context. The translation for the\nsame string in a different context can be different. The different\ntranslations of the same string in different contexts can be stored in\nthe in the same MO file, and can be edited by the translator in the same\nPO file.\n\nThe 'gettext.h' include file contains the lookup macros for strings\nwith contexts. They are implemented as thin macros and inline functions\nover the functions from ''.\n\nconst char *pgettext (const char *msgctxt, const char *msgid);\n\nIn a call of this macro, MSGCTXT and MSGID must be string literals.\nThe macro returns the translation of MSGID, restricted to the context\ngiven by MSGCTXT.\n\nThe MSGCTXT string is visible in the PO file to the translator. You\nshould try to make it somehow canonical and never changing. Because\nevery time you change an MSGCTXT, the translator will have to review the\ntranslation of MSGID.\n\nFinding a canonical MSGCTXT string that doesn't change over time can\nbe hard. But you shouldn't use the file name or class name containing\nthe 'pgettext' call - because it is a common development task to rename\na file or a class, and it shouldn't cause translator work. Also you\nshouldn't use a comment in the form of a complete English sentence as\nMSGCTXT - because orthography or grammar changes are often applied to\nsuch sentences, and again, it shouldn't force the translator to do a\nreview.\n\nThe 'p' in 'pgettext' stands for \"particular\": 'pgettext' fetches a\nparticular translation of the MSGID.\n\nconst char *dpgettext (const char *domainname,\nconst char *msgctxt, const char *msgid);\nconst char *dcpgettext (const char *domainname,\nconst char *msgctxt, const char *msgid,\nint category);\n\nThese are generalizations of 'pgettext'. They behave similarly to\n'dgettext' and 'dcgettext', respectively. The DOMAINNAME argument\ndefines the translation domain. The CATEGORY argument allows to use\nanother locale category than 'LCMESSAGES'.\n\nAs as example consider the following fictional situation. A GUI\nprogram has a menu bar with the following entries:\n\n+------------+------------+--------------------------------------+\n| File | Printer | |\n+------------+------------+--------------------------------------+\n| Open | | Select |\n| New | | Open |\n+----------+ | Connect |\n+----------+\n\nTo have the strings 'File', 'Printer', 'Open', 'New', 'Select', and\n'Connect' translated there has to be at some point in the code a call to\na function of the 'gettext' family. But in two places the string passed\ninto the function would be 'Open'. The translations might not be the\nsame and therefore we are in the dilemma described above.\n\nWhat distinguishes the two places is the menu path from the menu root\nto the particular menu entries:\n\nMenu|File\nMenu|Printer\nMenu|File|Open\nMenu|File|New\nMenu|Printer|Select\nMenu|Printer|Open\nMenu|Printer|Connect\n\nThe context is thus the menu path without its last part. So, the\ncalls look like this:\n\npgettext (\"Menu|\", \"File\")\npgettext (\"Menu|\", \"Printer\")\npgettext (\"Menu|File|\", \"Open\")\npgettext (\"Menu|File|\", \"New\")\npgettext (\"Menu|Printer|\", \"Select\")\npgettext (\"Menu|Printer|\", \"Open\")\npgettext (\"Menu|Printer|\", \"Connect\")\n\nWhether or not to use the '|' character at the end of the context is\na matter of style.\n\nFor more complex cases, where the MSGCTXT or MSGID are not string\nliterals, more general macros are available:\n\nconst char *pgettextexpr (const char *msgctxt, const char *msgid);\nconst char *dpgettextexpr (const char *domainname,\nconst char *msgctxt, const char *msgid);\nconst char *dcpgettextexpr (const char *domainname,\nconst char *msgctxt, const char *msgid,\nint category);\n\nHere MSGCTXT and MSGID can be arbitrary string-valued expressions.\nThese macros are more general. But in the case that both argument\nexpressions are string literals, the macros without the 'expr' suffix\nare more efficient.\n\nFile: gettext.info, Node: Plural forms, Next: Optimized gettext, Prev: Contexts, Up: gettext\n\n\nThe functions of the 'gettext' family described so far (and all the\n'catgets' functions as well) have one problem in the real world which\nhave been neglected completely in all existing approaches. What is\nmeant here is the handling of plural forms.\n\nLooking through Unix source code before the time anybody thought\nabout internationalization (and, sadly, even afterwards) one can often\nfind code similar to the following:\n\nprintf (\"%d file%s deleted\", n, n == 1 ? \"\" : \"s\");\n\nAfter the first complaints from people internationalizing the code\npeople either completely avoided formulations like this or used strings\nlike '\"file(s)\"'. Both look unnatural and should be avoided. First\ntries to solve the problem correctly looked like this:\n\nif (n == 1)\nprintf (\"%d file deleted\", n);\nelse\nprintf (\"%d files deleted\", n);\n\nBut this does not solve the problem. It helps languages where the\nplural form of a noun is not simply constructed by adding an 's' but\nthat is all. Once again people fell into the trap of believing the\nrules their language is using are universal. But the handling of plural\nforms differs widely between the language families. For example, Rafal\nMaszkowski '' reports:\n\nIn Polish we use e.g. plik (file) this way:\n1 plik\n2,3,4 pliki\n5-21 pliko'w\n22-24 pliki\n25-31 pliko'w\nand so on (o' means 8859-2 oacute which should be rather okreska,\nsimilar to aogonek).\n\nThere are two things which can differ between languages (and even\ninside language families);\n\n* The form how plural forms are built differs. This is a problem\nwith languages which have many irregularities. German, for\ninstance, is a drastic case. Though English and German are part of\nthe same language family (Germanic), the almost regular forming of\nplural noun forms (appending an 's') is hardly found in German.\n\n* The number of plural forms differ. This is somewhat surprising for\nthose who only have experiences with Romanic and Germanic languages\nsince here the number is the same (there are two).\n\nBut other language families have only one form or many forms. More\ninformation on this in an extra section.\n\nThe consequence of this is that application writers should not try to\nsolve the problem in their code. This would be localization since it is\nonly usable for certain, hardcoded language environments. Instead the\nextended 'gettext' interface should be used.\n\nThese extra functions are taking instead of the one key string two\nstrings and a numerical argument. The idea behind this is that using\nthe numerical argument and the first string as a key, the implementation\ncan select using rules specified by the translator the right plural\nform. The two string arguments then will be used to provide a return\nvalue in case no message catalog is found (similar to the normal\n'gettext' behavior). In this case the rules for Germanic language is\nused and it is assumed that the first string argument is the singular\nform, the second the plural form.\n\nThis has the consequence that programs without language catalogs can\ndisplay the correct strings only if the program itself is written using\na Germanic language. This is a limitation but since the GNU C library\n(as well as the GNU 'gettext' package) are written as part of the GNU\npackage and the coding standards for the GNU project require program\nbeing written in English, this solution nevertheless fulfills its\npurpose.\n\n-- Function: char * ngettext (const char *MSGID1, const char *MSGID2,\nunsigned long int N)\nThe 'ngettext' function is similar to the 'gettext' function as it\nfinds the message catalogs in the same way. But it takes two extra\narguments. The MSGID1 parameter must contain the singular form of\nthe string to be converted. It is also used as the key for the\nsearch in the catalog. The MSGID2 parameter is the plural form.\nThe parameter N is used to determine the plural form. If no\nmessage catalog is found MSGID1 is returned if 'n == 1', otherwise\n'msgid2'.\n\nAn example for the use of this function is:\n\nprintf (ngettext (\"%d file removed\", \"%d files removed\", n), n);\n\nPlease note that the numeric value N has to be passed to the\n'printf' function as well. It is not sufficient to pass it only to\n'ngettext'.\n\nIn the English singular case, the number - always 1 - can be\nreplaced with \"one\":\n\nprintf (ngettext (\"One file removed\", \"%d files removed\", n), n);\n\nThis works because the 'printf' function discards excess arguments\nthat are not consumed by the format string.\n\nIf this function is meant to yield a format string that takes two\nor more arguments, you can not use it like this:\n\nprintf (ngettext (\"%d file removed from directory %s\",\n\"%d files removed from directory %s\",\nn),\nn, dir);\n\nbecause in many languages the translators want to replace the '%d'\nwith an explicit word in the singular case, just like \"one\" in\nEnglish, and C format strings cannot consume the second argument\nbut skip the first argument. Instead, you have to reorder the\narguments so that 'n' comes last:\n\nprintf (ngettext (\"%2$d file removed from directory %1$s\",\n\"%2$d files removed from directory %1$s\",\nn),\ndir, n);\n\nSee *note c-format:: for details about this argument reordering\nsyntax.\n\nWhen you know that the value of 'n' is within a given range, you\ncan specify it as a comment directed to the 'xgettext' tool. This\ninformation may help translators to use more adequate translations.\nLike this:\n\nif (days > 7 && days < 14)\n/* xgettext: range: 1..6 */\nprintf (ngettext (\"one week and one day\", \"one week and %d days\",\ndays - 7),\ndays - 7);\n\nIt is also possible to use this function when the strings don't\ncontain a cardinal number:\n\nputs (ngettext (\"Delete the selected file?\",\n\"Delete the selected files?\",\nn));\n\nIn this case the number N is only used to choose the plural form.\n\n-- Function: char * dngettext (const char *DOMAIN, const char *MSGID1,\nconst char *MSGID2, unsigned long int N)\nThe 'dngettext' is similar to the 'dgettext' function in the way\nthe message catalog is selected. The difference is that it takes\ntwo extra parameter to provide the correct plural form. These two\nparameters are handled in the same way 'ngettext' handles them.\n\n-- Function: char * dcngettext (const char *DOMAIN, const char *MSGID1,\nconst char *MSGID2, unsigned long int N, int CATEGORY)\nThe 'dcngettext' is similar to the 'dcgettext' function in the way\nthe message catalog is selected. The difference is that it takes\ntwo extra parameter to provide the correct plural form. These two\nparameters are handled in the same way 'ngettext' handles them.\n\nNow, how do these functions solve the problem of the plural forms?\nWithout the input of linguists (which was not available) it was not\npossible to determine whether there are only a few different forms in\nwhich plural forms are formed or whether the number can increase with\nevery new supported language.\n\nTherefore the solution implemented is to allow the translator to\nspecify the rules of how to select the plural form. Since the formula\nvaries with every language this is the only viable solution except for\nhardcoding the information in the code (which still would require the\npossibility of extensions to not prevent the use of new languages).\n\nThe information about the plural form selection has to be stored in\nthe header entry of the PO file (the one with the empty 'msgid' string).\nThe plural form information looks like this:\n\nPlural-Forms: nplurals=2; plural=n == 1 ? 0 : 1;\n\nThe 'nplurals' value must be a decimal number which specifies how\nmany different plural forms exist for this language. The string\nfollowing 'plural' is an expression which is using the C language\nsyntax. Exceptions are that no negative numbers are allowed, numbers\nmust be decimal, and the only variable allowed is 'n'. Spaces are\nallowed in the expression, but backslash-newlines are not; in the\nexamples below the backslash-newlines are present for formatting\npurposes only. This expression will be evaluated whenever one of the\nfunctions 'ngettext', 'dngettext', or 'dcngettext' is called. The\nnumeric value passed to these functions is then substituted for all uses\nof the variable 'n' in the expression. The resulting value then must be\ngreater or equal to zero and smaller than the value given as the value\nof 'nplurals'.\n\nThe following rules are known at this point. The language with families\nare listed. But this does not necessarily mean the information can be\ngeneralized for the whole family (as can be easily seen in the table\nbelow).(1)\n\nOnly one form:\nSome languages only require one single form. There is no\ndistinction between the singular and plural form. An appropriate\nheader entry would look like this:\n\nPlural-Forms: nplurals=1; plural=0;\n\nLanguages with this property include:\n\nAsian family\nJapanese, Vietnamese, Korean\nTai-Kadai family\nThai\n\nTwo forms, singular used for one only\nThis is the form used in most existing programs since it is what\nEnglish is using. A header entry would look like this:\n\nPlural-Forms: nplurals=2; plural=n != 1;\n\n(Note: this uses the feature of C expressions that boolean\nexpressions have to value zero or one.)\n\nLanguages with this property include:\n\nGermanic family\nEnglish, German, Dutch, Swedish, Danish, Norwegian, Faroese\nRomanic family\nSpanish, Portuguese, Italian\nLatin/Greek family\nGreek\nSlavic family\nBulgarian\nFinno-Ugric family\nFinnish, Estonian\nSemitic family\nHebrew\nAustronesian family\nBahasa Indonesian\nArtificial\nEsperanto\n\nOther languages using the same header entry are:\n\nFinno-Ugric family\nHungarian\nTurkic/Altaic family\nTurkish\n\nHungarian does not appear to have a plural if you look at sentences\ninvolving cardinal numbers. For example, \"1 apple\" is \"1 alma\",\nand \"123 apples\" is \"123 alma\". But when the number is not\nexplicit, the distinction between singular and plural exists: \"the\napple\" is \"az alma\", and \"the apples\" is \"az alm??k\". Since\n'ngettext' has to support both types of sentences, it is classified\nhere, under \"two forms\".\n\nThe same holds for Turkish: \"1 apple\" is \"1 elma\", and \"123 apples\"\nis \"123 elma\". But when the number is omitted, the distinction\nbetween singular and plural exists: \"the apple\" is \"elma\", and \"the\napples\" is \"elmalar\".\n\nTwo forms, singular used for zero and one\nExceptional case in the language family. The header entry would\nbe:\n\nPlural-Forms: nplurals=2; plural=n>1;\n\nLanguages with this property include:\n\nRomanic family\nBrazilian Portuguese, French\n\nThree forms, special case for zero\nThe header entry would be:\n\nPlural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : 2;\n\nLanguages with this property include:\n\nBaltic family\nLatvian\n\nThree forms, special cases for one and two\nThe header entry would be:\n\nPlural-Forms: nplurals=3; plural=n==1 ? 0 : n==2 ? 1 : 2;\n\nLanguages with this property include:\n\nCeltic\nGaeilge (Irish)\n\nThree forms, special case for numbers ending in 00 or [2-9][0-9]\nThe header entry would be:\n\nPlural-Forms: nplurals=3; \\\nplural=n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < 20)) ? 1 : 2;\n\nLanguages with this property include:\n\nRomanic family\nRomanian\n\nThree forms, special case for numbers ending in 1[2-9]\nThe header entry would look like this:\n\nPlural-Forms: nplurals=3; \\\nplural=n%10==1 && n%100!=11 ? 0 : \\\nn%10>=2 && (n%100<10 || n%100>=20) ? 1 : 2;\n\nLanguages with this property include:\n\nBaltic family\nLithuanian\n\nThree forms, special cases for numbers ending in 1 and 2, 3, 4, except those ending in 1[1-4]\nThe header entry would look like this:\n\nPlural-Forms: nplurals=3; \\\nplural=n%10==1 && n%100!=11 ? 0 : \\\nn%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n\nLanguages with this property include:\n\nSlavic family\nRussian, Ukrainian, Belarusian, Serbian, Croatian\n\nThree forms, special cases for 1 and 2, 3, 4\nThe header entry would look like this:\n\nPlural-Forms: nplurals=3; \\\nplural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n\nLanguages with this property include:\n\nSlavic family\nCzech, Slovak\n\nThree forms, special case for one and some numbers ending in 2, 3, or 4\nThe header entry would look like this:\n\nPlural-Forms: nplurals=3; \\\nplural=n==1 ? 0 : \\\nn%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n\nLanguages with this property include:\n\nSlavic family\nPolish\n\nFour forms, special case for one and all numbers ending in 02, 03, or 04\nThe header entry would look like this:\n\nPlural-Forms: nplurals=4; \\\nplural=n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || n%100==4 ? 2 : 3;\n\nLanguages with this property include:\n\nSlavic family\nSlovenian\n\nSix forms, special cases for one, two, all numbers ending in 02, 03, ... 10, all numbers ending in 11 ... 99, and others\nThe header entry would look like this:\n\nPlural-Forms: nplurals=6; \\\nplural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 \\\n: n%100>=11 ? 4 : 5;\n\nLanguages with this property include:\n\nAfroasiatic family\nArabic\n\nYou might now ask, 'ngettext' handles only numbers N of type\n'unsigned long'. What about larger integer types? What about negative\nnumbers? What about floating-point numbers?\n\nAbout larger integer types, such as 'uintmaxt' or 'unsigned long\nlong': they can be handled by reducing the value to a range that fits in\nan 'unsigned long'. Simply casting the value to 'unsigned long' would\nnot do the right thing, since it would treat 'ULONGMAX + 1' like zero,\n'ULONGMAX + 2' like singular, and the like. Here you can exploit the\nfact that all mentioned plural form formulas eventually become periodic,\nwith a period that is a divisor of 100 (or 1000 or 1000000). So, when\nyou reduce a large value to another one in the range [1000000, 1999999]\nthat ends in the same 6 decimal digits, you can assume that it will lead\nto the same plural form selection. This code does this:\n\n#include \nuintmaxt nbytes = ...;\nprintf (ngettext (\"The file has %\"PRIuMAX\" byte.\",\n\"The file has %\"PRIuMAX\" bytes.\",\n(nbytes > ULONGMAX\n? (nbytes % 1000000) + 1000000\n: nbytes)),\nnbytes);\n\nNegative and floating-point values usually represent physical\nentities for which singular and plural don't clearly apply. In such\ncases, there is no need to use 'ngettext'; a simple 'gettext' call with\na form suitable for all values will do. For example:\n\nprintf (gettext (\"Time elapsed: %.3f seconds\"),\nnummilliseconds * 0.001);\n\nEven if NUMMILLISECONDS happens to be a multiple of 1000, the output\nTime elapsed: 1.000 seconds\nis acceptable in English, and similarly for other languages.\n\nThe translators' perspective regarding plural forms is explained in\n*note Translating plural forms::.\n\n---------- Footnotes ----------\n\n(1) Additions are welcome. Send appropriate information to\n and . The Unicode CLDR\nProject () provides a comprehensive set of\nplural forms in a different format. The 'msginit' program has\npreliminary support for the format so you can use it as a baseline\n(*note msginit Invocation::).\n\nFile: gettext.info, Node: Optimized gettext, Prev: Plural forms, Up: gettext\n\n\nAt this point of the discussion we should talk about an advantage of\nthe GNU 'gettext' implementation. Some readers might have pointed out\nthat an internationalized program might have a poor performance if some\nstring has to be translated in an inner loop. While this is unavoidable\nwhen the string varies from one run of the loop to the other it is\nsimply a waste of time when the string is always the same. Take the\nfollowing example:\n\n{\nwhile (...)\n{\nputs (gettext (\"Hello world\"));\n}\n}\n\nWhen the locale selection does not change between two runs the resulting\nstring is always the same. One way to use this is:\n\n{\nstr = gettext (\"Hello world\");\nwhile (...)\n{\nputs (str);\n}\n}\n\nBut this solution is not usable in all situation (e.g. when the locale\nselection changes) nor does it lead to legible code.\n\nFor this reason, GNU 'gettext' caches previous translation results.\nWhen the same translation is requested twice, with no new message\ncatalogs being loaded in between, 'gettext' will, the second time, find\nthe result through a single cache lookup.\n\nFile: gettext.info, Node: Comparison, Next: Using libintl.a, Prev: gettext, Up: Programmers\n" }, { "name": "11.3 Comparing the Two Interfaces", "content": "The following discussion is perhaps a little bit colored. As said\nabove we implemented GNU 'gettext' following the Uniforum proposal and\nthis surely has its reasons. But it should show how we came to this\ndecision.\n\nFirst we take a look at the developing process. When we write an\napplication using NLS provided by 'gettext' we proceed as always. Only\nwhen we come to a string which might be seen by the users and thus has\nto be translated we use 'gettext(\"...\")' instead of '\"...\"'. At the\nbeginning of each source file (or in a central header file) we define\n\n#define gettext(String) (String)\n\nEven this definition can be avoided when the system supports the\n'gettext' function in its C library. When we compile this code the\nresult is the same as if no NLS code is used. When you take a look at\nthe GNU 'gettext' code you will see that we use '(\"...\")' instead of\n'gettext(\"...\")'. This reduces the number of additional characters per\ntranslatable string to 3 (in words: three).\n\nWhen now a production version of the program is needed we simply\nreplace the definition\n\n#define (String) (String)\n\nby\n\n#include \n#define (String) gettext (String)\n\nAdditionally we run the program 'xgettext' on all source code file which\ncontain translatable strings and that's it: we have a running program\nwhich does not depend on translations to be available, but which can use\nany that becomes available.\n\nThe same procedure can be done for the 'gettextnoop' invocations\n(*note Special cases::). One usually defines 'gettextnoop' as a no-op\nmacro. So you should consider the following code for your project:\n\n#define gettextnoop(String) String\n#define N(String) gettextnoop (String)\n\n'N' is a short form similar to ''. The 'Makefile' in the 'po/'\ndirectory of GNU 'gettext' knows by default both of the mentioned short\nforms so you are invited to follow this proposal for your own ease.\n\nNow to 'catgets'. The main problem is the work for the programmer.\nEvery time he comes to a translatable string he has to define a number\n(or a symbolic constant) which has also be defined in the message\ncatalog file. He also has to take care for duplicate entries, duplicate\nmessage IDs etc. If he wants to have the same quality in the message\ncatalog as the GNU 'gettext' program provides he also has to put the\ndescriptive comments for the strings and the location in all source code\nfiles in the message catalog. This is nearly a Mission: Impossible.\n\nBut there are also some points people might call advantages speaking\nfor 'catgets'. If you have a single word in a string and this string is\nused in different contexts it is likely that in one or the other\nlanguage the word has different translations. Example:\n\nprintf (\"%s: %d\", gettext (\"number\"), numberoferrors)\n\nprintf (\"you should see %d %s\", numbercount,\nnumbercount == 1 ? gettext (\"number\") : gettext (\"numbers\"))\n\nHere we have to translate two times the string '\"number\"'. Even if\nyou do not speak a language beside English it might be possible to\nrecognize that the two words have a different meaning. In German the\nfirst appearance has to be translated to '\"Anzahl\"' and the second to\n'\"Zahl\"'.\n\nNow you can say that this example is really esoteric. And you are\nright! This is exactly how we felt about this problem and decide that\nit does not weight that much. The solution for the above problem could\nbe very easy:\n\nprintf (\"%s %d\", gettext (\"number:\"), numberoferrors)\n\nprintf (numbercount == 1 ? gettext (\"you should see %d number\")\n: gettext (\"you should see %d numbers\"),\nnumbercount)\n\nWe believe that we can solve all conflicts with this method. If it\nis difficult one can also consider changing one of the conflicting\nstring a little bit. But it is not impossible to overcome.\n\n'catgets' allows same original entry to have different translations,\nbut 'gettext' has another, scalable approach for solving ambiguities of\nthis kind: *Note Ambiguities::.\n\nFile: gettext.info, Node: Using libintl.a, Next: gettext grok, Prev: Comparison, Up: Programmers\n" }, { "name": "11.4 Using libintl.a in own programs", "content": "Starting with version 0.9.4 the library 'libintl.h' should be\nself-contained. I.e., you can use it in your own programs without\nproviding additional functions. The 'Makefile' will put the header and\nthe library in directories selected using the '$(prefix)'.\n\nFile: gettext.info, Node: gettext grok, Next: Temp Programmers, Prev: Using libintl.a, Up: Programmers\n" }, { "name": "11.5 Being a 'gettext' grok", "content": "* NOTE: * This documentation section is outdated and needs to be\nrevised.\n\nTo fully exploit the functionality of the GNU 'gettext' library it is\nsurely helpful to read the source code. But for those who don't want to\nspend that much time in reading the (sometimes complicated) code here is\na list comments:\n\n* Changing the language at runtime\n\nFor interactive programs it might be useful to offer a selection of\nthe used language at runtime. To understand how to do this one\nneed to know how the used language is determined while executing\nthe 'gettext' function. The method which is presented here only\nworks correctly with the GNU implementation of the 'gettext'\nfunctions.\n\nIn the function 'dcgettext' at every call the current setting of\nthe highest priority environment variable is determined and used.\nHighest priority means here the following list with decreasing\npriority:\n\n1. 'LANGUAGE'\n2. 'LCALL'\n3. 'LCxxx', according to selected locale category\n4. 'LANG'\n\nAfterwards the path is constructed using the found value and the\ntranslation file is loaded if available.\n\nWhat happens now when the value for, say, 'LANGUAGE' changes?\nAccording to the process explained above the new value of this\nvariable is found as soon as the 'dcgettext' function is called.\nBut this also means the (perhaps) different message catalog file is\nloaded. In other words: the used language is changed.\n\nBut there is one little hook. The code for gcc-2.7.0 and up\nprovides some optimization. This optimization normally prevents\nthe calling of the 'dcgettext' function as long as no new catalog\nis loaded. But if 'dcgettext' is not called the program also\ncannot find the 'LANGUAGE' variable be changed (*note Optimized\ngettext::). A solution for this is very easy. Include the\nfollowing code in the language switching function.\n\n/* Change language. */\nsetenv (\"LANGUAGE\", \"fr\", 1);\n\n/* Make change known. */\n{\nextern int nlmsgcatcntr;\n++nlmsgcatcntr;\n}\n\nThe variable 'nlmsgcatcntr' is defined in 'loadmsgcat.c'. You\ndon't need to know what this is for. But it can be used to detect\nwhether a 'gettext' implementation is GNU gettext and not non-GNU\nsystem's native gettext implementation.\n\nFile: gettext.info, Node: Temp Programmers, Prev: gettext grok, Up: Programmers\n" }, { "name": "11.6 Temporary Notes for the Programmers Chapter", "content": "* NOTE: * This documentation section is outdated and needs to be\nrevised.\n\n* Menu:\n\n* Temp Implementations:: Temporary - Two Possible Implementations\n* Temp catgets:: Temporary - About 'catgets'\n* Temp WSI:: Temporary - Why a single implementation\n* Temp Notes:: Temporary - Notes\n\nFile: gettext.info, Node: Temp Implementations, Next: Temp catgets, Up: Temp Programmers\n\n\nThere are two competing methods for language independent messages:\nthe X/Open 'catgets' method, and the Uniforum 'gettext' method. The\n'catgets' method indexes messages by integers; the 'gettext' method\nindexes them by their English translations. The 'catgets' method has\nbeen around longer and is supported by more vendors. The 'gettext'\nmethod is supported by Sun, and it has been heard that the COSE\nmulti-vendor initiative is supporting it. Neither method is a POSIX\nstandard; the POSIX.1 committee had a lot of disagreement in this area.\n\nNeither one is in the POSIX standard. There was much disagreement in\nthe POSIX.1 committee about using the 'gettext' routines vs. 'catgets'\n(XPG). In the end the committee couldn't agree on anything, so no\nmessaging system was included as part of the standard. I believe the\ninformative annex of the standard includes the XPG3 messaging\ninterfaces, \"...as an example of a messaging system that has been\nimplemented...\"\n\nThey were very careful not to say anywhere that you should use one\nset of interfaces over the other. For more on this topic please see the\nProgramming for Internationalization FAQ.\n\nFile: gettext.info, Node: Temp catgets, Next: Temp WSI, Prev: Temp Implementations, Up: Temp Programmers\n\n\nThere have been a few discussions of late on the use of 'catgets' as\na base. I think it important to present both sides of the argument and\nhence am opting to play devil's advocate for a little bit.\n\nI'll not deny the fact that 'catgets' could have been designed a lot\nbetter. It currently has quite a number of limitations and these have\nalready been pointed out.\n\nHowever there is a great deal to be said for consistency and\nstandardization. A common recurring problem when writing Unix software\nis the myriad portability problems across Unix platforms. It seems as\nif every Unix vendor had a look at the operating system and found parts\nthey could improve upon. Undoubtedly, these modifications are probably\ninnovative and solve real problems. However, software developers have a\nhard time keeping up with all these changes across so many platforms.\n\nAnd this has prompted the Unix vendors to begin to standardize their\nsystems. Hence the impetus for Spec1170. Every major Unix vendor has\ncommitted to supporting this standard and every Unix software developer\nwaits with glee the day they can write software to this standard and\nsimply recompile (without having to use autoconf) across different\nplatforms.\n\nAs I understand it, Spec1170 is roughly based upon version 4 of the\nX/Open Portability Guidelines (XPG4). Because 'catgets' and friends are\ndefined in XPG4, I'm led to believe that 'catgets' is a part of Spec1170\nand hence will become a standardized component of all Unix systems.\n\nFile: gettext.info, Node: Temp WSI, Next: Temp Notes, Prev: Temp catgets, Up: Temp Programmers\n\n\nNow it seems kind of wasteful to me to have two different systems\ninstalled for accessing message catalogs. If we do want to remedy\n'catgets' deficiencies why don't we try to expand 'catgets' (in a\ncompatible manner) rather than implement an entirely new system.\nOtherwise, we'll end up with two message catalog access systems\ninstalled with an operating system - one set of routines for packages\nusing GNU 'gettext' for their internationalization, and another set of\nroutines (catgets) for all other software. Bloated?\n\nSupposing another catalog access system is implemented. Which do we\nrecommend? At least for Linux, we need to attract as many software\ndevelopers as possible. Hence we need to make it as easy for them to\nport their software as possible. Which means supporting 'catgets'. We\nwill be implementing the 'libintl' code within our 'libc', but does this\nmean we also have to incorporate another message catalog access scheme\nwithin our 'libc' as well? And what about people who are going to be\nusing the 'libintl' + non-'catgets' routines. When they port their\nsoftware to other platforms, they're now going to have to include the\nfront-end ('libintl') code plus the back-end code (the non-'catgets'\naccess routines) with their software instead of just including the\n'libintl' code with their software.\n\nMessage catalog support is however only the tip of the iceberg. What\nabout the data for the other locale categories? They also have a number\nof deficiencies. Are we going to abandon them as well and develop\nanother duplicate set of routines (should 'libintl' expand beyond\nmessage catalog support)?\n\nLike many parts of Unix that can be improved upon, we're stuck with\nbalancing compatibility with the past with useful improvements and\ninnovations for the future.\n\nFile: gettext.info, Node: Temp Notes, Prev: Temp WSI, Up: Temp Programmers\n\n\nX/Open agreed very late on the standard form so that many\nimplementations differ from the final form. Both of my system (old\nLinux catgets and Ultrix-4) have a strange variation.\n\nOK. After incorporating the last changes I have to spend some time on\nmaking the GNU/Linux 'libc' 'gettext' functions. So in future Solaris\nis not the only system having 'gettext'.\n\nFile: gettext.info, Node: Translators, Next: Maintainers, Prev: Programmers, Up: Top\n" } ] }, "12 The Translator's View": { "content": "* Menu:\n\n* Trans Intro 0:: Introduction 0\n* Trans Intro 1:: Introduction 1\n* Discussions:: Discussions\n* Organization:: Organization\n* Information Flow:: Information Flow\n* Translating plural forms:: How to fill in 'msgstr[0]', 'msgstr[1]'\n* Prioritizing messages:: How to find which messages to translate first\n\nFile: gettext.info, Node: Trans Intro 0, Next: Trans Intro 1, Up: Translators\n", "subsections": [ { "name": "12.1 Introduction 0", "content": "* NOTE: * This documentation section is outdated and needs to be\nrevised.\n\nFree software is going international! The Translation Project is a\nway to get maintainers, translators and users all together, so free\nsoftware will gradually become able to speak many native languages.\n\nThe GNU 'gettext' tool set contains everything maintainers need for\ninternationalizing their packages for messages. It also contains quite\nuseful tools for helping translators at localizing messages to their\nnative language, once a package has already been internationalized.\n\nTo achieve the Translation Project, we need many interested people\nwho like their own language and write it well, and who are also able to\nsynergize with other translators speaking the same language. If you'd\nlike to volunteer to work at translating messages, please send mail to\nyour translating team.\n\nEach team has its own mailing list, courtesy of Linux International.\nYou may reach your translating team at the address 'LL@li.org',\nreplacing LL by the two-letter ISO 639 code for your language. Language\ncodes are not the same as country codes given in ISO 3166. The\nfollowing translating teams exist:\n\nChinese 'zh', Czech 'cs', Danish 'da', Dutch 'nl', Esperanto 'eo',\nFinnish 'fi', French 'fr', Irish 'ga', German 'de', Greek 'el',\nItalian 'it', Japanese 'ja', Indonesian 'in', Norwegian 'no',\nPolish 'pl', Portuguese 'pt', Russian 'ru', Spanish 'es', Swedish\n'sv' and Turkish 'tr'.\n\nFor example, you may reach the Chinese translating team by writing to\n'zh@li.org'. When you become a member of the translating team for your\nown language, you may subscribe to its list. For example, Swedish\npeople can send a message to 'sv-request@li.org', having this message\nbody:\n\nsubscribe\n\nKeep in mind that team members should be interested in working at\ntranslations, or at solving translational difficulties, rather than\nmerely lurking around. If your team does not exist yet and you want to\nstart one, please write to 'coordinator@translationproject.org'; you\nwill then reach the coordinator for all translator teams.\n\nA handful of GNU packages have already been adapted and provided with\nmessage translations for several languages. Translation teams have\nbegun to organize, using these packages as a starting point. But there\nare many more packages and many languages for which we have no volunteer\ntranslators. If you would like to volunteer to work at translating\nmessages, please send mail to 'coordinator@translationproject.org'\nindicating what language(s) you can work on.\n\nFile: gettext.info, Node: Trans Intro 1, Next: Discussions, Prev: Trans Intro 0, Up: Translators\n" }, { "name": "12.2 Introduction 1", "content": "* NOTE: * This documentation section is outdated and needs to be\nrevised.\n\nThis is now official, GNU is going international! Here is the\nannouncement submitted for the January 1995 GNU Bulletin:\n\nA handful of GNU packages have already been adapted and provided\nwith message translations for several languages. Translation teams\nhave begun to organize, using these packages as a starting point.\nBut there are many more packages and many languages for which we\nhave no volunteer translators. If you'd like to volunteer to work\nat translating messages, please send mail to\n'coordinator@translationproject.org' indicating what language(s)\nyou can work on.\n\nThis document should answer many questions for those who are curious\nabout the process or would like to contribute. Please at least skim\nover it, hoping to cut down a little of the high volume of e-mail\ngenerated by this collective effort towards internationalization of free\nsoftware.\n\nMost free programming which is widely shared is done in English, and\ncurrently, English is used as the main communicating language between\nnational communities collaborating to free software. This very document\nis written in English. This will not change in the foreseeable future.\n\nHowever, there is a strong appetite from national communities for\nhaving more software able to write using national language and habits,\nand there is an on-going effort to modify free software in such a way\nthat it becomes able to do so. The experiments driven so far raised an\nenthusiastic response from pretesters, so we believe that\ninternationalization of free software is dedicated to succeed.\n\nFor suggestion clarifications, additions or corrections to this\ndocument, please e-mail to 'coordinator@translationproject.org'.\n\nFile: gettext.info, Node: Discussions, Next: Organization, Prev: Trans Intro 1, Up: Translators\n" }, { "name": "12.3 Discussions", "content": "* NOTE: * This documentation section is outdated and needs to be\nrevised.\n\nFacing this internationalization effort, a few users expressed their\nconcerns. Some of these doubts are presented and discussed, here.\n\n* Smaller groups\n\nSome languages are not spoken by a very large number of people, so\npeople speaking them sometimes consider that there may not be all\nthat much demand such versions of free software packages.\nMoreover, many people being into computers, in some countries,\ngenerally seem to prefer English versions of their software.\n\nOn the other end, people might enjoy their own language a lot, and\nbe very motivated at providing to themselves the pleasure of having\ntheir beloved free software speaking their mother tongue. They do\nthemselves a personal favor, and do not pay that much attention to\nthe number of people benefiting of their work.\n\n* Misinterpretation\n\nOther users are shy to push forward their own language, seeing in\nthis some kind of misplaced propaganda. Someone thought there must\nbe some users of the language over the networks pestering other\npeople with it.\n\nBut any spoken language is worth localization, because there are\npeople behind the language for whom the language is important and\ndear to their hearts.\n\n* Odd translations\n\nThe biggest problem is to find the right translations so that\neverybody can understand the messages. Translations are usually a\nlittle odd. Some people get used to English, to the extent they\nmay find translations into their own language \"rather pushy,\nobnoxious and sometimes even hilarious.\" As a French speaking man,\nI have the experience of those instruction manuals for goods, so\npoorly translated in French in Korea or Taiwan...\n\nThe fact is that we sometimes have to create a kind of national\ncomputer culture, and this is not easy without the collaboration of\nmany people liking their mother tongue. This is why translations\nare better achieved by people knowing and loving their own\nlanguage, and ready to work together at improving the results they\nobtain.\n\n* Dependencies over the GPL or LGPL\n\nSome people wonder if using GNU 'gettext' necessarily brings their\npackage under the protective wing of the GNU General Public License\nor the GNU Lesser General Public License, when they do not want to\nmake their program free, or want other kinds of freedom. The\nsimplest answer is \"normally not\".\n\nThe 'gettext-runtime' part of GNU 'gettext', i.e. the contents of\n'libintl', is covered by the GNU Lesser General Public License.\nThe 'gettext-tools' part of GNU 'gettext', i.e. the rest of the GNU\n'gettext' package, is covered by the GNU General Public License.\n\nThe mere marking of localizable strings in a package, or\nconditional inclusion of a few lines for initialization, is not\nreally including GPL'ed or LGPL'ed code. However, since the\nlocalization routines in 'libintl' are under the LGPL, the LGPL\nneeds to be considered. It gives the right to distribute the\ncomplete unmodified source of 'libintl' even with non-free\nprograms. It also gives the right to use 'libintl' as a shared\nlibrary, even for non-free programs. But it gives the right to use\n'libintl' as a static library or to incorporate 'libintl' into\nanother library only to free software.\n\nFile: gettext.info, Node: Organization, Next: Information Flow, Prev: Discussions, Up: Translators\n" }, { "name": "12.4 Organization", "content": "* NOTE: * This documentation section is outdated and needs to be\nrevised.\n\nOn a larger scale, the true solution would be to organize some kind\nof fairly precise set up in which volunteers could participate. I gave\nsome thought to this idea lately, and realize there will be some touchy\npoints. I thought of writing to Richard Stallman to launch such a\nproject, but feel it might be good to shake out the ideas between\nourselves first. Most probably that Linux International has some\nexperience in the field already, or would like to orchestrate the\nvolunteer work, maybe. Food for thought, in any case!\n\nI guess we have to setup something early, somehow, that will help\nmany possible contributors of the same language to interlock and avoid\nwork duplication, and further be put in contact for solving together\nproblems particular to their tongue (in most languages, there are many\ndifficulties peculiar to translating technical English). My Swedish\ncontributor acknowledged these difficulties, and I'm well aware of them\nfor French.\n\nThis is surely not a technical issue, but we should manage so the\neffort of locale contributors be maximally useful, despite the national\nteam layer interface between contributors and maintainers.\n\nThe Translation Project needs some setup for coordinating language\ncoordinators. Localizing evolving programs will surely become a\npermanent and continuous activity in the free software community, once\nwell started. The setup should be minimally completed and tested before\nGNU 'gettext' becomes an official reality. The e-mail address\n'coordinator@translationproject.org' has been set up for receiving\noffers from volunteers and general e-mail on these topics. This address\nreaches the Translation Project coordinator.\n\n* Menu:\n\n* Central Coordination:: Central Coordination\n* National Teams:: National Teams\n* Mailing Lists:: Mailing Lists\n\nFile: gettext.info, Node: Central Coordination, Next: National Teams, Up: Organization\n\n\nI also think GNU will need sooner than it thinks, that someone set up\na way to organize and coordinate these groups. Some kind of group of\ngroups. My opinion is that it would be good that GNU delegates this\ntask to a small group of collaborating volunteers, shortly. Perhaps in\n'gnu.announce' a list of this national committee's can be published.\n\nMy role as coordinator would simply be to refer to Ulrich any German\nspeaking volunteer interested to localization of free software packages,\nand maybe helping national groups to initially organize, while\nmaintaining national registries for until national groups are ready to\ntake over. In fact, the coordinator should ease volunteers to get in\ncontact with one another for creating national teams, which should then\nselect one coordinator per language, or country (regionalized language).\nIf well done, the coordination should be useful without being an\noverwhelming task, the time to put delegations in place.\n\nFile: gettext.info, Node: National Teams, Next: Mailing Lists, Prev: Central Coordination, Up: Organization\n\n\nI suggest we look for volunteer coordinators/editors for individual\nlanguages. These people will scan contributions of translation files\nfor various programs, for their own languages, and will ensure high and\nuniform standards of diction.\n\nFrom my current experience with other people in these days, those who\nprovide localizations are very enthusiastic about the process, and are\nmore interested in the localization process than in the program they\nlocalize, and want to do many programs, not just one. This seems to\nconfirm that having a coordinator/editor for each language is a good\nidea.\n\nWe need to choose someone who is good at writing clear and concise\nprose in the language in question. That is hard--we can't check it\nourselves. So we need to ask a few people to judge each others' writing\nand select the one who is best.\n\nI announce my prerelease to a few dozen people, and you would not\nbelieve all the discussions it generated already. I shudder to think\nwhat will happen when this will be launched, for true, officially, world\nwide. Who am I to arbitrate between two Czekolsovak users contradicting\neach other, for example?\n\nI assume that your German is not much better than my French so that I\nwould not be able to judge about these formulations. What I would\nsuggest is that for each language there is a group for people who\nmaintain the PO files and judge about changes. I suspect there will be\ncultural differences between how such groups of people will behave.\nSome will have relaxed ways, reach consensus easily, and have anyone of\nthe group relate to the maintainers, while others will fight to death,\norganize heavy administrations up to national standards, and use strict\nchannels.\n\nThe German team is putting out a good example. Right now, they are\nmaybe half a dozen people revising translations of each other and\ndiscussing the linguistic issues. I do not even have all the names.\nUlrich Drepper is taking care of coordinating the German team. He\nsubscribed to all my pretest lists, so I do not even have to warn him\nspecifically of incoming releases.\n\nI'm sure, that is a good idea to get teams for each language working\non translations. That will make the translations better and more\nconsistent.\n\n* Menu:\n\n* Sub-Cultures:: Sub-Cultures\n* Organizational Ideas:: Organizational Ideas\n\nFile: gettext.info, Node: Sub-Cultures, Next: Organizational Ideas, Up: National Teams\n\n12.4.2.1 Sub-Cultures\n.....................\n\nTaking French for example, there are a few sub-cultures around\ncomputers which developed diverging vocabularies. Picking volunteers\nhere and there without addressing this problem in an organized way, soon\nin the project, might produce a distasteful mix of internationalized\nprograms, and possibly trigger endless quarrels among those who really\ncare.\n\nKeeping some kind of unity in the way French localization of\ninternationalized programs is achieved is a difficult (and delicate)\njob. Knowing the latin character of French people (:-), if we take this\nthe wrong way, we could end up nowhere, or spoil a lot of energies.\nMaybe we should begin to address this problem seriously before GNU\n'gettext' become officially published. And I suspect that this means\nsoon!\n\nFile: gettext.info, Node: Organizational Ideas, Prev: Sub-Cultures, Up: National Teams\n\n12.4.2.2 Organizational Ideas\n.............................\n\nI expect the next big changes after the official release. Please\nnote that I use the German translation of the short GPL message. We\nneed to set a few good examples before the localization goes out for\ntrue in the free software community. Here are a few points to discuss:\n\n* Each group should have one FTP server (at least one master).\n\n* The files on the server should reflect the latest version (of\ncourse!) and it should also contain a RCS directory with the\ncorresponding archives (I don't have this now).\n\n* There should also be a ChangeLog file (this is more useful than the\nRCS archive but can be generated automatically from the later by\nEmacs).\n\n* A \"core group\" should judge about questionable changes (for now\nthis group consists solely by me but I ask some others\noccasionally; this also seems to work).\n\nFile: gettext.info, Node: Mailing Lists, Prev: National Teams, Up: Organization\n\n\nIf we get any inquiries about GNU 'gettext', send them on to:\n\ncoordinator@translationproject.org\n\nThe '*-pretest' lists are quite useful to me, maybe the idea could be\ngeneralized to many GNU, and non-GNU packages. But each maintainer\nhis/her way!\n\nFranc,ois, we have a mechanism in place here at 'gnu.ai.mit.edu' to\ntrack teams, support mailing lists for them and log members. We have a\nslight preference that you use it. If this is OK with you, I can get\nyou clued in.\n\nThings are changing! A few years ago, when Daniel Fekete and I asked\nfor a mailing list for GNU localization, nested at the FSF, we were\npolitely invited to organize it anywhere else, and so did we. For\ncommunicating with my pretesters, I later made a handful of mailing\nlists located at iro.umontreal.ca and administrated by 'majordomo'.\nThese lists have been very dependable so far...\n\nI suspect that the German team will organize itself a mailing list\nlocated in Germany, and so forth for other countries. But before they\norganize for true, it could surely be useful to offer mailing lists\nlocated at the FSF to each national team. So yes, please explain me how\nI should proceed to create and handle them.\n\nWe should create temporary mailing lists, one per country, to help\npeople organize. Temporary, because once regrouped and structured, it\nwould be fair the volunteers from country bring back their list in\nthere and manage it as they want. My feeling is that, in the long run,\neach team should run its own list, from within their country. There\nalso should be some central list to which all teams could subscribe as\nthey see fit, as long as each team is represented in it.\n\nFile: gettext.info, Node: Information Flow, Next: Translating plural forms, Prev: Organization, Up: Translators\n" }, { "name": "12.5 Information Flow", "content": "* NOTE: * This documentation section is outdated and needs to be\nrevised.\n\nThere will surely be some discussion about this messages after the\npackages are finally released. If people now send you some proposals\nfor better messages, how do you proceed? Jim, please note that right\nnow, as I put forward nearly a dozen of localizable programs, I receive\nboth the translations and the coordination concerns about them.\n\nIf I put one of my things to pretest, Ulrich receives the\nannouncement and passes it on to the German team, who make last minute\nrevisions. Then he submits the translation files to me as the\nmaintainer. For free packages I do not maintain, I would not even hear\nabout it. This scheme could be made to work for the whole Translation\nProject, I think. For security reasons, maybe Ulrich (national\ncoordinators, in fact) should update central registry kept at the\nTranslation Project (Jim, me, or Len's recruits) once in a while.\n\nIn December/January, I was aggressively ready to internationalize all\nof GNU, giving myself the duty of one small GNU package per week or so,\ntaking many weeks or months for bigger packages. But it does not work\nthis way. I first did all the things I'm responsible for. I've nothing\nagainst some missionary work on other maintainers, but I'm also losing a\nlot of energy over it--same debates over again.\n\nAnd when the first localized packages are released we'll get a lot of\nresponses about ugly translations :-). Surely, and we need to have\nbeforehand a fairly good idea about how to handle the information flow\nbetween the national teams and the package maintainers.\n\nPlease start saving somewhere a quick history of each PO file. I\nknow for sure that the file format will change, allowing for comments.\nIt would be nice that each file has a kind of log, and references for\nthose who want to submit comments or gripes, or otherwise contribute. I\nsent a proposal for a fast and flexible format, but it is not receiving\nacceptance yet by the GNU deciders. I'll tell you when I have more\ninformation about this.\n\nFile: gettext.info, Node: Translating plural forms, Next: Prioritizing messages, Prev: Information Flow, Up: Translators\n" }, { "name": "12.6 Translating plural forms", "content": "Suppose you are translating a PO file, and it contains an entry like\nthis:\n\n#, c-format\nmsgid \"One file removed\"\nmsgidplural \"%d files removed\"\nmsgstr[0] \"\"\nmsgstr[1] \"\"\n\nWhat does this mean? How do you fill it in?\n\nSuch an entry denotes a message with plural forms, that is, a message\nwhere the text depends on a cardinal number. The general form of the\nmessage, in English, is the 'msgidplural' line. The 'msgid' line is\nthe English singular form, that is, the form for when the number is\nequal to 1. More details about plural forms are explained in *note\nPlural forms::.\n\nThe first thing you need to look at is the 'Plural-Forms' line in the\nheader entry of the PO file. It contains the number of plural forms and\na formula. If the PO file does not yet have such a line, you have to\nadd it. It only depends on the language into which you are translating.\nYou can get this info by using the 'msginit' command (see *note\nCreating::) - it contains a database of known plural formulas - or by\nasking other members of your translation team.\n\nSuppose the line looks as follows:\n\n\"Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n\"\n\"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\\n\"\n\nIt's logically one line; recall that the PO file formatting is\nallowed to break long lines so that each physical line fits in 80\nmonospaced columns.\n\nThe value of 'nplurals' here tells you that there are three plural\nforms. The first thing you need to do is to ensure that the entry\ncontains an 'msgstr' line for each of the forms:\n\n#, c-format\nmsgid \"One file removed\"\nmsgidplural \"%d files removed\"\nmsgstr[0] \"\"\nmsgstr[1] \"\"\nmsgstr[2] \"\"\n\nThen translate the 'msgidplural' line and fill it in into each\n'msgstr' line:\n\n#, c-format\nmsgid \"One file removed\"\nmsgidplural \"%d files removed\"\nmsgstr[0] \"%d slika uklonjenih\"\nmsgstr[1] \"%d slika uklonjenih\"\nmsgstr[2] \"%d slika uklonjenih\"\n\nNow you can refine the translation so that it matches the plural\nform. According to the formula above, 'msgstr[0]' is used when the\nnumber ends in 1 but does not end in 11; 'msgstr[1]' is used when the\nnumber ends in 2, 3, 4, but not in 12, 13, 14; and 'msgstr[2]' is used\nin all other cases. With this knowledge, you can refine the\ntranslations:\n\n#, c-format\nmsgid \"One file removed\"\nmsgidplural \"%d files removed\"\nmsgstr[0] \"%d slika je uklonjena\"\nmsgstr[1] \"%d datoteke uklonjenih\"\nmsgstr[2] \"%d slika uklonjenih\"\n\nYou noticed that in the English singular form ('msgid') the number\nplaceholder could be omitted and replaced by the numeral word \"one\".\nCan you do this in your translation as well?\n\nmsgstr[0] \"jednom datotekom je uklonjen\"\n\nWell, it depends on whether 'msgstr[0]' applies only to the number 1, or\nto other numbers as well. If, according to the plural formula,\n'msgstr[0]' applies only to 'n == 1', then you can use the specialized\ntranslation without the number placeholder. In our case, however,\n'msgstr[0]' also applies to the numbers 21, 31, 41, etc., and therefore\nyou cannot omit the placeholder.\n\nFile: gettext.info, Node: Prioritizing messages, Prev: Translating plural forms, Up: Translators\n" }, { "name": "12.7 Prioritizing messages: How to determine which messages to translate first", "content": "A translator sometimes has only a limited amount of time per week to\nspend on a package, and some packages have quite large message catalogs\n(over 1000 messages). Therefore she wishes to translate the messages\nfirst that are the most visible to the user, or that occur most\nfrequently. This section describes how to determine these \"most urgent\"\nmessages. It also applies to determine the \"next most urgent\" messages\nafter the message catalog has already been partially translated.\n\nIn a first step, she uses the programs like a user would do. While\nshe does this, the GNU 'gettext' library logs into a file the not yet\ntranslated messages for which a translation was requested from the\nprogram.\n\nIn a second step, she uses the PO mode to translate precisely this\nset of messages.\n\nHere are more details. The GNU 'libintl' library (but not the\ncorresponding functions in GNU 'libc') supports an environment variable\n'GETTEXTLOGUNTRANSLATED'. The GNU 'libintl' library will log into\nthis file the messages for which 'gettext()' and related functions\ncouldn't find the translation. If the file doesn't exist, it will be\ncreated as needed. On systems with GNU 'libc' a shared library\n'preloadablelibintl.so' is provided that can be used with the ELF\n'LDPRELOAD' mechanism.\n\nSo, in the first step, the translator uses these commands on systems\nwith GNU 'libc':\n\n$ LDPRELOAD=/usr/local/lib/preloadablelibintl.so\n$ export LDPRELOAD\n$ GETTEXTLOGUNTRANSLATED=$HOME/gettextlogused\n$ export GETTEXTLOGUNTRANSLATED\n\nand these commands on other systems:\n\n$ GETTEXTLOGUNTRANSLATED=$HOME/gettextlogused\n$ export GETTEXTLOGUNTRANSLATED\n\nThen she uses and peruses the programs. (It is a good and\nrecommended practice to use the programs for which you provide\ntranslations: it gives you the needed context.) When done, she removes\nthe environment variables:\n\n$ unset LDPRELOAD\n$ unset GETTEXTLOGUNTRANSLATED\n\nThe second step starts with removing duplicates:\n\n$ msguniq $HOME/gettextlogused > missing.po\n\nThe result is a PO file, but needs some preprocessing before a PO\nfile editor can be used with it. First, it is a multi-domain PO file,\ncontaining messages from many translation domains. Second, it lacks all\ntranslator comments and source references. Here is how to get a list of\nthe affected translation domains:\n\n$ sed -n -e 's,^domain \"\\(.*\\)\"$,\\1,p' < missing.po | sort | uniq\n\nThen the translator can handle the domains one by one. For\nsimplicity, let's use environment variables to denote the language,\ndomain and source package.\n\n$ lang=nl # your language\n$ domain=coreutils # the name of the domain to be handled\n$ package=/usr/src/gnu/coreutils-4.5.4 # the package where it comes from\n\nShe takes the latest copy of '$lang.po' from the Translation Project,\nor from the package (in most cases, '$package/po/$lang.po'), or creates\na fresh one if she's the first translator (see *note Creating::). She\nthen uses the following commands to mark the not urgent messages as\n\"obsolete\". (This doesn't mean that these messages - translated and\nuntranslated ones - will go away. It simply means that the PO file\neditor will ignore them in the following editing session.)\n\n$ msggrep --domain=$domain missing.po | grep -v '^domain' \\\n> $domain-missing.po\n$ msgattrib --set-obsolete --ignore-file $domain-missing.po $domain.$lang.po \\\n> $domain.$lang-urgent.po\n\nThe she translates '$domain.$lang-urgent.po' by use of a PO file\neditor (*note Editing::). (FIXME: I don't know whether 'KBabel' and\n'gtranslator' also preserve obsolete messages, as they should.) Finally\nshe restores the not urgent messages (with their earlier translations,\nfor those which were already translated) through this command:\n\n$ msgmerge --no-fuzzy-matching $domain.$lang-urgent.po $package/po/$domain.pot \\\n> $domain.$lang.po\n\nThen she can submit '$domain.$lang.po' and proceed to the next\ndomain.\n\nFile: gettext.info, Node: Maintainers, Next: Installers, Prev: Translators, Up: Top\n" } ] }, "13 The Maintainer's View": { "content": "The maintainer of a package has many responsibilities. One of them\nis ensuring that the package will install easily on many platforms, and\nthat the magic we described earlier (*note Users::) will work for\ninstallers and end users.\n\nOf course, there are many possible ways by which GNU 'gettext' might\nbe integrated in a distribution, and this chapter does not cover them in\nall generality. Instead, it details one possible approach which is\nespecially adequate for many free software distributions following GNU\nstandards, or even better, Gnits standards, because GNU 'gettext' is\npurposely for helping the internationalization of the whole GNU project,\nand as many other good free packages as possible. So, the maintainer's\nview presented here presumes that the package already has a\n'configure.ac' file and uses GNU Autoconf.\n\nNevertheless, GNU 'gettext' may surely be useful for free packages\nnot following GNU standards and conventions, but the maintainers of such\npackages might have to show imagination and initiative in organizing\ntheir distributions so 'gettext' work for them in all situations. There\nare surely many, out there.\n\nEven if 'gettext' methods are now stabilizing, slight adjustments\nmight be needed between successive 'gettext' versions, so you should\nideally revise this chapter in subsequent releases, looking for changes.\n\n* Menu:\n\n* Flat and Non-Flat:: Flat or Non-Flat Directory Structures\n* Prerequisites:: Prerequisite Works\n* gettextize Invocation:: Invoking the 'gettextize' Program\n* Adjusting Files:: Files You Must Create or Alter\n* autoconf macros:: Autoconf macros for use in 'configure.ac'\n* Version Control Issues::\n* Release Management:: Creating a Distribution Tarball\n\nFile: gettext.info, Node: Flat and Non-Flat, Next: Prerequisites, Up: Maintainers\n", "subsections": [ { "name": "13.1 Flat or Non-Flat Directory Structures", "content": "Some free software packages are distributed as 'tar' files which\nunpack in a single directory, these are said to be \"flat\" distributions.\nOther free software packages have a one level hierarchy of\nsubdirectories, using for example a subdirectory named 'doc/' for the\nTexinfo manual and man pages, another called 'lib/' for holding\nfunctions meant to replace or complement C libraries, and a subdirectory\n'src/' for holding the proper sources for the package. These other\ndistributions are said to be \"non-flat\".\n\nWe cannot say much about flat distributions. A flat directory\nstructure has the disadvantage of increasing the difficulty of updating\nto a new version of GNU 'gettext'. Also, if you have many PO files,\nthis could somewhat pollute your single directory. Also, GNU\n'gettext''s libintl sources consist of C sources, shell scripts, 'sed'\nscripts and complicated Makefile rules, which don't fit well into an\nexisting flat structure. For these reasons, we recommend to use\nnon-flat approach in this case as well.\n\nMaybe because GNU 'gettext' itself has a non-flat structure, we have\nmore experience with this approach, and this is what will be described\nin the remaining of this chapter. Some maintainers might use this as an\nopportunity to unflatten their package structure.\n\nFile: gettext.info, Node: Prerequisites, Next: gettextize Invocation, Prev: Flat and Non-Flat, Up: Maintainers\n" }, { "name": "13.2 Prerequisite Works", "content": "There are some works which are required for using GNU 'gettext' in\none of your package. These works have some kind of generality that\nescape the point by point descriptions used in the remainder of this\nchapter. So, we describe them here.\n\n* Before attempting to use 'gettextize' you should install some other\npackages first. Ensure that recent versions of GNU 'm4', GNU\nAutoconf and GNU 'gettext' are already installed at your site, and\nif not, proceed to do this first. If you get to install these\nthings, beware that GNU 'm4' must be fully installed before GNU\nAutoconf is even configured.\n\nTo further ease the task of a package maintainer the 'automake'\npackage was designed and implemented. GNU 'gettext' now uses this\ntool and the 'Makefile' in the 'po/' directory therefore knows\nabout all the goals necessary for using 'automake'.\n\nThose four packages are only needed by you, as a maintainer; the\ninstallers of your own package and end users do not really need any\nof GNU 'm4', GNU Autoconf, GNU 'gettext', or GNU 'automake' for\nsuccessfully installing and running your package, with messages\nproperly translated. But this is not completely true if you\nprovide internationalized shell scripts within your own package:\nGNU 'gettext' shall then be installed at the user site if the end\nusers want to see the translation of shell script messages.\n\n* Your package should use Autoconf and have a 'configure.ac' or\n'configure.in' file. If it does not, you have to learn how. The\nAutoconf documentation is quite well written, it is a good idea\nthat you print it and get familiar with it.\n\n* Your C sources should have already been modified according to\ninstructions given earlier in this manual. *Note Sources::.\n\n* Your 'po/' directory should receive all PO files submitted to you\nby the translator teams, each having 'LL.po' as a name. This is\nnot usually easy to get translation work done before your package\ngets internationalized and available! Since the cycle has to start\nsomewhere, the easiest for the maintainer is to start with\nabsolutely no PO files, and wait until various translator teams get\ninterested in your package, and submit PO files.\n\nIt is worth adding here a few words about how the maintainer should\nideally behave with PO files submissions. As a maintainer, your role is\nto authenticate the origin of the submission as being the representative\nof the appropriate translating teams of the Translation Project (forward\nthe submission to 'coordinator@translationproject.org' in case of\ndoubt), to ensure that the PO file format is not severely broken and\ndoes not prevent successful installation, and for the rest, to merely\nput these PO files in 'po/' for distribution.\n\nAs a maintainer, you do not have to take on your shoulders the\nresponsibility of checking if the translations are adequate or complete,\nand should avoid diving into linguistic matters. Translation teams\ndrive themselves and are fully responsible of their linguistic choices\nfor the Translation Project. Keep in mind that translator teams are\nnot driven by maintainers. You can help by carefully redirecting all\ncommunications and reports from users about linguistic matters to the\nappropriate translation team, or explain users how to reach or join\ntheir team.\n\nMaintainers should never ever apply PO file bug reports themselves,\nshort-cutting translation teams. If some translator has difficulty to\nget some of her points through her team, it should not be an option for\nher to directly negotiate translations with maintainers. Teams ought to\nsettle their problems themselves, if any. If you, as a maintainer, ever\nthink there is a real problem with a team, please never try to solve a\nteam's problem on your own.\n\nFile: gettext.info, Node: gettextize Invocation, Next: Adjusting Files, Prev: Prerequisites, Up: Maintainers\n" }, { "name": "13.3 Invoking the 'gettextize' Program", "content": "The 'gettextize' program is an interactive tool that helps the\nmaintainer of a package internationalized through GNU 'gettext'. It is\nused for two purposes:\n\n* As a wizard, when a package is modified to use GNU 'gettext' for\nthe first time.\n\n* As a migration tool, for upgrading the GNU 'gettext' support in a\npackage from a previous to a newer version of GNU 'gettext'.\n\nThis program performs the following tasks:\n\n* It copies into the package some files that are consistently and\nidentically needed in every package internationalized through GNU\n'gettext'.\n\n* It performs as many of the tasks mentioned in the next section\n*note Adjusting Files:: as can be performed automatically.\n\n* It removes obsolete files and idioms used for previous GNU\n'gettext' versions to the form recommended for the current GNU\n'gettext' version.\n\n* It prints a summary of the tasks that ought to be done manually and\ncould not be done automatically by 'gettextize'.\n\nIt can be invoked as follows:\n\ngettextize [ OPTION... ] [ DIRECTORY ]\n\nand accepts the following options:\n\n'-f'\n'--force'\nForce replacement of files which already exist.\n\n'--po-dir=DIR'\nSpecify a directory containing PO files. Such a directory contains\nthe translations into various languages of a particular POT file.\nThis option can be specified multiple times, once for each\ntranslation domain. If it is not specified, the directory named\n'po/' is updated.\n\n'--no-changelog'\nDon't update or create ChangeLog files. By default, 'gettextize'\nlogs all changes (file additions, modifications and removals) in a\nfile called 'ChangeLog' in each affected directory.\n\n'--symlink'\nMake symbolic links instead of copying the needed files. This can\nbe useful to save a few kilobytes of disk space, but it requires\nextra effort to create self-contained tarballs, it may disturb some\nmechanism the maintainer applies to the sources, and it is likely\nto introduce bugs when a newer version of 'gettext' is installed on\nthe system.\n\n'-n'\n'--dry-run'\nPrint modifications but don't perform them. All actions that\n'gettextize' would normally execute are inhibited and instead only\nlisted on standard output.\n\n'--help'\nDisplay this help and exit.\n\n'--version'\nOutput version information and exit.\n\nIf DIRECTORY is given, this is the top level directory of a package\nto prepare for using GNU 'gettext'. If not given, it is assumed that\nthe current directory is the top level directory of such a package.\n\nThe program 'gettextize' provides the following files. However, no\nexisting file will be replaced unless the option '--force' ('-f') is\nspecified.\n\n1. The 'ABOUT-NLS' file is copied in the main directory of your\npackage, the one being at the top level. This file contains a\nreference to the GNU gettext documentation. It also avoids an\nerror from Automake in packages that use the Automake option 'gnu'\nor 'gnits': \"error: required file './ABOUT-NLS' not found\".\n\n2. A 'po/' directory is created for eventually holding all translation\nfiles, but initially only containing the file 'po/Makefile.in.in'\nfrom the GNU 'gettext' distribution (beware the double '.in' in the\nfile name) and a few auxiliary files. If the 'po/' directory\nalready exists, it will be preserved along with the files it\ncontains, and only 'Makefile.in.in' and the auxiliary files will be\noverwritten.\n\nIf '--po-dir' has been specified, this holds for every directory\nspecified through '--po-dir', instead of 'po/'.\n\n3. The file 'config.rpath' is copied into the directory containing\nconfiguration support files. It is needed by the 'AMGNUGETTEXT'\nautoconf macro.\n\n4. Only if the project is using GNU 'automake': A set of 'autoconf'\nmacro files is copied into the package's 'autoconf' macro\nrepository, usually in a directory called 'm4/'.\n\nIf your site support symbolic links, 'gettextize' will not actually\ncopy the files into your package, but establish symbolic links instead.\nThis avoids duplicating the disk space needed in all packages. Merely\nusing the '-h' option while creating the 'tar' archive of your\ndistribution will resolve each link by an actual copy in the\ndistribution archive. So, to insist, you really should use '-h' option\nwith 'tar' within your 'dist' goal of your main 'Makefile.in'.\n\nFurthermore, 'gettextize' will update all 'Makefile.am' files in each\naffected directory, as well as the top level 'configure.ac' or\n'configure.in' file.\n\nIt is interesting to understand that most new files for supporting\nGNU 'gettext' facilities in one package go in 'po/' and 'm4/'\nsubdirectories. Still, these directories will mostly contain package\ndependent files.\n\nThe 'gettextize' program makes backup files for all files it replaces\nor changes, and also write ChangeLog entries about these changes. This\nway, the careful maintainer can check after running 'gettextize' whether\nits changes are acceptable to him, and possibly adjust them. An\nexception to this rule is the 'intl/' directory, which is removed as a\nwhole if it still existed.\n\nIt is important to understand that 'gettextize' can not do the entire\njob of adapting a package for using GNU 'gettext'. The amount of\nremaining work depends on whether the package uses GNU 'automake' or\nnot. But in any case, the maintainer should still read the section\n*note Adjusting Files:: after invoking 'gettextize'.\n\nIn particular, if after using 'gettexize', you get an error\n'ACCOMPILEIFELSE was called before ACGNUSOURCE' or 'ACRUNIFELSE\nwas called before ACGNUSOURCE', you can fix it by modifying\n'configure.ac', as described in *note configure.ac::.\n\nIt is also important to understand that 'gettextize' is not part of\nthe GNU build system, in the sense that it should not be invoked\nautomatically, and not be invoked by someone who doesn't assume the\nresponsibilities of a package maintainer. For the latter purpose, a\nseparate tool is provided, see *note autopoint Invocation::.\n\nFile: gettext.info, Node: Adjusting Files, Next: autoconf macros, Prev: gettextize Invocation, Up: Maintainers\n" }, { "name": "13.4 Files You Must Create or Alter", "content": "Besides files which are automatically added through 'gettextize',\nthere are many files needing revision for properly interacting with GNU\n'gettext'. If you are closely following GNU standards for Makefile\nengineering and auto-configuration, the adaptations should be easier to\nachieve. Here is a point by point description of the changes needed in\neach.\n\nSo, here comes a list of files, each one followed by a description of\nall alterations it needs. Many examples are taken out from the GNU\n'gettext' 0.21 distribution itself, or from the GNU 'hello' distribution\n(). You may indeed refer to the\nsource code of the GNU 'gettext' and GNU 'hello' packages, as they are\nintended to be good examples for using GNU gettext functionality.\n\n* Menu:\n\n* po/POTFILES.in:: 'POTFILES.in' in 'po/'\n* po/LINGUAS:: 'LINGUAS' in 'po/'\n* po/Makevars:: 'Makevars' in 'po/'\n* po/Rules-*:: Extending 'Makefile' in 'po/'\n* configure.ac:: 'configure.ac' at top level\n* config.guess:: 'config.guess', 'config.sub' at top level\n* mkinstalldirs:: 'mkinstalldirs' at top level\n* aclocal:: 'aclocal.m4' at top level\n* config.h.in:: 'config.h.in' at top level\n* Makefile:: 'Makefile.in' at top level\n* src/Makefile:: 'Makefile.in' in 'src/'\n* lib/gettext.h:: 'gettext.h' in 'lib/'\n\nFile: gettext.info, Node: po/POTFILES.in, Next: po/LINGUAS, Up: Adjusting Files\n\n\nThe 'po/' directory should receive a file named 'POTFILES.in'. This\nfile tells which files, among all program sources, have marked strings\nneeding translation. Here is an example of such a file:\n\n# List of source files containing translatable strings.\n# Copyright (C) 1995 Free Software Foundation, Inc.\n\n# Common library files\nlib/error.c\nlib/getopt.c\nlib/xmalloc.c\n\n# Package source files\nsrc/gettext.c\nsrc/msgfmt.c\nsrc/xgettext.c\n\nHash-marked comments and white lines are ignored. All other lines list\nthose source files containing strings marked for translation (*note Mark\nKeywords::), in a notation relative to the top level of your whole\ndistribution, rather than the location of the 'POTFILES.in' file itself.\n\nWhen a C file is automatically generated by a tool, like 'flex' or\n'bison', that doesn't introduce translatable strings by itself, it is\nrecommended to list in 'po/POTFILES.in' the real source file (ending in\n'.l' in the case of 'flex', or in '.y' in the case of 'bison'), not the\ngenerated C file.\n\nFile: gettext.info, Node: po/LINGUAS, Next: po/Makevars, Prev: po/POTFILES.in, Up: Adjusting Files\n\n\nThe 'po/' directory should also receive a file named 'LINGUAS'. This\nfile contains the list of available translations. It is a whitespace\nseparated list. Hash-marked comments and white lines are ignored. Here\nis an example file:\n\n# Set of available languages.\nde fr\n\nThis example means that German and French PO files are available, so\nthat these languages are currently supported by your package. If you\nwant to further restrict, at installation time, the set of installed\nlanguages, this should not be done by modifying the 'LINGUAS' file, but\nrather by using the 'LINGUAS' environment variable (*note Installers::).\n\nIt is recommended that you add the \"languages\" 'en@quot' and\n'en@boldquot' to the 'LINGUAS' file. 'en@quot' is a variant of English\nmessage catalogs ('en') which uses real quotation marks instead of the\nugly looking asymmetric ASCII substitutes '`' and '''. 'en@boldquot' is\na variant of 'en@quot' that additionally outputs quoted pieces of text\nin a bold font, when used in a terminal emulator which supports the\nVT100 escape sequences (such as 'xterm' or the Linux console, but not\nEmacs in 'M-x shell' mode).\n\nThese extra message catalogs 'en@quot' and 'en@boldquot' are\nconstructed automatically, not by translators; to support them, you need\nthe files 'Rules-quot', 'quot.sed', 'boldquot.sed', 'en@quot.header',\n'en@boldquot.header', 'insert-header.sin' in the 'po/' directory. You\ncan copy them from GNU gettext's 'po/' directory; they are also\ninstalled by running 'gettextize'.\n\nFile: gettext.info, Node: po/Makevars, Next: po/Rules-*, Prev: po/LINGUAS, Up: Adjusting Files\n\n\nThe 'po/' directory also has a file named 'Makevars'. It contains\nvariables that are specific to your project. 'po/Makevars' gets\ninserted into the 'po/Makefile' when the latter is created. The\nvariables thus take effect when the POT file is created or updated, and\nwhen the message catalogs get installed.\n\nThe first three variables can be left unmodified if your package has\na single message domain and, accordingly, a single 'po/' directory.\nOnly packages which have multiple 'po/' directories at different\nlocations need to adjust the three first variables defined in\n'Makevars'.\n\nAs an alternative to the 'XGETTEXTOPTIONS' variable, it is also\npossible to specify 'xgettext' options through the 'AMXGETTEXTOPTION'\nautoconf macro. See *note AMXGETTEXTOPTION::.\n\nFile: gettext.info, Node: po/Rules-*, Next: configure.ac, Prev: po/Makevars, Up: Adjusting Files\n\n\nAll files called 'Rules-*' in the 'po/' directory get appended to the\n'po/Makefile' when it is created. They present an opportunity to add\nrules for special PO files to the Makefile, without needing to mess with\n'po/Makefile.in.in'.\n\nGNU gettext comes with a 'Rules-quot' file, containing rules for\nbuilding catalogs 'en@quot.po' and 'en@boldquot.po'. The effect of\n'en@quot.po' is that people who set their 'LANGUAGE' environment\nvariable to 'en@quot' will get messages with proper looking symmetric\nUnicode quotation marks instead of abusing the ASCII grave accent and\nthe ASCII apostrophe for indicating quotations. To enable this catalog,\nsimply add 'en@quot' to the 'po/LINGUAS' file. The effect of\n'en@boldquot.po' is that people who set 'LANGUAGE' to 'en@boldquot' will\nget not only proper quotation marks, but also the quoted text will be\nshown in a bold font on terminals and consoles. This catalog is useful\nonly for command-line programs, not GUI programs. To enable it,\nsimilarly add 'en@boldquot' to the 'po/LINGUAS' file.\n\nSimilarly, you can create rules for building message catalogs for the\n'sr@latin' locale - Serbian written with the Latin alphabet - from those\nfor the 'sr' locale - Serbian written with Cyrillic letters. See *note\nmsgfilter Invocation::.\n\nFile: gettext.info, Node: configure.ac, Next: config.guess, Prev: po/Rules-*, Up: Adjusting Files\n\n\n'configure.ac' or 'configure.in' - this is the source from which\n'autoconf' generates the 'configure' script.\n\n1. Declare the package and version.\n\nThis is done by a set of lines like these:\n\nPACKAGE=gettext\nVERSION=0.21\nACDEFINEUNQUOTED(PACKAGE, \"$PACKAGE\")\nACDEFINEUNQUOTED(VERSION, \"$VERSION\")\nACSUBST(PACKAGE)\nACSUBST(VERSION)\n\nor, if you are using GNU 'automake', by a line like this:\n\nAMINITAUTOMAKE(gettext, 0.21)\n\nOf course, you replace 'gettext' with the name of your package, and\n'0.21' by its version numbers, exactly as they should appear in the\npackaged 'tar' file name of your distribution\n('gettext-0.21.tar.gz', here).\n\n2. Check for internationalization support.\n\nHere is the main 'm4' macro for triggering internationalization\nsupport. Just add this line to 'configure.ac':\n\nAMGNUGETTEXT([external])\n\nThis call is purposely simple, even if it generates a lot of\nconfigure time checking and actions.\n\n3. Have output files created.\n\nThe 'ACOUTPUT' directive, at the end of your 'configure.ac' file,\nneeds to be modified in two ways:\n\nACOUTPUT([EXISTING CONFIGURATION FILES po/Makefile.in],\n[EXISTING ADDITIONAL ACTIONS])\n\nThe modification to the first argument to 'ACOUTPUT' asks for\nsubstitution in the 'po/' directory. Note the '.in' suffix used\nfor 'po/' only. This is because the distributed file is really\n'po/Makefile.in.in'.\n\nFile: gettext.info, Node: config.guess, Next: mkinstalldirs, Prev: configure.ac, Up: Adjusting Files\n\n\nYou need to add the GNU 'config.guess' and 'config.sub' files to your\ndistribution. They are needed because the 'AMICONV' macro contains\nknowledge about specific platforms and therefore needs to identify the\nplatform.\n\nYou can obtain the newest version of 'config.guess' and 'config.sub'\nfrom the 'config' project at 'https://savannah.gnu.org/'. The commands\nto fetch them are\n$ wget -O config.guess 'https://git.savannah.gnu.org/gitweb/?p=config.git;a=blobplain;f=config.guess;hb=HEAD'\n$ wget -O config.sub 'https://git.savannah.gnu.org/gitweb/?p=config.git;a=blobplain;f=config.sub;hb=HEAD'\nLess recent versions are also contained in the GNU 'automake' and GNU\n'libtool' packages.\n\nNormally, 'config.guess' and 'config.sub' are put at the top level of\na distribution. But it is also possible to put them in a subdirectory,\naltogether with other configuration support files like 'install-sh',\n'ltconfig', 'ltmain.sh' or 'missing'. All you need to do, other than\nmoving the files, is to add the following line to your 'configure.ac'.\n\nACCONFIGAUXDIR([SUBDIR])\n\nFile: gettext.info, Node: mkinstalldirs, Next: aclocal, Prev: config.guess, Up: Adjusting Files\n\n\nWith earlier versions of GNU gettext, you needed to add the GNU\n'mkinstalldirs' script to your distribution. This is not needed any\nmore. You can remove it.\n\nFile: gettext.info, Node: aclocal, Next: config.h.in, Prev: mkinstalldirs, Up: Adjusting Files\n\n\nIf you do not have an 'aclocal.m4' file in your distribution, the\nsimplest is to concatenate the files 'gettext.m4', 'host-cpu-c-abi.m4',\n'intlmacosx.m4', 'iconv.m4', 'lib-ld.m4', 'lib-link.m4',\n'lib-prefix.m4', 'nls.m4', 'po.m4', 'progtest.m4' from GNU 'gettext''s\n'm4/' directory into a single file.\n\nIf you already have an 'aclocal.m4' file, then you will have to merge\nthe said macro files into your 'aclocal.m4'. Note that if you are\nupgrading from a previous release of GNU 'gettext', you should most\nprobably replace the macros ('AMGNUGETTEXT', etc.), as they usually\nchange a little from one release of GNU 'gettext' to the next. Their\ncontents may vary as we get more experience with strange systems out\nthere.\n\nYou should be using GNU 'automake' 1.9 or newer. With it, you need\nto copy the files 'gettext.m4', 'host-cpu-c-abi.m4', 'intlmacosx.m4',\n'iconv.m4', 'lib-ld.m4', 'lib-link.m4', 'lib-prefix.m4', 'nls.m4',\n'po.m4', 'progtest.m4' from GNU 'gettext''s 'm4/' directory to a\nsubdirectory named 'm4/' and add the line\n\nACLOCALAMFLAGS = -I m4\n\nto your top level 'Makefile.am'.\n\nIf you are using GNU 'automake' 1.10 or newer, it is even easier: Add\nthe line\n\nACLOCALAMFLAGS = --install -I m4\n\nto your top level 'Makefile.am', and run 'aclocal --install -I m4'.\nThis will copy the needed files to the 'm4/' subdirectory automatically,\nbefore updating 'aclocal.m4'.\n\nThese macros check for the internationalization support functions and\nrelated informations. Hopefully, once stabilized, these macros might be\nintegrated in the standard Autoconf set, because this piece of 'm4' code\nwill be the same for all projects using GNU 'gettext'.\n\nFile: gettext.info, Node: config.h.in, Next: Makefile, Prev: aclocal, Up: Adjusting Files\n\n\nThe include file template that holds the C macros to be defined by\n'configure' is usually called 'config.h.in' and may be maintained either\nmanually or automatically.\n\nIf it is maintained automatically, by use of the 'autoheader'\nprogram, you need to do nothing about it. This is the case in\nparticular if you are using GNU 'automake'.\n\nIf it is maintained manually, you can get away by adding the\nfollowing lines to 'config.h.in':\n\n/* Define to 1 if translation of program messages to the user's\nnative language is requested. */\n#undef ENABLENLS\n\nFile: gettext.info, Node: Makefile, Next: src/Makefile, Prev: config.h.in, Up: Adjusting Files\n\n\nHere are a few modifications you need to make to your main, top-level\n'Makefile.in' file.\n\n1. Add the following lines near the beginning of your 'Makefile.in',\nso the 'dist:' goal will work properly (as explained further down):\n\nPACKAGE = @PACKAGE@\nVERSION = @VERSION@\n\n2. Wherever you process subdirectories in your 'Makefile.in', be sure\nyou also process the subdirectory 'po'. Special rules in the\n'Makefiles' take care for the case where no internationalization is\nwanted.\n\nIf you are using Makefiles, either generated by automake, or\nhand-written so they carefully follow the GNU coding standards, the\neffected goals for which the new subdirectories must be handled\ninclude 'installdirs', 'install', 'uninstall', 'clean',\n'distclean'.\n\nHere is an example of a canonical order of processing. In this\nexample, we also define 'SUBDIRS' in 'Makefile.in' for it to be\nfurther used in the 'dist:' goal.\n\nSUBDIRS = doc lib src po\n\n3. A delicate point is the 'dist:' goal, as 'po/Makefile' will later\nassume that the proper directory has been set up from the main\n'Makefile'. Here is an example at what the 'dist:' goal might look\nlike:\n\ndistdir = $(PACKAGE)-$(VERSION)\ndist: Makefile\nrm -fr $(distdir)\nmkdir $(distdir)\nchmod 777 $(distdir)\nfor file in $(DISTFILES); do \\\nln $$file $(distdir) 2>/dev/null || cp -p $$file $(distdir); \\\ndone\nfor subdir in $(SUBDIRS); do \\\nmkdir $(distdir)/$$subdir || exit 1; \\\nchmod 777 $(distdir)/$$subdir; \\\n(cd $$subdir && $(MAKE) $@) || exit 1; \\\ndone\ntar chozf $(distdir).tar.gz $(distdir)\nrm -fr $(distdir)\n\nNote that if you are using GNU 'automake', 'Makefile.in' is\nautomatically generated from 'Makefile.am', and all needed changes to\n'Makefile.am' are already made by running 'gettextize'.\n\nFile: gettext.info, Node: src/Makefile, Next: lib/gettext.h, Prev: Makefile, Up: Adjusting Files\n\n\nSome of the modifications made in the main 'Makefile.in' will also be\nneeded in the 'Makefile.in' from your package sources, which we assume\nhere to be in the 'src/' subdirectory. Here are all the modifications\nneeded in 'src/Makefile.in':\n\n1. In view of the 'dist:' goal, you should have these lines near the\nbeginning of 'src/Makefile.in':\n\nPACKAGE = @PACKAGE@\nVERSION = @VERSION@\n\n2. If not done already, you should guarantee that 'topsrcdir' gets\ndefined. This will serve for 'cpp' include files. Just add the\nline:\n\ntopsrcdir = @topsrcdir@\n\n3. You might also want to define 'subdir' as 'src', later allowing for\nalmost uniform 'dist:' goals in all your 'Makefile.in'. At list,\nthe 'dist:' goal below assume that you used:\n\nsubdir = src\n\n4. The 'main' function of your program will normally call\n'bindtextdomain' (see *note Triggering::), like this:\n\nbindtextdomain (PACKAGE, LOCALEDIR);\ntextdomain (PACKAGE);\n\nOn native Windows platforms, the 'main' function may call\n'wbindtextdomain' instead of 'bindtextdomain'.\n\nTo make LOCALEDIR known to the program, add the following lines to\n'Makefile.in':\n\ndatadir = @datadir@\ndatarootdir= @datarootdir@\nlocaledir = @localedir@\nDEFS = -DLOCALEDIR=\\\"$(localedir)\\\" @DEFS@\n\nNote that '@datadir@' defaults to '$(prefix)/share', and\n'$(localedir)' defaults to '$(prefix)/share/locale'.\n\n5. You should ensure that the final linking will use '@LIBINTL@' or\n'@LTLIBINTL@' as a library. '@LIBINTL@' is for use without\n'libtool', '@LTLIBINTL@' is for use with 'libtool'. An easy way to\nachieve this is to manage that it gets into 'LIBS', like this:\n\nLIBS = @LIBINTL@ @LIBS@\n\nIn most packages internationalized with GNU 'gettext', one will\nfind a directory 'lib/' in which a library containing some helper\nfunctions will be build. (You need at least the few functions\nwhich the GNU 'gettext' Library itself needs.) However some of the\nfunctions in the 'lib/' also give messages to the user which of\ncourse should be translated, too. Taking care of this, the support\nlibrary (say 'libsupport.a') should be placed before '@LIBINTL@'\nand '@LIBS@' in the above example. So one has to write this:\n\nLIBS = ../lib/libsupport.a @LIBINTL@ @LIBS@\n\n6. Your 'dist:' goal has to conform with others. Here is a reasonable\ndefinition for it:\n\ndistdir = ../$(PACKAGE)-$(VERSION)/$(subdir)\ndist: Makefile $(DISTFILES)\nfor file in $(DISTFILES); do \\\nln $$file $(distdir) 2>/dev/null || cp -p $$file $(distdir) || exit 1; \\\ndone\n\nNote that if you are using GNU 'automake', 'Makefile.in' is\nautomatically generated from 'Makefile.am', and the first three changes\nand the last change are not necessary. The remaining needed\n'Makefile.am' modifications are the following:\n\n1. To make LOCALEDIR known to the program, add the following to\n'Makefile.am':\n\nCPPFLAGS = -DLOCALEDIR=\\\"$(localedir)\\\"\n\nfor each specific module or compilation unit, or\n\nAMCPPFLAGS = -DLOCALEDIR=\\\"$(localedir)\\\"\n\nfor all modules and compilation units together. Furthermore, if\nyou are using an Autoconf version older then 2.60, add this line to\ndefine 'localedir':\n\nlocaledir = $(datadir)/locale\n\n2. To ensure that the final linking will use '@LIBINTL@' or\n'@LTLIBINTL@' as a library, add the following to 'Makefile.am':\n\nLDADD = @LIBINTL@\n\nfor each specific program, or\n\nLDADD = @LIBINTL@\n\nfor all programs together. Remember that when you use 'libtool' to\nlink a program, you need to use @LTLIBINTL@ instead of @LIBINTL@\nfor that program.\n\nFile: gettext.info, Node: lib/gettext.h, Prev: src/Makefile, Up: Adjusting Files\n\n\nInternationalization of packages, as provided by GNU 'gettext', is\noptional. It can be turned off in two situations:\n\n* When the installer has specified './configure --disable-nls'. This\ncan be useful when small binaries are more important than features,\nfor example when building utilities for boot diskettes. It can\nalso be useful in order to get some specific C compiler warnings\nabout code quality with some older versions of GCC (older than\n3.0).\n\n* When the libintl.h header (with its associated libintl library, if\nany) is not already installed on the system, it is preferable that\nthe package builds without internationalization support, rather\nthan to give a compilation error.\n\nA C preprocessor macro can be used to detect these two cases.\nUsually, when 'libintl.h' was found and not explicitly disabled, the\n'ENABLENLS' macro will be defined to 1 in the autoconf generated\nconfiguration file (usually called 'config.h'). In the two negative\nsituations, however, this macro will not be defined, thus it will\nevaluate to 0 in C preprocessor expressions.\n\n'gettext.h' is a convenience header file for conditional use of\n'', depending on the 'ENABLENLS' macro. If 'ENABLENLS' is\nset, it includes ''; otherwise it defines no-op substitutes\nfor the libintl.h functions. We recommend the use of '\"gettext.h\"' over\ndirect use of '', so that portability to older systems is\nguaranteed and installers can turn off internationalization if they want\nto. In the C code, you will then write\n\n#include \"gettext.h\"\n\ninstead of\n\n#include \n\nThe location of 'gettext.h' is usually in a directory containing\nauxiliary include files. In many GNU packages, there is a directory\n'lib/' containing helper functions; 'gettext.h' fits there. In other\npackages, it can go into the 'src' directory.\n\nDo not install the 'gettext.h' file in public locations. Every\npackage that needs it should contain a copy of it on its own.\n\nFile: gettext.info, Node: autoconf macros, Next: Version Control Issues, Prev: Adjusting Files, Up: Maintainers\n" }, { "name": "13.5 Autoconf macros for use in 'configure.ac'", "content": "GNU 'gettext' installs macros for use in a package's 'configure.ac'\nor 'configure.in'. *Note Introduction: (autoconf)Top. The primary\nmacro is, of course, 'AMGNUGETTEXT'.\n\n* Menu:\n\n* AMGNUGETTEXT:: AMGNUGETTEXT in 'gettext.m4'\n* AMGNUGETTEXTVERSION:: AMGNUGETTEXTVERSION in 'gettext.m4'\n* AMGNUGETTEXTNEED:: AMGNUGETTEXTNEED in 'gettext.m4'\n* AMPOSUBDIRS:: AMPOSUBDIRS in 'po.m4'\n* AMXGETTEXTOPTION:: AMXGETTEXTOPTION in 'po.m4'\n* AMICONV:: AMICONV in 'iconv.m4'\n\nFile: gettext.info, Node: AMGNUGETTEXT, Next: AMGNUGETTEXTVERSION, Up: autoconf macros\n\n\nThe 'AMGNUGETTEXT' macro tests for the presence of the GNU gettext\nfunction family in either the C library or a separate 'libintl' library\n(shared or static libraries are both supported). It also invokes\n'AMPOSUBDIRS', thus preparing the 'po/' directories of the package for\nbuilding.\n\n'AMGNUGETTEXT' accepts up to three optional arguments. The general\nsyntax is\n\nAMGNUGETTEXT([INTLSYMBOL], [NEEDSYMBOL])\n\nINTLSYMBOL should always be 'external'.\n\nIf NEEDSYMBOL is specified and is 'need-ngettext', then GNU gettext\nimplementations (in libc or libintl) without the 'ngettext()' function\nwill be ignored. If NEEDSYMBOL is specified and is\n'need-formatstring-macros', then GNU gettext implementations that don't\nsupport the ISO C 99 '' formatstring macros will be ignored.\nOnly one NEEDSYMBOL can be specified. These requirements can also be\nspecified by using the macro 'AMGNUGETTEXTNEED' elsewhere. To\nspecify more than one requirement, just specify the strongest one among\nthem, or invoke the 'AMGNUGETTEXTNEED' macro several times. The\nhierarchy among the various alternatives is as follows:\n'need-formatstring-macros' implies 'need-ngettext'.\n\nThe 'AMGNUGETTEXT' macro determines whether GNU gettext is\navailable and should be used. If so, it sets the 'USENLS' variable to\n'yes'; it defines 'ENABLENLS' to 1 in the autoconf generated\nconfiguration file (usually called 'config.h'); it sets the variables\n'LIBINTL' and 'LTLIBINTL' to the linker options for use in a Makefile\n('LIBINTL' for use without libtool, 'LTLIBINTL' for use with libtool);\nit adds an '-I' option to 'CPPFLAGS' if necessary. In the negative\ncase, it sets 'USENLS' to 'no'; it sets 'LIBINTL' and 'LTLIBINTL' to\nempty and doesn't change 'CPPFLAGS'.\n\nThe complexities that 'AMGNUGETTEXT' deals with are the following:\n\n* Some operating systems have 'gettext' in the C library, for example\nglibc. Some have it in a separate library 'libintl'. GNU\n'libintl' might have been installed as part of the GNU 'gettext'\npackage.\n\n* GNU 'libintl', if installed, is not necessarily already in the\nsearch path ('CPPFLAGS' for the include file search path, 'LDFLAGS'\nfor the library search path).\n\n* Except for glibc, the operating system's native 'gettext' cannot\nexploit the GNU mo files, doesn't have the necessary locale\ndependency features, and cannot convert messages from the catalog's\ntext encoding to the user's locale encoding.\n\n* GNU 'libintl', if installed, is not necessarily already in the run\ntime library search path. To avoid the need for setting an\nenvironment variable like 'LDLIBRARYPATH', the macro adds the\nappropriate run time search path options to the 'LIBINTL' and\n'LTLIBINTL' variables. This works on most systems, but not on some\noperating systems with limited shared library support, like SCO.\n\n* GNU 'libintl' relies on POSIX/XSI 'iconv'. The macro checks for\nlinker options needed to use iconv and appends them to the\n'LIBINTL' and 'LTLIBINTL' variables.\n\nFile: gettext.info, Node: AMGNUGETTEXTVERSION, Next: AMGNUGETTEXTNEED, Prev: AMGNUGETTEXT, Up: autoconf macros\n\n\nThe 'AMGNUGETTEXTVERSION' macro declares the version number of the\nGNU gettext infrastructure that is used by the package.\n\nThe use of this macro is optional; only the 'autopoint' program makes\nuse of it (*note Version Control Issues::).\n\nFile: gettext.info, Node: AMGNUGETTEXTNEED, Next: AMPOSUBDIRS, Prev: AMGNUGETTEXTVERSION, Up: autoconf macros\n\n\nThe 'AMGNUGETTEXTNEED' macro declares a constraint regarding the\nGNU gettext implementation. The syntax is\n\nAMGNUGETTEXTNEED([NEEDSYMBOL])\n\nIf NEEDSYMBOL is 'need-ngettext', then GNU gettext implementations\n(in libc or libintl) without the 'ngettext()' function will be ignored.\nIf NEEDSYMBOL is 'need-formatstring-macros', then GNU gettext\nimplementations that don't support the ISO C 99 ''\nformatstring macros will be ignored.\n\nThe optional second argument of 'AMGNUGETTEXT' is also taken into\naccount.\n\nThe 'AMGNUGETTEXTNEED' invocations can occur before or after the\n'AMGNUGETTEXT' invocation; the order doesn't matter.\n\nFile: gettext.info, Node: AMPOSUBDIRS, Next: AMXGETTEXTOPTION, Prev: AMGNUGETTEXTNEED, Up: autoconf macros\n\n\nThe 'AMPOSUBDIRS' macro prepares the 'po/' directories of the\npackage for building. This macro should be used in internationalized\nprograms written in other programming languages than C, C++, Objective\nC, for example 'sh', 'Python', 'Lisp'. See *note Programming\nLanguages:: for a list of programming languages that support\nlocalization through PO files.\n\nThe 'AMPOSUBDIRS' macro determines whether internationalization\nshould be used. If so, it sets the 'USENLS' variable to 'yes',\notherwise to 'no'. It also determines the right values for Makefile\nvariables in each 'po/' directory.\n\nFile: gettext.info, Node: AMXGETTEXTOPTION, Next: AMICONV, Prev: AMPOSUBDIRS, Up: autoconf macros\n\n\nThe 'AMXGETTEXTOPTION' macro registers a command-line option to be\nused in the invocations of 'xgettext' in the 'po/' directories of the\npackage.\n\nFor example, if you have a source file that defines a function\n'erroratline' whose fifth argument is a format string, you can use\nAMXGETTEXTOPTION([--flag=erroratline:5:c-format])\nto instruct 'xgettext' to mark all translatable strings in 'gettext'\ninvocations that occur as fifth argument to this function as 'c-format'.\n\nSee *note xgettext Invocation:: for the list of options that\n'xgettext' accepts.\n\nThe use of this macro is an alternative to the use of the\n'XGETTEXTOPTIONS' variable in 'po/Makevars'.\n\nFile: gettext.info, Node: AMICONV, Prev: AMXGETTEXTOPTION, Up: autoconf macros\n\n\nThe 'AMICONV' macro tests for the presence of the POSIX/XSI 'iconv'\nfunction family in either the C library or a separate 'libiconv'\nlibrary. If found, it sets the 'amcvfunciconv' variable to 'yes'; it\ndefines 'HAVEICONV' to 1 in the autoconf generated configuration file\n(usually called 'config.h'); it defines 'ICONVCONST' to 'const' or to\nempty, depending on whether the second argument of 'iconv()' is of type\n'const char ' or 'char '; it sets the variables 'LIBICONV' and\n'LTLIBICONV' to the linker options for use in a Makefile ('LIBICONV' for\nuse without libtool, 'LTLIBICONV' for use with libtool); it adds an '-I'\noption to 'CPPFLAGS' if necessary. If not found, it sets 'LIBICONV' and\n'LTLIBICONV' to empty and doesn't change 'CPPFLAGS'.\n\nThe complexities that 'AMICONV' deals with are the following:\n\n* Some operating systems have 'iconv' in the C library, for example\nglibc. Some have it in a separate library 'libiconv', for example\nOSF/1 or FreeBSD. Regardless of the operating system, GNU\n'libiconv' might have been installed. In that case, it should be\nused instead of the operating system's native 'iconv'.\n\n* GNU 'libiconv', if installed, is not necessarily already in the\nsearch path ('CPPFLAGS' for the include file search path, 'LDFLAGS'\nfor the library search path).\n\n* GNU 'libiconv' is binary incompatible with some operating system's\nnative 'iconv', for example on FreeBSD. Use of an 'iconv.h' and\n'libiconv.so' that don't fit together would produce program\ncrashes.\n\n* GNU 'libiconv', if installed, is not necessarily already in the run\ntime library search path. To avoid the need for setting an\nenvironment variable like 'LDLIBRARYPATH', the macro adds the\nappropriate run time search path options to the 'LIBICONV'\nvariable. This works on most systems, but not on some operating\nsystems with limited shared library support, like SCO.\n\n'iconv.m4' is distributed with the GNU gettext package because\n'gettext.m4' relies on it.\n\nFile: gettext.info, Node: Version Control Issues, Next: Release Management, Prev: autoconf macros, Up: Maintainers\n" }, { "name": "13.6 Integrating with Version Control Systems", "content": "Many projects use version control systems for distributed development\nand source backup. This section gives some advice how to manage the\nuses of 'gettextize', 'autopoint' and 'autoconf' on version controlled\nfiles.\n\n* Menu:\n\n* Distributed Development:: Avoiding version mismatch in distributed development\n* Files under Version Control:: Files to put under version control\n* Translations under Version Control:: Put PO Files under Version Control\n* autopoint Invocation:: Invoking the 'autopoint' Program\n\nFile: gettext.info, Node: Distributed Development, Next: Files under Version Control, Up: Version Control Issues\n\n\nIn a project development with multiple developers, there should be a\nsingle developer who occasionally - when there is desire to upgrade to a\nnew 'gettext' version - runs 'gettextize' and performs the changes\nlisted in *note Adjusting Files::, and then commits his changes to the\nrepository.\n\nIt is highly recommended that all developers on a project use the\nsame version of GNU 'gettext' in the package. In other words, if a\ndeveloper runs 'gettextize', he should go the whole way, make the\nnecessary remaining changes and commit his changes to the repository.\nOtherwise the following damages will likely occur:\n\n* Apparent version mismatch between developers. Since some 'gettext'\nspecific portions in 'configure.ac', 'configure.in' and\n'Makefile.am', 'Makefile.in' files depend on the 'gettext' version,\nthe use of infrastructure files belonging to different 'gettext'\nversions can easily lead to build errors.\n\n* Hidden version mismatch. Such version mismatch can also lead to\nmalfunctioning of the package, that may be undiscovered by the\ndevelopers. The worst case of hidden version mismatch is that\ninternationalization of the package doesn't work at all.\n\n* Release risks. All developers implicitly perform constant testing\non a package. This is important in the days and weeks before a\nrelease. If the guy who makes the release tar files uses a\ndifferent version of GNU 'gettext' than the other developers, the\ndistribution will be less well tested than if all had been using\nthe same 'gettext' version. For example, it is possible that a\nplatform specific bug goes undiscovered due to this constellation.\n\nFile: gettext.info, Node: Files under Version Control, Next: Translations under Version Control, Prev: Distributed Development, Up: Version Control Issues\n\n\nThere are basically three ways to deal with generated files in the\ncontext of a version controlled repository, such as 'configure'\ngenerated from 'configure.ac', 'PARSER.c' generated from 'PARSER.y', or\n'po/Makefile.in.in' autoinstalled by 'gettextize' or 'autopoint'.\n\n1. All generated files are always committed into the repository.\n\n2. All generated files are committed into the repository occasionally,\nfor example each time a release is made.\n\n3. Generated files are never committed into the repository.\n\nEach of these three approaches has different advantages and\ndrawbacks.\n\n1. The advantage is that anyone can check out the source at any moment\nand gets a working build. The drawbacks are: 1a. It requires some\nfrequent \"push\" actions by the maintainers. 1b. The repository\ngrows in size quite fast.\n\n2. The advantage is that anyone can check out the source, and the\nusual \"./configure; make\" will work. The drawbacks are: 2a. The\none who checks out the repository needs tools like GNU 'automake',\nGNU 'autoconf', GNU 'm4' installed in his PATH; sometimes he even\nneeds particular versions of them. 2b. When a release is made and\na commit is made on the generated files, the other developers get\nconflicts on the generated files when merging the local work back\nto the repository. Although these conflicts are easy to resolve,\nthey are annoying.\n\n3. The advantage is less work for the maintainers. The drawback is\nthat anyone who checks out the source not only needs tools like GNU\n'automake', GNU 'autoconf', GNU 'm4' installed in his PATH, but\nalso that he needs to perform a package specific pre-build step\nbefore being able to \"./configure; make\".\n\nFor the first and second approach, all files modified or brought in\nby the occasional 'gettextize' invocation and update should be committed\ninto the repository.\n\nFor the third approach, the maintainer can omit from the repository\nall the files that 'gettextize' mentions as \"copy\". Instead, he adds to\nthe 'configure.ac' or 'configure.in' a line of the form\n\nAMGNUGETTEXTVERSION(0.21)\n\nand adds to the package's pre-build script an invocation of 'autopoint'.\nFor everyone who checks out the source, this 'autopoint' invocation will\ncopy into the right place the 'gettext' infrastructure files that have\nbeen omitted from the repository.\n\nThe version number used as argument to 'AMGNUGETTEXTVERSION' is\nthe version of the 'gettext' infrastructure that the package wants to\nuse. It is also the minimum version number of the 'autopoint' program.\nSo, if you write 'AMGNUGETTEXTVERSION(0.11.5)' then the developers\ncan have any version >= 0.11.5 installed; the package will work with the\n0.11.5 infrastructure in all developers' builds. When the maintainer\nthen runs gettextize from, say, version 0.12.1 on the package, the\noccurrence of 'AMGNUGETTEXTVERSION(0.11.5)' will be changed into\n'AMGNUGETTEXTVERSION(0.12.1)', and all other developers that use the\nCVS will henceforth need to have GNU 'gettext' 0.12.1 or newer\ninstalled.\n\nFile: gettext.info, Node: Translations under Version Control, Next: autopoint Invocation, Prev: Files under Version Control, Up: Version Control Issues\n\n\nSince translations are valuable assets as well as the source code, it\nwould make sense to put them under version control. The GNU gettext\ninfrastructure supports two ways to deal with translations in the\ncontext of a version controlled repository.\n\n1. Both POT file and PO files are committed into the repository.\n\n2. Only PO files are committed into the repository.\n\nIf a POT file is absent when building, it will be generated by\nscanning the source files with 'xgettext', and then the PO files are\nregenerated as a dependency. On the other hand, some maintainers want\nto keep the POT file unchanged during the development phase. So, even\nif a POT file is present and older than the source code, it won't be\nupdated automatically. You can manually update it with 'make\n$(DOMAIN).pot-update', and commit it at certain point.\n\nSpecial advices for particular version control systems:\n\n* Recent version control systems, Git for instance, ignore file's\ntimestamp. In that case, PO files can be accidentally updated even\nif a POT file is not updated. To prevent this, you can set\n'PODEPENDSONPOT' variable to 'no' in the 'Makevars' file and do\n'make update-po' manually.\n\n* Location comments such as '#: lib/error.c:116' are sometimes\nannoying, since these comments are volatile and may introduce\nunwanted change to the working copy when building. To mitigate\nthis, you can decide to omit those comments from the PO files in\nthe repository.\n\nThis is possible with the '--no-location' option of the 'msgmerge'\ncommand (1). The drawback is that, if the location information is\nneeded, translators have to recover the location comments by\nrunning 'msgmerge' again.\n\n---------- Footnotes ----------\n\n(1) you can also use it through the 'MSGMERGEOPTIONS' option from\n'Makevars'\n\nFile: gettext.info, Node: autopoint Invocation, Prev: Translations under Version Control, Up: Version Control Issues\n\n\nautopoint [OPTION]...\n\nThe 'autopoint' program copies standard gettext infrastructure files\ninto a source package. It extracts from a macro call of the form\n'AMGNUGETTEXTVERSION(VERSION)', found in the package's 'configure.in'\nor 'configure.ac' file, the gettext version used by the package, and\ncopies the infrastructure files belonging to this version into the\npackage.\n\nTo extract the latest available infrastructure which satisfies a\nversion requirement, then you can use the form\n'AMGNUGETTEXTREQUIREVERSION(VERSION)' instead. For example, if\ngettext 0.21 is installed on your system and '0.19.1' is requested, then\nthe infrastructure files of version 0.21 will be copied into a source\npackage.\n\n13.6.4.1 Options\n................\n\n'-f'\n'--force'\nForce overwriting of files that already exist.\n\n'-n'\n'--dry-run'\nPrint modifications but don't perform them. All file copying\nactions that 'autopoint' would normally execute are inhibited and\ninstead only listed on standard output.\n\n13.6.4.2 Informative output\n...........................\n\n'--help'\nDisplay this help and exit.\n\n'--version'\nOutput version information and exit.\n\n'autopoint' supports the GNU 'gettext' versions from 0.10.35 to the\ncurrent one, 0.21. In order to apply 'autopoint' to a package using a\n'gettext' version newer than 0.21, you need to install this same version\nof GNU 'gettext' at least.\n\nIn packages using GNU 'automake', an invocation of 'autopoint' should\nbe followed by invocations of 'aclocal' and then 'autoconf' and\n'autoheader'. The reason is that 'autopoint' installs some autoconf\nmacro files, which are used by 'aclocal' to create 'aclocal.m4', and the\nlatter is used by 'autoconf' to create the package's 'configure' script\nand by 'autoheader' to create the package's 'config.h.in' include file\ntemplate.\n\nThe name 'autopoint' is an abbreviation of 'auto-po-intl-m4'; in\nearlier versions, the tool copied or updated mostly files in the 'po',\n'intl', 'm4' directories.\n\nFile: gettext.info, Node: Release Management, Prev: Version Control Issues, Up: Maintainers\n" }, { "name": "13.7 Creating a Distribution Tarball", "content": "In projects that use GNU 'automake', the usual commands for creating\na distribution tarball, 'make dist' or 'make distcheck', automatically\nupdate the PO files as needed.\n\nIf GNU 'automake' is not used, the maintainer needs to perform this\nupdate before making a release:\n\n$ ./configure\n$ (cd po; make update-po)\n$ make distclean\n\nFile: gettext.info, Node: Installers, Next: Programming Languages, Prev: Maintainers, Up: Top\n" } ] }, "14 The Installer's and Distributor's View": { "content": "By default, packages fully using GNU 'gettext', internally, are\ninstalled in such a way as to allow translation of messages. At\nconfiguration time, those packages should automatically detect whether\nthe underlying host system already provides the GNU 'gettext' functions.\nIf not, the GNU 'gettext' library should be automatically prepared and\nused. Installers may use special options at configuration time for\nchanging this behavior. The command './configure\n--with-included-gettext' bypasses system 'gettext' to use the included\nGNU 'gettext' instead, while './configure --disable-nls' produces\nprograms totally unable to translate messages.\n\nInternationalized packages have usually many 'LL.po' files. Unless\ntranslations are disabled, all those available are installed together\nwith the package. However, the environment variable 'LINGUAS' may be\nset, prior to configuration, to limit the installed set. 'LINGUAS'\nshould then contain a space separated list of two-letter codes, stating\nwhich languages are allowed.\n\nFile: gettext.info, Node: Programming Languages, Next: Data Formats, Prev: Installers, Up: Top\n", "subsections": [] }, "15 Other Programming Languages": { "content": "While the presentation of 'gettext' focuses mostly on C and\nimplicitly applies to C++ as well, its scope is far broader than that:\nMany programming languages, scripting languages and other textual data\nlike GUI resources or package descriptions can make use of the gettext\napproach.\n\n* Menu:\n\n* Language Implementors:: The Language Implementor's View\n* Programmers for other Languages:: The Programmer's View\n* Translators for other Languages:: The Translator's View\n* Maintainers for other Languages:: The Maintainer's View\n* List of Programming Languages:: Individual Programming Languages\n\nFile: gettext.info, Node: Language Implementors, Next: Programmers for other Languages, Up: Programming Languages\n", "subsections": [ { "name": "15.1 The Language Implementor's View", "content": "All programming and scripting languages that have the notion of\nstrings are eligible to supporting 'gettext'. Supporting 'gettext'\nmeans the following:\n\n1. You should add to the language a syntax for translatable strings.\nIn principle, a function call of 'gettext' would do, but a\nshorthand syntax helps keeping the legibility of internationalized\nprograms. For example, in C we use the syntax '(\"string\")', and\nin GNU awk we use the shorthand '\"string\"'.\n\n2. You should arrange that evaluation of such a translatable string at\nruntime calls the 'gettext' function, or performs equivalent\nprocessing.\n\n3. Similarly, you should make the functions 'ngettext', 'dcgettext',\n'dcngettext' available from within the language. These functions\nare less often used, but are nevertheless necessary for particular\npurposes: 'ngettext' for correct plural handling, and 'dcgettext'\nand 'dcngettext' for obeying other locale-related environment\nvariables than 'LCMESSAGES', such as 'LCTIME' or 'LCMONETARY'.\nFor these latter functions, you need to make the 'LC*' constants,\navailable in the C header '', referenceable from within\nthe language, usually either as enumeration values or as strings.\n\n4. You should allow the programmer to designate a message domain,\neither by making the 'textdomain' function available from within\nthe language, or by introducing a magic variable called\n'TEXTDOMAIN'. Similarly, you should allow the programmer to\ndesignate where to search for message catalogs, by providing access\nto the 'bindtextdomain' function or -- on native Windows platforms --\nto the 'wbindtextdomain' function.\n\n5. You should either perform a 'setlocale (LCALL, \"\")' call during\nthe startup of your language runtime, or allow the programmer to do\nso. Remember that gettext will act as a no-op if the 'LCMESSAGES'\nand 'LCCTYPE' locale categories are not both set.\n\n6. A programmer should have a way to extract translatable strings from\na program into a PO file. The GNU 'xgettext' program is being\nextended to support very different programming languages. Please\ncontact the GNU 'gettext' maintainers to help them doing this. The\nGNU 'gettext' maintainers will need from you a formal description\nof the lexical structure of source files. It should answer the\nquestions:\n* What does a token look like?\n* What does a string literal look like? What escape characters\nexist inside a string?\n* What escape characters exist outside of strings? If Unicode\nescapes are supported, are they applied before or after\ntokenization?\n* What is the syntax for function calls? How are consecutive\narguments in the same function call separated?\n* What is the syntax for comments?\nBased on this description, the GNU 'gettext' maintainers can add\nsupport to 'xgettext'.\n\nIf the string extractor is best integrated into your language's\nparser, GNU 'xgettext' can function as a front end to your string\nextractor.\n\n7. The language's library should have a string formatting facility.\nAdditionally:\n1. There must be a way, in the format string, to denote the\narguments by a positional number or a name. This is needed\nbecause for some languages and some messages with more than\none substitutable argument, the translation will need to\noutput the substituted arguments in different order. *Note\nc-format Flag::.\n2. The syntax of format strings must be documented in a way that\ntranslators can understand. The GNU 'gettext' manual will be\nextended to include a pointer to this documentation.\nBased on this, the GNU 'gettext' maintainers can add a format\nstring equivalence checker to 'msgfmt', so that translators get\ntold immediately when they have made a mistake during the\ntranslation of a format string.\n\n8. If the language has more than one implementation, and not all of\nthe implementations use 'gettext', but the programs should be\nportable across implementations, you should provide a no-i18n\nemulation, that makes the other implementations accept programs\nwritten for yours, without actually translating the strings.\n\n9. To help the programmer in the task of marking translatable strings,\nwhich is sometimes performed using the Emacs PO mode (*note\nMarking::), you are welcome to contact the GNU 'gettext'\nmaintainers, so they can add support for your language to\n'po-mode.el'.\n\nOn the implementation side, two approaches are possible, with\ndifferent effects on portability and copyright:\n\n* You may link against GNU 'gettext' functions if they are found in\nthe C library. For example, an autoconf test for 'gettext()' and\n'ngettext()' will detect this situation. For the moment, this test\nwill succeed on GNU systems and on Solaris 11 platforms. No severe\ncopyright restrictions apply, except if you want to distribute\nstatically linked binaries.\n\n* You may emulate or reimplement the GNU 'gettext' functionality.\nThis has the advantage of full portability and no copyright\nrestrictions, but also the drawback that you have to reimplement\nthe GNU 'gettext' features (such as the 'LANGUAGE' environment\nvariable, the locale aliases database, the automatic charset\nconversion, and plural handling).\n\nFile: gettext.info, Node: Programmers for other Languages, Next: Translators for other Languages, Prev: Language Implementors, Up: Programming Languages\n" }, { "name": "15.2 The Programmer's View", "content": "For the programmer, the general procedure is the same as for the C\nlanguage. The Emacs PO mode marking supports other languages, and the\nGNU 'xgettext' string extractor recognizes other languages based on the\nfile extension or a command-line option. In some languages, 'setlocale'\nis not needed because it is already performed by the underlying language\nruntime.\n\nFile: gettext.info, Node: Translators for other Languages, Next: Maintainers for other Languages, Prev: Programmers for other Languages, Up: Programming Languages\n" }, { "name": "15.3 The Translator's View", "content": "The translator works exactly as in the C language case. The only\ndifference is that when translating format strings, she has to be aware\nof the language's particular syntax for positional arguments in format\nstrings.\n\n* Menu:\n\n* c-format:: C Format Strings\n* objc-format:: Objective C Format Strings\n* python-format:: Python Format Strings\n* java-format:: Java Format Strings\n* csharp-format:: C# Format Strings\n* javascript-format:: JavaScript Format Strings\n* scheme-format:: Scheme Format Strings\n* lisp-format:: Lisp Format Strings\n* elisp-format:: Emacs Lisp Format Strings\n* librep-format:: librep Format Strings\n* ruby-format:: Ruby Format Strings\n* sh-format:: Shell Format Strings\n* awk-format:: awk Format Strings\n* lua-format:: Lua Format Strings\n* object-pascal-format:: Object Pascal Format Strings\n* smalltalk-format:: Smalltalk Format Strings\n* qt-format:: Qt Format Strings\n* qt-plural-format:: Qt Plural Format Strings\n* kde-format:: KDE Format Strings\n* kde-kuit-format:: KUIT Format Strings\n* boost-format:: Boost Format Strings\n* tcl-format:: Tcl Format Strings\n* perl-format:: Perl Format Strings\n* php-format:: PHP Format Strings\n* gcc-internal-format:: GCC internal Format Strings\n* gfc-internal-format:: GFC internal Format Strings\n* ycp-format:: YCP Format Strings\n\nFile: gettext.info, Node: c-format, Next: objc-format, Up: Translators for other Languages\n\n\nC format strings are described in POSIX (IEEE P1003.1 2001), section\nXSH 3 fprintf(),\n.\nSee also the fprintf() manual page,\n,\n.\n\nAlthough format strings with positions that reorder arguments, such\nas\n\n\"Only %2$d bytes free on '%1$s'.\"\n\nwhich is semantically equivalent to\n\n\"'%s' has only %d bytes free.\"\n\nare a POSIX/XSI feature and not specified by ISO C 99, translators can\nrely on this reordering ability: On the few platforms where 'printf()',\n'fprintf()' etc. don't support this feature natively, 'libintl.a' or\n'libintl.so' provides replacement functions, and GNU ''\nactivates these replacement functions automatically.\n\nAs a special feature for Farsi (Persian) and maybe Arabic,\ntranslators can insert an 'I' flag into numeric format directives. For\nexample, the translation of '\"%d\"' can be '\"%Id\"'. The effect of this\nflag, on systems with GNU 'libc', is that in the output, the ASCII\ndigits are replaced with the 'outdigits' defined in the 'LCCTYPE'\nlocale category. On other systems, the 'gettext' function removes this\nflag, so that it has no effect.\n\nNote that the programmer should not put this flag into the\nuntranslated string. (Putting the 'I' format directive flag into an\nMSGID string would lead to undefined behaviour on platforms without\nglibc when NLS is disabled.)\n\nFile: gettext.info, Node: objc-format, Next: python-format, Prev: c-format, Up: Translators for other Languages\n\n\nObjective C format strings are like C format strings. They support\nan additional format directive: \"%@\", which when executed consumes an\nargument of type 'Object *'.\n\nFile: gettext.info, Node: python-format, Next: java-format, Prev: objc-format, Up: Translators for other Languages\n\n\nThere are two kinds of format strings in Python: those acceptable to\nthe Python built-in format operator '%', labelled as 'python-format',\nand those acceptable to the 'format' method of the 'str' object.\n\nPython '%' format strings are described in Python Library reference /\n5. Built-in Types / 5.6. Sequence Types /\n5.6.2. String Formatting Operations.\n.\n\nPython brace format strings are described in\nPEP 3101 - Advanced String Formatting,\n.\n\nFile: gettext.info, Node: java-format, Next: csharp-format, Prev: python-format, Up: Translators for other Languages\n\n\nThere are two kinds of format strings in Java: those acceptable to\nthe 'MessageFormat.format' function, labelled as 'java-format', and\nthose acceptable to the 'String.format' and 'PrintStream.printf'\nfunctions, labelled as 'java-printf-format'.\n\nJava format strings are described in the JDK documentation for class\n'java.text.MessageFormat',\n.\nSee also the ICU documentation\n.\n\nJava 'printf' format strings are described in the JDK documentation\nfor class 'java.util.Formatter',\n.\n\nFile: gettext.info, Node: csharp-format, Next: javascript-format, Prev: java-format, Up: Translators for other Languages\n\n\nC# format strings are described in the .NET documentation for class\n'System.String' and in\n.\n\nFile: gettext.info, Node: javascript-format, Next: scheme-format, Prev: csharp-format, Up: Translators for other Languages\n\n\nAlthough JavaScript specification itself does not define any format\nstrings, many JavaScript implementations provide printf-like functions.\n'xgettext' understands a set of common format strings used in popular\nJavaScript implementations including Gjs, Seed, and Node.JS. In such a\nformat string, a directive starts with '%' and is finished by a\nspecifier: '%' denotes a literal percent sign, 'c' denotes a character,\n's' denotes a string, 'b', 'd', 'o', 'x', 'X' denote an integer, 'f'\ndenotes floating-point number, 'j' denotes a JSON object.\n\nFile: gettext.info, Node: scheme-format, Next: lisp-format, Prev: javascript-format, Up: Translators for other Languages\n\n\nScheme format strings are documented in the SLIB manual, section\nFormat Specification.\n\nFile: gettext.info, Node: lisp-format, Next: elisp-format, Prev: scheme-format, Up: Translators for other Languages\n\n\nLisp format strings are described in the Common Lisp HyperSpec,\nchapter 22.3 Formatted Output,\n.\n\nFile: gettext.info, Node: elisp-format, Next: librep-format, Prev: lisp-format, Up: Translators for other Languages\n\n\nEmacs Lisp format strings are documented in the Emacs Lisp reference,\nsection Formatting Strings,\n.\nNote that as of version 21, XEmacs supports numbered argument\nspecifications in format strings while FSF Emacs doesn't.\n\nFile: gettext.info, Node: librep-format, Next: ruby-format, Prev: elisp-format, Up: Translators for other Languages\n\n\nlibrep format strings are documented in the librep manual, section\nFormatted Output,\n,\n.\n\nFile: gettext.info, Node: ruby-format, Next: sh-format, Prev: librep-format, Up: Translators for other Languages\n\n\nRuby format strings are described in the documentation of the Ruby\nfunctions 'format' and 'sprintf', in\n.\n\nThere are two kinds of format strings in Ruby:\n* Those that take a list of arguments without names. They support\nargument reordering by use of the '%N$' syntax. Note that if one\nargument uses this syntax, all must use this syntax.\n* Those that take a hash table, containing named arguments. The\nsyntax is '%'. Note that '%{NAME}' is equivalent to\n'%s'.\n\nFile: gettext.info, Node: sh-format, Next: awk-format, Prev: ruby-format, Up: Translators for other Languages\n\n\nShell format strings, as supported by GNU gettext and the 'envsubst'\nprogram, are strings with references to shell variables in the form\n'$VARIABLE' or '${VARIABLE}'. References of the form\n'${VARIABLE-DEFAULT}', '${VARIABLE:-DEFAULT}', '${VARIABLE=DEFAULT}',\n'${VARIABLE:=DEFAULT}', '${VARIABLE+REPLACEMENT}',\n'${VARIABLE:+REPLACEMENT}', '${VARIABLE?IGNORED}',\n'${VARIABLE:?IGNORED}', that would be valid inside shell scripts, are\nnot supported. The VARIABLE names must consist solely of alphanumeric\nor underscore ASCII characters, not start with a digit and be nonempty;\notherwise such a variable reference is ignored.\n\nFile: gettext.info, Node: awk-format, Next: lua-format, Prev: sh-format, Up: Translators for other Languages\n\n\nawk format strings are described in the gawk documentation, section\nPrintf, .\n\nFile: gettext.info, Node: lua-format, Next: object-pascal-format, Prev: awk-format, Up: Translators for other Languages\n\n\nLua format strings are described in the Lua reference manual, section\nString Manipulation,\n.\n\nFile: gettext.info, Node: object-pascal-format, Next: smalltalk-format, Prev: lua-format, Up: Translators for other Languages\n\n\nObject Pascal format strings are described in the documentation of\nthe Free Pascal runtime library, section Format,\n.\n\nFile: gettext.info, Node: smalltalk-format, Next: qt-format, Prev: object-pascal-format, Up: Translators for other Languages\n\n\nSmalltalk format strings are described in the GNU Smalltalk\ndocumentation, class 'CharArray', methods 'bindWith:' and\n'bindWithArguments:'.\n.\nIn summary, a directive starts with '%' and is followed by '%' or a\nnonzero digit ('1' to '9').\n\nFile: gettext.info, Node: qt-format, Next: qt-plural-format, Prev: smalltalk-format, Up: Translators for other Languages\n\n\nQt format strings are described in the documentation of the QString\nclass . In summary, a\ndirective consists of a '%' followed by a digit. The same directive\ncannot occur more than once in a format string.\n\nFile: gettext.info, Node: qt-plural-format, Next: kde-format, Prev: qt-format, Up: Translators for other Languages\n\n\nQt format strings are described in the documentation of the\nQObject::tr method . In\nsummary, the only allowed directive is '%n'.\n\nFile: gettext.info, Node: kde-format, Next: kde-kuit-format, Prev: qt-plural-format, Up: Translators for other Languages\n\n\nKDE 4 format strings are defined as follows: A directive consists of\na '%' followed by a non-zero decimal number. If a '%n' occurs in a\nformat strings, all of '%1', ..., '%(n-1)' must occur as well, except\npossibly one of them.\n\nFile: gettext.info, Node: kde-kuit-format, Next: boost-format, Prev: kde-format, Up: Translators for other Languages\n\n\nKUIT (KDE User Interface Text) is compatible with KDE 4 format\nstrings, while it also allows programmers to add semantic information to\na format string, through XML markup tags. For example, if the first\nformat directive in a string is a filename, programmers could indicate\nthat with a 'filename' tag, like '%1'.\n\nKUIT format strings are described in\n.\n\nFile: gettext.info, Node: boost-format, Next: tcl-format, Prev: kde-kuit-format, Up: Translators for other Languages\n\n\nBoost format strings are described in the documentation of the\n'boost::format' class, at\n. In summary, a\ndirective has either the same syntax as in a C format string, such as\n'%1$+5d', or may be surrounded by vertical bars, such as '%|1$+5d|' or\n'%|1$+5|', or consists of just an argument number between percent signs,\nsuch as '%1%'.\n\nFile: gettext.info, Node: tcl-format, Next: perl-format, Prev: boost-format, Up: Translators for other Languages\n\n\nTcl format strings are described in the 'format.n' manual page,\n.\n\nFile: gettext.info, Node: perl-format, Next: php-format, Prev: tcl-format, Up: Translators for other Languages\n\n\nThere are two kinds of format strings in Perl: those acceptable to\nthe Perl built-in function 'printf', labelled as 'perl-format', and\nthose acceptable to the 'libintl-perl' function 'x', labelled as\n'perl-brace-format'.\n\nPerl 'printf' format strings are described in the 'sprintf' section\nof 'man perlfunc'.\n\nPerl brace format strings are described in the\n'Locale::TextDomain(3pm)' manual page of the CPAN package libintl-perl.\nIn brief, Perl format uses placeholders put between braces ('{' and\n'}'). The placeholder must have the syntax of simple identifiers.\n\nFile: gettext.info, Node: php-format, Next: gcc-internal-format, Prev: perl-format, Up: Translators for other Languages\n\n\nPHP format strings are described in the documentation of the PHP\nfunction 'sprintf', in 'phpdoc/manual/function.sprintf.html' or\n.\n\nFile: gettext.info, Node: gcc-internal-format, Next: gfc-internal-format, Prev: php-format, Up: Translators for other Languages\n\n\nThese format strings are used inside the GCC sources. In such a\nformat string, a directive starts with '%', is optionally followed by a\nsize specifier 'l', an optional flag '+', another optional flag '#', and\nis finished by a specifier: '%' denotes a literal percent sign, 'c'\ndenotes a character, 's' denotes a string, 'i' and 'd' denote an\ninteger, 'o', 'u', 'x' denote an unsigned integer, '.*s' denotes a\nstring preceded by a width specification, 'H' denotes a 'locationt *'\npointer, 'D' denotes a general declaration, 'F' denotes a function\ndeclaration, 'T' denotes a type, 'A' denotes a function argument, 'C'\ndenotes a tree code, 'E' denotes an expression, 'L' denotes a\nprogramming language, 'O' denotes a binary operator, 'P' denotes a\nfunction parameter, 'Q' denotes an assignment operator, 'V' denotes a\nconst/volatile qualifier.\n\nFile: gettext.info, Node: gfc-internal-format, Next: ycp-format, Prev: gcc-internal-format, Up: Translators for other Languages\n\n\nThese format strings are used inside the GNU Fortran Compiler\nsources, that is, the Fortran frontend in the GCC sources. In such a\nformat string, a directive starts with '%' and is finished by a\nspecifier: '%' denotes a literal percent sign, 'C' denotes the current\nsource location, 'L' denotes a source location, 'c' denotes a character,\n's' denotes a string, 'i' and 'd' denote an integer, 'u' denotes an\nunsigned integer. 'i', 'd', and 'u' may be preceded by a size specifier\n'l'.\n\nFile: gettext.info, Node: ycp-format, Prev: gfc-internal-format, Up: Translators for other Languages\n\n\nYCP sformat strings are described in the libycp documentation\n. In summary, a\ndirective starts with '%' and is followed by '%' or a nonzero digit ('1'\nto '9').\n\nFile: gettext.info, Node: Maintainers for other Languages, Next: List of Programming Languages, Prev: Translators for other Languages, Up: Programming Languages\n" }, { "name": "15.4 The Maintainer's View", "content": "For the maintainer, the general procedure differs from the C language\ncase:\n\n* If only a single programming language is used, the\n'XGETTEXTOPTIONS' variable in 'po/Makevars' (*note po/Makevars::)\nshould be adjusted to match the 'xgettext' options for that\nparticular programming language. If the package uses more than one\nprogramming language with 'gettext' support, it becomes necessary\nto change the POT file construction rule in 'po/Makefile.in.in'.\nIt is recommended to make one 'xgettext' invocation per programming\nlanguage, each with the options appropriate for that language, and\nto combine the resulting files using 'msgcat'.\n\nFile: gettext.info, Node: List of Programming Languages, Prev: Maintainers for other Languages, Up: Programming Languages\n" }, { "name": "15.5 Individual Programming Languages", "content": "* Menu:\n\n* C:: C, C++, Objective C\n* Python:: Python\n* Java:: Java\n* C#:: C#\n* JavaScript:: JavaScript\n* Scheme:: GNU guile - Scheme\n* Common Lisp:: GNU clisp - Common Lisp\n* clisp C:: GNU clisp C sources\n* Emacs Lisp:: Emacs Lisp\n* librep:: librep\n* Ruby:: Ruby\n* sh:: sh - Shell Script\n* bash:: bash - Bourne-Again Shell Script\n* gawk:: GNU awk\n* Lua:: Lua\n* Pascal:: Pascal - Free Pascal Compiler\n* Smalltalk:: GNU Smalltalk\n* Vala:: Vala\n* wxWidgets:: wxWidgets library\n* Tcl:: Tcl - Tk's scripting language\n* Perl:: Perl\n* PHP:: PHP Hypertext Preprocessor\n* Pike:: Pike\n* GCC-source:: GNU Compiler Collection sources\n* YCP:: YCP - YaST2 scripting language\n\nFile: gettext.info, Node: C, Next: Python, Up: List of Programming Languages\n\n\nRPMs\ngcc, gpp, gobjc, glibc, gettext\n\nUbuntu packages\ngcc, g++, gobjc, libc6-dev, libasprintf-dev\n\nFile extension\nFor C: 'c', 'h'.\nFor C++: 'C', 'c++', 'cc', 'cxx', 'cpp', 'hpp'.\nFor Objective C: 'm'.\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n'(\"abc\")'\n\ngettext/ngettext functions\n'gettext', 'dgettext', 'dcgettext', 'ngettext', 'dngettext',\n'dcngettext'\n\ntextdomain\n'textdomain' function\n\nbindtextdomain\n'bindtextdomain' and 'wbindtextdomain' functions\n\nsetlocale\nProgrammer must call 'setlocale (LCALL, \"\")'\n\nPrerequisite\n'#include '\n'#include '\n'#define (string) gettext (string)'\n\nUse or emulate GNU gettext\nUse\n\nExtractor\n'xgettext -k'\n\nFormatting with positions\n'fprintf \"%2$d %1$d\"'\nIn C++: 'autosprintf \"%2$d %1$d\"' (*note Introduction:\n(autosprintf)Top.)\n\nPortability\nautoconf (gettext.m4) and #if ENABLENLS\n\npo-mode marking\nyes\n\nThe following examples are available in the 'examples' directory:\n'hello-c', 'hello-c-gnome', 'hello-c++', 'hello-c++-qt',\n'hello-c++-kde', 'hello-c++-gnome', 'hello-c++-wxwidgets', 'hello-objc',\n'hello-objc-gnustep', 'hello-objc-gnome'.\n\nFile: gettext.info, Node: Python, Next: Java, Prev: C, Up: List of Programming Languages\n\n\nRPMs\npython\n\nUbuntu packages\npython\n\nFile extension\n'py'\n\nString syntax\n''abc'', 'u'abc'', 'r'abc'', 'ur'abc'',\n'\"abc\"', 'u\"abc\"', 'r\"abc\"', 'ur\"abc\"',\n''''abc'''', 'u'''abc'''', 'r'''abc'''', 'ur'''abc'''',\n'\"\"\"abc\"\"\"', 'u\"\"\"abc\"\"\"', 'r\"\"\"abc\"\"\"', 'ur\"\"\"abc\"\"\"'\n\ngettext shorthand\n'('abc')' etc.\n\ngettext/ngettext functions\n'gettext.gettext', 'gettext.dgettext', 'gettext.ngettext',\n'gettext.dngettext', also 'ugettext', 'ungettext'\n\ntextdomain\n'gettext.textdomain' function, or 'gettext.install(DOMAIN)'\nfunction\n\nbindtextdomain\n'gettext.bindtextdomain' function, or\n'gettext.install(DOMAIN,LOCALEDIR)' function\n\nsetlocale\nnot used by the gettext emulation\n\nPrerequisite\n'import gettext'\n\nUse or emulate GNU gettext\nemulate\n\nExtractor\n'xgettext'\n\nFormatting with positions\n''...%(ident)d...' % { 'ident': value }'\n\nPortability\nfully portable\n\npo-mode marking\n--\n\nAn example is available in the 'examples' directory: 'hello-python'.\n\nA note about format strings: Python supports format strings with\nunnamed arguments, such as ''...%d...'', and format strings with named\narguments, such as ''...%(ident)d...''. The latter are preferable for\ninternationalized programs, for two reasons:\n\n* When a format string takes more than one argument, the translator\ncan provide a translation that uses the arguments in a different\norder, if the format string uses named arguments. For example, the\ntranslator can reformulate\n\"'%(volume)s' has only %(freespace)d bytes free.\"\nto\n\"Only %(freespace)d bytes free on '%(volume)s'.\"\nAdditionally, the identifiers also provide some context to the\ntranslator.\n\n* In the context of plural forms, the format string used for the\nsingular form does not use the numeric argument in many languages.\nEven in English, one prefers to write '\"one hour\"' instead of '\"1\nhour\"'. Omitting individual arguments from format strings like\nthis is only possible with the named argument syntax. (With\nunnamed arguments, Python - unlike C - verifies that the format\nstring uses all supplied arguments.)\n\nFile: gettext.info, Node: Java, Next: C#, Prev: Python, Up: List of Programming Languages\n\n\nRPMs\njava, java2\n\nUbuntu packages\ndefault-jdk\n\nFile extension\n'java'\n\nString syntax\n\"abc\", \"\"\"text block\"\"\"\n\ngettext shorthand\ni18n(\"abc\")\n\ngettext/ngettext functions\n'GettextResource.gettext', 'GettextResource.ngettext',\n'GettextResource.pgettext', 'GettextResource.npgettext'\n\ntextdomain\n--, use 'ResourceBundle.getResource' instead\n\nbindtextdomain\n--, use CLASSPATH instead\n\nsetlocale\nautomatic\n\nPrerequisite\n--\n\nUse or emulate GNU gettext\n--, uses a Java specific message catalog format\n\nExtractor\n'xgettext -ki18n'\n\nFormatting with positions\n'MessageFormat.format \"{1,number} {0,number}\"' or 'String.format\n\"%2$d %1$d\"'\n\nPortability\nfully portable\n\npo-mode marking\n--\n\nBefore marking strings as internationalizable, uses of the string\nconcatenation operator need to be converted to 'MessageFormat'\napplications. For example, '\"file \"+filename+\" not found\"' becomes\n'MessageFormat.format(\"file {0} not found\", new Object[] { filename })'.\nOnly after this is done, can the strings be marked and extracted.\n\nGNU gettext uses the native Java internationalization mechanism,\nnamely 'ResourceBundle's. There are two formats of 'ResourceBundle's:\n'.properties' files and '.class' files. The '.properties' format is a\ntext file which the translators can directly edit, like PO files, but\nwhich doesn't support plural forms. Whereas the '.class' format is\ncompiled from '.java' source code and can support plural forms (provided\nit is accessed through an appropriate API, see below).\n\nTo convert a PO file to a '.properties' file, the 'msgcat' program\ncan be used with the option '--properties-output'. To convert a\n'.properties' file back to a PO file, the 'msgcat' program can be used\nwith the option '--properties-input'. All the tools that manipulate PO\nfiles can work with '.properties' files as well, if given the\n'--properties-input' and/or '--properties-output' option.\n\nTo convert a PO file to a ResourceBundle class, the 'msgfmt' program\ncan be used with the option '--java' or '--java2'. To convert a\nResourceBundle back to a PO file, the 'msgunfmt' program can be used\nwith the option '--java'.\n\nTwo different programmatic APIs can be used to access\nResourceBundles. Note that both APIs work with all kinds of\nResourceBundles, whether GNU gettext generated classes, or other\n'.class' or '.properties' files.\n\n1. The 'java.util.ResourceBundle' API.\n\nIn particular, its 'getString' function returns a string\ntranslation. Note that a missing translation yields a\n'MissingResourceException'.\n\nThis has the advantage of being the standard API. And it does not\nrequire any additional libraries, only the 'msgcat' generated\n'.properties' files or the 'msgfmt' generated '.class' files. But\nit cannot do plural handling, even if the resource was generated by\n'msgfmt' from a PO file with plural handling.\n\n2. The 'gnu.gettext.GettextResource' API.\n\nReference documentation in Javadoc 1.1 style format is in the\njavadoc2 directory (javadoc2/index.html).\n\nIts 'gettext' function returns a string translation. Note that\nwhen a translation is missing, the MSGID argument is returned\nunchanged.\n\nThis has the advantage of having the 'ngettext' function for plural\nhandling and the 'pgettext' and 'npgettext' for strings constraint\nto a particular context.\n\nTo use this API, one needs the 'libintl.jar' file which is part of\nthe GNU gettext package and distributed under the LGPL.\n\nFour examples, using the second API, are available in the 'examples'\ndirectory: 'hello-java', 'hello-java-awt', 'hello-java-swing',\n'hello-java-qtjambi'.\n\nNow, to make use of the API and define a shorthand for 'getString',\nthere are three idioms that you can choose from:\n\n* (This one assumes Java 1.5 or newer.) In a unique class of your\nproject, say 'Util', define a static variable holding the\n'ResourceBundle' instance and the shorthand:\n\nprivate static ResourceBundle myResources =\nResourceBundle.getBundle(\"domain-name\");\npublic static String i18n(String s) {\nreturn myResources.getString(s);\n}\n\nAll classes containing internationalized strings then contain\n\nimport static Util.i18n;\n\nand the shorthand is used like this:\n\nSystem.out.println(i18n(\"Operation completed.\"));\n\n* In a unique class of your project, say 'Util', define a static\nvariable holding the 'ResourceBundle' instance:\n\npublic static ResourceBundle myResources =\nResourceBundle.getBundle(\"domain-name\");\n\nAll classes containing internationalized strings then contain\n\nprivate static ResourceBundle res = Util.myResources;\nprivate static String i18n(String s) { return res.getString(s); }\n\nand the shorthand is used like this:\n\nSystem.out.println(i18n(\"Operation completed.\"));\n\n* You add a class with a very short name, say 'S', containing just\nthe definition of the resource bundle and of the shorthand:\n\npublic class S {\npublic static ResourceBundle myResources =\nResourceBundle.getBundle(\"domain-name\");\npublic static String i18n(String s) {\nreturn myResources.getString(s);\n}\n}\n\nand the shorthand is used like this:\n\nSystem.out.println(S.i18n(\"Operation completed.\"));\n\nWhich of the three idioms you choose, will depend on whether your\nproject requires portability to Java versions prior to Java 1.5 and, if\nso, whether copying two lines of codes into every class is more\nacceptable in your project than a class with a single-letter name.\n\nFile: gettext.info, Node: C#, Next: JavaScript, Prev: Java, Up: List of Programming Languages\n\n\nRPMs\nmono\n\nUbuntu packages\nmono-mcs\n\nFile extension\n'cs'\n\nString syntax\n'\"abc\"', '@\"abc\"'\n\ngettext shorthand\n(\"abc\")\n\ngettext/ngettext functions\n'GettextResourceManager.GetString',\n'GettextResourceManager.GetPluralString'\n'GettextResourceManager.GetParticularString'\n'GettextResourceManager.GetParticularPluralString'\n\ntextdomain\n'new GettextResourceManager(domain)'\n\nbindtextdomain\n--, compiled message catalogs are located in subdirectories of the\ndirectory containing the executable\n\nsetlocale\nautomatic\n\nPrerequisite\n--\n\nUse or emulate GNU gettext\n--, uses a C# specific message catalog format\n\nExtractor\n'xgettext -k'\n\nFormatting with positions\n'String.Format \"{1} {0}\"'\n\nPortability\nfully portable\n\npo-mode marking\n--\n\nBefore marking strings as internationalizable, uses of the string\nconcatenation operator need to be converted to 'String.Format'\ninvocations. For example, '\"file \"+filename+\" not found\"' becomes\n'String.Format(\"file {0} not found\", filename)'. Only after this is\ndone, can the strings be marked and extracted.\n\nGNU gettext uses the native C#/.NET internationalization mechanism,\nnamely the classes 'ResourceManager' and 'ResourceSet'. Applications\nuse the 'ResourceManager' methods to retrieve the native language\ntranslation of strings. An instance of 'ResourceSet' is the in-memory\nrepresentation of a message catalog file. The 'ResourceManager' loads\nand accesses 'ResourceSet' instances as needed to look up the\ntranslations.\n\nThere are two formats of 'ResourceSet's that can be directly loaded\nby the C# runtime: '.resources' files and '.dll' files.\n\n* The '.resources' format is a binary file usually generated through\nthe 'resgen' or 'monoresgen' utility, but which doesn't support\nplural forms. '.resources' files can also be embedded in .NET\n'.exe' files. This only affects whether a file system access is\nperformed to load the message catalog; it doesn't affect the\ncontents of the message catalog.\n\n* On the other hand, the '.dll' format is a binary file that is\ncompiled from '.cs' source code and can support plural forms\n(provided it is accessed through the GNU gettext API, see below).\n\nNote that these .NET '.dll' and '.exe' files are not tied to a\nparticular platform; their file format and GNU gettext for C# can be\nused on any platform.\n\nTo convert a PO file to a '.resources' file, the 'msgfmt' program can\nbe used with the option '--csharp-resources'. To convert a '.resources'\nfile back to a PO file, the 'msgunfmt' program can be used with the\noption '--csharp-resources'. You can also, in some cases, use the\n'monoresgen' program (from the 'mono'/'mcs' package). This program can\nalso convert a '.resources' file back to a PO file. But beware: as of\nthis writing (January 2004), the 'monoresgen' converter is quite buggy.\n\nTo convert a PO file to a '.dll' file, the 'msgfmt' program can be\nused with the option '--csharp'. The result will be a '.dll' file\ncontaining a subclass of 'GettextResourceSet', which itself is a\nsubclass of 'ResourceSet'. To convert a '.dll' file containing a\n'GettextResourceSet' subclass back to a PO file, the 'msgunfmt' program\ncan be used with the option '--csharp'.\n\nThe advantages of the '.dll' format over the '.resources' format are:\n\n1. Freedom to localize: Users can add their own translations to an\napplication after it has been built and distributed. Whereas when\nthe programmer uses a 'ResourceManager' constructor provided by the\nsystem, the set of '.resources' files for an application must be\nspecified when the application is built and cannot be extended\nafterwards.\n\n2. Plural handling: A message catalog in '.dll' format supports the\nplural handling function 'GetPluralString'. Whereas '.resources'\nfiles can only contain data and only support lookups that depend on\na single string.\n\n3. Context handling: A message catalog in '.dll' format supports the\nquery-with-context functions 'GetParticularString' and\n'GetParticularPluralString'. Whereas '.resources' files can only\ncontain data and only support lookups that depend on a single\nstring.\n\n4. The 'GettextResourceManager' that loads the message catalogs in\n'.dll' format also provides for inheritance on a per-message basis.\nFor example, in Austrian ('deAT') locale, translations from the\nGerman ('de') message catalog will be used for messages not found\nin the Austrian message catalog. This has the consequence that the\nAustrian translators need only translate those few messages for\nwhich the translation into Austrian differs from the German one.\nWhereas when working with '.resources' files, each message catalog\nmust provide the translations of all messages by itself.\n\n5. The 'GettextResourceManager' that loads the message catalogs in\n'.dll' format also provides for a fallback: The English MSGID is\nreturned when no translation can be found. Whereas when working\nwith '.resources' files, a language-neutral '.resources' file must\nexplicitly be provided as a fallback.\n\nOn the side of the programmatic APIs, the programmer can use either\nthe standard 'ResourceManager' API and the GNU 'GettextResourceManager'\nAPI. The latter is an extension of the former, because\n'GettextResourceManager' is a subclass of 'ResourceManager'.\n\n1. The 'System.Resources.ResourceManager' API.\n\nThis API works with resources in '.resources' format.\n\nThe creation of the 'ResourceManager' is done through\nnew ResourceManager(domainname, Assembly.GetExecutingAssembly())\n\nThe 'GetString' function returns a string's translation. Note that\nthis function returns null when a translation is missing (i.e. not\neven found in the fallback resource file).\n\n2. The 'GNU.Gettext.GettextResourceManager' API.\n\nThis API works with resources in '.dll' format.\n\nReference documentation is in the csharpdoc directory\n(csharpdoc/index.html).\n\nThe creation of the 'ResourceManager' is done through\nnew GettextResourceManager(domainname)\n\nThe 'GetString' function returns a string's translation. Note that\nwhen a translation is missing, the MSGID argument is returned\nunchanged.\n\nThe 'GetPluralString' function returns a string translation with\nplural handling, like the 'ngettext' function in C.\n\nThe 'GetParticularString' function returns a string's translation,\nspecific to a particular context, like the 'pgettext' function in\nC. Note that when a translation is missing, the MSGID argument is\nreturned unchanged.\n\nThe 'GetParticularPluralString' function returns a string\ntranslation, specific to a particular context, with plural\nhandling, like the 'npgettext' function in C.\n\nTo use this API, one needs the 'GNU.Gettext.dll' file which is part\nof the GNU gettext package and distributed under the LGPL.\n\nYou can also mix both approaches: use the\n'GNU.Gettext.GettextResourceManager' constructor, but otherwise use only\nthe 'ResourceManager' type and only the 'GetString' method. This is\nappropriate when you want to profit from the tools for PO files, but\ndon't want to change an existing source code that uses 'ResourceManager'\nand don't (yet) need the 'GetPluralString' method.\n\nTwo examples, using the second API, are available in the 'examples'\ndirectory: 'hello-csharp', 'hello-csharp-forms'.\n\nNow, to make use of the API and define a shorthand for 'GetString',\nthere are two idioms that you can choose from:\n\n* In a unique class of your project, say 'Util', define a static\nvariable holding the 'ResourceManager' instance:\n\npublic static GettextResourceManager MyResourceManager =\nnew GettextResourceManager(\"domain-name\");\n\nAll classes containing internationalized strings then contain\n\nprivate static GettextResourceManager Res = Util.MyResourceManager;\nprivate static String (String s) { return Res.GetString(s); }\n\nand the shorthand is used like this:\n\nConsole.WriteLine((\"Operation completed.\"));\n\n* You add a class with a very short name, say 'S', containing just\nthe definition of the resource manager and of the shorthand:\n\npublic class S {\npublic static GettextResourceManager MyResourceManager =\nnew GettextResourceManager(\"domain-name\");\npublic static String (String s) {\nreturn MyResourceManager.GetString(s);\n}\n}\n\nand the shorthand is used like this:\n\nConsole.WriteLine(S.(\"Operation completed.\"));\n\nWhich of the two idioms you choose, will depend on whether copying\ntwo lines of codes into every class is more acceptable in your project\nthan a class with a single-letter name.\n\nFile: gettext.info, Node: JavaScript, Next: Scheme, Prev: C#, Up: List of Programming Languages\n\n\nRPMs\njs\n\nUbuntu packages\ngjs\n\nFile extension\n'js'\n\nString syntax\n\n* '\"abc\"'\n\n* ''abc''\n\n* '`abc`'\n\ngettext shorthand\n'(\"abc\")'\n\ngettext/ngettext functions\n'gettext', 'dgettext', 'dcgettext', 'ngettext', 'dngettext'\n\ntextdomain\n'textdomain' function\n\nbindtextdomain\n'bindtextdomain' function\n\nsetlocale\nautomatic\n\nPrerequisite\n--\n\nUse or emulate GNU gettext\nuse, or emulate\n\nExtractor\n'xgettext'\n\nFormatting with positions\n--\n\nPortability\nOn platforms without gettext, the functions are not available.\n\npo-mode marking\n--\n\nFile: gettext.info, Node: Scheme, Next: Common Lisp, Prev: JavaScript, Up: List of Programming Languages\n\n\nRPMs\nguile\n\nUbuntu packages\nguile-2.0\n\nFile extension\n'scm'\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n'( \"abc\")', '\"abc\"' (GIMP script-fu extension)\n\ngettext/ngettext functions\n'gettext', 'ngettext'\n\ntextdomain\n'textdomain'\n\nbindtextdomain\n'bindtextdomain'\n\nsetlocale\n'(catch #t (lambda () (setlocale LCALL \"\")) (lambda args #f))'\n\nPrerequisite\n'(use-modules (ice-9 format))'\n\nUse or emulate GNU gettext\nuse\n\nExtractor\n'xgettext -k'\n\nFormatting with positions\n--\n\nPortability\nOn platforms without gettext, no translation.\n\npo-mode marking\n--\n\nAn example is available in the 'examples' directory: 'hello-guile'.\n\nFile: gettext.info, Node: Common Lisp, Next: clisp C, Prev: Scheme, Up: List of Programming Languages\n\n\nRPMs\nclisp 2.28 or newer\n\nUbuntu packages\nclisp\n\nFile extension\n'lisp'\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n'( \"abc\")', '(ENGLISH \"abc\")'\n\ngettext/ngettext functions\n'i18n:gettext', 'i18n:ngettext'\n\ntextdomain\n'i18n:textdomain'\n\nbindtextdomain\n'i18n:textdomaindir'\n\nsetlocale\nautomatic\n\nPrerequisite\n--\n\nUse or emulate GNU gettext\nuse\n\nExtractor\n'xgettext -k -kENGLISH'\n\nFormatting with positions\n'format \"~1@*~D ~0@*~D\"'\n\nPortability\nOn platforms without gettext, no translation.\n\npo-mode marking\n--\n\nAn example is available in the 'examples' directory: 'hello-clisp'.\n\nFile: gettext.info, Node: clisp C, Next: Emacs Lisp, Prev: Common Lisp, Up: List of Programming Languages\n\n\nRPMs\nclisp\n\nUbuntu packages\nclisp\n\nFile extension\n'd'\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n'ENGLISH ? \"abc\" : \"\"'\n'GETTEXT(\"abc\")'\n'GETTEXTL(\"abc\")'\n\ngettext/ngettext functions\n'clgettext', 'clgettextl'\n\ntextdomain\n--\n\nbindtextdomain\n--\n\nsetlocale\nautomatic\n\nPrerequisite\n'#include \"lispbibl.c\"'\n\nUse or emulate GNU gettext\nuse\n\nExtractor\n'clisp-xgettext'\n\nFormatting with positions\n'fprintf \"%2$d %1$d\"'\n\nPortability\nOn platforms without gettext, no translation.\n\npo-mode marking\n--\n\nFile: gettext.info, Node: Emacs Lisp, Next: librep, Prev: clisp C, Up: List of Programming Languages\n\n\nRPMs\nemacs, xemacs\n\nUbuntu packages\nemacs, xemacs21\n\nFile extension\n'el'\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n'(\"abc\")'\n\ngettext/ngettext functions\n'gettext', 'dgettext' (xemacs only)\n\ntextdomain\n'domain' special form (xemacs only)\n\nbindtextdomain\n'bind-text-domain' function (xemacs only)\n\nsetlocale\nautomatic\n\nPrerequisite\n--\n\nUse or emulate GNU gettext\nuse\n\nExtractor\n'xgettext'\n\nFormatting with positions\n'format \"%2$d %1$d\"'\n\nPortability\nOnly XEmacs. Without 'I18N3' defined at build time, no\ntranslation.\n\npo-mode marking\n--\n\nFile: gettext.info, Node: librep, Next: Ruby, Prev: Emacs Lisp, Up: List of Programming Languages\n\n\nRPMs\nlibrep 0.15.3 or newer\n\nUbuntu packages\nlibrep16\n\nFile extension\n'jl'\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n'(\"abc\")'\n\ngettext/ngettext functions\n'gettext'\n\ntextdomain\n'textdomain' function\n\nbindtextdomain\n'bindtextdomain' function\n\nsetlocale\n--\n\nPrerequisite\n'(require 'rep.i18n.gettext)'\n\nUse or emulate GNU gettext\nuse\n\nExtractor\n'xgettext'\n\nFormatting with positions\n'format \"%2$d %1$d\"'\n\nPortability\nOn platforms without gettext, no translation.\n\npo-mode marking\n--\n\nAn example is available in the 'examples' directory: 'hello-librep'.\n\nFile: gettext.info, Node: Ruby, Next: sh, Prev: librep, Up: List of Programming Languages\n\n\nRPMs\nruby, ruby-gettext\n\nUbuntu packages\nruby, ruby-gettext\n\nFile extension\n'rb'\n\nString syntax\n'\"abc\"', ''abc'', '%q/abc/' etc., '%q(abc)', '%q[abc]', '%q{abc}'\n\ngettext shorthand\n'(\"abc\")'\n\ngettext/ngettext functions\n'gettext', 'ngettext'\n\ntextdomain\n--\n\nbindtextdomain\n'bindtextdomain' function\n\nsetlocale\n--\n\nPrerequisite\n'require 'gettext'' 'include GetText'\n\nUse or emulate GNU gettext\nemulate\n\nExtractor\n'xgettext'\n\nFormatting with positions\n'sprintf(\"%2$d %1$d\", x, y)'\n'\"%{new} replaces %{old}\" % {:old => oldvalue, :new => newvalue}'\n\nPortability\nfully portable\n\npo-mode marking\n--\n\nFile: gettext.info, Node: sh, Next: bash, Prev: Ruby, Up: List of Programming Languages\n\n\nRPMs\nbash, gettext\n\nUbuntu packages\nbash, gettext-base\n\nFile extension\n'sh'\n\nString syntax\n'\"abc\"', ''abc'', 'abc'\n\ngettext shorthand\n'\"`gettext \\\"abc\\\"`\"'\n\ngettext/ngettext functions\n'gettext', 'ngettext' programs\n'evalgettext', 'evalngettext', 'evalpgettext', 'evalnpgettext'\nshell functions\n\ntextdomain\nenvironment variable 'TEXTDOMAIN'\n\nbindtextdomain\nenvironment variable 'TEXTDOMAINDIR'\n\nsetlocale\nautomatic\n\nPrerequisite\n'. gettext.sh'\n\nUse or emulate GNU gettext\nuse\n\nExtractor\n'xgettext'\n\nFormatting with positions\n--\n\nPortability\nfully portable\n\npo-mode marking\n--\n\nAn example is available in the 'examples' directory: 'hello-sh'.\n\n* Menu:\n\n* Preparing Shell Scripts:: Preparing Shell Scripts for Internationalization\n* gettext.sh:: Contents of 'gettext.sh'\n* gettext Invocation:: Invoking the 'gettext' program\n* ngettext Invocation:: Invoking the 'ngettext' program\n* envsubst Invocation:: Invoking the 'envsubst' program\n* evalgettext Invocation:: Invoking the 'evalgettext' function\n* evalngettext Invocation:: Invoking the 'evalngettext' function\n* evalpgettext Invocation:: Invoking the 'evalpgettext' function\n* evalnpgettext Invocation:: Invoking the 'evalnpgettext' function\n\nFile: gettext.info, Node: Preparing Shell Scripts, Next: gettext.sh, Up: sh\n\n15.5.12.1 Preparing Shell Scripts for Internationalization\n..........................................................\n\nPreparing a shell script for internationalization is conceptually\nsimilar to the steps described in *note Sources::. The concrete steps\nfor shell scripts are as follows.\n\n1. Insert the line\n\n. gettext.sh\n\nnear the top of the script. 'gettext.sh' is a shell function\nlibrary that provides the functions 'evalgettext' (see *note\nevalgettext Invocation::), 'evalngettext' (see *note\nevalngettext Invocation::), 'evalpgettext' (see *note\nevalpgettext Invocation::), and 'evalnpgettext' (see *note\nevalnpgettext Invocation::). You have to ensure that 'gettext.sh'\ncan be found in the 'PATH'.\n\n2. Set and export the 'TEXTDOMAIN' and 'TEXTDOMAINDIR' environment\nvariables. Usually 'TEXTDOMAIN' is the package or program name,\nand 'TEXTDOMAINDIR' is the absolute pathname corresponding to\n'$prefix/share/locale', where '$prefix' is the installation\nlocation.\n\nTEXTDOMAIN=@PACKAGE@\nexport TEXTDOMAIN\nTEXTDOMAINDIR=@LOCALEDIR@\nexport TEXTDOMAINDIR\n\n3. Prepare the strings for translation, as described in *note\nPreparing Strings::.\n\n4. Simplify translatable strings so that they don't contain command\nsubstitution ('\"`...`\"' or '\"$(...)\"'), variable access with\ndefaulting (like '${VARIABLE-DEFAULT}'), access to positional\narguments (like '$0', '$1', ...) or highly volatile shell\nvariables (like '$?'). This can always be done through simple\nlocal code restructuring. For example,\n\necho \"Usage: $0 [OPTION] FILE...\"\n\nbecomes\n\nprogramname=$0\necho \"Usage: $programname [OPTION] FILE...\"\n\nSimilarly,\n\necho \"Remaining files: `ls | wc -l`\"\n\nbecomes\n\nfilecount=\"`ls | wc -l`\"\necho \"Remaining files: $filecount\"\n\n5. For each translatable string, change the output command 'echo' or\n'$echo' to 'gettext' (if the string contains no references to shell\nvariables) or to 'evalgettext' (if it refers to shell variables),\nfollowed by a no-argument 'echo' command (to account for the\nterminating newline). Similarly, for cases with plural handling,\nreplace a conditional 'echo' command with an invocation of\n'ngettext' or 'evalngettext', followed by a no-argument 'echo'\ncommand.\n\nWhen doing this, you also need to add an extra backslash before the\ndollar sign in references to shell variables, so that the\n'evalgettext' function receives the translatable string before the\nvariable values are substituted into it. For example,\n\necho \"Remaining files: $filecount\"\n\nbecomes\n\nevalgettext \"Remaining files: \\$filecount\"; echo\n\nIf the output command is not 'echo', you can make it use 'echo'\nnevertheless, through the use of backquotes. However, note that\ninside backquotes, backslashes must be doubled to be effective\n(because the backquoting eats one level of backslashes). For\nexample, assuming that 'error' is a shell function that signals an\nerror,\n\nerror \"file not found: $filename\"\n\nis first transformed into\n\nerror \"`echo \\\"file not found: \\$filename\\\"`\"\n\nwhich then becomes\n\nerror \"`evalgettext \\\"file not found: \\\\\\$filename\\\"`\"\n\nFile: gettext.info, Node: gettext.sh, Next: gettext Invocation, Prev: Preparing Shell Scripts, Up: sh\n\n15.5.12.2 Contents of 'gettext.sh'\n..................................\n\n'gettext.sh', contained in the run-time package of GNU gettext,\nprovides the following:\n\n* $echo The variable 'echo' is set to a command that outputs its\nfirst argument and a newline, without interpreting backslashes in\nthe argument string.\n\n* evalgettext See *note evalgettext Invocation::.\n\n* evalngettext See *note evalngettext Invocation::.\n\n* evalpgettext See *note evalpgettext Invocation::.\n\n* evalnpgettext See *note evalnpgettext Invocation::.\n\nFile: gettext.info, Node: gettext Invocation, Next: ngettext Invocation, Prev: gettext.sh, Up: sh\n\n15.5.12.3 Invoking the 'gettext' program\n........................................\n\ngettext [OPTION] [[TEXTDOMAIN] MSGID]\ngettext [OPTION] -s [MSGID]...\n\nThe 'gettext' program displays the native language translation of a\ntextual message.\n\n*Arguments*\n\n'-c CONTEXT'\n'--context=CONTEXT'\nSpecify the context for the messages to be translated. See *note\nContexts:: for details.\n\n'-d TEXTDOMAIN'\n'--domain=TEXTDOMAIN'\nRetrieve translated messages from TEXTDOMAIN. Usually a TEXTDOMAIN\ncorresponds to a package, a program, or a module of a program.\n\n'-e'\nEnable expansion of some escape sequences. This option is for\ncompatibility with the 'echo' program or shell built-in. The\nescape sequences '\\a', '\\b', '\\c', '\\f', '\\n', '\\r', '\\t', '\\v',\n'\\\\', and '\\' followed by one to three octal digits, are\ninterpreted like the System V 'echo' program did.\n\n'-E'\nThis option is only for compatibility with the 'echo' program or\nshell built-in. It has no effect.\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-n'\nThis option has only an effect if the '-s' option is given. It\nsuppresses the additional newline at the end.\n\n'-V'\n'--version'\nOutput version information and exit.\n\n'[TEXTDOMAIN] MSGID'\nRetrieve translated message corresponding to MSGID from TEXTDOMAIN.\n\nIf the TEXTDOMAIN parameter is not given, the domain is determined\nfrom the environment variable 'TEXTDOMAIN'. If the message catalog is\nnot found in the regular directory, another location can be specified\nwith the environment variable 'TEXTDOMAINDIR'.\n\nWhen used with the '-s' option the program behaves like the 'echo'\ncommand. But it does not simply copy its arguments to stdout. Instead\nthose messages found in the selected catalog are translated. Also, a\nnewline is added at the end, unless either the option '-n' is specified\nor the option '-e' is specified and some of the argument strings\ncontains a '\\c' escape sequence.\n\nNote: 'xgettext' supports only the one-argument form of the 'gettext'\ninvocation, where no options are present and the TEXTDOMAIN is implicit,\nfrom the environment.\n\nFile: gettext.info, Node: ngettext Invocation, Next: envsubst Invocation, Prev: gettext Invocation, Up: sh\n\n15.5.12.4 Invoking the 'ngettext' program\n.........................................\n\nngettext [OPTION] [TEXTDOMAIN] MSGID MSGID-PLURAL COUNT\n\nThe 'ngettext' program displays the native language translation of a\ntextual message whose grammatical form depends on a number.\n\n*Arguments*\n\n'-c CONTEXT'\n'--context=CONTEXT'\nSpecify the context for the messages to be translated. See *note\nContexts:: for details.\n\n'-d TEXTDOMAIN'\n'--domain=TEXTDOMAIN'\nRetrieve translated messages from TEXTDOMAIN. Usually a TEXTDOMAIN\ncorresponds to a package, a program, or a module of a program.\n\n'-e'\nEnable expansion of some escape sequences. This option is for\ncompatibility with the 'gettext' program. The escape sequences\n'\\a', '\\b', '\\f', '\\n', '\\r', '\\t', '\\v', '\\\\', and '\\' followed by\none to three octal digits, are interpreted like the System V 'echo'\nprogram did.\n\n'-E'\nThis option is only for compatibility with the 'gettext' program.\nIt has no effect.\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\n'TEXTDOMAIN'\nRetrieve translated message from TEXTDOMAIN.\n\n'MSGID MSGID-PLURAL'\nTranslate MSGID (English singular) / MSGID-PLURAL (English plural).\n\n'COUNT'\nChoose singular/plural form based on this value.\n\nIf the TEXTDOMAIN parameter is not given, the domain is determined\nfrom the environment variable 'TEXTDOMAIN'. If the message catalog is\nnot found in the regular directory, another location can be specified\nwith the environment variable 'TEXTDOMAINDIR'.\n\nNote: 'xgettext' supports only the three-arguments form of the\n'ngettext' invocation, where no options are present and the TEXTDOMAIN\nis implicit, from the environment.\n\nFile: gettext.info, Node: envsubst Invocation, Next: evalgettext Invocation, Prev: ngettext Invocation, Up: sh\n\n15.5.12.5 Invoking the 'envsubst' program\n.........................................\n\nenvsubst [OPTION] [SHELL-FORMAT]\n\nThe 'envsubst' program substitutes the values of environment\nvariables.\n\n*Operation mode*\n\n'-v'\n'--variables'\nOutput the variables occurring in SHELL-FORMAT.\n\n*Informative output*\n\n'-h'\n'--help'\nDisplay this help and exit.\n\n'-V'\n'--version'\nOutput version information and exit.\n\nIn normal operation mode, standard input is copied to standard\noutput, with references to environment variables of the form '$VARIABLE'\nor '${VARIABLE}' being replaced with the corresponding values. If a\nSHELL-FORMAT is given, only those environment variables that are\nreferenced in SHELL-FORMAT are substituted; otherwise all environment\nvariables references occurring in standard input are substituted.\n\nThese substitutions are a subset of the substitutions that a shell\nperforms on unquoted and double-quoted strings. Other kinds of\nsubstitutions done by a shell, such as '${VARIABLE-DEFAULT}' or\n'$(COMMAND-LIST)' or '`COMMAND-LIST`', are not performed by the\n'envsubst' program, due to security reasons.\n\nWhen '--variables' is used, standard input is ignored, and the output\nconsists of the environment variables that are referenced in\nSHELL-FORMAT, one per line.\n\nFile: gettext.info, Node: evalgettext Invocation, Next: evalngettext Invocation, Prev: envsubst Invocation, Up: sh\n\n15.5.12.6 Invoking the 'evalgettext' function\n..............................................\n\nevalgettext MSGID\n\nThis function outputs the native language translation of a textual\nmessage, performing dollar-substitution on the result. Note that only\nshell variables mentioned in MSGID will be dollar-substituted in the\nresult.\n\nFile: gettext.info, Node: evalngettext Invocation, Next: evalpgettext Invocation, Prev: evalgettext Invocation, Up: sh\n\n15.5.12.7 Invoking the 'evalngettext' function\n...............................................\n\nevalngettext MSGID MSGID-PLURAL COUNT\n\nThis function outputs the native language translation of a textual\nmessage whose grammatical form depends on a number, performing\ndollar-substitution on the result. Note that only shell variables\nmentioned in MSGID or MSGID-PLURAL will be dollar-substituted in the\nresult.\n\nFile: gettext.info, Node: evalpgettext Invocation, Next: evalnpgettext Invocation, Prev: evalngettext Invocation, Up: sh\n\n15.5.12.8 Invoking the 'evalpgettext' function\n...............................................\n\nevalpgettext MSGCTXT MSGID\n\nThis function outputs the native language translation of a textual\nmessage in the given context MSGCTXT (see *note Contexts::), performing\ndollar-substitution on the result. Note that only shell variables\nmentioned in MSGID will be dollar-substituted in the result.\n\nFile: gettext.info, Node: evalnpgettext Invocation, Prev: evalpgettext Invocation, Up: sh\n\n15.5.12.9 Invoking the 'evalnpgettext' function\n................................................\n\nevalnpgettext MSGCTXT MSGID MSGID-PLURAL COUNT\n\nThis function outputs the native language translation of a textual\nmessage whose grammatical form depends on a number in the given context\nMSGCTXT (see *note Contexts::), performing dollar-substitution on the\nresult. Note that only shell variables mentioned in MSGID or\nMSGID-PLURAL will be dollar-substituted in the result.\n\nFile: gettext.info, Node: bash, Next: gawk, Prev: sh, Up: List of Programming Languages\n\n\nGNU 'bash' 2.0 or newer has a special shorthand for translating a\nstring and substituting variable values in it: '$\"msgid\"'. But the use\nof this construct is *discouraged*, due to the security holes it opens\nand due to its portability problems.\n\nThe security holes of '$\"...\"' come from the fact that after looking\nup the translation of the string, 'bash' processes it like it processes\nany double-quoted string: dollar and backquote processing, like 'eval'\ndoes.\n\n1. In a locale whose encoding is one of BIG5, BIG5-HKSCS, GBK,\nGB18030, SHIFTJIS, JOHAB, some double-byte characters have a\nsecond byte whose value is '0x60'. For example, the byte sequence\n'\\xe0\\x60' is a single character in these locales. Many versions\nof 'bash' (all versions up to bash-2.05, and newer versions on\nplatforms without 'mbsrtowcs()' function) don't know about\ncharacter boundaries and see a backquote character where there is\nonly a particular Chinese character. Thus it can start executing\npart of the translation as a command list. This situation can\noccur even without the translator being aware of it: if the\ntranslator provides translations in the UTF-8 encoding, it is the\n'gettext()' function which will, during its conversion from the\ntranslator's encoding to the user's locale's encoding, produce the\ndangerous '\\x60' bytes.\n\n2. A translator could - voluntarily or inadvertently - use backquotes\n'\"`...`\"' or dollar-parentheses '\"$(...)\"' in her translations.\nThe enclosed strings would be executed as command lists by the\nshell.\n\nThe portability problem is that 'bash' must be built with\ninternationalization support; this is normally not the case on systems\nthat don't have the 'gettext()' function in libc.\n\nFile: gettext.info, Node: gawk, Next: Lua, Prev: bash, Up: List of Programming Languages\n\n\nRPMs\ngawk 3.1 or newer\n\nUbuntu packages\ngawk\n\nFile extension\n'awk', 'gawk', 'twjr'. The file extension 'twjr' is used by\nTexiWeb Jr ().\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n'\"abc\"'\n\ngettext/ngettext functions\n'dcgettext', missing 'dcngettext' in gawk-3.1.0\n\ntextdomain\n'TEXTDOMAIN' variable\n\nbindtextdomain\n'bindtextdomain' function\n\nsetlocale\nautomatic, but missing 'setlocale (LCMESSAGES, \"\")' in gawk-3.1.0\n\nPrerequisite\n--\n\nUse or emulate GNU gettext\nuse\n\nExtractor\n'xgettext'\n\nFormatting with positions\n'printf \"%2$d %1$d\"' (GNU awk only)\n\nPortability\nOn platforms without gettext, no translation. On non-GNU awks, you\nmust define 'dcgettext', 'dcngettext' and 'bindtextdomain'\nyourself.\n\npo-mode marking\n--\n\nAn example is available in the 'examples' directory: 'hello-gawk'.\n\nFile: gettext.info, Node: Lua, Next: Pascal, Prev: gawk, Up: List of Programming Languages\n\n\nRPMs\nlua\n\nUbuntu packages\nlua, lua-gettext\nYou need to install the 'lua-gettext' package from\n.\nDebian and Ubuntu packages of it are available. Download the\nappropriate one, and install it through 'sudo dpkg -i\nlua-gettext0.0amd64.deb'.\n\nFile extension\n'lua'\n\nString syntax\n\n* '\"abc\"'\n\n* ''abc''\n\n* '[[abc]]'\n\n* '[=[abc]=]'\n\n* '[==[abc]==]'\n\n* ...\n\ngettext shorthand\n'(\"abc\")'\n\ngettext/ngettext functions\n'gettext.gettext', 'gettext.dgettext', 'gettext.dcgettext',\n'gettext.ngettext', 'gettext.dngettext', 'gettext.dcngettext'\n\ntextdomain\n'textdomain' function\n\nbindtextdomain\n'bindtextdomain' function\n\nsetlocale\nautomatic\n\nPrerequisite\n'require 'gettext'' or running lua interpreter with '-l gettext'\noption\n\nUse or emulate GNU gettext\nuse\n\nExtractor\n'xgettext'\n\nFormatting with positions\n--\n\nPortability\nOn platforms without gettext, the functions are not available.\n\npo-mode marking\n--\n\nFile: gettext.info, Node: Pascal, Next: Smalltalk, Prev: Lua, Up: List of Programming Languages\n\n\nRPMs\nfpk\n\nUbuntu packages\nfp-compiler, fp-units-fcl\n\nFile extension\n'pp', 'pas'\n\nString syntax\n''abc''\n\ngettext shorthand\nautomatic\n\ngettext/ngettext functions\n--, use 'ResourceString' data type instead\n\ntextdomain\n--, use 'TranslateResourceStrings' function instead\n\nbindtextdomain\n--, use 'TranslateResourceStrings' function instead\n\nsetlocale\nautomatic, but uses only LANG, not LCMESSAGES or LCALL\n\nPrerequisite\n'{$mode delphi}' or '{$mode objfpc}'\n'uses gettext;'\n\nUse or emulate GNU gettext\nemulate partially\n\nExtractor\n'ppc386' followed by 'xgettext' or 'rstconv'\n\nFormatting with positions\n'uses sysutils;'\n'format \"%1:d %0:d\"'\n\nPortability\n?\n\npo-mode marking\n--\n\nThe Pascal compiler has special support for the 'ResourceString' data\ntype. It generates a '.rst' file. This is then converted to a '.pot'\nfile by use of 'xgettext' or 'rstconv'. At runtime, a '.mo' file\ncorresponding to translations of this '.pot' file can be loaded using\nthe 'TranslateResourceStrings' function in the 'gettext' unit.\n\nAn example is available in the 'examples' directory: 'hello-pascal'.\n\nFile: gettext.info, Node: Smalltalk, Next: Vala, Prev: Pascal, Up: List of Programming Languages\n\n\nRPMs\nsmalltalk\n\nUbuntu packages\ngnu-smalltalk\n\nFile extension\n'st'\n\nString syntax\n''abc''\n\ngettext shorthand\n'NLS ? 'abc''\n\ngettext/ngettext functions\n'LcMessagesDomain>>#at:', 'LcMessagesDomain>>#at:plural:with:'\n\ntextdomain\n'LcMessages>>#domain:localeDirectory:' (returns a\n'LcMessagesDomain' object).\nExample: 'I18N Locale default messages domain: 'gettext'\nlocaleDirectory: /usr/local/share/locale''\n\nbindtextdomain\n'LcMessages>>#domain:localeDirectory:', see above.\n\nsetlocale\nAutomatic if you use 'I18N Locale default'.\n\nPrerequisite\n'PackageLoader fileInPackage: 'I18N'!'\n\nUse or emulate GNU gettext\nemulate\n\nExtractor\n'xgettext'\n\nFormatting with positions\n''%1 %2' bindWith: 'Hello' with: 'world''\n\nPortability\nfully portable\n\npo-mode marking\n--\n\nAn example is available in the 'examples' directory:\n'hello-smalltalk'.\n\nFile: gettext.info, Node: Vala, Next: wxWidgets, Prev: Smalltalk, Up: List of Programming Languages\n\n\nRPMs\nvala\n\nUbuntu packages\nvalac\n\nFile extension\n'vala'\n\nString syntax\n\n* '\"abc\"'\n\n* '\"\"\"abc\"\"\"'\n\ngettext shorthand\n'(\"abc\")'\n\ngettext/ngettext functions\n'gettext', 'dgettext', 'dcgettext', 'ngettext', 'dngettext',\n'dpgettext', 'dpgettext2'\n\ntextdomain\n'textdomain' function, defined under the 'Intl' namespace\n\nbindtextdomain\n'bindtextdomain' function, defined under the 'Intl' namespace\n\nsetlocale\nProgrammer must call 'Intl.setlocale (LocaleCategory.ALL, \"\")'\n\nPrerequisite\n--\n\nUse or emulate GNU gettext\nUse\n\nExtractor\n'xgettext'\n\nFormatting with positions\nSame as for the C language.\n\nPortability\nautoconf (gettext.m4) and #if ENABLENLS\n\npo-mode marking\nyes\n\nFile: gettext.info, Node: wxWidgets, Next: Tcl, Prev: Vala, Up: List of Programming Languages\n\n\nRPMs\nwxGTK, gettext\n\nUbuntu packages\nlibwxgtk3.0-dev\n\nFile extension\n'cpp'\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n'(\"abc\")'\n\ngettext/ngettext functions\n'wxLocale::GetString', 'wxGetTranslation'\n\ntextdomain\n'wxLocale::AddCatalog'\n\nbindtextdomain\n'wxLocale::AddCatalogLookupPathPrefix'\n\nsetlocale\n'wxLocale::Init', 'wxSetLocale'\n\nPrerequisite\n'#include '\n\nUse or emulate GNU gettext\nemulate, see 'include/wx/intl.h' and 'src/common/intl.cpp'\n\nExtractor\n'xgettext'\n\nFormatting with positions\nwxString::Format supports positions if and only if the system has\n'wprintf()', 'vswprintf()' functions and they support positions\naccording to POSIX.\n\nPortability\nfully portable\n\npo-mode marking\nyes\n\nFile: gettext.info, Node: Tcl, Next: Perl, Prev: wxWidgets, Up: List of Programming Languages\n\n\nRPMs\ntcl\n\nUbuntu packages\ntcl\n\nFile extension\n'tcl'\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n'[ \"abc\"]'\n\ngettext/ngettext functions\n'::msgcat::mc'\n\ntextdomain\n--\n\nbindtextdomain\n--, use '::msgcat::mcload' instead\n\nsetlocale\nautomatic, uses LANG, but ignores LCMESSAGES and LCALL\n\nPrerequisite\n'package require msgcat'\n'proc {s} {return [::msgcat::mc $s]}'\n\nUse or emulate GNU gettext\n--, uses a Tcl specific message catalog format\n\nExtractor\n'xgettext -k'\n\nFormatting with positions\n'format \"%2\\$d %1\\$d\"'\n\nPortability\nfully portable\n\npo-mode marking\n--\n\nTwo examples are available in the 'examples' directory: 'hello-tcl',\n'hello-tcl-tk'.\n\nBefore marking strings as internationalizable, substitutions of\nvariables into the string need to be converted to 'format' applications.\nFor example, '\"file $filename not found\"' becomes '[format \"file %s not\nfound\" $filename]'. Only after this is done, can the strings be marked\nand extracted. After marking, this example becomes '[format [ \"file %s\nnot found\"] $filename]' or '[msgcat::mc \"file %s not found\" $filename]'.\nNote that the 'msgcat::mc' function implicitly calls 'format' when more\nthan one argument is given.\n\nFile: gettext.info, Node: Perl, Next: PHP, Prev: Tcl, Up: List of Programming Languages\n\n\nRPMs\nperl\n\nUbuntu packages\nperl, libintl-perl\n\nFile extension\n'pl', 'PL', 'pm', 'perl', 'cgi'\n\nString syntax\n\n* '\"abc\"'\n\n* ''abc''\n\n* 'qq (abc)'\n\n* 'q (abc)'\n\n* 'qr /abc/'\n\n* 'qx (/bin/date)'\n\n* '/pattern match/'\n\n* '?pattern match?'\n\n* 's/substitution/operators/'\n\n* '$tiedhash{\"message\"}'\n\n* '$tiedhashreference->{\"message\"}'\n\n* etc., issue the command 'man perlsyn' for details\n\ngettext shorthand\n'' (double underscore)\n\ngettext/ngettext functions\n'gettext', 'dgettext', 'dcgettext', 'ngettext', 'dngettext',\n'dcngettext', 'pgettext', 'dpgettext', 'dcpgettext', 'npgettext',\n'dnpgettext', 'dcnpgettext'\n\ntextdomain\n'textdomain' function\n\nbindtextdomain\n'bindtextdomain' function\n\nbindtextdomaincodeset\n'bindtextdomaincodeset' function\n\nsetlocale\nUse 'setlocale (LCALL, \"\");'\n\nPrerequisite\n'use POSIX;'\n'use Locale::TextDomain;' (included in the package libintl-perl\nwhich is available on the Comprehensive Perl Archive Network CPAN,\nhttps://www.cpan.org/).\n\nUse or emulate GNU gettext\nplatform dependent: gettextpp emulates, gettextxs uses GNU\ngettext\n\nExtractor\n'xgettext -k -k\\$ -k% -kx -kn:1,2 -knx:1,2 -kxn:1,2\n-kN -kNn:1,2 -kp:1c,2 -knp:1c,2,3 -kNp:1c,2\n-kNnp:1c,2,3'\n\nFormatting with positions\nBoth kinds of format strings support formatting with positions.\n'printf \"%2\\$d %1\\$d\", ...' (requires Perl 5.8.0 or newer)\n'expand(\"[new] replaces [old]\", old => $oldvalue, new =>\n$newvalue)'\n\nPortability\nThe 'libintl-perl' package is platform independent but is not part\nof the Perl core. The programmer is responsible for providing a\ndummy implementation of the required functions if the package is\nnot installed on the target system.\n\npo-mode marking\n--\n\nDocumentation\nIncluded in 'libintl-perl', available on CPAN\n(https://www.cpan.org/).\n\nAn example is available in the 'examples' directory: 'hello-perl'.\n\nThe 'xgettext' parser backend for Perl differs significantly from the\nparser backends for other programming languages, just as Perl itself\ndiffers significantly from other programming languages. The Perl parser\nbackend offers many more string marking facilities than the other\nbackends but it also has some Perl specific limitations, the worst\nprobably being its imperfectness.\n\n* Menu:\n\n* General Problems:: General Problems Parsing Perl Code\n* Default Keywords:: Which Keywords Will xgettext Look For?\n* Special Keywords:: How to Extract Hash Keys\n* Quote-like Expressions:: What are Strings And Quote-like Expressions?\n* Interpolation I:: Invalid String Interpolation\n* Interpolation II:: Valid String Interpolation\n* Parentheses:: When To Use Parentheses\n* Long Lines:: How To Grok with Long Lines\n* Perl Pitfalls:: Bugs, Pitfalls, and Things That Do Not Work\n\nFile: gettext.info, Node: General Problems, Next: Default Keywords, Up: Perl\n\n15.5.21.1 General Problems Parsing Perl Code\n............................................\n\nIt is often heard that only Perl can parse Perl. This is not true.\nPerl cannot be parsed at all, it can only be executed. Perl has\nvarious built-in ambiguities that can only be resolved at runtime.\n\nThe following example may illustrate one common problem:\n\nprint gettext \"Hello World!\";\n\nAlthough this example looks like a bullet-proof case of a function\ninvocation, it is not:\n\nopen gettext, \">testfile\" or die;\nprint gettext \"Hello world!\"\n\nIn this context, the string 'gettext' looks more like a file handle.\nBut not necessarily:\n\nuse Locale::Messages qw (:libintlh);\nopen gettext \">testfile\" or die;\nprint gettext \"Hello world!\";\n\nNow, the file is probably syntactically incorrect, provided that the\nmodule 'Locale::Messages' found first in the Perl include path exports a\nfunction 'gettext'. But what if the module 'Locale::Messages' really\nlooks like this?\n\nuse vars qw (*gettext);\n\n1;\n\nIn this case, the string 'gettext' will be interpreted as a file\nhandle again, and the above example will create a file 'testfile' and\nwrite the string \"Hello world!\" into it. Even advanced control flow\nanalysis will not really help:\n\nif (0.5 < rand) {\neval \"use Sane\";\n} else {\neval \"use InSane\";\n}\nprint gettext \"Hello world!\";\n\nIf the module 'Sane' exports a function 'gettext' that does what we\nexpect, and the module 'InSane' opens a file for writing and associates\nthe handle 'gettext' with this output stream, we are clueless again\nabout what will happen at runtime. It is completely unpredictable. The\ntruth is that Perl has so many ways to fill its symbol table at runtime\nthat it is impossible to interpret a particular piece of code without\nexecuting it.\n\nOf course, 'xgettext' will not execute your Perl sources while\nscanning for translatable strings, but rather use heuristics in order to\nguess what you meant.\n\nAnother problem is the ambiguity of the slash and the question mark.\nTheir interpretation depends on the context:\n\n# A pattern match.\nprint \"OK\\n\" if /foobar/;\n\n# A division.\nprint 1 / 2;\n\n# Another pattern match.\nprint \"OK\\n\" if ?foobar?;\n\n# Conditional.\nprint $x ? \"foo\" : \"bar\";\n\nThe slash may either act as the division operator or introduce a\npattern match, whereas the question mark may act as the ternary\nconditional operator or as a pattern match, too. Other programming\nlanguages like 'awk' present similar problems, but the consequences of a\nmisinterpretation are particularly nasty with Perl sources. In 'awk'\nfor instance, a statement can never exceed one line and the parser can\nrecover from a parsing error at the next newline and interpret the rest\nof the input stream correctly. Perl is different, as a pattern match is\nterminated by the next appearance of the delimiter (the slash or the\nquestion mark) in the input stream, regardless of the semantic context.\nIf a slash is really a division sign but mis-interpreted as a pattern\nmatch, the rest of the input file is most probably parsed incorrectly.\n\nThere are certain cases, where the ambiguity cannot be resolved at\nall:\n\n$x = wantarray ? 1 : 0;\n\nThe Perl built-in function 'wantarray' does not accept any arguments.\nThe Perl parser therefore knows that the question mark does not start a\nregular expression but is the ternary conditional operator.\n\nsub wantarrays {}\n$x = wantarrays ? 1 : 0;\n\nNow the situation is different. The function 'wantarrays' takes a\nvariable number of arguments (like any non-prototyped Perl function).\nThe question mark is now the delimiter of a pattern match, and hence the\npiece of code does not compile.\n\nsub wantarrays() {}\n$x = wantarrays ? 1 : 0;\n\nNow the function is prototyped, Perl knows that it does not accept\nany arguments, and the question mark is therefore interpreted as the\nternaray operator again. But that unfortunately outsmarts 'xgettext'.\n\nThe Perl parser in 'xgettext' cannot know whether a function has a\nprototype and what that prototype would look like. It therefore makes\nan educated guess. If a function is known to be a Perl built-in and\nthis function does not accept any arguments, a following question mark\nor slash is treated as an operator, otherwise as the delimiter of a\nfollowing regular expression. The Perl built-ins that do not accept\narguments are 'wantarray', 'fork', 'time', 'times', 'getlogin',\n'getppid', 'getpwent', 'getgrent', 'gethostent', 'getnetent',\n'getprotoent', 'getservent', 'setpwent', 'setgrent', 'endpwent',\n'endgrent', 'endhostent', 'endnetent', 'endprotoent', and 'endservent'.\n\nIf you find that 'xgettext' fails to extract strings from portions of\nyour sources, you should therefore look out for slashes and/or question\nmarks preceding these sections. You may have come across a bug in\n'xgettext''s Perl parser (and of course you should report that bug). In\nthe meantime you should consider to reformulate your code in a manner\nless challenging to 'xgettext'.\n\nIn particular, if the parser is too dumb to see that a function does\nnot accept arguments, use parentheses:\n\n$x = somefunc() ? 1 : 0;\n$y = (somefunc) ? 1 : 0;\n\nIn fact the Perl parser itself has similar problems and warns you\nabout such constructs.\n\nFile: gettext.info, Node: Default Keywords, Next: Special Keywords, Prev: General Problems, Up: Perl\n\n15.5.21.2 Which keywords will xgettext look for?\n................................................\n\nUnless you instruct 'xgettext' otherwise by invoking it with one of\nthe options '--keyword' or '-k', it will recognize the following\nkeywords in your Perl sources:\n\n* 'gettext'\n\n* 'dgettext:2'\n\nThe second argument will be extracted.\n\n* 'dcgettext:2'\n\nThe second argument will be extracted.\n\n* 'ngettext:1,2'\n\nThe first (singular) and the second (plural) argument will be\nextracted.\n\n* 'dngettext:2,3'\n\nThe second (singular) and the third (plural) argument will be\nextracted.\n\n* 'dcngettext:2,3'\n\nThe second (singular) and the third (plural) argument will be\nextracted.\n\n* 'pgettext:1c,2'\n\nThe first (message context) and the second argument will be\nextracted.\n\n* 'dpgettext:2c,3'\n\nThe second (message context) and the third argument will be\nextracted.\n\n* 'dcpgettext:2c,3'\n\nThe second (message context) and the third argument will be\nextracted.\n\n* 'npgettext:1c,2,3'\n\nThe first (message context), second (singular), and third (plural)\nargument will be extracted.\n\n* 'dnpgettext:2c,3,4'\n\nThe second (message context), third (singular), and fourth (plural)\nargument will be extracted.\n\n* 'dcnpgettext:2c,3,4'\n\nThe second (message context), third (singular), and fourth (plural)\nargument will be extracted.\n\n* 'gettextnoop'\n\n* '%gettext'\n\nThe keys of lookups into the hash '%gettext' will be extracted.\n\n* '$gettext'\n\nThe keys of lookups into the hash reference '$gettext' will be\nextracted.\n\nFile: gettext.info, Node: Special Keywords, Next: Quote-like Expressions, Prev: Default Keywords, Up: Perl\n\n15.5.21.3 How to Extract Hash Keys\n..................................\n\nTranslating messages at runtime is normally performed by looking up\nthe original string in the translation database and returning the\ntranslated version. The \"natural\" Perl implementation is a hash lookup,\nand, of course, 'xgettext' supports such practice.\n\nprint \"Hello world!\";\nprint ${\"Hello world!\"};\nprint $->{\"Hello world!\"};\nprint $${\"Hello world!\"};\n\nThe above four lines all do the same thing. The Perl module\n'Locale::TextDomain' exports by default a hash '%' that is tied to the\nfunction '()'. It also exports a reference '$' to '%'.\n\nIf an argument to the 'xgettext' option '--keyword', resp. '-k'\nstarts with a percent sign, the rest of the keyword is interpreted as\nthe name of a hash. If it starts with a dollar sign, the rest of the\nkeyword is interpreted as a reference to a hash.\n\nNote that you can omit the quotation marks (single or double) around\nthe hash key (almost) whenever Perl itself allows it:\n\nprint $gettext{Error};\n\nThe exact rule is: You can omit the surrounding quotes, when the hash\nkey is a valid C (!) identifier, i.e. when it starts with an underscore\nor an ASCII letter and is followed by an arbitrary number of\nunderscores, ASCII letters or digits. Other Unicode characters are\nnot allowed, regardless of the 'use utf8' pragma.\n\nFile: gettext.info, Node: Quote-like Expressions, Next: Interpolation I, Prev: Special Keywords, Up: Perl\n\n15.5.21.4 What are Strings And Quote-like Expressions?\n......................................................\n\nPerl offers a plethora of different string constructs. Those that\ncan be used either as arguments to functions or inside braces for hash\nlookups are generally supported by 'xgettext'.\n\n* *double-quoted strings*\nprint gettext \"Hello World!\";\n\n* *single-quoted strings*\nprint gettext 'Hello World!';\n\n* *the operator qq*\nprint gettext qq |Hello World!|;\nprint gettext qq >;\n\nThe operator 'qq' is fully supported. You can use arbitrary\ndelimiters, including the four bracketing delimiters (round, angle,\nsquare, curly) that nest.\n\n* *the operator q*\nprint gettext q |Hello World!|;\nprint gettext q >;\n\nThe operator 'q' is fully supported. You can use arbitrary\ndelimiters, including the four bracketing delimiters (round, angle,\nsquare, curly) that nest.\n\n* *the operator qx*\nprint gettext qx ;LANGUAGE=C /bin/date;\nprint gettext qx [/usr/bin/ls | grep '^[A-Z]*'];\n\nThe operator 'qx' is fully supported. You can use arbitrary\ndelimiters, including the four bracketing delimiters (round, angle,\nsquare, curly) that nest.\n\nThe example is actually a useless use of 'gettext'. It will invoke\nthe 'gettext' function on the output of the command specified with\nthe 'qx' operator. The feature was included in order to make the\ninterface consistent (the parser will extract all strings and\nquote-like expressions).\n\n* *here documents*\nprint gettext <<'EOF';\nprogram not found in $PATH\nEOF\n\nprint ngettext <My Homepage\n\nEOF\n\nThe parser will extract the entire here document, and it will appear\nentirely in the resulting PO file, including the JavaScript snippet\nembedded in the HTML code. If you exaggerate with constructs like the\nabove, you will run the risk that the translators of your package will\nlook out for a less challenging project. You should consider an\nalternative expression here:\n\nprint <$gettext{\"My Homepage\"}\n\nEOF\n\nOnly the translatable portions of the code will be extracted here,\nand the resulting PO file will begrudgingly improve in terms of\nreadability.\n\nYou can interpolate hash lookups in all strings or quote-like\nexpressions that are subject to interpolation (see the manual page 'man\nperlop' for details). Double interpolation is invalid, however:\n\n# TRANSLATORS: Replace \"the earth\" with the name of your planet.\nprint gettext qq{Welcome to $gettext->{\"the earth\"}};\n\nThe 'qq'-quoted string is recognized as an argument to 'xgettext' in\nthe first place, and checked for invalid variable interpolation. The\ndollar sign of hash-dereferencing will therefore terminate the parser\nwith an \"invalid interpolation\" error.\n\nIt is valid to interpolate hash lookups in regular expressions:\n\nif ($var =~ /$gettext{\"the earth\"}/) {\nprint gettext \"Match!\\n\";\n}\ns/$gettext{\"U. S. A.\"}/$gettext{\"U. S. A.\"} $gettext{\"(dial +0)\"}/g;\n\nFile: gettext.info, Node: Parentheses, Next: Long Lines, Prev: Interpolation II, Up: Perl\n\n15.5.21.7 When To Use Parentheses\n.................................\n\nIn Perl, parentheses around function arguments are mostly optional.\n'xgettext' will always assume that all recognized keywords (except for\nhashes and hash references) are names of properly prototyped functions,\nand will (hopefully) only require parentheses where Perl itself requires\nthem. All constructs in the following example are therefore ok to use:\n\nprint gettext (\"Hello World!\\n\");\nprint gettext \"Hello World!\\n\";\nprint dgettext ($package => \"Hello World!\\n\");\nprint dgettext $package, \"Hello World!\\n\";\n\n# The \"fat comma\" => turns the left-hand side argument into a\n# single-quoted string!\nprint dgettext smellovision => \"Hello World!\\n\";\n\n# The following assignment only works with prototyped functions.\n# Otherwise, the functions will act as \"greedy\" list operators and\n# eat up all following arguments.\nmy $anonymoushash = {\nplanet => gettext \"earth\",\ncakes => ngettext \"one cake\", \"several cakes\", $n,\nstill => $works,\n};\n# The same without fat comma:\nmy $otherhash = {\n'planet', gettext \"earth\",\n'cakes', ngettext \"one cake\", \"several cakes\", $n,\n'still', $works,\n};\n\n# Parentheses are only significant for the first argument.\nprint dngettext 'package', (\"one cake\", \"several cakes\", $n), $discarded;\n\nFile: gettext.info, Node: Long Lines, Next: Perl Pitfalls, Prev: Parentheses, Up: Perl\n\n15.5.21.8 How To Grok with Long Lines\n.....................................\n\nThe necessity of long messages can often lead to a cumbersome or\nunreadable coding style. Perl has several options that may prevent you\nfrom writing unreadable code, and 'xgettext' does its best to do\nlikewise. This is where the dot operator (the string concatenation\noperator) may come in handy:\n\nprint gettext (\"This is a very long\"\n. \" message that is still\"\n. \" readable, because\"\n. \" it is split into\"\n. \" multiple lines.\\n\");\n\nPerl is smart enough to concatenate these constant string fragments\ninto one long string at compile time, and so is 'xgettext'. You will\nonly find one long message in the resulting POT file.\n\nNote that the future Perl 6 will probably use the underscore ('') as\nthe string concatenation operator, and the dot ('.') for dereferencing.\nThis new syntax is not yet supported by 'xgettext'.\n\nIf embedded newline characters are not an issue, or even desired, you\nmay also insert newline characters inside quoted strings wherever you\nfeel like it:\n\nprint gettext (\"In HTML output\nembedded newlines are generally no\nproblem, since adjacent whitespace\nis always rendered into a single\nspace character.\");\n\nYou may also consider to use here documents:\n\nprint gettext <In HTML output\nembedded newlines are generally no\nproblem, since adjacent whitespace\nis always rendered into a single\nspace character.\nEOF\n\nPlease do not forget that the line breaks are real, i.e. they\ntranslate into newline characters that will consequently show up in the\nresulting POT file.\n\nFile: gettext.info, Node: Perl Pitfalls, Prev: Long Lines, Up: Perl\n\n15.5.21.9 Bugs, Pitfalls, And Things That Do Not Work\n.....................................................\n\nThe foregoing sections should have proven that 'xgettext' is quite\nsmart in extracting translatable strings from Perl sources. Yet, some\nmore or less exotic constructs that could be expected to work, actually\ndo not work.\n\nOne of the more relevant limitations can be found in the\nimplementation of variable interpolation inside quoted strings. Only\nsimple hash lookups can be used there:\n\nprint </gettext (\"Sunday\")/e;\n\nThe modifier 'e' will cause the substitution to be interpreted as an\nevaluable statement. Consequently, at runtime the function 'gettext()'\nis called, but again, the parser fails to extract the string \"Sunday\".\nUse a temporary variable as a simple workaround if you really happen to\nneed this feature:\n\nmy $sunday = gettext \"Sunday\";\ns//$sunday/;\n\nHash slices would also be handy but are not recognized:\n\nmy @weekdays = @gettext{'Sunday', 'Monday', 'Tuesday', 'Wednesday',\n'Thursday', 'Friday', 'Saturday'};\n# Or even:\n@weekdays = @gettext{qw (Sunday Monday Tuesday Wednesday Thursday\nFriday Saturday) };\n\nThis is perfectly valid usage of the tied hash '%gettext' but the\nstrings are not recognized and therefore will not be extracted.\n\nAnother caveat of the current version is its rudimentary support for\nnon-ASCII characters in identifiers. You may encounter serious problems\nif you use identifiers with characters outside the range of 'A'-'Z',\n'a'-'z', '0'-'9' and the underscore ''.\n\nMaybe some of these missing features will be implemented in future\nversions, but since you can always make do without them at minimal\neffort, these todos have very low priority.\n\nA nasty problem are brace format strings that already contain braces\nas part of the normal text, for example the usage strings typically\nencountered in programs:\n\ndie \"usage: $0 {OPTIONS} FILENAME...\\n\";\n\nIf you want to internationalize this code with Perl brace format\nstrings, you will run into a problem:\n\ndie x (\"usage: {program} {OPTIONS} FILENAME...\\n\", program => $0);\n\nWhereas '{program}' is a placeholder, '{OPTIONS}' is not and should\nprobably be translated. Yet, there is no way to teach the Perl parser\nin 'xgettext' to recognize the first one, and leave the other one alone.\n\nThere are two possible work-arounds for this problem. If you are\nsure that your program will run under Perl 5.8.0 or newer (these Perl\nversions handle positional parameters in 'printf()') or if you are sure\nthat the translator will not have to reorder the arguments in her\ntranslation - for example if you have only one brace placeholder in your\nstring, or if it describes a syntax, like in this one -, you can mark\nthe string as 'no-perl-brace-format' and use 'printf()':\n\n# xgettext: no-perl-brace-format\ndie sprintf (\"usage: %s {OPTIONS} FILENAME...\\n\", $0);\n\nIf you want to use the more portable Perl brace format, you will have\nto do put placeholders in place of the literal braces:\n\ndie x (\"usage: {program} {[}OPTIONS{]} FILENAME...\\n\",\nprogram => $0, '[' => '{', ']' => '}');\n\nPerl brace format strings know no escaping mechanism. No matter how\nthis escaping mechanism looked like, it would either give the programmer\na hard time, make translating Perl brace format strings heavy-going, or\nresult in a performance penalty at runtime, when the format directives\nget executed. Most of the time you will happily get along with\n'printf()' for this special case.\n\nFile: gettext.info, Node: PHP, Next: Pike, Prev: Perl, Up: List of Programming Languages\n\n\nRPMs\nmodphp4, modphp4-core, phpdoc\n\nUbuntu packages\nphp\n\nFile extension\n'php', 'php3', 'php4'\n\nString syntax\n'\"abc\"', ''abc''\n\ngettext shorthand\n'(\"abc\")'\n\ngettext/ngettext functions\n'gettext', 'dgettext', 'dcgettext'; starting with PHP 4.2.0 also\n'ngettext', 'dngettext', 'dcngettext'\n\ntextdomain\n'textdomain' function\n\nbindtextdomain\n'bindtextdomain' function\n\nsetlocale\nProgrammer must call 'setlocale (LCALL, \"\")'\n\nPrerequisite\n--\n\nUse or emulate GNU gettext\nuse\n\nExtractor\n'xgettext'\n\nFormatting with positions\n'printf \"%2\\$d %1\\$d\"'\n\nPortability\nOn platforms without gettext, the functions are not available.\n\npo-mode marking\n--\n\nAn example is available in the 'examples' directory: 'hello-php'.\n\nFile: gettext.info, Node: Pike, Next: GCC-source, Prev: PHP, Up: List of Programming Languages\n\n\nRPMs\nroxen\n\nUbuntu packages\npike8.0 or pike7.8\n\nFile extension\n'pike'\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n--\n\ngettext/ngettext functions\n'gettext', 'dgettext', 'dcgettext'\n\ntextdomain\n'textdomain' function\n\nbindtextdomain\n'bindtextdomain' function\n\nsetlocale\n'setlocale' function\n\nPrerequisite\n'import Locale.Gettext;'\n\nUse or emulate GNU gettext\nuse\n\nExtractor\n--\n\nFormatting with positions\n--\n\nPortability\nOn platforms without gettext, the functions are not available.\n\npo-mode marking\n--\n\nFile: gettext.info, Node: GCC-source, Next: YCP, Prev: Pike, Up: List of Programming Languages\n\n\nRPMs\ngcc\n\nUbuntu packages\ngcc\n\nFile extension\n'c', 'h'.\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n'(\"abc\")'\n\ngettext/ngettext functions\n'gettext', 'dgettext', 'dcgettext', 'ngettext', 'dngettext',\n'dcngettext'\n\ntextdomain\n'textdomain' function\n\nbindtextdomain\n'bindtextdomain' function\n\nsetlocale\nProgrammer must call 'setlocale (LCALL, \"\")'\n\nPrerequisite\n'#include \"intl.h\"'\n\nUse or emulate GNU gettext\nUse\n\nExtractor\n'xgettext -k'\n\nFormatting with positions\n--\n\nPortability\nUses autoconf macros\n\npo-mode marking\nyes\n\nFile: gettext.info, Node: YCP, Prev: GCC-source, Up: List of Programming Languages\n\n\nRPMs\nlibycp, libycp-devel, yast2-core, yast2-core-devel\n\nUbuntu packages\n--\n\nFile extension\n'ycp'\n\nString syntax\n'\"abc\"'\n\ngettext shorthand\n'(\"abc\")'\n\ngettext/ngettext functions\n'()' with 1 or 3 arguments\n\ntextdomain\n'textdomain' statement\n\nbindtextdomain\n--\n\nsetlocale\n--\n\nPrerequisite\n--\n\nUse or emulate GNU gettext\nuse\n\nExtractor\n'xgettext'\n\nFormatting with positions\n'sformat \"%2 %1\"'\n\nPortability\nfully portable\n\npo-mode marking\n--\n\nAn example is available in the 'examples' directory: 'hello-ycp'.\n\nFile: gettext.info, Node: Data Formats, Next: Conclusion, Prev: Programming Languages, Up: Top\n" } ] }, "16 Other Data Formats": { "content": "While the GNU gettext tools deal mainly with POT and PO files, they\ncan also manipulate a couple of other data formats.\n\n* Menu:\n\n* Internationalizable Data:: Internationalizable Data Formats\n* Localized Data:: Localized Data Formats\n\nFile: gettext.info, Node: Internationalizable Data, Next: Localized Data, Up: Data Formats\n", "subsections": [ { "name": "16.1 Internationalizable Data Formats", "content": "Here is a list of other data formats which can be internationalized\nusing GNU gettext.\n\n* Menu:\n\n* POT:: POT - Portable Object Template\n* RST:: Resource String Table\n* Glade:: Glade - GNOME user interface description\n* GSettings:: GSettings - GNOME user configuration schema\n* AppData:: AppData - freedesktop.org application description\n* Preparing ITS Rules:: Preparing Rules for XML Internationalization\n\nFile: gettext.info, Node: POT, Next: RST, Up: Internationalizable Data\n\n\nRPMs\ngettext\n\nUbuntu packages\ngettext\n\nFile extension\n'pot', 'po'\n\nExtractor\n'xgettext'\n\nFile: gettext.info, Node: RST, Next: Glade, Prev: POT, Up: Internationalizable Data\n\n\nRST is the format of resource string table files of the Free Pascal\ncompiler versions older than 3.0.0. RSJ is the new format of resource\nstring table files, created by the Free Pascal compiler version 3.0.0 or\nnewer.\n\nRPMs\nfpk\n\nUbuntu packages\nfp-compiler\n\nFile extension\n'rst', 'rsj'\n\nExtractor\n'xgettext', 'rstconv'\n\nFile: gettext.info, Node: Glade, Next: GSettings, Prev: RST, Up: Internationalizable Data\n\n\nRPMs\nglade, libglade, glade2, libglade2, intltool\n\nUbuntu packages\nglade, libglade2-dev, intltool\n\nFile extension\n'glade', 'glade2', 'ui'\n\nExtractor\n'xgettext', 'libglade-xgettext', 'xml-i18n-extract',\n'intltool-extract'\n\nFile: gettext.info, Node: GSettings, Next: AppData, Prev: Glade, Up: Internationalizable Data\n\n\nRPMs\nglib2\n\nUbuntu packages\nlibglib2.0-dev\n\nFile extension\n'gschema.xml'\n\nExtractor\n'xgettext', 'intltool-extract'\n\nFile: gettext.info, Node: AppData, Next: Preparing ITS Rules, Prev: GSettings, Up: Internationalizable Data\n\n\nThis file format is specified in\n.\n\nRPMs\nappdata-tools, appstream, libappstream-glib,\nlibappstream-glib-builder\n\nUbuntu packages\nappdata-tools, appstream, libappstream-glib-dev\n\nFile extension\n'appdata.xml', 'metainfo.xml'\n\nExtractor\n'xgettext', 'intltool-extract', 'itstool'\n\nFile: gettext.info, Node: Preparing ITS Rules, Prev: AppData, Up: Internationalizable Data\n\n\nMarking translatable strings in an XML file is done through a\nseparate \"rule\" file, making use of the Internationalization Tag Set\nstandard (ITS, ). The currently supported\nITS data categories are: 'Translate', 'Localization Note', 'Elements\nWithin Text', and 'Preserve Space'. In addition to them, 'xgettext'\nalso recognizes the following extended data categories:\n\n'Context'\n\nThis data category associates 'msgctxt' to the extracted text. In\nthe global rule, the 'contextRule' element contains the following:\n\n* A required 'selector' attribute. It contains an absolute\nselector that selects the nodes to which this rule applies.\n\n* A required 'contextPointer' attribute that contains a relative\nselector pointing to a node that holds the 'msgctxt' value.\n\n* An optional 'textPointer' attribute that contains a relative\nselector pointing to a node that holds the 'msgid' value.\n\n'Escape Special Characters'\n\nThis data category indicates whether the special XML characters\n('<', '>', '&', '\"') are escaped with entity reference. In the\nglobal rule, the 'escapeRule' element contains the following:\n\n* A required 'selector' attribute. It contains an absolute\nselector that selects the nodes to which this rule applies.\n\n* A required 'escape' attribute with the value 'yes' or 'no'.\n\n'Extended Preserve Space'\n\nThis data category extends the standard 'Preserve Space' data\ncategory with the additional values 'trim' and 'paragraph'. 'trim'\nmeans to remove the leading and trailing whitespaces of the\ncontent, but not to normalize whitespaces in the middle.\n'paragraph' means to normalize the content but keep the paragraph\nboundaries. In the global rule, the 'preserveSpaceRule' element\ncontains the following:\n\n* A required 'selector' attribute. It contains an absolute\nselector that selects the nodes to which this rule applies.\n\n* A required 'space' attribute with the value 'default',\n'preserve', 'trim', or 'paragraph'.\n\nAll those extended data categories can only be expressed with global\nrules, and the rule elements have to have the\n'https://www.gnu.org/s/gettext/ns/its/extensions/1.0' namespace.\n\nGiven the following XML document in a file 'messages.xml':\n\n\n\n\n

A translatable string

\n\n\n

A non-translatable string

\n\n\n\nTo extract the first text content (\"A translatable string\"), but not\nthe second (\"A non-translatable string\"), the following ITS rules can be\nused:\n\n\n\n\n\n\n\n\n\n\n'xgettext' needs another file called \"locating rule\" to associate an\nITS rule with an XML file. If the above ITS file is saved as\n'messages.its', the locating rule would look like:\n\n\n\n\n\n\n\n\n\nThe 'locatingRule' element must have a 'pattern' attribute, which\ndenotes either a literal file name or a wildcard pattern of the XML\nfile(1). The 'locatingRule' element can have child 'documentRule'\nelement, which adds checks on the content of the XML file.\n\nThe first rule matches any file with the '.xml' file extension, but\nit only applies to XML files whose root element is ''.\n\nThe second rule indicates that the same ITS rule file are also\napplicable to any file with the '.msg' file extension. The optional\n'name' attribute of 'locatingRule' allows to choose rules by name,\ntypically with 'xgettext''s '-L' option.\n\nThe associated ITS rule file is indicated by the 'target' attribute\nof 'locatingRule' or 'documentRule'. If it is specified in a\n'documentRule' element, the parent 'locatingRule' shouldn't have the\n'target' attribute.\n\nLocating rule files must have the '.loc' file extension. Both ITS\nrule files and locating rule files must be installed in the\n'$prefix/share/gettext/its' directory. Once those files are properly\ninstalled, 'xgettext' can extract translatable strings from the matching\nXML files.\n\n16.1.6.1 Two Use-cases of Translated Strings in XML\n...................................................\n\nFor XML, there are two use-cases of translated strings. One is the\ncase where the translated strings are directly consumed by programs, and\nthe other is the case where the translated strings are merged back to\nthe original XML document. In the former case, special characters in\nthe extracted strings shouldn't be escaped, while they should in the\nlatter case. To control wheter to escape special characters, the\n'Escape Special Characters' data category can be used.\n\nTo merge the translations, the 'msgfmt' program can be used with the\noption '--xml'. *Note msgfmt Invocation::, for more details about how\none calls the 'msgfmt' program. 'msgfmt''s '--xml' option doesn't\nperform character escaping, so translated strings can have arbitrary XML\nconstructs, such as elements for markup.\n\n---------- Footnotes ----------\n\n(1) Note that the file name matching is done after removing any '.in'\nsuffix from the input file name. Thus the 'pattern' attribute must not\ninclude a pattern matching '.in'. For example, if the input file name\nis 'foo.msg.in', the pattern should be either '*.msg' or just '*',\nrather than '*.in'.\n\nFile: gettext.info, Node: Localized Data, Prev: Internationalizable Data, Up: Data Formats\n" }, { "name": "16.2 Localized Data Formats", "content": "Here is a list of file formats that contain localized data and that\nthe GNU gettext tools can manipulate.\n\n* Menu:\n\n* Editable Message Catalogs:: Editable Message Catalogs\n* Compiled Message Catalogs:: Compiled Message Catalogs\n* Desktop Entry:: Desktop Entry files\n* XML:: XML files\n\nFile: gettext.info, Node: Editable Message Catalogs, Next: Compiled Message Catalogs, Up: Localized Data\n\n\nThese file formats can be used with all of the 'msg*' tools and with\nthe 'xgettext' program.\n\nIf you just want to convert among these formats, you can use the\n'msgcat' program (with the appropriate option) or the 'xgettext'\nprogram.\n\n* Menu:\n\n* PO:: PO - Portable Object\n* Java .properties:: Java .properties\n* GNUstep .strings:: NeXTstep/GNUstep .strings\n\nFile: gettext.info, Node: PO, Next: Java .properties, Up: Editable Message Catalogs\n\n16.2.1.1 PO - Portable Object\n.............................\n\nFile extension\n'po'\n\nFile: gettext.info, Node: Java .properties, Next: GNUstep .strings, Prev: PO, Up: Editable Message Catalogs\n\n16.2.1.2 Java .properties\n.........................\n\nFile extension\n'properties'\n\nFile: gettext.info, Node: GNUstep .strings, Prev: Java .properties, Up: Editable Message Catalogs\n\n16.2.1.3 NeXTstep/GNUstep .strings\n..................................\n\nFile extension\n'strings'\n\nFile: gettext.info, Node: Compiled Message Catalogs, Next: Desktop Entry, Prev: Editable Message Catalogs, Up: Localized Data\n\n\nThese file formats can be created through 'msgfmt' and converted back\nto PO format through 'msgunfmt'.\n\n* Menu:\n\n* MO:: MO - Machine Object\n* Java ResourceBundle:: Java ResourceBundle\n* C# Satellite Assembly:: C# Satellite Assembly\n* C# Resource:: C# Resource\n* Tcl message catalog:: Tcl message catalog\n* Qt message catalog:: Qt message catalog\n\nFile: gettext.info, Node: MO, Next: Java ResourceBundle, Up: Compiled Message Catalogs\n\n16.2.2.1 MO - Machine Object\n............................\n\nFile extension\n'mo'\n\nSee section *note MO Files:: for details.\n\nFile: gettext.info, Node: Java ResourceBundle, Next: C# Satellite Assembly, Prev: MO, Up: Compiled Message Catalogs\n\n16.2.2.2 Java ResourceBundle\n............................\n\nFile extension\n'class'\n\nFor more information, see the section *note Java:: and the examples\n'hello-java', 'hello-java-awt', 'hello-java-swing'.\n\nFile: gettext.info, Node: C# Satellite Assembly, Next: C# Resource, Prev: Java ResourceBundle, Up: Compiled Message Catalogs\n\n16.2.2.3 C# Satellite Assembly\n..............................\n\nFile extension\n'dll'\n\nFor more information, see the section *note C#::.\n\nFile: gettext.info, Node: C# Resource, Next: Tcl message catalog, Prev: C# Satellite Assembly, Up: Compiled Message Catalogs\n\n16.2.2.4 C# Resource\n....................\n\nFile extension\n'resources'\n\nFor more information, see the section *note C#::.\n\nFile: gettext.info, Node: Tcl message catalog, Next: Qt message catalog, Prev: C# Resource, Up: Compiled Message Catalogs\n\n16.2.2.5 Tcl message catalog\n............................\n\nFile extension\n'msg'\n\nFor more information, see the section *note Tcl:: and the examples\n'hello-tcl', 'hello-tcl-tk'.\n\nFile: gettext.info, Node: Qt message catalog, Prev: Tcl message catalog, Up: Compiled Message Catalogs\n\n16.2.2.6 Qt message catalog\n...........................\n\nFile extension\n'qm'\n\nFor more information, see the examples 'hello-c++-qt' and\n'hello-c++-kde'.\n\nFile: gettext.info, Node: Desktop Entry, Next: XML, Prev: Compiled Message Catalogs, Up: Localized Data\n\n\nThe programmer produces a desktop entry file template with only the\nEnglish strings. These strings get included in the POT file, by way of\n'xgettext' (usually by listing the template in 'po/POTFILES.in'). The\ntranslators produce PO files, one for each language. Finally, an\n'msgfmt --desktop' invocation collects all the translations in the\ndesktop entry file.\n\nFor more information, see the example 'hello-c-gnome3'.\n\n* Menu:\n\n* Icons:: Handling icons\n\nFile: gettext.info, Node: Icons, Up: Desktop Entry\n\n16.2.3.1 How to handle icons in Desktop Entry files\n...................................................\n\nIcons are generally locale dependent, for the following reasons:\n\n* Icons may contain signs that are considered rude in some cultures.\nFor example, the high-five sign, in some cultures, is perceived as\nan unfriendly \"stop\" sign.\n* Icons may contain metaphors that are culture specific. For\nexample, a mailbox in the U.S. looks different than mailboxes all\naround the world.\n* Icons may need to be mirrored for right-to-left locales.\n* Icons may contain text strings (a bad practice, but anyway).\n\nHowever, icons are not covered by GNU gettext localization, because\n* Icons cannot be easily embedded in PO files,\n* The need to localize an icon is rare, and the ability to do so in a\nPO file would introduce translator mistakes.\n\nDesktop Entry files may contain an 'Icon' property, and this property\nis localizable. If a translator wishes to localize an icon, she should\ndo so by bypassing the normal workflow with PO files:\n1. The translator contacts the package developers directly, sending\nthem the icon appropriate for her locale, with a request to change\nthe template file.\n2. The package developers add the icon file to their repository, and a\nline\nIcon[LOCALE]=ICONFILENAME\nto the template file.\nThis line remains in place when this template file is merged with the\ntranslators' PO files, through 'msgfmt'.\n\nFile: gettext.info, Node: XML, Prev: Desktop Entry, Up: Localized Data\n\n\nSee the section *note Preparing ITS Rules:: and *note msgfmt\nInvocation::, subsection \"XML mode operations\".\n\nFile: gettext.info, Node: Conclusion, Next: Language Codes, Prev: Data Formats, Up: Top\n" } ] }, "17 Concluding Remarks": { "content": "We would like to conclude this GNU 'gettext' manual by presenting an\nhistory of the Translation Project so far. We finally give a few\npointers for those who want to do further research or readings about\nNative Language Support matters.\n\n* Menu:\n\n* History:: History of GNU 'gettext'\n* The original ABOUT-NLS:: Historical introduction\n* References:: Related Readings\n\nFile: gettext.info, Node: History, Next: The original ABOUT-NLS, Up: Conclusion\n", "subsections": [ { "name": "17.1 History of GNU 'gettext'", "content": "Internationalization concerns and algorithms have been informally and\ncasually discussed for years in GNU, sometimes around GNU 'libc', maybe\naround the incoming 'Hurd', or otherwise (nobody clearly remembers).\nAnd even then, when the work started for real, this was somewhat\nindependently of these previous discussions.\n\nThis all began in July 1994, when Patrick D'Cruze had the idea and\ninitiative of internationalizing version 3.9.2 of GNU 'fileutils'. He\nthen asked Jim Meyering, the maintainer, how to get those changes folded\ninto an official release. That first draft was full of '#ifdef's and\nsomewhat disconcerting, and Jim wanted to find nicer ways. Patrick and\nJim shared some tries and experimentations in this area. Then, feeling\nthat this might eventually have a deeper impact on GNU, Jim wanted to\nknow what standards were, and contacted Richard Stallman, who very\nquickly and verbally described an overall design for what was meant to\nbecome 'glocale', at that time.\n\nJim implemented 'glocale' and got a lot of exhausting feedback from\nPatrick and Richard, of course, but also from Mitchum DSouza (who wrote\na 'catgets'-like package), Roland McGrath, maybe David MacKenzie,\nFranc,ois Pinard, and Paul Eggert, all pushing and pulling in various\ndirections, not always compatible, to the extent that after a couple of\ntest releases, 'glocale' was torn apart. In particular, Paul Eggert -\nalways keeping an eye on developments in Solaris - advocated the use of\nthe 'gettext' API over 'glocale''s 'catgets'-based API.\n\nWhile Jim took some distance and time and became dad for a second\ntime, Roland wanted to get GNU 'libc' internationalized, and got Ulrich\nDrepper involved in that project. Instead of starting from 'glocale',\nUlrich rewrote something from scratch, but more conforming to the set of\nguidelines who emerged out of the 'glocale' effort. Then, Ulrich got\npeople from the previous forum to involve themselves into this new\nproject, and the switch from 'glocale' to what was first named\n'msgutils', renamed 'nlsutils', and later 'gettext', became officially\naccepted by Richard in May 1995 or so.\n\nLet's summarize by saying that Ulrich Drepper wrote GNU 'gettext' in\nApril 1995. The first official release of the package, including PO\nmode, occurred in July 1995, and was numbered 0.7. Other people\ncontributed to the effort by providing a discussion forum around Ulrich,\nwriting little pieces of code, or testing. These are quoted in the\n'THANKS' file which comes with the GNU 'gettext' distribution.\n\nWhile this was being done, Franc,ois adapted half a dozen of GNU\npackages to 'glocale' first, then later to 'gettext', putting them in\npretest, so providing along the way an effective user environment for\nfine tuning the evolving tools. He also took the responsibility of\norganizing and coordinating the Translation Project. After nearly a\nyear of informal exchanges between people from many countries,\ntranslator teams started to exist in May 1995, through the creation and\nsupport by Patrick D'Cruze of twenty unmoderated mailing lists for that\nmany native languages, and two moderated lists: one for reaching all\nteams at once, the other for reaching all willing maintainers of\ninternationalized free software packages.\n\nFranc,ois also wrote PO mode in June 1995 with the collaboration of\nGreg McGary, as a kind of contribution to Ulrich's package. He also\ngave a hand with the GNU 'gettext' Texinfo manual.\n\nIn 1997, Ulrich Drepper released the GNU libc 2.0, which included the\n'gettext', 'textdomain' and 'bindtextdomain' functions.\n\nIn 2000, Ulrich Drepper added plural form handling (the 'ngettext'\nfunction) to GNU libc. Later, in 2001, he released GNU libc 2.2.x,\nwhich is the first free C library with full internationalization\nsupport.\n\nUlrich being quite busy in his role of General Maintainer of GNU\nlibc, he handed over the GNU 'gettext' maintenance to Bruno Haible in\n2000. Bruno added the plural form handling to the tools as well, added\nsupport for UTF-8 and CJK locales, and wrote a few new tools for\nmanipulating PO files.\n\nFile: gettext.info, Node: The original ABOUT-NLS, Next: References, Prev: History, Up: Conclusion\n" }, { "name": "17.2 Notes on the Free Translation Project", "content": "This section contains the text that was, for a long time, distributed\nas a file named 'ABOUT-NLS'.\n\n* NOTE: * This documentation section is outdated. It it included\nhere for historical purposes only.\n\nFree software is going international! The Free Translation Project\nis a way to get maintainers of free software, translators, and users all\ntogether, so that free software will gradually become able to speak many\nlanguages. A few packages already provide translations for their\nmessages.\n\nIf you found this 'ABOUT-NLS' file inside a distribution, you may\nassume that the distributed package does use GNU 'gettext' internally,\nitself available at your nearest GNU archive site. But you do not\nneed to install GNU 'gettext' prior to configuring, installing or using\nthis package with messages translated.\n\nInstallers will find here some useful hints. These notes also\nexplain how users should proceed for getting the programs to use the\navailable translations. They tell how people wanting to contribute and\nwork on translations can contact the appropriate team.\n\n* Menu:\n\n* INSTALL Matters::\n* Using This Package::\n* Translating Teams::\n* Available Packages::\n* Using gettext in own code::\n\nFile: gettext.info, Node: INSTALL Matters, Next: Using This Package, Up: The original ABOUT-NLS\n\n\nSome packages are \"localizable\" when properly installed; the programs\nthey contain can be made to speak your own native language. Most such\npackages use GNU 'gettext'. Other packages have their own ways to\ninternationalization, predating GNU 'gettext'.\n\nBy default, this package will be installed to allow translation of\nmessages. It will automatically detect whether the system already\nprovides the GNU 'gettext' functions. Installers may use special\noptions at configuration time for changing the default behaviour. The\ncommand:\n\n./configure --disable-nls\n\nwill totally disable translation of messages.\n\nWhen you already have GNU 'gettext' installed on your system and run\nconfigure without an option for your new package, 'configure' will\nprobably detect the previously built and installed 'libintl' library and\nwill decide to use it. If not, you may have to to use the\n'--with-libintl-prefix' option to tell 'configure' where to look for it.\n\nInternationalized packages usually have many 'po/LL.po' files, where\nLL gives an ISO 639 two-letter code identifying the language. Unless\ntranslations have been forbidden at 'configure' time by using the\n'--disable-nls' switch, all available translations are installed\ntogether with the package. However, the environment variable 'LINGUAS'\nmay be set, prior to configuration, to limit the installed set.\n'LINGUAS' should then contain a space separated list of two-letter\ncodes, stating which languages are allowed.\n\nFile: gettext.info, Node: Using This Package, Next: Translating Teams, Prev: INSTALL Matters, Up: The original ABOUT-NLS\n\n\nAs a user, if your language has been installed for this package, you\nonly have to set the 'LANG' environment variable to the appropriate\n'LLCC' combination. If you happen to have the 'LCALL' or some other\n'LCxxx' environment variables set, you should unset them before setting\n'LANG', otherwise the setting of 'LANG' will not have the desired\neffect. Here 'LL' is an ISO 639 two-letter language code, and 'CC' is\nan ISO 3166 two-letter country code. For example, let's suppose that\nyou speak German and live in Germany. At the shell prompt, merely\nexecute 'setenv LANG deDE' (in 'csh'), 'export LANG; LANG=deDE' (in\n'sh') or 'export LANG=deDE' (in 'bash'). This can be done from your\n'.login' or '.profile' file, once and for all.\n\nYou might think that the country code specification is redundant.\nBut in fact, some languages have dialects in different countries. For\nexample, 'deAT' is used for Austria, and 'ptBR' for Brazil. The\ncountry code serves to distinguish the dialects.\n\nThe locale naming convention of 'LLCC', with 'LL' denoting the\nlanguage and 'CC' denoting the country, is the one use on systems based\non GNU libc. On other systems, some variations of this scheme are used,\nsuch as 'LL' or 'LLCC.ENCODING'. You can get the list of locales\nsupported by your system for your language by running the command\n'locale -a | grep '^LL''.\n\nNot all programs have translations for all languages. By default, an\nEnglish message is shown in place of a nonexistent translation. If you\nunderstand other languages, you can set up a priority list of languages.\nThis is done through a different environment variable, called\n'LANGUAGE'. GNU 'gettext' gives preference to 'LANGUAGE' over 'LANG'\nfor the purpose of message handling, but you still need to have 'LANG'\nset to the primary language; this is required by other parts of the\nsystem libraries. For example, some Swedish users who would rather read\ntranslations in German than English for when Swedish is not available,\nset 'LANGUAGE' to 'sv:de' while leaving 'LANG' to 'svSE'.\n\nSpecial advice for Norwegian users: The language code for Norwegian\nbokm??l changed from 'no' to 'nb' recently (in 2003). During the\ntransition period, while some message catalogs for this language are\ninstalled under 'nb' and some older ones under 'no', it's recommended\nfor Norwegian users to set 'LANGUAGE' to 'nb:no' so that both newer and\nolder translations are used.\n\nIn the 'LANGUAGE' environment variable, but not in the 'LANG'\nenvironment variable, 'LLCC' combinations can be abbreviated as 'LL' to\ndenote the language's main dialect. For example, 'de' is equivalent to\n'deDE' (German as spoken in Germany), and 'pt' to 'ptPT' (Portuguese\nas spoken in Portugal) in this context.\n\nFile: gettext.info, Node: Translating Teams, Next: Available Packages, Prev: Using This Package, Up: The original ABOUT-NLS\n\n\nFor the Free Translation Project to be a success, we need interested\npeople who like their own language and write it well, and who are also\nable to synergize with other translators speaking the same language.\nEach translation team has its own mailing list. The up-to-date list of\nteams can be found at the Free Translation Project's homepage,\n'https://translationproject.org/', in the \"Teams\" area.\n\nIf you'd like to volunteer to work at translating messages, you\nshould become a member of the translating team for your own language.\nThe subscribing address is not the same as the list itself, it has\n'-request' appended. For example, speakers of Swedish can send a\nmessage to 'sv-request@li.org', having this message body:\n\nsubscribe\n\nKeep in mind that team members are expected to participate actively\nin translations, or at solving translational difficulties, rather than\nmerely lurking around. If your team does not exist yet and you want to\nstart one, or if you are unsure about what to do or how to get started,\nplease write to 'coordinator@translationproject.org' to reach the\ncoordinator for all translator teams.\n\nThe English team is special. It works at improving and uniformizing\nthe terminology in use. Proven linguistic skills are praised more than\nprogramming skills, here.\n\nFile: gettext.info, Node: Available Packages, Next: Using gettext in own code, Prev: Translating Teams, Up: The original ABOUT-NLS\n\n\nLanguages are not equally supported in all packages. The following\nmatrix shows the current state of internationalization, as of July 2020.\nThe matrix shows, in regard of each package, for which languages PO\nfiles have been submitted to translation coordination, with a\ntranslation percentage of at least 50%.\n\nReady PO files af an ar ast be bg bn bnIN ca ckb crh cs da de\n+---------------------------------------------------+\na2ps | [] [] [] [] [] |\naegis | [] [] |\nanubis | [] [] |\naspell | [] [] [] [] [] |\nbash | [] [] [] [] |\nbfd | |\nbinutils | [] |\nbison | [] [] |\nbison-runtime | [] [] [] [] [] |\nbuzztrax | [] [] [] |\nccd2cue | [] [] |\nccide | [] [] |\ncflow | [] [] |\nclisp | [] [] |\ncoreutils | [] [] [] [] [] |\ncpio | [] [] |\ncppi | [] [] |\ncpplib | [] [] [] |\ncryptsetup | [] [] [] |\ndatamash | [] [] |\ndenemo | [] [] [] |\ndfarc | [] [] [] |\ndialog | [] [] [] [] [] [] |\ndico | [] [] |\ndiffutils | [] [] [] [] |\ndink | [] [] [] |\ndirevent | [] [] |\ndoodle | [] [] [] |\ndos2unix | [] [] |\ndos2unix-man | [] |\ne2fsprogs | [] [] [] [] |\nenscript | [] [] [] |\nexif | [] [] [] [] |\nfetchmail | [] [] [] () |\nfindutils | [] [] [] [] |\nflex | [] [] [] [] |\nfreedink | [] [] [] [] |\nfusionforge | [] |\ngas | |\ngawk | [] [] |\ngcal | [] [] [] |\ngcc | [] |\ngdbm | [] [] |\ngettext-examples | [] [] [] [] [] [] [] |\ngettext-runtime | [] [] [] [] [] [] |\ngettext-tools | [] [] [] [] |\ngjay | [] |\nglunarclock | [] [] [] [] [] |\ngnubiff | [] () |\ngnubik | [] [] [] |\ngnucash | [] () [] () |\ngnuchess | [] [] |\ngnucobol | |\ngnulib | [] [] [] [] |\ngnunet | |\ngnunet-gtk | [] |\ngnutls | [] [] |\ngold | |\ngphoto2 | [] [] () |\ngprof | [] [] [] |\ngramadoir | [] [] |\ngrep | [] [] [] [] [] |\ngrip | [] [] [] [] [] |\ngrub | [] [] [] [] |\ngsasl | [] [] |\ngss | [] [] |\ngst-plugins-bad | [] [] [] [] [] |\ngst-plugins-base | [] [] [] [] [] |\ngst-plugins-good | [] [] [] [] [] |\ngst-plugins-ugly | [] [] [] [] [] [] |\ngstreamer | [] [] [] [] [] [] |\ngtick | [] [] () |\ngtkam | [] [] [] () |\ngtkspell | [] [] [] [] [] [] [] |\nguix | [] [] |\nguix-manual | [] |\nguix-packages | |\ngutenprint | [] [] [] |\nhello | [] [] [] [] |\nhelp2man | [] [] |\nhelp2man-texi | [] |\nhylafax | [] |\nidutils | [] [] |\njwhois | [] |\nkbd | [] |\nklavaro | [] [] [] [] [] [] [] |\nld | [] |\nlibc | [] [] [] [] [] |\nlibexif | () [] [] |\nlibextractor | [] [] |\nlibgphoto2 | [] [] () |\nlibgphoto2port | [] [] () |\nlibgsasl | [] [] |\nlibiconv | [] [] [] [] |\nlibidn | [] [] [] |\nlibidn2 | [] [] [] |\nlilypond | [] [] [] [] |\nlordsawar | [] [] [] |\nlprng | |\nlynx | [] [] [] [] |\nm4 | [] [] [] [] |\nmailfromd | [] |\nmailutils | [] |\nmake | [] [] [] [] |\nman-db | [] [] [] [] [] |\nman-db-manpages | [] |\nmeritous | [] |\nmidi-instruments | [] [] [] [] [] |\nminicom | [] [] [] |\nmkisofs | [] |\nmpop | [] |\nmsmtp | [] |\nmuibase | () |\nmyserver | [] [] |\nnano | [] [] [] [] |\nopcodes | [] |\nparted | [] [] [] |\npies | [] |\npnmixer | [] [] |\nprocps-ng | [] |\nprocps-ng-man | [] |\npsmisc | [] [] [] |\npspp | [] [] |\npushover | [] () |\npwdutils | [] [] |\npyspread | [] [] |\nradius | [] |\nrecode | [] [] [] [] [] |\nrecutils | [] |\nrush | [] [] |\nsarg | [] [] |\nsavane | |\nsed | [] [] [] [] [] [] |\nsharutils | [] [] |\nshepherd | [] [] |\nshishi | [] |\nskribilo | [] |\nsolfege | [] [] [] [] |\nsolfege-manual | [] [] |\nspotmachine | [] [] |\nsudo | [] [] [] [] [] |\nsudoers | [] [] [] [] |\nsysstat | [] [] |\ntar | [] [] [] [] [] |\ntexinfo | [] [] [] [] |\ntexinfodocument | [] [] [] |\ntigervnc | [] [] [] [] |\ntin | [] [] |\ntin-man | |\ntracgoogleappsa... | [] [] |\ntrader | [] [] |\nutil-linux | [] [] [] |\nve | [] |\nvmm | [] |\nvorbis-tools | [] [] [] |\nwastesedge | [] |\nwcd | [] [] |\nwcd-man | [] |\nwdiff | [] [] [] [] |\nwget | [] [] |\nwget2 | [] |\nwyslij-po | [] [] |\nxboard | [] [] |\nxdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] |\nxkeyboard-config | [] [] [] [] [] |\nxz | [] [] |\n+---------------------------------------------------+\naf an ar ast be bg bn bnIN ca ckb crh cs da de\n3 2 4 17 6 31 1 1 54 1 1 69 114 138\n\nel en enGB eo es et eu fa fi fr fur ga gd gl\n+-------------------------------------------------+\na2ps | [] [] [] [] [] [] [] |\naegis | [] [] |\nanubis | [] [] [] |\naspell | [] [] [] [] [] [] [] |\nbash | [] [] [] [] |\nbfd | [] |\nbinutils | [] |\nbison | [] [] [] |\nbison-runtime | [] [] [] [] [] [] [] [] |\nbuzztrax | [] [] [] |\nccd2cue | [] [] [] |\nccide | [] [] [] [] [] |\ncflow | [] [] [] [] [] |\nclisp | [] [] [] |\ncoreutils | [] [] [] |\ncpio | [] [] [] [] |\ncppi | [] [] [] [] [] |\ncpplib | [] [] [] [] |\ncryptsetup | [] [] |\ndatamash | [] [] [] |\ndenemo | |\ndfarc | [] [] [] [] [] |\ndialog | [] [] [] [] [] [] [] [] [] [] [] |\ndico | [] [] [] |\ndiffutils | [] [] [] [] [] |\ndink | [] [] [] [] |\ndirevent | [] [] [] |\ndoodle | [] [] [] [] [] |\ndos2unix | [] [] [] [] |\ndos2unix-man | [] [] |\ne2fsprogs | [] [] |\nenscript | [] [] [] [] [] [] |\nexif | [] [] [] [] [] [] |\nfetchmail | [] [] [] [] [] |\nfindutils | [] [] [] [] [] [] [] [] |\nflex | [] [] [] [] [] |\nfreedink | [] [] [] [] [] [] [] |\nfusionforge | [] [] |\ngas | [] [] [] |\ngawk | [] [] [] |\ngcal | [] [] |\ngcc | [] [] |\ngdbm | [] [] [] [] |\ngettext-examples | [] [] [] [] [] [] [] |\ngettext-runtime | [] [] [] [] [] [] |\ngettext-tools | [] [] [] |\ngjay | [] [] [] [] |\nglunarclock | [] [] [] [] [] [] |\ngnubiff | [] [] () |\ngnubik | [] [] [] [] [] [] |\ngnucash | () () () () () |\ngnuchess | [] [] [] |\ngnucobol | [] [] |\ngnulib | [] [] [] [] [] |\ngnunet | [] |\ngnunet-gtk | [] |\ngnutls | [] [] [] [] |\ngold | [] [] [] |\ngphoto2 | [] [] |\ngprof | [] [] [] [] [] |\ngramadoir | [] [] [] [] [] |\ngrep | [] [] [] [] [] [] |\ngrip | [] [] [] [] |\ngrub | [] [] [] [] |\ngsasl | [] [] [] [] [] |\ngss | [] [] [] [] [] |\ngst-plugins-bad | [] [] |\ngst-plugins-base | [] [] [] [] [] [] |\ngst-plugins-good | [] [] [] [] [] [] |\ngst-plugins-ugly | [] [] [] [] [] [] [] [] |\ngstreamer | [] [] [] [] [] [] |\ngtick | [] [] [] [] [] [] |\ngtkam | [] [] [] [] |\ngtkspell | [] [] [] [] [] [] [] [] [] |\nguix | [] [] |\nguix-manual | [] [] |\nguix-packages | |\ngutenprint | [] [] [] |\nhello | [] [] [] [] [] [] [] [] |\nhelp2man | [] [] [] [] [] |\nhelp2man-texi | [] [] |\nhylafax | [] |\nidutils | [] [] [] [] |\njwhois | [] [] [] [] [] |\nkbd | [] |\nklavaro | [] [] [] [] [] [] |\nld | [] [] |\nlibc | [] [] [] [] |\nlibexif | () [] [] |\nlibextractor | [] [] |\nlibgphoto2 | [] [] |\nlibgphoto2port | [] [] [] [] |\nlibgsasl | [] [] [] [] [] |\nlibiconv | [] [] [] [] [] [] [] |\nlibidn | [] [] [] |\nlibidn2 | [] [] |\nlilypond | [] [] [] [] |\nlordsawar | [] |\nlprng | |\nlynx | [] [] [] [] |\nm4 | [] [] [] [] [] [] [] |\nmailfromd | [] |\nmailutils | [] [] [] |\nmake | [] [] [] [] |\nman-db | [] [] [] |\nman-db-manpages | [] [] |\nmeritous | [] |\nmidi-instruments | [] [] [] [] [] [] [] [] |\nminicom | [] [] [] |\nmkisofs | [] [] [] [] |\nmpop | [] [] |\nmsmtp | [] [] |\nmuibase | [] |\nmyserver | [] [] [] |\nnano | [] [] [] [] [] [] |\nopcodes | [] [] |\nparted | [] [] [] |\npies | [] [] |\npnmixer | [] |\nprocps-ng | [] |\nprocps-ng-man | [] |\npsmisc | [] [] [] [] [] |\npspp | [] [] [] [] |\npushover | [] [] [] |\npwdutils | [] |\npyspread | [] |\nradius | [] [] |\nrecode | [] [] [] [] [] [] |\nrecutils | [] [] |\nrush | [] [] |\nsarg | [] [] |\nsavane | [] [] |\nsed | [] [] [] [] [] [] [] [] |\nsharutils | [] [] [] |\nshepherd | [] [] |\nshishi | [] [] |\nskribilo | [] [] [] |\nsolfege | [] [] [] [] [] [] [] |\nsolfege-manual | [] [] [] [] |\nspotmachine | [] [] [] |\nsudo | [] [] [] [] [] [] |\nsudoers | [] [] [] |\nsysstat | [] [] [] |\ntar | [] [] [] [] [] [] |\ntexinfo | [] [] [] |\ntexinfodocument | [] [] [] |\ntigervnc | [] [] [] [] [] [] |\ntin | [] [] |\ntin-man | [] |\ntracgoogleappsa... | [] [] [] [] |\ntrader | [] [] [] [] |\nutil-linux | [] [] |\nve | [] [] [] [] [] |\nvmm | [] |\nvorbis-tools | [] [] [] |\nwastesedge | [] |\nwcd | [] [] [] [] [] |\nwcd-man | [] |\nwdiff | [] [] [] [] [] [] [] |\nwget | [] [] [] [] [] [] |\nwget2 | [] |\nwyslij-po | [] [] [] [] [] |\nxboard | [] [] |\nxdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] |\nxkeyboard-config | [] [] [] [] [] [] |\nxz | [] [] [] |\n+-------------------------------------------------+\nel en enGB eo es et eu fa fi fr fur ga gd gl\n24 1 6 89 122 20 8 4 90 154 24 33 2 38\n\ngu he hi hr hu hy id is it ja ka kk kn ko ku ky\n+-------------------------------------------------+\na2ps | [] [] [] [] |\naegis | [] |\nanubis | [] [] [] [] |\naspell | [] [] [] [] |\nbash | [] [] [] |\nbfd | |\nbinutils | |\nbison | [] |\nbison-runtime | [] [] [] [] [] [] |\nbuzztrax | |\nccd2cue | [] |\nccide | [] [] |\ncflow | [] [] |\nclisp | |\ncoreutils | [] [] |\ncpio | [] [] [] [] [] [] |\ncppi | [] [] [] [] |\ncpplib | [] [] |\ncryptsetup | [] [] |\ndatamash | |\ndenemo | [] |\ndfarc | [] [] [] |\ndialog | [] [] [] [] [] [] [] |\ndico | |\ndiffutils | [] [] [] [] [] |\ndink | [] |\ndirevent | [] |\ndoodle | [] |\ndos2unix | [] [] |\ndos2unix-man | |\ne2fsprogs | [] |\nenscript | [] [] |\nexif | [] [] [] [] [] [] |\nfetchmail | [] [] [] |\nfindutils | [] [] [] [] [] |\nflex | |\nfreedink | [] [] [] [] |\nfusionforge | |\ngas | [] |\ngawk | [] () [] |\ngcal | |\ngcc | |\ngdbm | |\ngettext-examples | [] [] [] [] [] [] |\ngettext-runtime | [] [] [] [] [] |\ngettext-tools | [] [] [] [] |\ngjay | |\nglunarclock | [] [] [] [] |\ngnubiff | [] [] () |\ngnubik | [] [] |\ngnucash | () () () () () () [] () () |\ngnuchess | |\ngnucobol | |\ngnulib | [] [] [] |\ngnunet | |\ngnunet-gtk | |\ngnutls | [] |\ngold | |\ngphoto2 | [] [] [] [] |\ngprof | [] [] [] |\ngramadoir | [] [] |\ngrep | [] [] [] [] [] [] |\ngrip | [] [] [] [] |\ngrub | [] [] [] |\ngsasl | [] [] [] [] |\ngss | [] [] [] [] |\ngst-plugins-bad | [] [] [] [] |\ngst-plugins-base | [] [] [] [] |\ngst-plugins-good | [] [] [] [] [] |\ngst-plugins-ugly | [] [] [] [] [] |\ngstreamer | [] [] [] [] |\ngtick | [] [] [] |\ngtkam | [] [] [] [] [] |\ngtkspell | [] [] [] [] [] [] [] [] [] |\nguix | |\nguix-manual | |\nguix-packages | |\ngutenprint | [] [] [] |\nhello | [] [] [] |\nhelp2man | [] [] [] |\nhelp2man-texi | |\nhylafax | [] |\nidutils | [] [] |\njwhois | [] [] [] |\nkbd | |\nklavaro | [] [] [] [] |\nld | |\nlibc | [] [] [] [] [] |\nlibexif | [] |\nlibextractor | |\nlibgphoto2 | |\nlibgphoto2port | [] [] |\nlibgsasl | [] [] [] |\nlibiconv | [] [] [] [] [] |\nlibidn | [] [] [] [] |\nlibidn2 | [] |\nlilypond | [] [] |\nlordsawar | |\nlprng | [] |\nlynx | [] [] [] [] |\nm4 | [] [] [] |\nmailfromd | |\nmailutils | |\nmake | [] [] [] [] [] |\nman-db | [] [] |\nman-db-manpages | [] |\nmeritous | |\nmidi-instruments | [] [] [] [] [] [] [] [] [] [] |\nminicom | [] [] [] |\nmkisofs | [] [] |\nmpop | |\nmsmtp | |\nmuibase | |\nmyserver | [] |\nnano | [] [] [] [] [] |\nopcodes | |\nparted | [] [] [] [] [] |\npies | |\npnmixer | [] [] |\nprocps-ng | |\nprocps-ng-man | |\npsmisc | [] [] [] |\npspp | [] [] |\npushover | [] |\npwdutils | [] |\npyspread | |\nradius | [] |\nrecode | [] [] [] [] [] |\nrecutils | |\nrush | |\nsarg | |\nsavane | |\nsed | [] [] [] [] [] [] |\nsharutils | |\nshepherd | |\nshishi | |\nskribilo | [] |\nsolfege | [] |\nsolfege-manual | |\nspotmachine | |\nsudo | [] [] [] [] [] |\nsudoers | [] [] [] [] |\nsysstat | [] [] |\ntar | [] [] [] [] [] [] [] |\ntexinfo | [] [] [] |\ntexinfodocument | [] [] [] |\ntigervnc | [] [] [] |\ntin | |\ntin-man | |\ntracgoogleappsa... | [] [] [] [] |\ntrader | [] [] |\nutil-linux | [] [] |\nve | [] [] |\nvmm | |\nvorbis-tools | [] [] |\nwastesedge | [] |\nwcd | |\nwcd-man | |\nwdiff | [] [] |\nwget | [] [] [] [] |\nwget2 | [] [] |\nwyslij-po | [] [] [] |\nxboard | |\nxdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] [] [] |\nxkeyboard-config | [] [] [] [] [] |\nxz | [] [] [] |\n+-------------------------------------------------+\ngu he hi hr hu hy id is it ja ka kk kn ko ku ky\n1 5 1 61 69 2 63 7 76 49 0 2 1 20 3 6\n\nlg lt lv mk ml mn mr ms mt nb ne nl nn or pa pl\n+---------------------------------------------------+\na2ps | [] [] [] |\naegis | [] |\nanubis | [] [] [] [] |\naspell | [] [] [] |\nbash | [] [] [] |\nbfd | |\nbinutils | |\nbison | |\nbison-runtime | [] [] [] [] [] [] |\nbuzztrax | |\nccd2cue | |\nccide | [] [] [] |\ncflow | [] [] |\nclisp | [] |\ncoreutils | [] [] [] |\ncpio | [] [] |\ncppi | [] |\ncpplib | [] |\ncryptsetup | [] |\ndatamash | [] [] |\ndenemo | |\ndfarc | [] [] [] |\ndialog | [] [] [] [] [] [] |\ndico | [] |\ndiffutils | [] [] [] [] |\ndink | [] |\ndirevent | [] [] |\ndoodle | [] |\ndos2unix | [] [] [] |\ndos2unix-man | [] [] |\ne2fsprogs | [] [] |\nenscript | [] [] |\nexif | [] [] [] [] |\nfetchmail | [] [] |\nfindutils | [] [] [] |\nflex | [] [] |\nfreedink | [] [] [] |\nfusionforge | |\ngas | |\ngawk | [] [] |\ngcal | |\ngcc | |\ngdbm | [] |\ngettext-examples | [] [] [] [] [] [] [] |\ngettext-runtime | [] [] [] [] |\ngettext-tools | [] |\ngjay | |\nglunarclock | [] [] [] |\ngnubiff | [] |\ngnubik | [] [] [] |\ngnucash | () () () () () [] () |\ngnuchess | [] [] |\ngnucobol | |\ngnulib | [] [] |\ngnunet | |\ngnunet-gtk | |\ngnutls | [] [] |\ngold | |\ngphoto2 | [] [] |\ngprof | [] [] |\ngramadoir | [] |\ngrep | [] [] [] |\ngrip | [] [] [] |\ngrub | [] [] [] [] |\ngsasl | [] [] |\ngss | [] |\ngst-plugins-bad | [] [] [] [] |\ngst-plugins-base | [] [] [] [] |\ngst-plugins-good | [] [] [] [] |\ngst-plugins-ugly | [] [] [] [] [] [] |\ngstreamer | [] [] [] [] |\ngtick | [] [] |\ngtkam | [] [] [] [] |\ngtkspell | [] [] [] [] [] [] [] |\nguix | |\nguix-manual | |\nguix-packages | |\ngutenprint | [] |\nhello | [] [] [] [] |\nhelp2man | [] [] |\nhelp2man-texi | [] |\nhylafax | [] |\nidutils | [] [] [] |\njwhois | [] [] [] |\nkbd | [] |\nklavaro | [] [] [] [] |\nld | |\nlibc | [] [] |\nlibexif | [] [] |\nlibextractor | [] [] |\nlibgphoto2 | [] [] |\nlibgphoto2port | [] [] |\nlibgsasl | [] [] |\nlibiconv | [] [] [] |\nlibidn | [] [] |\nlibidn2 | [] |\nlilypond | [] |\nlordsawar | |\nlprng | [] |\nlynx | [] |\nm4 | [] [] |\nmailfromd | [] |\nmailutils | [] |\nmake | [] [] |\nman-db | [] [] |\nman-db-manpages | [] |\nmeritous | |\nmidi-instruments | [] [] [] [] [] [] |\nminicom | [] [] |\nmkisofs | [] [] |\nmpop | |\nmsmtp | |\nmuibase | [] |\nmyserver | |\nnano | [] [] [] [] |\nopcodes | |\nparted | [] [] |\npies | [] |\npnmixer | [] |\nprocps-ng | [] |\nprocps-ng-man | [] |\npsmisc | [] [] |\npspp | [] [] [] |\npushover | |\npwdutils | [] [] |\npyspread | [] |\nradius | [] [] |\nrecode | [] [] [] |\nrecutils | [] |\nrush | [] [] |\nsarg | |\nsavane | |\nsed | [] [] [] |\nsharutils | [] [] |\nshepherd | |\nshishi | [] |\nskribilo | |\nsolfege | [] [] [] |\nsolfege-manual | [] [] |\nspotmachine | [] |\nsudo | [] [] [] |\nsudoers | [] [] [] |\nsysstat | [] [] [] |\ntar | [] [] [] |\ntexinfo | [] [] [] |\ntexinfodocument | [] [] |\ntigervnc | [] |\ntin | |\ntin-man | |\ntracgoogleappsa... | [] [] [] [] |\ntrader | [] |\nutil-linux | [] [] |\nve | [] [] |\nvmm | [] |\nvorbis-tools | [] [] |\nwastesedge | [] |\nwcd | [] |\nwcd-man | [] |\nwdiff | [] [] [] [] |\nwget | [] [] [] |\nwget2 | [] |\nwyslij-po | [] [] [] |\nxboard | [] [] |\nxdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] |\nxkeyboard-config | [] [] |\nxz | [] |\n+---------------------------------------------------+\nlg lt lv mk ml mn mr ms mt nb ne nl nn or pa pl\n1 9 16 2 1 3 1 12 2 44 1 111 5 1 3 107\n\nps pt ptBR ro ru rw sk sl sq sr sv sw ta te tg\n+---------------------------------------------------+\na2ps | [] [] [] [] [] [] [] |\naegis | [] [] [] [] |\nanubis | [] [] [] [] |\naspell | [] [] [] [] [] [] [] [] [] |\nbash | [] [] [] [] [] |\nbfd | [] [] [] |\nbinutils | [] [] [] [] |\nbison | [] [] [] [] |\nbison-runtime | [] [] [] [] [] [] [] [] [] |\nbuzztrax | [] [] [] |\nccd2cue | [] [] [] |\nccide | [] [] [] |\ncflow | [] [] [] |\nclisp | [] [] |\ncoreutils | [] [] [] [] [] [] |\ncpio | [] [] [] [] [] |\ncppi | [] [] [] |\ncpplib | [] [] [] [] |\ncryptsetup | [] [] [] [] |\ndatamash | [] [] [] |\ndenemo | |\ndfarc | [] [] [] |\ndialog | [] [] [] [] [] [] [] [] [] [] |\ndico | [] [] [] |\ndiffutils | [] [] [] [] [] |\ndink | [] |\ndirevent | [] [] [] |\ndoodle | [] [] [] |\ndos2unix | [] [] [] [] |\ndos2unix-man | [] [] |\ne2fsprogs | [] [] [] |\nenscript | [] [] [] [] [] [] |\nexif | [] [] [] [] [] [] [] |\nfetchmail | [] [] [] [] [] |\nfindutils | [] [] [] [] [] [] [] |\nflex | [] [] [] [] [] [] |\nfreedink | [] [] [] [] [] |\nfusionforge | |\ngas | [] [] |\ngawk | [] [] [] [] |\ngcal | [] |\ngcc | [] [] |\ngdbm | [] [] [] [] |\ngettext-examples | [] [] [] [] [] [] [] [] [] [] |\ngettext-runtime | [] [] [] [] [] [] [] [] |\ngettext-tools | [] [] [] [] [] [] [] [] |\ngjay | [] [] |\nglunarclock | [] [] [] [] [] [] |\ngnubiff | [] [] |\ngnubik | [] [] [] [] |\ngnucash | () () () [] () () |\ngnuchess | [] [] [] |\ngnucobol | [] |\ngnulib | [] [] [] [] [] [] |\ngnunet | |\ngnunet-gtk | |\ngnutls | [] [] [] |\ngold | [] |\ngphoto2 | [] [] [] [] [] |\ngprof | [] [] [] [] [] |\ngramadoir | [] [] [] |\ngrep | [] [] [] [] [] [] [] |\ngrip | [] [] [] |\ngrub | [] [] [] [] [] [] |\ngsasl | [] [] [] [] |\ngss | [] [] [] [] [] |\ngst-plugins-bad | [] [] [] [] [] [] |\ngst-plugins-base | [] [] [] [] [] [] [] |\ngst-plugins-good | [] [] [] [] [] [] [] |\ngst-plugins-ugly | [] [] [] [] [] [] [] [] |\ngstreamer | [] [] [] [] [] [] [] |\ngtick | [] [] [] [] [] |\ngtkam | [] [] [] [] [] |\ngtkspell | [] [] [] [] [] [] [] [] [] [] |\nguix | [] |\nguix-manual | |\nguix-packages | |\ngutenprint | [] [] [] [] |\nhello | [] [] [] [] [] [] [] [] |\nhelp2man | [] [] [] [] |\nhelp2man-texi | [] [] |\nhylafax | [] |\nidutils | [] [] [] [] |\njwhois | [] [] [] [] |\nkbd | [] [] [] [] |\nklavaro | [] [] [] [] [] [] |\nld | [] [] [] |\nlibc | [] [] [] [] |\nlibexif | [] [] |\nlibextractor | [] [] |\nlibgphoto2 | [] |\nlibgphoto2port | [] [] [] [] [] |\nlibgsasl | [] [] [] [] [] |\nlibiconv | [] [] [] [] [] [] |\nlibidn | [] [] [] |\nlibidn2 | [] [] [] [] [] |\nlilypond | [] |\nlordsawar | [] |\nlprng | [] |\nlynx | [] [] [] |\nm4 | [] [] [] [] [] |\nmailfromd | [] [] |\nmailutils | [] |\nmake | [] [] [] [] [] |\nman-db | [] [] [] [] [] [] |\nman-db-manpages | [] [] [] [] [] [] |\nmeritous | [] [] |\nmidi-instruments | [] [] [] [] [] [] [] [] |\nminicom | [] [] [] [] [] |\nmkisofs | [] [] [] |\nmpop | [] [] |\nmsmtp | [] [] |\nmuibase | [] |\nmyserver | [] [] [] |\nnano | [] [] [] [] [] [] |\nopcodes | [] [] [] |\nparted | [] [] [] [] [] [] |\npies | [] |\npnmixer | [] () [] [] |\nprocps-ng | [] [] |\nprocps-ng-man | [] [] |\npsmisc | [] [] [] [] [] |\npspp | [] [] |\npushover | [] [] |\npwdutils | [] [] |\npyspread | [] |\nradius | [] |\nrecode | [] [] [] [] [] [] [] [] |\nrecutils | [] [] [] |\nrush | [] [] [] |\nsarg | [] [] [] |\nsavane | [] () |\nsed | [] [] [] [] [] [] [] [] |\nsharutils | [] [] [] |\nshepherd | [] [] [] [] |\nshishi | [] [] |\nskribilo | [] [] [] |\nsolfege | [] [] [] |\nsolfege-manual | [] |\nspotmachine | [] [] [] |\nsudo | [] [] [] [] [] [] [] |\nsudoers | [] [] [] [] [] |\nsysstat | [] [] [] [] [] [] |\ntar | [] [] [] [] [] [] [] |\ntexinfo | [] [] [] [] |\ntexinfodocument | [] [] [] |\ntigervnc | [] [] [] [] |\ntin | [] |\ntin-man | |\ntracgoogleappsa... | [] [] [] [] [] [] |\ntrader | [] [] [] [] |\nutil-linux | [] [] [] |\nve | [] [] [] [] |\nvmm | [] [] |\nvorbis-tools | [] [] [] |\nwastesedge | [] [] |\nwcd | [] [] |\nwcd-man | [] |\nwdiff | [] [] [] [] [] |\nwget | [] [] [] [] [] [] [] |\nwget2 | [] |\nwyslij-po | [] [] [] |\nxboard | [] [] |\nxdg-user-dirs | [] [] [] [] [] [] [] [] [] [] [] [] |\nxkeyboard-config | [] [] [] [] [] |\nxz | [] [] [] |\n+---------------------------------------------------+\nps pt ptBR ro ru rw sk sl sq sr sv sw ta te tg\n1 46 121 43 86 0 35 35 8 121 132 1 8 1 0\n\nth tr uk ur vi wa wo zhCN zhHK zhTW\n+------------------------------------------+\na2ps | [] [] [] [] | 30\naegis | [] | 11\nanubis | [] [] [] | 20\naspell | [] [] [] [] | 32\nbash | [] [] [] [] [] | 24\nbfd | [] | 5\nbinutils | [] | 7\nbison | [] [] | 12\nbison-runtime | [] [] [] [] [] [] | 40\nbuzztrax | [] [] | 11\nccd2cue | [] [] [] [] | 13\nccide | [] [] [] | 18\ncflow | [] [] [] | 17\nclisp | | 11\ncoreutils | [] [] [] [] | 23\ncpio | [] [] [] [] | 23\ncppi | [] [] [] | 18\ncpplib | [] [] [] [] [] | 19\ncryptsetup | [] | 13\ndatamash | [] | 11\ndenemo | [] | 5\ndfarc | [] | 18\ndialog | [] [] [] [] [] [] | 46\ndico | [] | 10\ndiffutils | [] [] [] [] [] | 28\ndink | [] | 11\ndirevent | [] [] | 13\ndoodle | [] | 14\ndos2unix | [] [] [] [] | 19\ndos2unix-man | [] [] | 9\ne2fsprogs | [] [] [] | 15\nenscript | [] [] [] | 22\nexif | [] [] [] [] | 31\nfetchmail | [] [] [] | 21\nfindutils | [] [] [] [] [] | 32\nflex | [] [] [] [] [] | 22\nfreedink | [] [] | 25\nfusionforge | | 3\ngas | [] | 7\ngawk | [] [] | 15\ngcal | [] [] | 8\ngcc | | 5\ngdbm | [] [] | 13\ngettext-examples | [] [] [] [] [] [] | 43\ngettext-runtime | [] [] [] [] [] | 34\ngettext-tools | [] [] [] [] [] | 25\ngjay | [] [] [] | 10\nglunarclock | [] [] [] [] | 28\ngnubiff | [] [] | 10\ngnubik | [] [] [] | 21\ngnucash | [] [] () () () | 8\ngnuchess | [] [] [] | 13\ngnucobol | | 3\ngnulib | [] [] [] [] | 24\ngnunet | | 1\ngnunet-gtk | | 2\ngnutls | [] [] [] | 15\ngold | [] | 5\ngphoto2 | [] [] [] [] | 19\ngprof | [] [] [] | 21\ngramadoir | [] [] | 15\ngrep | [] [] [] [] [] | 32\ngrip | [] [] [] [] [] | 24\ngrub | [] [] [] [] | 25\ngsasl | [] [] [] [] | 21\ngss | [] [] | 19\ngst-plugins-bad | [] [] [] [] [] | 26\ngst-plugins-base | [] [] [] [] | 30\ngst-plugins-good | [] [] [] [] [] | 32\ngst-plugins-ugly | [] [] [] [] [] | 38\ngstreamer | [] [] [] [] [] | 32\ngtick | [] [] [] | 21\ngtkam | [] [] [] | 24\ngtkspell | [] [] [] [] [] [] [] [] | 50\nguix | | 5\nguix-manual | | 3\nguix-packages | | 0\ngutenprint | [] [] [] | 17\nhello | [] [] [] [] [] [] | 33\nhelp2man | [] [] [] | 19\nhelp2man-texi | [] | 7\nhylafax | [] | 6\nidutils | [] [] [] | 18\njwhois | [] [] [] [] | 20\nkbd | [] | 8\nklavaro | [] [] [] [] [] | 32\nld | [] | 7\nlibc | [] [] [] [] [] | 25\nlibexif | [] [] () | 11\nlibextractor | [] [] | 10\nlibgphoto2 | [] [] | 9\nlibgphoto2port | [] [] [] [] | 19\nlibgsasl | [] [] [] | 20\nlibiconv | [] [] [] [] [] | 30\nlibidn | [] [] [] | 18\nlibidn2 | [] [] | 14\nlilypond | | 12\nlordsawar | [] | 6\nlprng | [] | 4\nlynx | [] [] [] | 19\nm4 | [] [] [] | 24\nmailfromd | [] [] | 7\nmailutils | [] | 7\nmake | [] [] [] [] | 24\nman-db | [] [] [] [] | 22\nman-db-manpages | [] [] | 13\nmeritous | | 4\nmidi-instruments | [] [] [] [] [] [] | 43\nminicom | [] [] | 18\nmkisofs | [] [] [] | 15\nmpop | [] | 6\nmsmtp | [] | 6\nmuibase | [] | 4\nmyserver | [] | 10\nnano | [] [] [] [] [] | 30\nopcodes | [] | 7\nparted | [] [] [] [] [] | 24\npies | [] [] | 7\npnmixer | [] [] () | 13\nprocps-ng | [] [] | 7\nprocps-ng-man | [] | 6\npsmisc | [] [] [] [] | 22\npspp | [] [] [] | 16\npushover | | 7\npwdutils | [] | 9\npyspread | [] | 6\nradius | [] [] | 9\nrecode | [] [] [] [] | 31\nrecutils | [] [] | 9\nrush | [] [] [] | 12\nsarg | | 7\nsavane | | 3\nsed | [] [] [] [] [] | 36\nsharutils | [] [] [] | 13\nshepherd | [] | 9\nshishi | [] [] | 8\nskribilo | [] | 9\nsolfege | [] [] [] | 21\nsolfege-manual | [] | 10\nspotmachine | [] [] | 11\nsudo | [] [] [] [] [] | 31\nsudoers | [] [] [] [] | 23\nsysstat | [] [] [] | 19\ntar | [] [] [] [] [] | 33\ntexinfo | [] [] [] | 20\ntexinfodocument | [] | 15\ntigervnc | [] [] [] [] [] | 23\ntin | [] [] [] | 8\ntin-man | | 1\ntracgoogleappsa... | [] [] [] [] [] | 25\ntrader | | 13\nutil-linux | [] [] [] [] | 16\nve | [] [] [] | 17\nvmm | | 5\nvorbis-tools | [] | 14\nwastesedge | [] | 7\nwcd | [] [] [] | 13\nwcd-man | [] | 5\nwdiff | [] [] [] [] | 26\nwget | [] [] [] [] [] | 27\nwget2 | [] | 7\nwyslij-po | [] [] [] | 19\nxboard | [] [] [] | 11\nxdg-user-dirs | [] [] [] [] [] [] [] [] | 70\nxkeyboard-config | [] [] | 25\nxz | [] [] [] [] | 16\n+------------------------------------------+\n85 teams th tr uk ur vi wa wo zhCN zhHK zhTW\n166 domains 12 55 117 1 111 6 1 92 4 48 2827\n\nSome counters in the preceding matrix are higher than the number of\nvisible blocks let us expect. This is because a few extra PO files are\nused for implementing regional variants of languages, or language\ndialects.\n\nFor a PO file in the matrix above to be effective, the package to\nwhich it applies should also have been internationalized and distributed\nas such by its maintainer. There might be an observable lag between the\nmere existence a PO file and its wide availability in a distribution.\n\nIf July 2020 seems to be old, you may fetch a more recent copy of\nthis 'ABOUT-NLS' file on most GNU archive sites. The most up-to-date\nmatrix with full percentage details can be found at\n'https://translationproject.org/extra/matrix.html'.\n\nFile: gettext.info, Node: Using gettext in own code, Prev: Available Packages, Up: The original ABOUT-NLS\n\n\nIf you are writing a freely available program and want to\ninternationalize it you are welcome to use GNU 'gettext' in your\npackage. Of course you have to respect the GNU Lesser General Public\nLicense which covers the use of the GNU 'gettext' library. This means\nin particular that even non-free programs can use 'libintl' as a shared\nlibrary, whereas only free software can use 'libintl' as a static\nlibrary or use modified versions of 'libintl'.\n\nOnce the sources are changed appropriately and the setup can handle\nthe use of 'gettext' the only thing missing are the translations. The\nFree Translation Project is also available for packages which are not\ndeveloped inside the GNU project. Therefore the information given above\napplies also for every other Free Software Project. Contact\n'coordinator@translationproject.org' to make the '.pot' files available\nto the translation teams.\n\nFile: gettext.info, Node: References, Prev: The original ABOUT-NLS, Up: Conclusion\n" }, { "name": "17.3 Related Readings", "content": "* NOTE: * This documentation section is outdated and needs to be\nrevised.\n\nEugene H. Dorr ('dorre@well.com') maintains an interesting\nbibliography on internationalization matters, called\n'Internationalization Reference List', which is available as:\nftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/i18n-books.txt\n\nMichael Gschwind ('mike@vlsivie.tuwien.ac.at') maintains a Frequently\nAsked Questions (FAQ) list, entitled 'Programming for\nInternationalisation'. This FAQ discusses writing programs which can\nhandle different language conventions, character sets, etc.; and is\napplicable to all character set encodings, with particular emphasis on\nISO 8859-1. It is regularly published in Usenet groups\n'comp.unix.questions', 'comp.std.internat',\n'comp.software.international', 'comp.lang.c', 'comp.windows.x',\n'comp.std.c', 'comp.answers' and 'news.answers'. The home location of\nthis document is:\nftp://ftp.vlsivie.tuwien.ac.at/pub/8bit/ISO-programming\n\nPatrick D'Cruze ('pdcruze@li.org') wrote a tutorial about NLS\nmatters, and Jochen Hein ('Hein@student.tu-clausthal.de') took over the\nresponsibility of maintaining it. It may be found as:\nftp://sunsite.unc.edu/pub/Linux/utils/nls/catalogs/Incoming/...\n...locale-tutorial-0.8.txt.gz\nThis site is mirrored in:\nftp://ftp.ibp.fr/pub/linux/sunsite/\n\nA French version of the same tutorial should be findable at:\nftp://ftp.ibp.fr/pub/linux/french/docs/\ntogether with French translations of many Linux-related documents.\n\nFile: gettext.info, Node: Language Codes, Next: Country Codes, Prev: Conclusion, Up: Top\n" } ] }, "Appendix A Language Codes": { "content": "The ISO 639 standard defines two-letter codes for many languages, and\nthree-letter codes for more rarely used languages. All abbreviations\nfor languages used in the Translation Project should come from this\nstandard.\n\n* Menu:\n\n* Usual Language Codes:: Two-letter ISO 639 language codes\n* Rare Language Codes:: Three-letter ISO 639 language codes\n\nFile: gettext.info, Node: Usual Language Codes, Next: Rare Language Codes, Up: Language Codes\n", "subsections": [ { "name": "A.1 Usual Language Codes", "content": "For the commonly used languages, the ISO 639-1 standard defines\ntwo-letter codes.\n\n'aa'\nAfar.\n'ab'\nAbkhazian.\n'ae'\nAvestan.\n'af'\nAfrikaans.\n'ak'\nAkan.\n'am'\nAmharic.\n'an'\nAragonese.\n'ar'\nArabic.\n'as'\nAssamese.\n'av'\nAvaric.\n'ay'\nAymara.\n'az'\nAzerbaijani.\n'ba'\nBashkir.\n'be'\nBelarusian.\n'bg'\nBulgarian.\n'bh'\nBihari languages.\n'bi'\nBislama.\n'bm'\nBambara.\n'bn'\nBengali.\n'bo'\nTibetan.\n'br'\nBreton.\n'bs'\nBosnian.\n'ca'\nCatalan; Valencian.\n'ce'\nChechen.\n'ch'\nChamorro.\n'co'\nCorsican.\n'cr'\nCree.\n'cs'\nCzech.\n'cu'\nChurch Slavic; Old Slavonic; Church Slavonic; Old Bulgarian; Old\nChurch Slavonic.\n'cv'\nChuvash.\n'cy'\nWelsh.\n'da'\nDanish.\n'de'\nGerman.\n'dv'\nDivehi; Dhivehi; Maldivian.\n'dz'\nDzongkha.\n'ee'\nEwe.\n'el'\nGreek, Modern (1453-).\n'en'\nEnglish.\n'eo'\nEsperanto.\n'es'\nSpanish; Castilian.\n'et'\nEstonian.\n'eu'\nBasque.\n'fa'\nPersian.\n'ff'\nFulah.\n'fi'\nFinnish.\n'fj'\nFijian.\n'fo'\nFaroese.\n'fr'\nFrench.\n'fy'\nWestern Frisian.\n'ga'\nIrish.\n'gd'\nGaelic; Scottish Gaelic.\n'gl'\nGalician.\n'gn'\nGuarani.\n'gu'\nGujarati.\n'gv'\nManx.\n'ha'\nHausa.\n'he'\nHebrew.\n'hi'\nHindi.\n'ho'\nHiri Motu.\n'hr'\nCroatian.\n'ht'\nHaitian; Haitian Creole.\n'hu'\nHungarian.\n'hy'\nArmenian.\n'hz'\nHerero.\n'ia'\nInterlingua (International Auxiliary Language Association).\n'id'\nIndonesian.\n'ie'\nInterlingue; Occidental.\n'ig'\nIgbo.\n'ii'\nSichuan Yi; Nuosu.\n'ik'\nInupiak.\n'io'\nIdo.\n'is'\nIcelandic.\n'it'\nItalian.\n'iu'\nInuktitut.\n'ja'\nJapanese.\n'jv'\nJavanese.\n'ka'\nGeorgian.\n'kg'\nKongo.\n'ki'\nKikuyu; Gikuyu.\n'kj'\nKuanyama; Kwanyama.\n'kk'\nKazakh.\n'kl'\nKalaallisut; Greenlandic.\n'km'\nCentral Khmer.\n'kn'\nKannada.\n'ko'\nKorean.\n'kr'\nKanuri.\n'ks'\nKashmiri.\n'ku'\nKurdish.\n'kv'\nKomi.\n'kw'\nCornish.\n'ky'\nKirghiz; Kyrgyz.\n'la'\nLatin.\n'lb'\nLuxembourgish; Letzeburgesch.\n'lg'\nGanda.\n'li'\nLimburgan; Limburger; Limburgish.\n'ln'\nLingala.\n'lo'\nLao.\n'lt'\nLithuanian.\n'lu'\nLuba-Katanga.\n'lv'\nLatvian.\n'mg'\nMalagasy.\n'mh'\nMarshallese.\n'mi'\nMaori.\n'mk'\nMacedonian.\n'ml'\nMalayalam.\n'mn'\nMongolian.\n'mr'\nMarathi.\n'ms'\nMalay.\n'mt'\nMaltese.\n'my'\nBurmese.\n'na'\nNauru.\n'nb'\nBokm??l, Norwegian; Norwegian Bokm??l.\n'nd'\nNdebele, North; North Ndebele.\n'ne'\nNepali.\n'ng'\nNdonga.\n'nl'\nDutch; Flemish.\n'nn'\nNorwegian Nynorsk; Nynorsk, Norwegian.\n'no'\nNorwegian.\n'nr'\nNdebele, South; South Ndebele.\n'nv'\nNavajo; Navaho.\n'ny'\nChichewa; Nyanja.\n'oc'\nOccitan (post 1500); Provenc,al.\n'oj'\nOjibwa.\n'om'\nOromo.\n'or'\nOriya.\n'os'\nOssetian; Ossetic.\n'pa'\nPanjabi; Punjabi.\n'pi'\nPali.\n'pl'\nPolish.\n'ps'\nPushto; Pashto.\n'pt'\nPortuguese.\n'qu'\nQuechua.\n'rm'\nRomansh.\n'rn'\nRundi.\n'ro'\nRomanian; Moldavian; Moldovan.\n'ru'\nRussian.\n'rw'\nKinyarwanda.\n'sa'\nSanskrit.\n'sc'\nSardinian.\n'sd'\nSindhi.\n'se'\nNorthern Sami.\n'sg'\nSango.\n'si'\nSinhala; Sinhalese.\n'sk'\nSlovak.\n'sl'\nSlovenian.\n'sm'\nSamoan.\n'sn'\nShona.\n'so'\nSomali.\n'sq'\nAlbanian.\n'sr'\nSerbian.\n'ss'\nSwati.\n'st'\nSotho, Southern.\n'su'\nSundanese.\n'sv'\nSwedish.\n'sw'\nSwahili.\n'ta'\nTamil.\n'te'\nTelugu.\n'tg'\nTajik.\n'th'\nThai.\n'ti'\nTigrinya.\n'tk'\nTurkmen.\n'tl'\nTagalog.\n'tn'\nTswana.\n'to'\nTonga (Tonga Islands).\n'tr'\nTurkish.\n'ts'\nTsonga.\n'tt'\nTatar.\n'tw'\nTwi.\n'ty'\nTahitian.\n'ug'\nUighur; Uyghur.\n'uk'\nUkrainian.\n'ur'\nUrdu.\n'uz'\nUzbek.\n've'\nVenda.\n'vi'\nVietnamese.\n'vo'\nVolapu\"k.\n'wa'\nWalloon.\n'wo'\nWolof.\n'xh'\nXhosa.\n'yi'\nYiddish.\n'yo'\nYoruba.\n'za'\nZhuang; Chuang.\n'zh'\nChinese.\n'zu'\nZulu.\n\nFile: gettext.info, Node: Rare Language Codes, Prev: Usual Language Codes, Up: Language Codes\n" }, { "name": "A.2 Rare Language Codes", "content": "For rarely used languages, the ISO 639-2 standard defines\nthree-letter codes. Here is the current list, reduced to only living\nlanguages with at least one million of speakers.\n\n'ace'\nAchinese.\n'awa'\nAwadhi.\n'bal'\nBaluchi.\n'ban'\nBalinese.\n'bej'\nBeja; Bedawiyet.\n'bem'\nBemba.\n'bho'\nBhojpuri.\n'bik'\nBikol.\n'bin'\nBini; Edo.\n'bug'\nBuginese.\n'ceb'\nCebuano.\n'din'\nDinka.\n'doi'\nDogri.\n'fil'\nFilipino; Pilipino.\n'fon'\nFon.\n'gon'\nGondi.\n'gsw'\nSwiss German; Alemannic; Alsatian.\n'hil'\nHiligaynon.\n'hmn'\nHmong.\n'ilo'\nIloko.\n'kab'\nKabyle.\n'kam'\nKamba.\n'kbd'\nKabardian.\n'kmb'\nKimbundu.\n'kok'\nKonkani.\n'kru'\nKurukh.\n'lua'\nLuba-Lulua.\n'luo'\nLuo (Kenya and Tanzania).\n'mad'\nMadurese.\n'mag'\nMagahi.\n'mai'\nMaithili.\n'mak'\nMakasar.\n'man'\nMandingo.\n'men'\nMende.\n'min'\nMinangkabau.\n'mni'\nManipuri.\n'mos'\nMossi.\n'mwr'\nMarwari.\n'nap'\nNeapolitan.\n'nso'\nPedi; Sepedi; Northern Sotho.\n'nym'\nNyamwezi.\n'nyn'\nNyankole.\n'pag'\nPangasinan.\n'pam'\nPampanga; Kapampangan.\n'raj'\nRajasthani.\n'sas'\nSasak.\n'sat'\nSantali.\n'scn'\nSicilian.\n'shn'\nShan.\n'sid'\nSidamo.\n'srr'\nSerer.\n'suk'\nSukuma.\n'sus'\nSusu.\n'tem'\nTimne.\n'tiv'\nTiv.\n'tum'\nTumbuka.\n'umb'\nUmbundu.\n'wal'\nWalamo.\n'war'\nWaray.\n'yao'\nYao.\n\nFile: gettext.info, Node: Country Codes, Next: Licenses, Prev: Language Codes, Up: Top\n" } ] }, "Appendix B Country Codes": { "content": "The ISO 3166 standard defines two character codes for many countries\nand territories. All abbreviations for countries used in the\nTranslation Project should come from this standard.\n\n'AD'\nAndorra.\n'AE'\nUnited Arab Emirates.\n'AF'\nAfghanistan.\n'AG'\nAntigua and Barbuda.\n'AI'\nAnguilla.\n'AL'\nAlbania.\n'AM'\nArmenia.\n'AO'\nAngola.\n'AQ'\nAntarctica.\n'AR'\nArgentina.\n'AS'\nAmerican Samoa.\n'AT'\nAustria.\n'AU'\nAustralia.\n'AW'\nAruba.\n'AX'\nAaland Islands.\n'AZ'\nAzerbaijan.\n'BA'\nBosnia and Herzegovina.\n'BB'\nBarbados.\n'BD'\nBangladesh.\n'BE'\nBelgium.\n'BF'\nBurkina Faso.\n'BG'\nBulgaria.\n'BH'\nBahrain.\n'BI'\nBurundi.\n'BJ'\nBenin.\n'BL'\nSaint Barthelemy.\n'BM'\nBermuda.\n'BN'\nBrunei Darussalam.\n'BO'\nBolivia, Plurinational State of.\n'BQ'\nBonaire, Sint Eustatius and Saba.\n'BR'\nBrazil.\n'BS'\nBahamas.\n'BT'\nBhutan.\n'BV'\nBouvet Island.\n'BW'\nBotswana.\n'BY'\nBelarus.\n'BZ'\nBelize.\n'CA'\nCanada.\n'CC'\nCocos (Keeling) Islands.\n'CD'\nCongo, The Democratic Republic of the.\n'CF'\nCentral African Republic.\n'CG'\nCongo.\n'CH'\nSwitzerland.\n'CI'\nC??te d'Ivoire.\n'CK'\nCook Islands.\n'CL'\nChile.\n'CM'\nCameroon.\n'CN'\nChina.\n'CO'\nColombia.\n'CR'\nCosta Rica.\n'CU'\nCuba.\n'CV'\nCape Verde.\n'CW'\nCurac,ao.\n'CX'\nChristmas Island.\n'CY'\nCyprus.\n'CZ'\nCzech Republic.\n'DE'\nGermany.\n'DJ'\nDjibouti.\n'DK'\nDenmark.\n'DM'\nDominica.\n'DO'\nDominican Republic.\n'DZ'\nAlgeria.\n'EC'\nEcuador.\n'EE'\nEstonia.\n'EG'\nEgypt.\n'EH'\nWestern Sahara.\n'ER'\nEritrea.\n'ES'\nSpain.\n'ET'\nEthiopia.\n'FI'\nFinland.\n'FJ'\nFiji.\n'FK'\nFalkland Islands (Malvinas).\n'FM'\nMicronesia, Federated States of.\n'FO'\nFaroe Islands.\n'FR'\nFrance.\n'GA'\nGabon.\n'GB'\nUnited Kingdom.\n'GD'\nGrenada.\n'GE'\nGeorgia.\n'GF'\nFrench Guiana.\n'GG'\nGuernsey.\n'GH'\nGhana.\n'GI'\nGibraltar.\n'GL'\nGreenland.\n'GM'\nGambia.\n'GN'\nGuinea.\n'GP'\nGuadeloupe.\n'GQ'\nEquatorial Guinea.\n'GR'\nGreece.\n'GS'\nSouth Georgia and the South Sandwich Islands.\n'GT'\nGuatemala.\n'GU'\nGuam.\n'GW'\nGuinea-Bissau.\n'GY'\nGuyana.\n'HK'\nHong Kong.\n'HM'\nHeard Island and McDonald Islands.\n'HN'\nHonduras.\n'HR'\nCroatia.\n'HT'\nHaiti.\n'HU'\nHungary.\n'ID'\nIndonesia.\n'IE'\nIreland.\n'IL'\nIsrael.\n'IM'\nIsle of Man.\n'IN'\nIndia.\n'IO'\nBritish Indian Ocean Territory.\n'IQ'\nIraq.\n'IR'\nIran, Islamic Republic of.\n'IS'\nIceland.\n'IT'\nItaly.\n'JE'\nJersey.\n'JM'\nJamaica.\n'JO'\nJordan.\n'JP'\nJapan.\n'KE'\nKenya.\n'KG'\nKyrgyzstan.\n'KH'\nCambodia.\n'KI'\nKiribati.\n'KM'\nComoros.\n'KN'\nSaint Kitts and Nevis.\n'KP'\nKorea, Democratic People's Republic of.\n'KR'\nKorea, Republic of.\n'KW'\nKuwait.\n'KY'\nCayman Islands.\n'KZ'\nKazakhstan.\n'LA'\nLao People's Democratic Republic.\n'LB'\nLebanon.\n'LC'\nSaint Lucia.\n'LI'\nLiechtenstein.\n'LK'\nSri Lanka.\n'LR'\nLiberia.\n'LS'\nLesotho.\n'LT'\nLithuania.\n'LU'\nLuxembourg.\n'LV'\nLatvia.\n'LY'\nLibya.\n'MA'\nMorocco.\n'MC'\nMonaco.\n'MD'\nMoldova, Republic of.\n'ME'\nMontenegro.\n'MF'\nSaint Martin (French part).\n'MG'\nMadagascar.\n'MH'\nMarshall Islands.\n'MK'\nNorth Macedonia.\n'ML'\nMali.\n'MM'\nMyanmar.\n'MN'\nMongolia.\n'MO'\nMacao.\n'MP'\nNorthern Mariana Islands.\n'MQ'\nMartinique.\n'MR'\nMauritania.\n'MS'\nMontserrat.\n'MT'\nMalta.\n'MU'\nMauritius.\n'MV'\nMaldives.\n'MW'\nMalawi.\n'MX'\nMexico.\n'MY'\nMalaysia.\n'MZ'\nMozambique.\n'NA'\nNamibia.\n'NC'\nNew Caledonia.\n'NE'\nNiger.\n'NF'\nNorfolk Island.\n'NG'\nNigeria.\n'NI'\nNicaragua.\n'NL'\nNetherlands.\n'NO'\nNorway.\n'NP'\nNepal.\n'NR'\nNauru.\n'NU'\nNiue.\n'NZ'\nNew Zealand.\n'OM'\nOman.\n'PA'\nPanama.\n'PE'\nPeru.\n'PF'\nFrench Polynesia.\n'PG'\nPapua New Guinea.\n'PH'\nPhilippines.\n'PK'\nPakistan.\n'PL'\nPoland.\n'PM'\nSaint Pierre and Miquelon.\n'PN'\nPitcairn.\n'PR'\nPuerto Rico.\n'PS'\nPalestine, State of.\n'PT'\nPortugal.\n'PW'\nPalau.\n'PY'\nParaguay.\n'QA'\nQatar.\n'RE'\nReunion.\n'RO'\nRomania.\n'RS'\nSerbia.\n'RU'\nRussian Federation.\n'RW'\nRwanda.\n'SA'\nSaudi Arabia.\n'SB'\nSolomon Islands.\n'SC'\nSeychelles.\n'SD'\nSudan.\n'SE'\nSweden.\n'SG'\nSingapore.\n'SH'\nSaint Helena, Ascension and Tristan da Cunha.\n'SI'\nSlovenia.\n'SJ'\nSvalbard and Jan Mayen.\n'SK'\nSlovakia.\n'SL'\nSierra Leone.\n'SM'\nSan Marino.\n'SN'\nSenegal.\n'SO'\nSomalia.\n'SR'\nSuriname.\n'SS'\nSouth Sudan.\n'ST'\nSao Tome and Principe.\n'SV'\nEl Salvador.\n'SX'\nSint Maarten (Dutch part).\n'SY'\nSyrian Arab Republic.\n'SZ'\nSwaziland.\n'TC'\nTurks and Caicos Islands.\n'TD'\nChad.\n'TF'\nFrench Southern Territories.\n'TG'\nTogo.\n'TH'\nThailand.\n'TJ'\nTajikistan.\n'TK'\nTokelau.\n'TL'\nTimor-Leste.\n'TM'\nTurkmenistan.\n'TN'\nTunisia.\n'TO'\nTonga.\n'TR'\nTurkey.\n'TT'\nTrinidad and Tobago.\n'TV'\nTuvalu.\n'TW'\nTaiwan, Province of China.\n'TZ'\nTanzania, United Republic of.\n'UA'\nUkraine.\n'UG'\nUganda.\n'UM'\nUnited States Minor Outlying Islands.\n'US'\nUnited States.\n'UY'\nUruguay.\n'UZ'\nUzbekistan.\n'VA'\nHoly See (Vatican City State).\n'VC'\nSaint Vincent and the Grenadines.\n'VE'\nVenezuela, Bolivarian Republic of.\n'VG'\nVirgin Islands, British.\n'VI'\nVirgin Islands, U.S..\n'VN'\nViet Nam.\n'VU'\nVanuatu.\n'WF'\nWallis and Futuna.\n'WS'\nSamoa.\n'YE'\nYemen.\n'YT'\nMayotte.\n'ZA'\nSouth Africa.\n'ZM'\nZambia.\n'ZW'\nZimbabwe.\n\nFile: gettext.info, Node: Licenses, Next: Program Index, Prev: Country Codes, Up: Top\n", "subsections": [] }, "Appendix C Licenses": { "content": "The files of this package are covered by the licenses indicated in\neach particular file or directory. Here is a summary:\n\n* The 'libintl' and 'libasprintf' libraries are covered by the GNU\nLesser General Public License (LGPL). A copy of the license is\nincluded in *note GNU LGPL::.\n\n* The executable programs of this package and the 'libgettextpo'\nlibrary are covered by the GNU General Public License (GPL). A copy\nof the license is included in *note GNU GPL::.\n\n* This manual is free documentation. It is dually licensed under the\nGNU FDL and the GNU GPL. This means that you can redistribute this\nmanual under either of these two licenses, at your choice.\nThis manual is covered by the GNU FDL. Permission is granted to\ncopy, distribute and/or modify this document under the terms of the\nGNU Free Documentation License (FDL), either version 1.2 of the\nLicense, or (at your option) any later version published by the\nFree Software Foundation (FSF); with no Invariant Sections, with no\nFront-Cover Text, and with no Back-Cover Texts. A copy of the\nlicense is included in *note GNU FDL::.\nThis manual is covered by the GNU GPL. You can redistribute it\nand/or modify it under the terms of the GNU General Public License\n(GPL), either version 2 of the License, or (at your option) any\nlater version published by the Free Software Foundation (FSF). A\ncopy of the license is included in *note GNU GPL::.\n\n* Menu:\n\n* GNU GPL:: GNU General Public License\n* GNU LGPL:: GNU Lesser General Public License\n* GNU FDL:: GNU Free Documentation License\n\nFile: gettext.info, Node: GNU GPL, Next: GNU LGPL, Up: Licenses\n", "subsections": [ { "name": "C.1 GNU GENERAL PUBLIC LICENSE", "content": "Version 2, June 1991\n\nCopyright (C) 1989, 1991 Free Software Foundation, Inc.\n51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA\n\nEveryone is permitted to copy and distribute verbatim copies\nof this license document, but changing it is not allowed.\n" }, { "name": "Preamble", "content": "The licenses for most software are designed to take away your freedom\nto share and change it. By contrast, the GNU General Public License is\nintended to guarantee your freedom to share and change free software--to\nmake sure the software is free for all its users. This General Public\nLicense applies to most of the Free Software Foundation's software and\nto any other program whose authors commit to using it. (Some other Free\nSoftware Foundation software is covered by the GNU Lesser General Public\nLicense instead.) You can apply it to your programs, too.\n\nWhen we speak of free software, we are referring to freedom, not\nprice. Our General Public Licenses are designed to make sure that you\nhave the freedom to distribute copies of free software (and charge for\nthis service if you wish), that you receive source code or can get it if\nyou want it, that you can change the software or use pieces of it in new\nfree programs; and that you know you can do these things.\n\nTo protect your rights, we need to make restrictions that forbid\nanyone to deny you these rights or to ask you to surrender the rights.\nThese restrictions translate to certain responsibilities for you if you\ndistribute copies of the software, or if you modify it.\n\nFor example, if you distribute copies of such a program, whether\ngratis or for a fee, you must give the recipients all the rights that\nyou have. You must make sure that they, too, receive or can get the\nsource code. And you must show them these terms so they know their\nrights.\n\nWe protect your rights with two steps: (1) copyright the software,\nand (2) offer you this license which gives you legal permission to copy,\ndistribute and/or modify the software.\n\nAlso, for each author's protection and ours, we want to make certain\nthat everyone understands that there is no warranty for this free\nsoftware. If the software is modified by someone else and passed on, we\nwant its recipients to know that what they have is not the original, so\nthat any problems introduced by others will not reflect on the original\nauthors' reputations.\n\nFinally, any free program is threatened constantly by software\npatents. We wish to avoid the danger that redistributors of a free\nprogram will individually obtain patent licenses, in effect making the\nprogram proprietary. To prevent this, we have made it clear that any\npatent must be licensed for everyone's free use or not licensed at all.\n\nThe precise terms and conditions for copying, distribution and\nmodification follow.\n" }, { "name": "TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION", "content": "0. This License applies to any program or other work which contains a\nnotice placed by the copyright holder saying it may be distributed\nunder the terms of this General Public License. The \"Program\",\nbelow, refers to any such program or work, and a \"work based on the\nProgram\" means either the Program or any derivative work under\ncopyright law: that is to say, a work containing the Program or a\nportion of it, either verbatim or with modifications and/or\ntranslated into another language. (Hereinafter, translation is\nincluded without limitation in the term \"modification\".) Each\nlicensee is addressed as \"you\".\n\nActivities other than copying, distribution and modification are\nnot covered by this License; they are outside its scope. The act\nof running the Program is not restricted, and the output from the\nProgram is covered only if its contents constitute a work based on\nthe Program (independent of having been made by running the\nProgram). Whether that is true depends on what the Program does.\n\n1. You may copy and distribute verbatim copies of the Program's source\ncode as you receive it, in any medium, provided that you\nconspicuously and appropriately publish on each copy an appropriate\ncopyright notice and disclaimer of warranty; keep intact all the\nnotices that refer to this License and to the absence of any\nwarranty; and give any other recipients of the Program a copy of\nthis License along with the Program.\n\nYou may charge a fee for the physical act of transferring a copy,\nand you may at your option offer warranty protection in exchange\nfor a fee.\n\n2. You may modify your copy or copies of the Program or any portion of\nit, thus forming a work based on the Program, and copy and\ndistribute such modifications or work under the terms of Section 1\nabove, provided that you also meet all of these conditions:\n\na. You must cause the modified files to carry prominent notices\nstating that you changed the files and the date of any change.\n\nb. You must cause any work that you distribute or publish, that\nin whole or in part contains or is derived from the Program or\nany part thereof, to be licensed as a whole at no charge to\nall third parties under the terms of this License.\n\nc. If the modified program normally reads commands interactively\nwhen run, you must cause it, when started running for such\ninteractive use in the most ordinary way, to print or display\nan announcement including an appropriate copyright notice and\na notice that there is no warranty (or else, saying that you\nprovide a warranty) and that users may redistribute the\nprogram under these conditions, and telling the user how to\nview a copy of this License. (Exception: if the Program\nitself is interactive but does not normally print such an\nannouncement, your work based on the Program is not required\nto print an announcement.)\n\nThese requirements apply to the modified work as a whole. If\nidentifiable sections of that work are not derived from the\nProgram, and can be reasonably considered independent and separate\nworks in themselves, then this License, and its terms, do not apply\nto those sections when you distribute them as separate works. But\nwhen you distribute the same sections as part of a whole which is a\nwork based on the Program, the distribution of the whole must be on\nthe terms of this License, whose permissions for other licensees\nextend to the entire whole, and thus to each and every part\nregardless of who wrote it.\n\nThus, it is not the intent of this section to claim rights or\ncontest your rights to work written entirely by you; rather, the\nintent is to exercise the right to control the distribution of\nderivative or collective works based on the Program.\n\nIn addition, mere aggregation of another work not based on the\nProgram with the Program (or with a work based on the Program) on a\nvolume of a storage or distribution medium does not bring the other\nwork under the scope of this License.\n\n3. You may copy and distribute the Program (or a work based on it,\nunder Section 2) in object code or executable form under the terms\nof Sections 1 and 2 above provided that you also do one of the\nfollowing:\n\na. Accompany it with the complete corresponding machine-readable\nsource code, which must be distributed under the terms of\nSections 1 and 2 above on a medium customarily used for\nsoftware interchange; or,\n\nb. Accompany it with a written offer, valid for at least three\nyears, to give any third party, for a charge no more than your\ncost of physically performing source distribution, a complete\nmachine-readable copy of the corresponding source code, to be\ndistributed under the terms of Sections 1 and 2 above on a\nmedium customarily used for software interchange; or,\n\nc. Accompany it with the information you received as to the offer\nto distribute corresponding source code. (This alternative is\nallowed only for noncommercial distribution and only if you\nreceived the program in object code or executable form with\nsuch an offer, in accord with Subsection b above.)\n\nThe source code for a work means the preferred form of the work for\nmaking modifications to it. For an executable work, complete\nsource code means all the source code for all modules it contains,\nplus any associated interface definition files, plus the scripts\nused to control compilation and installation of the executable.\nHowever, as a special exception, the source code distributed need\nnot include anything that is normally distributed (in either source\nor binary form) with the major components (compiler, kernel, and so\non) of the operating system on which the executable runs, unless\nthat component itself accompanies the executable.\n\nIf distribution of executable or object code is made by offering\naccess to copy from a designated place, then offering equivalent\naccess to copy the source code from the same place counts as\ndistribution of the source code, even though third parties are not\ncompelled to copy the source along with the object code.\n\n4. You may not copy, modify, sublicense, or distribute the Program\nexcept as expressly provided under this License. Any attempt\notherwise to copy, modify, sublicense or distribute the Program is\nvoid, and will automatically terminate your rights under this\nLicense. However, parties who have received copies, or rights,\nfrom you under this License will not have their licenses terminated\nso long as such parties remain in full compliance.\n\n5. You are not required to accept this License, since you have not\nsigned it. However, nothing else grants you permission to modify\nor distribute the Program or its derivative works. These actions\nare prohibited by law if you do not accept this License.\nTherefore, by modifying or distributing the Program (or any work\nbased on the Program), you indicate your acceptance of this License\nto do so, and all its terms and conditions for copying,\ndistributing or modifying the Program or works based on it.\n\n6. Each time you redistribute the Program (or any work based on the\nProgram), the recipient automatically receives a license from the\noriginal licensor to copy, distribute or modify the Program subject\nto these terms and conditions. You may not impose any further\nrestrictions on the recipients' exercise of the rights granted\nherein. You are not responsible for enforcing compliance by third\nparties to this License.\n\n7. If, as a consequence of a court judgment or allegation of patent\ninfringement or for any other reason (not limited to patent\nissues), conditions are imposed on you (whether by court order,\nagreement or otherwise) that contradict the conditions of this\nLicense, they do not excuse you from the conditions of this\nLicense. If you cannot distribute so as to satisfy simultaneously\nyour obligations under this License and any other pertinent\nobligations, then as a consequence you may not distribute the\nProgram at all. For example, if a patent license would not permit\nroyalty-free redistribution of the Program by all those who receive\ncopies directly or indirectly through you, then the only way you\ncould satisfy both it and this License would be to refrain entirely\nfrom distribution of the Program.\n\nIf any portion of this section is held invalid or unenforceable\nunder any particular circumstance, the balance of the section is\nintended to apply and the section as a whole is intended to apply\nin other circumstances.\n\nIt is not the purpose of this section to induce you to infringe any\npatents or other property right claims or to contest validity of\nany such claims; this section has the sole purpose of protecting\nthe integrity of the free software distribution system, which is\nimplemented by public license practices. Many people have made\ngenerous contributions to the wide range of software distributed\nthrough that system in reliance on consistent application of that\nsystem; it is up to the author/donor to decide if he or she is\nwilling to distribute software through any other system and a\nlicensee cannot impose that choice.\n\nThis section is intended to make thoroughly clear what is believed\nto be a consequence of the rest of this License.\n\n8. If the distribution and/or use of the Program is restricted in\ncertain countries either by patents or by copyrighted interfaces,\nthe original copyright holder who places the Program under this\nLicense may add an explicit geographical distribution limitation\nexcluding those countries, so that distribution is permitted only\nin or among countries not thus excluded. In such case, this\nLicense incorporates the limitation as if written in the body of\nthis License.\n\n9. The Free Software Foundation may publish revised and/or new\nversions of the General Public License from time to time. Such new\nversions will be similar in spirit to the present version, but may\ndiffer in detail to address new problems or concerns.\n\nEach version is given a distinguishing version number. If the\nProgram specifies a version number of this License which applies to\nit and \"any later version\", you have the option of following the\nterms and conditions either of that version or of any later version\npublished by the Free Software Foundation. If the Program does not\nspecify a version number of this License, you may choose any\nversion ever published by the Free Software Foundation.\n\n10. If you wish to incorporate parts of the Program into other free\nprograms whose distribution conditions are different, write to the\nauthor to ask for permission. For software which is copyrighted by\nthe Free Software Foundation, write to the Free Software\nFoundation; we sometimes make exceptions for this. Our decision\nwill be guided by the two goals of preserving the free status of\nall derivatives of our free software and of promoting the sharing\nand reuse of software generally.\n\nNO WARRANTY\n\n11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO\nWARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE\nLAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS\nAND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY\nOF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT\nLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS\nFOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND\nPERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE\nDEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR\nOR CORRECTION.\n\n12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN\nWRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY\nMODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE\nLIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,\nINCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR\nINABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF\nDATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU\nOR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY\nOTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN\nADVISED OF THE POSSIBILITY OF SUCH DAMAGES.\n\nEND OF TERMS AND CONDITIONS\n" }, { "name": "Appendix: How to Apply These Terms to Your New Programs", "content": "If you develop a new program, and you want it to be of the greatest\npossible use to the public, the best way to achieve this is to make it\nfree software which everyone can redistribute and change under these\nterms.\n\nTo do so, attach the following notices to the program. It is safest\nto attach them to the start of each source file to most effectively\nconvey the exclusion of warranty; and each file should have at least the\n\"copyright\" line and a pointer to where the full notice is found.\n\nONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES.\nCopyright (C) YYYY NAME OF AUTHOR\n\nThis program is free software; you can redistribute it and/or modify\nit under the terms of the GNU General Public License as published by\nthe Free Software Foundation; either version 2 of the License, or\n(at your option) any later version.\n\nThis program is distributed in the hope that it will be useful,\nbut WITHOUT ANY WARRANTY; without even the implied warranty of\nMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\nGNU General Public License for more details.\n\nYou should have received a copy of the GNU General Public License\nalong with this program; if not, write to the Free Software\nFoundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.\n\nAlso add information on how to contact you by electronic and paper\nmail.\n\nIf the program is interactive, make it output a short notice like\nthis when it starts in an interactive mode:\n\nGnomovision version 69, Copyright (C) YEAR NAME OF AUTHOR\nGnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\nThis is free software, and you are welcome to redistribute it\nunder certain conditions; type `show c' for details.\n\nThe hypothetical commands 'show w' and 'show c' should show the\nappropriate parts of the General Public License. Of course, the\ncommands you use may be called something other than 'show w' and 'show\nc'; they could even be mouse-clicks or menu items--whatever suits your\nprogram.\n\nYou should also get your employer (if you work as a programmer) or\nyour school, if any, to sign a \"copyright disclaimer\" for the program,\nif necessary. Here is a sample; alter the names:\n\nYoyodyne, Inc., hereby disclaims all copyright interest in the program\n`Gnomovision' (which makes passes at compilers) written by James Hacker.\n\nSIGNATURE OF TY COON, 1 April 1989\nTy Coon, President of Vice\n\nThis General Public License does not permit incorporating your\nprogram into proprietary programs. If your program is a subroutine\nlibrary, you may consider it more useful to permit linking proprietary\napplications with the library. If this is what you want to do, use the\nGNU Lesser General Public License instead of this License.\n\nFile: gettext.info, Node: GNU LGPL, Next: GNU FDL, Prev: GNU GPL, Up: Licenses\n" }, { "name": "C.2 GNU LESSER GENERAL PUBLIC LICENSE", "content": "Version 2.1, February 1999\n\nCopyright (C) 1991, 1999 Free Software Foundation, Inc.\n51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA\n\nEveryone is permitted to copy and distribute verbatim copies\nof this license document, but changing it is not allowed.\n\n[This is the first released version of the Lesser GPL. It also counts\nas the successor of the GNU Library Public License, version 2, hence the\nversion number 2.1.]\n\n\nThe licenses for most software are designed to take away your freedom\nto share and change it. By contrast, the GNU General Public Licenses\nare intended to guarantee your freedom to share and change free\nsoftware--to make sure the software is free for all its users.\n\nThis license, the Lesser General Public License, applies to some\nspecially designated software--typically libraries--of the Free Software\nFoundation and other authors who decide to use it. You can use it too,\nbut we suggest you first think carefully about whether this license or\nthe ordinary General Public License is the better strategy to use in any\nparticular case, based on the explanations below.\n\nWhen we speak of free software, we are referring to freedom of use,\nnot price. Our General Public Licenses are designed to make sure that\nyou have the freedom to distribute copies of free software (and charge\nfor this service if you wish); that you receive source code or can get\nit if you want it; that you can change the software and use pieces of it\nin new free programs; and that you are informed that you can do these\nthings.\n\nTo protect your rights, we need to make restrictions that forbid\ndistributors to deny you these rights or to ask you to surrender these\nrights. These restrictions translate to certain responsibilities for\nyou if you distribute copies of the library or if you modify it.\n\nFor example, if you distribute copies of the library, whether gratis\nor for a fee, you must give the recipients all the rights that we gave\nyou. You must make sure that they, too, receive or can get the source\ncode. If you link other code with the library, you must provide\ncomplete object files to the recipients, so that they can relink them\nwith the library after making changes to the library and recompiling it.\nAnd you must show them these terms so they know their rights.\n\nWe protect your rights with a two-step method: (1) we copyright the\nlibrary, and (2) we offer you this license, which gives you legal\npermission to copy, distribute and/or modify the library.\n\nTo protect each distributor, we want to make it very clear that there\nis no warranty for the free library. Also, if the library is modified\nby someone else and passed on, the recipients should know that what they\nhave is not the original version, so that the original author's\nreputation will not be affected by problems that might be introduced by\nothers.\n\nFinally, software patents pose a constant threat to the existence of\nany free program. We wish to make sure that a company cannot\neffectively restrict the users of a free program by obtaining a\nrestrictive license from a patent holder. Therefore, we insist that any\npatent license obtained for a version of the library must be consistent\nwith the full freedom of use specified in this license.\n\nMost GNU software, including some libraries, is covered by the\nordinary GNU General Public License. This license, the GNU Lesser\nGeneral Public License, applies to certain designated libraries, and is\nquite different from the ordinary General Public License. We use this\nlicense for certain libraries in order to permit linking those libraries\ninto non-free programs.\n\nWhen a program is linked with a library, whether statically or using\na shared library, the combination of the two is legally speaking a\ncombined work, a derivative of the original library. The ordinary\nGeneral Public License therefore permits such linking only if the entire\ncombination fits its criteria of freedom. The Lesser General Public\nLicense permits more lax criteria for linking other code with the\nlibrary.\n\nWe call this license the \"Lesser\" General Public License because it\ndoes Less to protect the user's freedom than the ordinary General\nPublic License. It also provides other free software developers Less of\nan advantage over competing non-free programs. These disadvantages are\nthe reason we use the ordinary General Public License for many\nlibraries. However, the Lesser license provides advantages in certain\nspecial circumstances.\n\nFor example, on rare occasions, there may be a special need to\nencourage the widest possible use of a certain library, so that it\nbecomes a de-facto standard. To achieve this, non-free programs must be\nallowed to use the library. A more frequent case is that a free library\ndoes the same job as widely used non-free libraries. In this case,\nthere is little to gain by limiting the free library to free software\nonly, so we use the Lesser General Public License.\n\nIn other cases, permission to use a particular library in non-free\nprograms enables a greater number of people to use a large body of free\nsoftware. For example, permission to use the GNU C Library in non-free\nprograms enables many more people to use the whole GNU operating system,\nas well as its variant, the GNU/Linux operating system.\n\nAlthough the Lesser General Public License is Less protective of the\nusers' freedom, it does ensure that the user of a program that is linked\nwith the Library has the freedom and the wherewithal to run that program\nusing a modified version of the Library.\n\nThe precise terms and conditions for copying, distribution and\nmodification follow. Pay close attention to the difference between a\n\"work based on the library\" and a \"work that uses the library\". The\nformer contains code derived from the library, whereas the latter must\nbe combined with the library in order to run.\n\n\n0. This License Agreement applies to any software library or other\nprogram which contains a notice placed by the copyright holder or\nother authorized party saying it may be distributed under the terms\nof this Lesser General Public License (also called \"this License\").\nEach licensee is addressed as \"you\".\n\nA \"library\" means a collection of software functions and/or data\nprepared so as to be conveniently linked with application programs\n(which use some of those functions and data) to form executables.\n\nThe \"Library\", below, refers to any such software library or work\nwhich has been distributed under these terms. A \"work based on the\nLibrary\" means either the Library or any derivative work under\ncopyright law: that is to say, a work containing the Library or a\nportion of it, either verbatim or with modifications and/or\ntranslated straightforwardly into another language. (Hereinafter,\ntranslation is included without limitation in the term\n\"modification\".)\n\n\"Source code\" for a work means the preferred form of the work for\nmaking modifications to it. For a library, complete source code\nmeans all the source code for all modules it contains, plus any\nassociated interface definition files, plus the scripts used to\ncontrol compilation and installation of the library.\n\nActivities other than copying, distribution and modification are\nnot covered by this License; they are outside its scope. The act\nof running a program using the Library is not restricted, and\noutput from such a program is covered only if its contents\nconstitute a work based on the Library (independent of the use of\nthe Library in a tool for writing it). Whether that is true\ndepends on what the Library does and what the program that uses the\nLibrary does.\n\n1. You may copy and distribute verbatim copies of the Library's\ncomplete source code as you receive it, in any medium, provided\nthat you conspicuously and appropriately publish on each copy an\nappropriate copyright notice and disclaimer of warranty; keep\nintact all the notices that refer to this License and to the\nabsence of any warranty; and distribute a copy of this License\nalong with the Library.\n\nYou may charge a fee for the physical act of transferring a copy,\nand you may at your option offer warranty protection in exchange\nfor a fee.\n\n2. You may modify your copy or copies of the Library or any portion of\nit, thus forming a work based on the Library, and copy and\ndistribute such modifications or work under the terms of Section 1\nabove, provided that you also meet all of these conditions:\n\na. The modified work must itself be a software library.\n\nb. You must cause the files modified to carry prominent notices\nstating that you changed the files and the date of any change.\n\nc. You must cause the whole of the work to be licensed at no\ncharge to all third parties under the terms of this License.\n\nd. If a facility in the modified Library refers to a function or\na table of data to be supplied by an application program that\nuses the facility, other than as an argument passed when the\nfacility is invoked, then you must make a good faith effort to\nensure that, in the event an application does not supply such\nfunction or table, the facility still operates, and performs\nwhatever part of its purpose remains meaningful.\n\n(For example, a function in a library to compute square roots\nhas a purpose that is entirely well-defined independent of the\napplication. Therefore, Subsection 2d requires that any\napplication-supplied function or table used by this function\nmust be optional: if the application does not supply it, the\nsquare root function must still compute square roots.)\n\nThese requirements apply to the modified work as a whole. If\nidentifiable sections of that work are not derived from the\nLibrary, and can be reasonably considered independent and separate\nworks in themselves, then this License, and its terms, do not apply\nto those sections when you distribute them as separate works. But\nwhen you distribute the same sections as part of a whole which is a\nwork based on the Library, the distribution of the whole must be on\nthe terms of this License, whose permissions for other licensees\nextend to the entire whole, and thus to each and every part\nregardless of who wrote it.\n\nThus, it is not the intent of this section to claim rights or\ncontest your rights to work written entirely by you; rather, the\nintent is to exercise the right to control the distribution of\nderivative or collective works based on the Library.\n\nIn addition, mere aggregation of another work not based on the\nLibrary with the Library (or with a work based on the Library) on a\nvolume of a storage or distribution medium does not bring the other\nwork under the scope of this License.\n\n3. You may opt to apply the terms of the ordinary GNU General Public\nLicense instead of this License to a given copy of the Library. To\ndo this, you must alter all the notices that refer to this License,\nso that they refer to the ordinary GNU General Public License,\nversion 2, instead of to this License. (If a newer version than\nversion 2 of the ordinary GNU General Public License has appeared,\nthen you can specify that version instead if you wish.) Do not\nmake any other change in these notices.\n\nOnce this change is made in a given copy, it is irreversible for\nthat copy, so the ordinary GNU General Public License applies to\nall subsequent copies and derivative works made from that copy.\n\nThis option is useful when you wish to copy part of the code of the\nLibrary into a program that is not a library.\n\n4. You may copy and distribute the Library (or a portion or derivative\nof it, under Section 2) in object code or executable form under the\nterms of Sections 1 and 2 above provided that you accompany it with\nthe complete corresponding machine-readable source code, which must\nbe distributed under the terms of Sections 1 and 2 above on a\nmedium customarily used for software interchange.\n\nIf distribution of object code is made by offering access to copy\nfrom a designated place, then offering equivalent access to copy\nthe source code from the same place satisfies the requirement to\ndistribute the source code, even though third parties are not\ncompelled to copy the source along with the object code.\n\n5. A program that contains no derivative of any portion of the\nLibrary, but is designed to work with the Library by being compiled\nor linked with it, is called a \"work that uses the Library\". Such\na work, in isolation, is not a derivative work of the Library, and\ntherefore falls outside the scope of this License.\n\nHowever, linking a \"work that uses the Library\" with the Library\ncreates an executable that is a derivative of the Library (because\nit contains portions of the Library), rather than a \"work that uses\nthe library\". The executable is therefore covered by this License.\nSection 6 states terms for distribution of such executables.\n\nWhen a \"work that uses the Library\" uses material from a header\nfile that is part of the Library, the object code for the work may\nbe a derivative work of the Library even though the source code is\nnot. Whether this is true is especially significant if the work\ncan be linked without the Library, or if the work is itself a\nlibrary. The threshold for this to be true is not precisely\ndefined by law.\n\nIf such an object file uses only numerical parameters, data\nstructure layouts and accessors, and small macros and small inline\nfunctions (ten lines or less in length), then the use of the object\nfile is unrestricted, regardless of whether it is legally a\nderivative work. (Executables containing this object code plus\nportions of the Library will still fall under Section 6.)\n\nOtherwise, if the work is a derivative of the Library, you may\ndistribute the object code for the work under the terms of Section\n6. Any executables containing that work also fall under Section 6,\nwhether or not they are linked directly with the Library itself.\n\n6. As an exception to the Sections above, you may also combine or link\na \"work that uses the Library\" with the Library to produce a work\ncontaining portions of the Library, and distribute that work under\nterms of your choice, provided that the terms permit modification\nof the work for the customer's own use and reverse engineering for\ndebugging such modifications.\n\nYou must give prominent notice with each copy of the work that the\nLibrary is used in it and that the Library and its use are covered\nby this License. You must supply a copy of this License. If the\nwork during execution displays copyright notices, you must include\nthe copyright notice for the Library among them, as well as a\nreference directing the user to the copy of this License. Also,\nyou must do one of these things:\n\na. Accompany the work with the complete corresponding\nmachine-readable source code for the Library including\nwhatever changes were used in the work (which must be\ndistributed under Sections 1 and 2 above); and, if the work is\nan executable linked with the Library, with the complete\nmachine-readable \"work that uses the Library\", as object code\nand/or source code, so that the user can modify the Library\nand then relink to produce a modified executable containing\nthe modified Library. (It is understood that the user who\nchanges the contents of definitions files in the Library will\nnot necessarily be able to recompile the application to use\nthe modified definitions.)\n\nb. Use a suitable shared library mechanism for linking with the\nLibrary. A suitable mechanism is one that (1) uses at run\ntime a copy of the library already present on the user's\ncomputer system, rather than copying library functions into\nthe executable, and (2) will operate properly with a modified\nversion of the library, if the user installs one, as long as\nthe modified version is interface-compatible with the version\nthat the work was made with.\n\nc. Accompany the work with a written offer, valid for at least\nthree years, to give the same user the materials specified in\nSubsection 6a, above, for a charge no more than the cost of\nperforming this distribution.\n\nd. If distribution of the work is made by offering access to copy\nfrom a designated place, offer equivalent access to copy the\nabove specified materials from the same place.\n\ne. Verify that the user has already received a copy of these\nmaterials or that you have already sent this user a copy.\n\nFor an executable, the required form of the \"work that uses the\nLibrary\" must include any data and utility programs needed for\nreproducing the executable from it. However, as a special\nexception, the materials to be distributed need not include\nanything that is normally distributed (in either source or binary\nform) with the major components (compiler, kernel, and so on) of\nthe operating system on which the executable runs, unless that\ncomponent itself accompanies the executable.\n\nIt may happen that this requirement contradicts the license\nrestrictions of other proprietary libraries that do not normally\naccompany the operating system. Such a contradiction means you\ncannot use both them and the Library together in an executable that\nyou distribute.\n\n7. You may place library facilities that are a work based on the\nLibrary side-by-side in a single library together with other\nlibrary facilities not covered by this License, and distribute such\na combined library, provided that the separate distribution of the\nwork based on the Library and of the other library facilities is\notherwise permitted, and provided that you do these two things:\n\na. Accompany the combined library with a copy of the same work\nbased on the Library, uncombined with any other library\nfacilities. This must be distributed under the terms of the\nSections above.\n\nb. Give prominent notice with the combined library of the fact\nthat part of it is a work based on the Library, and explaining\nwhere to find the accompanying uncombined form of the same\nwork.\n\n8. You may not copy, modify, sublicense, link with, or distribute the\nLibrary except as expressly provided under this License. Any\nattempt otherwise to copy, modify, sublicense, link with, or\ndistribute the Library is void, and will automatically terminate\nyour rights under this License. However, parties who have received\ncopies, or rights, from you under this License will not have their\nlicenses terminated so long as such parties remain in full\ncompliance.\n\n9. You are not required to accept this License, since you have not\nsigned it. However, nothing else grants you permission to modify\nor distribute the Library or its derivative works. These actions\nare prohibited by law if you do not accept this License.\nTherefore, by modifying or distributing the Library (or any work\nbased on the Library), you indicate your acceptance of this License\nto do so, and all its terms and conditions for copying,\ndistributing or modifying the Library or works based on it.\n\n10. Each time you redistribute the Library (or any work based on the\nLibrary), the recipient automatically receives a license from the\noriginal licensor to copy, distribute, link with or modify the\nLibrary subject to these terms and conditions. You may not impose\nany further restrictions on the recipients' exercise of the rights\ngranted herein. You are not responsible for enforcing compliance\nby third parties with this License.\n\n11. If, as a consequence of a court judgment or allegation of patent\ninfringement or for any other reason (not limited to patent\nissues), conditions are imposed on you (whether by court order,\nagreement or otherwise) that contradict the conditions of this\nLicense, they do not excuse you from the conditions of this\nLicense. If you cannot distribute so as to satisfy simultaneously\nyour obligations under this License and any other pertinent\nobligations, then as a consequence you may not distribute the\nLibrary at all. For example, if a patent license would not permit\nroyalty-free redistribution of the Library by all those who receive\ncopies directly or indirectly through you, then the only way you\ncould satisfy both it and this License would be to refrain entirely\nfrom distribution of the Library.\n\nIf any portion of this section is held invalid or unenforceable\nunder any particular circumstance, the balance of the section is\nintended to apply, and the section as a whole is intended to apply\nin other circumstances.\n\nIt is not the purpose of this section to induce you to infringe any\npatents or other property right claims or to contest validity of\nany such claims; this section has the sole purpose of protecting\nthe integrity of the free software distribution system which is\nimplemented by public license practices. Many people have made\ngenerous contributions to the wide range of software distributed\nthrough that system in reliance on consistent application of that\nsystem; it is up to the author/donor to decide if he or she is\nwilling to distribute software through any other system and a\nlicensee cannot impose that choice.\n\nThis section is intended to make thoroughly clear what is believed\nto be a consequence of the rest of this License.\n\n12. If the distribution and/or use of the Library is restricted in\ncertain countries either by patents or by copyrighted interfaces,\nthe original copyright holder who places the Library under this\nLicense may add an explicit geographical distribution limitation\nexcluding those countries, so that distribution is permitted only\nin or among countries not thus excluded. In such case, this\nLicense incorporates the limitation as if written in the body of\nthis License.\n\n13. The Free Software Foundation may publish revised and/or new\nversions of the Lesser General Public License from time to time.\nSuch new versions will be similar in spirit to the present version,\nbut may differ in detail to address new problems or concerns.\n\nEach version is given a distinguishing version number. If the\nLibrary specifies a version number of this License which applies to\nit and \"any later version\", you have the option of following the\nterms and conditions either of that version or of any later version\npublished by the Free Software Foundation. If the Library does not\nspecify a license version number, you may choose any version ever\npublished by the Free Software Foundation.\n\n14. If you wish to incorporate parts of the Library into other free\nprograms whose distribution conditions are incompatible with these,\nwrite to the author to ask for permission. For software which is\ncopyrighted by the Free Software Foundation, write to the Free\nSoftware Foundation; we sometimes make exceptions for this. Our\ndecision will be guided by the two goals of preserving the free\nstatus of all derivatives of our free software and of promoting the\nsharing and reuse of software generally.\n\nNO WARRANTY\n\n15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO\nWARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE\nLAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS\nAND/OR OTHER PARTIES PROVIDE THE LIBRARY \"AS IS\" WITHOUT WARRANTY\nOF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT\nLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS\nFOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND\nPERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE\nDEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR\nOR CORRECTION.\n\n16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN\nWRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY\nMODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE\nLIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,\nINCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR\nINABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF\nDATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU\nOR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY\nOTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN\nADVISED OF THE POSSIBILITY OF SUCH DAMAGES.\n\n\n\nIf you develop a new library, and you want it to be of the greatest\npossible use to the public, we recommend making it free software that\neveryone can redistribute and change. You can do so by permitting\nredistribution under these terms (or, alternatively, under the terms of\nthe ordinary General Public License).\n\nTo apply these terms, attach the following notices to the library.\nIt is safest to attach them to the start of each source file to most\neffectively convey the exclusion of warranty; and each file should have\nat least the \"copyright\" line and a pointer to where the full notice is\nfound.\n\nONE LINE TO GIVE THE LIBRARY'S NAME AND AN IDEA OF WHAT IT DOES.\nCopyright (C) YEAR NAME OF AUTHOR\n\nThis library is free software; you can redistribute it and/or modify it\nunder the terms of the GNU Lesser General Public License as published by\nthe Free Software Foundation; either version 2.1 of the License, or (at\nyour option) any later version.\n\nThis library is distributed in the hope that it will be useful, but\nWITHOUT ANY WARRANTY; without even the implied warranty of\nMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU\nLesser General Public License for more details.\n\nYou should have received a copy of the GNU Lesser General Public\nLicense along with this library; if not, write to the Free Software\nFoundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,\nUSA.\n\nAlso add information on how to contact you by electronic and paper\nmail.\n\nYou should also get your employer (if you work as a programmer) or\nyour school, if any, to sign a \"copyright disclaimer\" for the library,\nif necessary. Here is a sample; alter the names:\n\nYoyodyne, Inc., hereby disclaims all copyright interest in the library\n`Frob' (a library for tweaking knobs) written by James Random Hacker.\n\nSIGNATURE OF TY COON, 1 April 1990\nTy Coon, President of Vice\n\nThat's all there is to it!\n\nFile: gettext.info, Node: GNU FDL, Prev: GNU LGPL, Up: Licenses\n" }, { "name": "C.3 GNU Free Documentation License", "content": "Version 1.2, November 2002\n\nCopyright (C) 2000,2001,2002 Free Software Foundation, Inc.\n51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA\n\nEveryone is permitted to copy and distribute verbatim copies\nof this license document, but changing it is not allowed.\n\n0. PREAMBLE\n\nThe purpose of this License is to make a manual, textbook, or other\nfunctional and useful document \"free\" in the sense of freedom: to\nassure everyone the effective freedom to copy and redistribute it,\nwith or without modifying it, either commercially or\nnoncommercially. Secondarily, this License preserves for the\nauthor and publisher a way to get credit for their work, while not\nbeing considered responsible for modifications made by others.\n\nThis License is a kind of \"copyleft\", which means that derivative\nworks of the document must themselves be free in the same sense.\nIt complements the GNU General Public License, which is a copyleft\nlicense designed for free software.\n\nWe have designed this License in order to use it for manuals for\nfree software, because free software needs free documentation: a\nfree program should come with manuals providing the same freedoms\nthat the software does. But this License is not limited to\nsoftware manuals; it can be used for any textual work, regardless\nof subject matter or whether it is published as a printed book. We\nrecommend this License principally for works whose purpose is\ninstruction or reference.\n\n1. APPLICABILITY AND DEFINITIONS\n\nThis License applies to any manual or other work, in any medium,\nthat contains a notice placed by the copyright holder saying it can\nbe distributed under the terms of this License. Such a notice\ngrants a world-wide, royalty-free license, unlimited in duration,\nto use that work under the conditions stated herein. The\n\"Document\", below, refers to any such manual or work. Any member\nof the public is a licensee, and is addressed as \"you\". You accept\nthe license if you copy, modify or distribute the work in a way\nrequiring permission under copyright law.\n\nA \"Modified Version\" of the Document means any work containing the\nDocument or a portion of it, either copied verbatim, or with\nmodifications and/or translated into another language.\n\nA \"Secondary Section\" is a named appendix or a front-matter section\nof the Document that deals exclusively with the relationship of the\npublishers or authors of the Document to the Document's overall\nsubject (or to related matters) and contains nothing that could\nfall directly within that overall subject. (Thus, if the Document\nis in part a textbook of mathematics, a Secondary Section may not\nexplain any mathematics.) The relationship could be a matter of\nhistorical connection with the subject or with related matters, or\nof legal, commercial, philosophical, ethical or political position\nregarding them.\n\nThe \"Invariant Sections\" are certain Secondary Sections whose\ntitles are designated, as being those of Invariant Sections, in the\nnotice that says that the Document is released under this License.\nIf a section does not fit the above definition of Secondary then it\nis not allowed to be designated as Invariant. The Document may\ncontain zero Invariant Sections. If the Document does not identify\nany Invariant Sections then there are none.\n\nThe \"Cover Texts\" are certain short passages of text that are\nlisted, as Front-Cover Texts or Back-Cover Texts, in the notice\nthat says that the Document is released under this License. A\nFront-Cover Text may be at most 5 words, and a Back-Cover Text may\nbe at most 25 words.\n\nA \"Transparent\" copy of the Document means a machine-readable copy,\nrepresented in a format whose specification is available to the\ngeneral public, that is suitable for revising the document\nstraightforwardly with generic text editors or (for images composed\nof pixels) generic paint programs or (for drawings) some widely\navailable drawing editor, and that is suitable for input to text\nformatters or for automatic translation to a variety of formats\nsuitable for input to text formatters. A copy made in an otherwise\nTransparent file format whose markup, or absence of markup, has\nbeen arranged to thwart or discourage subsequent modification by\nreaders is not Transparent. An image format is not Transparent if\nused for any substantial amount of text. A copy that is not\n\"Transparent\" is called \"Opaque\".\n\nExamples of suitable formats for Transparent copies include plain\nASCII without markup, Texinfo input format, LaTeX input format,\nSGML or XML using a publicly available DTD, and standard-conforming\nsimple HTML, PostScript or PDF designed for human modification.\nExamples of transparent image formats include PNG, XCF and JPG.\nOpaque formats include proprietary formats that can be read and\nedited only by proprietary word processors, SGML or XML for which\nthe DTD and/or processing tools are not generally available, and\nthe machine-generated HTML, PostScript or PDF produced by some word\nprocessors for output purposes only.\n\nThe \"Title Page\" means, for a printed book, the title page itself,\nplus such following pages as are needed to hold, legibly, the\nmaterial this License requires to appear in the title page. For\nworks in formats which do not have any title page as such, \"Title\nPage\" means the text near the most prominent appearance of the\nwork's title, preceding the beginning of the body of the text.\n\nA section \"Entitled XYZ\" means a named subunit of the Document\nwhose title either is precisely XYZ or contains XYZ in parentheses\nfollowing text that translates XYZ in another language. (Here XYZ\nstands for a specific section name mentioned below, such as\n\"Acknowledgements\", \"Dedications\", \"Endorsements\", or \"History\".)\nTo \"Preserve the Title\" of such a section when you modify the\nDocument means that it remains a section \"Entitled XYZ\" according\nto this definition.\n\nThe Document may include Warranty Disclaimers next to the notice\nwhich states that this License applies to the Document. These\nWarranty Disclaimers are considered to be included by reference in\nthis License, but only as regards disclaiming warranties: any other\nimplication that these Warranty Disclaimers may have is void and\nhas no effect on the meaning of this License.\n\n2. VERBATIM COPYING\n\nYou may copy and distribute the Document in any medium, either\ncommercially or noncommercially, provided that this License, the\ncopyright notices, and the license notice saying this License\napplies to the Document are reproduced in all copies, and that you\nadd no other conditions whatsoever to those of this License. You\nmay not use technical measures to obstruct or control the reading\nor further copying of the copies you make or distribute. However,\nyou may accept compensation in exchange for copies. If you\ndistribute a large enough number of copies you must also follow the\nconditions in section 3.\n\nYou may also lend copies, under the same conditions stated above,\nand you may publicly display copies.\n\n3. COPYING IN QUANTITY\n\nIf you publish printed copies (or copies in media that commonly\nhave printed covers) of the Document, numbering more than 100, and\nthe Document's license notice requires Cover Texts, you must\nenclose the copies in covers that carry, clearly and legibly, all\nthese Cover Texts: Front-Cover Texts on the front cover, and\nBack-Cover Texts on the back cover. Both covers must also clearly\nand legibly identify you as the publisher of these copies. The\nfront cover must present the full title with all words of the title\nequally prominent and visible. You may add other material on the\ncovers in addition. Copying with changes limited to the covers, as\nlong as they preserve the title of the Document and satisfy these\nconditions, can be treated as verbatim copying in other respects.\n\nIf the required texts for either cover are too voluminous to fit\nlegibly, you should put the first ones listed (as many as fit\nreasonably) on the actual cover, and continue the rest onto\nadjacent pages.\n\nIf you publish or distribute Opaque copies of the Document\nnumbering more than 100, you must either include a machine-readable\nTransparent copy along with each Opaque copy, or state in or with\neach Opaque copy a computer-network location from which the general\nnetwork-using public has access to download using public-standard\nnetwork protocols a complete Transparent copy of the Document, free\nof added material. If you use the latter option, you must take\nreasonably prudent steps, when you begin distribution of Opaque\ncopies in quantity, to ensure that this Transparent copy will\nremain thus accessible at the stated location until at least one\nyear after the last time you distribute an Opaque copy (directly or\nthrough your agents or retailers) of that edition to the public.\n\nIt is requested, but not required, that you contact the authors of\nthe Document well before redistributing any large number of copies,\nto give them a chance to provide you with an updated version of the\nDocument.\n\n4. MODIFICATIONS\n\nYou may copy and distribute a Modified Version of the Document\nunder the conditions of sections 2 and 3 above, provided that you\nrelease the Modified Version under precisely this License, with the\nModified Version filling the role of the Document, thus licensing\ndistribution and modification of the Modified Version to whoever\npossesses a copy of it. In addition, you must do these things in\nthe Modified Version:\n\nA. Use in the Title Page (and on the covers, if any) a title\ndistinct from that of the Document, and from those of previous\nversions (which should, if there were any, be listed in the\nHistory section of the Document). You may use the same title\nas a previous version if the original publisher of that\nversion gives permission.\n\nB. List on the Title Page, as authors, one or more persons or\nentities responsible for authorship of the modifications in\nthe Modified Version, together with at least five of the\nprincipal authors of the Document (all of its principal\nauthors, if it has fewer than five), unless they release you\nfrom this requirement.\n\nC. State on the Title page the name of the publisher of the\nModified Version, as the publisher.\n\nD. Preserve all the copyright notices of the Document.\n\nE. Add an appropriate copyright notice for your modifications\nadjacent to the other copyright notices.\n\nF. Include, immediately after the copyright notices, a license\nnotice giving the public permission to use the Modified\nVersion under the terms of this License, in the form shown in\nthe Addendum below.\n\nG. Preserve in that license notice the full lists of Invariant\nSections and required Cover Texts given in the Document's\nlicense notice.\n\nH. Include an unaltered copy of this License.\n\nI. Preserve the section Entitled \"History\", Preserve its Title,\nand add to it an item stating at least the title, year, new\nauthors, and publisher of the Modified Version as given on the\nTitle Page. If there is no section Entitled \"History\" in the\nDocument, create one stating the title, year, authors, and\npublisher of the Document as given on its Title Page, then add\nan item describing the Modified Version as stated in the\nprevious sentence.\n\nJ. Preserve the network location, if any, given in the Document\nfor public access to a Transparent copy of the Document, and\nlikewise the network locations given in the Document for\nprevious versions it was based on. These may be placed in the\n\"History\" section. You may omit a network location for a work\nthat was published at least four years before the Document\nitself, or if the original publisher of the version it refers\nto gives permission.\n\nK. For any section Entitled \"Acknowledgements\" or \"Dedications\",\nPreserve the Title of the section, and preserve in the section\nall the substance and tone of each of the contributor\nacknowledgements and/or dedications given therein.\n\nL. Preserve all the Invariant Sections of the Document, unaltered\nin their text and in their titles. Section numbers or the\nequivalent are not considered part of the section titles.\n\nM. Delete any section Entitled \"Endorsements\". Such a section\nmay not be included in the Modified Version.\n\nN. Do not retitle any existing section to be Entitled\n\"Endorsements\" or to conflict in title with any Invariant\nSection.\n\nO. Preserve any Warranty Disclaimers.\n\nIf the Modified Version includes new front-matter sections or\nappendices that qualify as Secondary Sections and contain no\nmaterial copied from the Document, you may at your option designate\nsome or all of these sections as invariant. To do this, add their\ntitles to the list of Invariant Sections in the Modified Version's\nlicense notice. These titles must be distinct from any other\nsection titles.\n\nYou may add a section Entitled \"Endorsements\", provided it contains\nnothing but endorsements of your Modified Version by various\nparties--for example, statements of peer review or that the text has\nbeen approved by an organization as the authoritative definition of\na standard.\n\nYou may add a passage of up to five words as a Front-Cover Text,\nand a passage of up to 25 words as a Back-Cover Text, to the end of\nthe list of Cover Texts in the Modified Version. Only one passage\nof Front-Cover Text and one of Back-Cover Text may be added by (or\nthrough arrangements made by) any one entity. If the Document\nalready includes a cover text for the same cover, previously added\nby you or by arrangement made by the same entity you are acting on\nbehalf of, you may not add another; but you may replace the old\none, on explicit permission from the previous publisher that added\nthe old one.\n\nThe author(s) and publisher(s) of the Document do not by this\nLicense give permission to use their names for publicity for or to\nassert or imply endorsement of any Modified Version.\n\n5. COMBINING DOCUMENTS\n\nYou may combine the Document with other documents released under\nthis License, under the terms defined in section 4 above for\nmodified versions, provided that you include in the combination all\nof the Invariant Sections of all of the original documents,\nunmodified, and list them all as Invariant Sections of your\ncombined work in its license notice, and that you preserve all\ntheir Warranty Disclaimers.\n\nThe combined work need only contain one copy of this License, and\nmultiple identical Invariant Sections may be replaced with a single\ncopy. If there are multiple Invariant Sections with the same name\nbut different contents, make the title of each such section unique\nby adding at the end of it, in parentheses, the name of the\noriginal author or publisher of that section if known, or else a\nunique number. Make the same adjustment to the section titles in\nthe list of Invariant Sections in the license notice of the\ncombined work.\n\nIn the combination, you must combine any sections Entitled\n\"History\" in the various original documents, forming one section\nEntitled \"History\"; likewise combine any sections Entitled\n\"Acknowledgements\", and any sections Entitled \"Dedications\". You\nmust delete all sections Entitled \"Endorsements.\"\n\n6. COLLECTIONS OF DOCUMENTS\n\nYou may make a collection consisting of the Document and other\ndocuments released under this License, and replace the individual\ncopies of this License in the various documents with a single copy\nthat is included in the collection, provided that you follow the\nrules of this License for verbatim copying of each of the documents\nin all other respects.\n\nYou may extract a single document from such a collection, and\ndistribute it individually under this License, provided you insert\na copy of this License into the extracted document, and follow this\nLicense in all other respects regarding verbatim copying of that\ndocument.\n\n7. AGGREGATION WITH INDEPENDENT WORKS\n\nA compilation of the Document or its derivatives with other\nseparate and independent documents or works, in or on a volume of a\nstorage or distribution medium, is called an \"aggregate\" if the\ncopyright resulting from the compilation is not used to limit the\nlegal rights of the compilation's users beyond what the individual\nworks permit. When the Document is included in an aggregate, this\nLicense does not apply to the other works in the aggregate which\nare not themselves derivative works of the Document.\n\nIf the Cover Text requirement of section 3 is applicable to these\ncopies of the Document, then if the Document is less than one half\nof the entire aggregate, the Document's Cover Texts may be placed\non covers that bracket the Document within the aggregate, or the\nelectronic equivalent of covers if the Document is in electronic\nform. Otherwise they must appear on printed covers that bracket\nthe whole aggregate.\n\n8. TRANSLATION\n\nTranslation is considered a kind of modification, so you may\ndistribute translations of the Document under the terms of section\n4. Replacing Invariant Sections with translations requires special\npermission from their copyright holders, but you may include\ntranslations of some or all Invariant Sections in addition to the\noriginal versions of these Invariant Sections. You may include a\ntranslation of this License, and all the license notices in the\nDocument, and any Warranty Disclaimers, provided that you also\ninclude the original English version of this License and the\noriginal versions of those notices and disclaimers. In case of a\ndisagreement between the translation and the original version of\nthis License or a notice or disclaimer, the original version will\nprevail.\n\nIf a section in the Document is Entitled \"Acknowledgements\",\n\"Dedications\", or \"History\", the requirement (section 4) to\nPreserve its Title (section 1) will typically require changing the\nactual title.\n\n9. TERMINATION\n\nYou may not copy, modify, sublicense, or distribute the Document\nexcept as expressly provided for under this License. Any other\nattempt to copy, modify, sublicense or distribute the Document is\nvoid, and will automatically terminate your rights under this\nLicense. However, parties who have received copies, or rights,\nfrom you under this License will not have their licenses terminated\nso long as such parties remain in full compliance.\n\n10. FUTURE REVISIONS OF THIS LICENSE\n\nThe Free Software Foundation may publish new, revised versions of\nthe GNU Free Documentation License from time to time. Such new\nversions will be similar in spirit to the present version, but may\ndiffer in detail to address new problems or concerns. See\n.\n\nEach version of the License is given a distinguishing version\nnumber. If the Document specifies that a particular numbered\nversion of this License \"or any later version\" applies to it, you\nhave the option of following the terms and conditions either of\nthat specified version or of any later version that has been\npublished (not as a draft) by the Free Software Foundation. If the\nDocument does not specify a version number of this License, you may\nchoose any version ever published (not as a draft) by the Free\nSoftware Foundation.\n" }, { "name": "ADDENDUM: How to use this License for your documents", "content": "To use this License in a document you have written, include a copy of\nthe License in the document and put the following copyright and license\nnotices just after the title page:\n\nCopyright (C) YEAR YOUR NAME.\nPermission is granted to copy, distribute and/or modify this document\nunder the terms of the GNU Free Documentation License, Version 1.2\nor any later version published by the Free Software Foundation;\nwith no Invariant Sections, no Front-Cover Texts, and no Back-Cover\nTexts. A copy of the license is included in the section entitled ``GNU\nFree Documentation License''.\n\nIf you have Invariant Sections, Front-Cover Texts and Back-Cover\nTexts, replace the \"with...Texts.\" line with this:\n\nwith the Invariant Sections being LIST THEIR TITLES, with\nthe Front-Cover Texts being LIST, and with the Back-Cover Texts\nbeing LIST.\n\nIf you have Invariant Sections without Cover Texts, or some other\ncombination of the three, merge those two alternatives to suit the\nsituation.\n\nIf your document contains nontrivial examples of program code, we\nrecommend releasing these examples in parallel under your choice of free\nsoftware license, such as the GNU General Public License, to permit\ntheir use in free software.\n\nFile: gettext.info, Node: Program Index, Next: Option Index, Prev: Licenses, Up: Top\n" } ] }, "Program Index": { "content": "* Menu:\n\n* autopoint: autopoint Invocation.\n(line 6)\n* boldquot: msgfilter Invocation.\n(line 111)\n* envsubst: envsubst Invocation. (line 6)\n* gettext: sh. (line 22)\n* gettext <1>: gettext Invocation. (line 6)\n* gettextize: gettextize Invocation.\n(line 34)\n* msgattrib: msgattrib Invocation.\n(line 6)\n* msgcat: msgcat Invocation. (line 6)\n* msgcmp: msgcmp Invocation. (line 6)\n* msgcomm: msgcomm Invocation. (line 6)\n* msgconv: msgconv Invocation. (line 6)\n* msgen: msgen Invocation. (line 6)\n* msgexec: msgexec Invocation. (line 6)\n* msgfilter: msgfilter Invocation.\n(line 6)\n* msgfmt: msgfmt Invocation. (line 6)\n* msggrep: msggrep Invocation. (line 6)\n* msginit: msginit Invocation. (line 6)\n* msgmerge: msgmerge Invocation. (line 6)\n* msgunfmt: msgunfmt Invocation. (line 6)\n* msguniq: msguniq Invocation. (line 6)\n* ngettext: sh. (line 22)\n* ngettext <1>: ngettext Invocation. (line 6)\n* quot: msgfilter Invocation.\n(line 107)\n* recode-sr-latin: msgfilter Invocation.\n(line 101)\n* xgettext: xgettext Invocation. (line 6)\n\nFile: gettext.info, Node: Option Index, Next: Variable Index, Prev: Program Index, Up: Top\n", "subsections": [] }, "Option Index": { "content": "* Menu:\n\n* --add-comments, xgettext option: xgettext Invocation. (line 94)\n* --add-location, msgattrib option: msgattrib Invocation.\n(line 138)\n* --add-location, msgcat option: msgcat Invocation. (line 118)\n* --add-location, msgcomm option: msgcomm Invocation. (line 100)\n* --add-location, msgconv option: msgconv Invocation. (line 80)\n* --add-location, msgen option: msgen Invocation. (line 83)\n* --add-location, msgfilter option: msgfilter Invocation.\n(line 161)\n* --add-location, msggrep option: msggrep Invocation. (line 152)\n* --add-location, msgmerge option: msgmerge Invocation. (line 157)\n* --add-location, msguniq option: msguniq Invocation. (line 97)\n* --add-location, xgettext option: xgettext Invocation. (line 371)\n* --alignment, msgfmt option: msgfmt Invocation. (line 288)\n* --backup, msgmerge option: msgmerge Invocation. (line 62)\n* --boost, xgettext option: xgettext Invocation. (line 329)\n* --c++, xgettext option: xgettext Invocation. (line 63)\n* --check, msgfmt option: msgfmt Invocation. (line 226)\n* --check, xgettext option: xgettext Invocation. (line 116)\n* --check-accelerators, msgfmt option: msgfmt Invocation. (line 267)\n* --check-compatibility, msgfmt option: msgfmt Invocation. (line 263)\n* --check-domain, msgfmt option: msgfmt Invocation. (line 258)\n* --check-format, msgfmt option: msgfmt Invocation. (line 230)\n* --check-header, msgfmt option: msgfmt Invocation. (line 253)\n* --clear-fuzzy, msgattrib option: msgattrib Invocation.\n(line 68)\n* --clear-obsolete, msgattrib option: msgattrib Invocation.\n(line 74)\n* --clear-previous, msgattrib option: msgattrib Invocation.\n(line 81)\n* --color, msgattrib option: msgattrib Invocation.\n(line 119)\n* --color, msgcat option: msgcat Invocation. (line 99)\n* --color, msgcat option <1>: The --color option. (line 6)\n* --color, msgcomm option: msgcomm Invocation. (line 81)\n* --color, msgconv option: msgconv Invocation. (line 61)\n* --color, msgen option: msgen Invocation. (line 64)\n* --color, msgfilter option: msgfilter Invocation.\n(line 138)\n* --color, msggrep option: msggrep Invocation. (line 134)\n* --color, msginit option: msginit Invocation. (line 96)\n* --color, msgmerge option: msgmerge Invocation. (line 138)\n* --color, msgunfmt option: msgunfmt Invocation. (line 103)\n* --color, msguniq option: msguniq Invocation. (line 78)\n* --color, xgettext option: xgettext Invocation. (line 350)\n* --comment, msggrep option: msggrep Invocation. (line 86)\n* --compendium, msgmerge option: msgmerge Invocation. (line 36)\n* --context, gettext option: gettext Invocation. (line 16)\n* --context, ngettext option: ngettext Invocation. (line 15)\n* --copyright-holder, xgettext option: xgettext Invocation. (line 435)\n* --csharp, msgfmt option: msgfmt Invocation. (line 36)\n* --csharp, msgunfmt option: msgunfmt Invocation. (line 19)\n* --csharp-resources, msgfmt option: msgfmt Invocation. (line 40)\n* --csharp-resources, msgunfmt option: msgunfmt Invocation. (line 23)\n* --debug, xgettext option: xgettext Invocation. (line 333)\n* --default-domain, xgettext option: xgettext Invocation. (line 35)\n* --desktop, msgfmt option: msgfmt Invocation. (line 49)\n* --directory, msgattrib option: msgattrib Invocation.\n(line 19)\n* --directory, msgcat option: msgcat Invocation. (line 35)\n* --directory, msgcmp option: msgcmp Invocation. (line 27)\n* --directory, msgcomm option: msgcomm Invocation. (line 30)\n* --directory, msgconv option: msgconv Invocation. (line 19)\n* --directory, msgen option: msgen Invocation. (line 25)\n* --directory, msgexec option: msgexec Invocation. (line 54)\n* --directory, msgfilter option: msgfilter Invocation.\n(line 34)\n* --directory, msgfmt option: msgfmt Invocation. (line 18)\n* --directory, msggrep option: msggrep Invocation. (line 19)\n* --directory, msgmerge option: msgmerge Invocation. (line 30)\n* --directory, msguniq option: msguniq Invocation. (line 26)\n* --directory, xgettext option: xgettext Invocation. (line 24)\n* --domain, gettext option: gettext Invocation. (line 21)\n* --domain, msggrep option: msggrep Invocation. (line 70)\n* --domain, ngettext option: ngettext Invocation. (line 20)\n* --dry-run, autopoint option: autopoint Invocation.\n(line 31)\n* --dry-run, gettextize option: gettextize Invocation.\n(line 64)\n* --empty, msgattrib option: msgattrib Invocation.\n(line 84)\n* --endianness, msgfmt option: msgfmt Invocation. (line 291)\n* --exclude-file, xgettext option: xgettext Invocation. (line 89)\n* --expression, msgfilter option: msgfilter Invocation.\n(line 87)\n* --extended-regexp, msggrep option: msggrep Invocation. (line 94)\n* --extract-all, xgettext option: xgettext Invocation. (line 165)\n* --extracted-comment, msggrep option: msggrep Invocation. (line 90)\n* --file, msgfilter option: msgfilter Invocation.\n(line 91)\n* --file, msggrep option: msggrep Invocation. (line 106)\n* --files-from, msgcat option: msgcat Invocation. (line 30)\n* --files-from, msgcomm option: msgcomm Invocation. (line 25)\n* --files-from, xgettext option: xgettext Invocation. (line 19)\n* --fixed-strings, msggrep option: msggrep Invocation. (line 98)\n* --flag, xgettext option: xgettext Invocation. (line 276)\n* --for-msgfmt, msgmerge option: msgmerge Invocation. (line 99)\n* --force, autopoint option: autopoint Invocation.\n(line 27)\n* --force, gettextize option: gettextize Invocation.\n(line 40)\n* --force-po, msgattrib option: msgattrib Invocation.\n(line 127)\n* --force-po, msgcat option: msgcat Invocation. (line 107)\n* --force-po, msgcomm option: msgcomm Invocation. (line 89)\n* --force-po, msgconv option: msgconv Invocation. (line 69)\n* --force-po, msgen option: msgen Invocation. (line 72)\n* --force-po, msgfilter option: msgfilter Invocation.\n(line 146)\n* --force-po, msggrep option: msggrep Invocation. (line 142)\n* --force-po, msgmerge option: msgmerge Invocation. (line 146)\n* --force-po, msgunfmt option: msgunfmt Invocation. (line 111)\n* --force-po, msguniq option: msguniq Invocation. (line 86)\n* --force-po, xgettext option: xgettext Invocation. (line 358)\n* --foreign-user, xgettext option: xgettext Invocation. (line 450)\n* --from-code, xgettext option: xgettext Invocation. (line 72)\n* --fuzzy, msgattrib option: msgattrib Invocation.\n(line 95)\n* --help, autopoint option: autopoint Invocation.\n(line 39)\n* --help, envsubst option: envsubst Invocation. (line 21)\n* --help, gettext option: gettext Invocation. (line 37)\n* --help, gettextize option: gettextize Invocation.\n(line 69)\n* --help, msgattrib option: msgattrib Invocation.\n(line 188)\n* --help, msgcat option: msgcat Invocation. (line 168)\n* --help, msgcmp option: msgcmp Invocation. (line 69)\n* --help, msgcomm option: msgcomm Invocation. (line 153)\n* --help, msgconv option: msgconv Invocation. (line 130)\n* --help, msgen option: msgen Invocation. (line 133)\n* --help, msgexec option: msgexec Invocation. (line 77)\n* --help, msgfilter option: msgfilter Invocation.\n(line 211)\n* --help, msgfmt option: msgfmt Invocation. (line 311)\n* --help, msggrep option: msggrep Invocation. (line 200)\n* --help, msginit option: msginit Invocation. (line 131)\n* --help, msgmerge option: msgmerge Invocation. (line 207)\n* --help, msgunfmt option: msgunfmt Invocation. (line 155)\n* --help, msguniq option: msguniq Invocation. (line 147)\n* --help, ngettext option: ngettext Invocation. (line 36)\n* --help, xgettext option: xgettext Invocation. (line 497)\n* --ignore-case, msggrep option: msggrep Invocation. (line 110)\n* --ignore-file, msgattrib option: msgattrib Invocation.\n(line 91)\n* --indent, msgattrib option: msgattrib Invocation.\n(line 131)\n* --indent, msgcat option: msgcat Invocation. (line 111)\n* --indent, msgcomm option: msgcomm Invocation. (line 93)\n* --indent, msgconv option: msgconv Invocation. (line 73)\n* --indent, msgen option: msgen Invocation. (line 76)\n* --indent, msgfilter option: msgfilter Invocation.\n(line 149)\n* --indent, msggrep option: msggrep Invocation. (line 145)\n* --indent, msgmerge option: msgmerge Invocation. (line 150)\n* --indent, msgunfmt option: msgunfmt Invocation. (line 115)\n* --indent, msguniq option: msguniq Invocation. (line 90)\n* --indent, xgettext option: xgettext Invocation. (line 362)\n* --input, msgexec option: msgexec Invocation. (line 50)\n* --input, msgfilter option: msgfilter Invocation.\n(line 30)\n* --input, msginit option: msginit Invocation. (line 51)\n* --invert-match, msggrep option: msggrep Invocation. (line 114)\n* --its, xgettext option: xgettext Invocation. (line 394)\n* --itstool, xgettext option: xgettext Invocation. (line 398)\n* --java, msgfmt option: msgfmt Invocation. (line 30)\n* --java, msgunfmt option: msgunfmt Invocation. (line 16)\n* --java2, msgfmt option: msgfmt Invocation. (line 33)\n* --join-existing, xgettext option: xgettext Invocation. (line 85)\n* --kde, xgettext option: xgettext Invocation. (line 325)\n* --keep-header, msgfilter option: msgfilter Invocation.\n(line 152)\n* --keyword, msgfmt option: msgfmt Invocation. (line 140)\n* --keyword, xgettext option: xgettext Invocation. (line 174)\n* --lang, msgcat option: msgcat Invocation. (line 93)\n* --lang, msgen option: msgen Invocation. (line 57)\n* --lang, msgmerge option: msgmerge Invocation. (line 130)\n* --language, msgfmt option: msgfmt Invocation. (line 180)\n* --language, xgettext option: xgettext Invocation. (line 54)\n* --less-than, msgcat option: msgcat Invocation. (line 56)\n* --less-than, msgcomm option: msgcomm Invocation. (line 51)\n* --locale, msgfmt option: msgfmt Invocation. (line 83)\n* --locale, msgfmt option <1>: msgfmt Invocation. (line 106)\n* --locale, msgfmt option <2>: msgfmt Invocation. (line 122)\n* --locale, msgfmt option <3>: msgfmt Invocation. (line 146)\n* --locale, msgfmt option <4>: msgfmt Invocation. (line 184)\n* --locale, msginit option: msginit Invocation. (line 84)\n* --locale, msgunfmt option: msgunfmt Invocation. (line 45)\n* --locale, msgunfmt option <1>: msgunfmt Invocation. (line 62)\n* --locale, msgunfmt option <2>: msgunfmt Invocation. (line 78)\n* --location, msggrep option: msggrep Invocation. (line 65)\n* --more-than, msgcat option: msgcat Invocation. (line 61)\n* --more-than, msgcomm option: msgcomm Invocation. (line 56)\n* --msgctxt, msggrep option: msggrep Invocation. (line 74)\n* --msgid, msggrep option: msggrep Invocation. (line 78)\n* --msgid-bugs-address, xgettext option: xgettext Invocation. (line 463)\n* --msgstr, msggrep option: msggrep Invocation. (line 82)\n* --msgstr-prefix, xgettext option: xgettext Invocation. (line 486)\n* --msgstr-suffix, xgettext option: xgettext Invocation. (line 490)\n* --multi-domain, msgcmp option: msgcmp Invocation. (line 35)\n* --multi-domain, msgmerge option: msgmerge Invocation. (line 96)\n* --newline, msgfilter option: msgfilter Invocation.\n(line 59)\n* --newline, msgfilter option <1>: msgexec Invocation. (line 19)\n* --no-changelog, gettextize option: gettextize Invocation.\n(line 50)\n* --no-fuzzy, msgattrib option: msgattrib Invocation.\n(line 45)\n* --no-fuzzy-matching, msgcmp option: msgcmp Invocation. (line 39)\n* --no-fuzzy-matching, msgmerge option: msgmerge Invocation. (line 107)\n* --no-hash, msgfmt option: msgfmt Invocation. (line 303)\n* --no-location, msgattrib option: msgattrib Invocation.\n(line 134)\n* --no-location, msgcat option: msgcat Invocation. (line 114)\n* --no-location, msgcomm option: msgcomm Invocation. (line 96)\n* --no-location, msgconv option: msgconv Invocation. (line 76)\n* --no-location, msgen option: msgen Invocation. (line 79)\n* --no-location, msgfilter option: msgfilter Invocation.\n(line 157)\n* --no-location, msggrep option: msggrep Invocation. (line 148)\n* --no-location, msgmerge option: msgmerge Invocation. (line 153)\n* --no-location, msguniq option: msguniq Invocation. (line 93)\n* --no-location, xgettext option: xgettext Invocation. (line 365)\n* --no-obsolete, msgattrib option: msgattrib Invocation.\n(line 51)\n* --no-translator, msginit option: msginit Invocation. (line 91)\n* --no-wrap, msgattrib option: msgattrib Invocation.\n(line 169)\n* --no-wrap, msgcat option: msgcat Invocation. (line 149)\n* --no-wrap, msgcomm option: msgcomm Invocation. (line 131)\n* --no-wrap, msgconv option: msgconv Invocation. (line 111)\n* --no-wrap, msgen option: msgen Invocation. (line 114)\n* --no-wrap, msgfilter option: msgfilter Invocation.\n(line 192)\n* --no-wrap, msggrep option: msggrep Invocation. (line 183)\n* --no-wrap, msginit option: msginit Invocation. (line 121)\n* --no-wrap, msgmerge option: msgmerge Invocation. (line 188)\n* --no-wrap, msgunfmt option: msgunfmt Invocation. (line 140)\n* --no-wrap, msguniq option: msguniq Invocation. (line 128)\n* --no-wrap, xgettext option: xgettext Invocation. (line 409)\n* --obsolete, msgattrib option: msgattrib Invocation.\n(line 99)\n* --omit-header, msgcomm option: msgcomm Invocation. (line 146)\n* --omit-header, xgettext option: xgettext Invocation. (line 424)\n* --only-file, msgattrib option: msgattrib Invocation.\n(line 87)\n* --only-fuzzy, msgattrib option: msgattrib Invocation.\n(line 48)\n* --only-obsolete, msgattrib option: msgattrib Invocation.\n(line 54)\n* --output, xgettext option: xgettext Invocation. (line 39)\n* --output-dir, xgettext option: xgettext Invocation. (line 44)\n* --output-file, msgattrib option: msgattrib Invocation.\n(line 30)\n* --output-file, msgcat option: msgcat Invocation. (line 46)\n* --output-file, msgcomm option: msgcomm Invocation. (line 41)\n* --output-file, msgconv option: msgconv Invocation. (line 30)\n* --output-file, msgen option: msgen Invocation. (line 36)\n* --output-file, msgfilter option: msgfilter Invocation.\n(line 45)\n* --output-file, msgfmt option: msgfmt Invocation. (line 59)\n* --output-file, msggrep option: msggrep Invocation. (line 30)\n* --output-file, msginit option: msginit Invocation. (line 61)\n* --output-file, msgmerge option: msgmerge Invocation. (line 51)\n* --output-file, msgunfmt option: msgunfmt Invocation. (line 93)\n* --output-file, msguniq option: msguniq Invocation. (line 37)\n* --package-name, xgettext option: xgettext Invocation. (line 456)\n* --package-version, xgettext option: xgettext Invocation. (line 459)\n* --po-dir, gettextize option: gettextize Invocation.\n(line 43)\n* --previous, msgattrib option: msgattrib Invocation.\n(line 77)\n* --previous, msgmerge option: msgmerge Invocation. (line 111)\n* --properties-input, msgattrib option: msgattrib Invocation.\n(line 107)\n* --properties-input, msgcat option: msgcat Invocation. (line 74)\n* --properties-input, msgcmp option: msgcmp Invocation. (line 57)\n* --properties-input, msgcomm option: msgcomm Invocation. (line 69)\n* --properties-input, msgconv option: msgconv Invocation. (line 49)\n* --properties-input, msgen option: msgen Invocation. (line 46)\n* --properties-input, msgexec option: msgexec Invocation. (line 65)\n* --properties-input, msgfilter option: msgfilter Invocation.\n(line 126)\n* --properties-input, msgfmt option: msgfmt Invocation. (line 214)\n* --properties-input, msggrep option: msggrep Invocation. (line 122)\n* --properties-input, msginit option: msginit Invocation. (line 72)\n* --properties-input, msgmerge option: msgmerge Invocation. (line 119)\n* --properties-input, msguniq option: msguniq Invocation. (line 58)\n* --properties-output, msgattrib option: msgattrib Invocation.\n(line 153)\n* --properties-output, msgcat option: msgcat Invocation. (line 133)\n* --properties-output, msgcomm option: msgcomm Invocation. (line 115)\n* --properties-output, msgconv option: msgconv Invocation. (line 95)\n* --properties-output, msgen option: msgen Invocation. (line 98)\n* --properties-output, msgfilter option: msgfilter Invocation.\n(line 176)\n* --properties-output, msggrep option: msggrep Invocation. (line 167)\n* --properties-output, msginit option: msginit Invocation. (line 105)\n* --properties-output, msgmerge option: msgmerge Invocation. (line 172)\n* --properties-output, msgunfmt option: msgunfmt Invocation. (line 124)\n* --properties-output, msguniq option: msguniq Invocation. (line 112)\n* --properties-output, xgettext option: xgettext Invocation. (line 385)\n* --qt, msgfmt option: msgfmt Invocation. (line 46)\n* --qt, xgettext option: xgettext Invocation. (line 321)\n* --quiet, msgfilter option: msgfilter Invocation.\n(line 96)\n* --quiet, msgmerge option: msgmerge Invocation. (line 220)\n* --regexp=, msggrep option: msggrep Invocation. (line 102)\n* --repeated, msguniq option: msguniq Invocation. (line 47)\n* --resource, msgfmt option: msgfmt Invocation. (line 79)\n* --resource, msgfmt option <1>: msgfmt Invocation. (line 102)\n* --resource, msgunfmt option: msgunfmt Invocation. (line 41)\n* --resource, msgunfmt option <1>: msgunfmt Invocation. (line 58)\n* --sentence-end, xgettext option: xgettext Invocation. (line 152)\n* --set-fuzzy, msgattrib option: msgattrib Invocation.\n(line 65)\n* --set-obsolete, msgattrib option: msgattrib Invocation.\n(line 71)\n* --silent, msgfilter option: msgfilter Invocation.\n(line 96)\n* --silent, msgmerge option: msgmerge Invocation. (line 220)\n* --sort-by-file, msgattrib option: msgattrib Invocation.\n(line 181)\n* --sort-by-file, msgcat option: msgcat Invocation. (line 161)\n* --sort-by-file, msgcomm option: msgcomm Invocation. (line 143)\n* --sort-by-file, msgconv option: msgconv Invocation. (line 123)\n* --sort-by-file, msgen option: msgen Invocation. (line 126)\n* --sort-by-file, msgfilter option: msgfilter Invocation.\n(line 204)\n* --sort-by-file, msggrep option: msggrep Invocation. (line 193)\n* --sort-by-file, msgmerge option: msgmerge Invocation. (line 200)\n* --sort-by-file, msguniq option: msguniq Invocation. (line 140)\n* --sort-by-file, xgettext option: xgettext Invocation. (line 421)\n* --sort-output, msgattrib option: msgattrib Invocation.\n(line 176)\n* --sort-output, msgcat option: msgcat Invocation. (line 156)\n* --sort-output, msgcomm option: msgcomm Invocation. (line 138)\n* --sort-output, msgconv option: msgconv Invocation. (line 118)\n* --sort-output, msgen option: msgen Invocation. (line 121)\n* --sort-output, msgfilter option: msgfilter Invocation.\n(line 199)\n* --sort-output, msggrep option: msggrep Invocation. (line 189)\n* --sort-output, msgmerge option: msgmerge Invocation. (line 195)\n* --sort-output, msgunfmt option: msgunfmt Invocation. (line 147)\n* --sort-output, msguniq option: msguniq Invocation. (line 135)\n* --sort-output, xgettext option: xgettext Invocation. (line 416)\n* --source, msgfmt option: msgfmt Invocation. (line 91)\n* --statistics, msgfmt option: msgfmt Invocation. (line 318)\n* --strict, msgattrib option: msgattrib Invocation.\n(line 147)\n* --strict, msgcat option: msgcat Invocation. (line 127)\n* --strict, msgcomm option: msgcomm Invocation. (line 109)\n* --strict, msgconv option: msgconv Invocation. (line 89)\n* --strict, msgen option: msgen Invocation. (line 92)\n* --strict, msgfilter option: msgfilter Invocation.\n(line 170)\n* --strict, msgfmt option: msgfmt Invocation. (line 62)\n* --strict, msggrep option: msggrep Invocation. (line 161)\n* --strict, msgmerge option: msgmerge Invocation. (line 166)\n* --strict, msgunfmt option: msgunfmt Invocation. (line 118)\n* --strict, msguniq option: msguniq Invocation. (line 106)\n* --strict, xgettext option: xgettext Invocation. (line 380)\n* --stringtable-input, msgattrib option: msgattrib Invocation.\n(line 111)\n* --stringtable-input, msgcat option: msgcat Invocation. (line 78)\n* --stringtable-input, msgcmp option: msgcmp Invocation. (line 61)\n* --stringtable-input, msgcomm option: msgcomm Invocation. (line 73)\n* --stringtable-input, msgen option: msgen Invocation. (line 50)\n* --stringtable-input, msgexec option: msgexec Invocation. (line 69)\n* --stringtable-input, msgfilter option: msgfilter Invocation.\n(line 130)\n* --stringtable-input, msgfmt option: msgfmt Invocation. (line 218)\n* --stringtable-input, msggrep option: msggrep Invocation. (line 126)\n* --stringtable-input, msginit option: msginit Invocation. (line 76)\n* --stringtable-input, msgmerge option: msgmerge Invocation. (line 123)\n* --stringtable-input, msgonv option: msgconv Invocation. (line 53)\n* --stringtable-input, msguniq option: msguniq Invocation. (line 62)\n* --stringtable-output, msgattrib option: msgattrib Invocation.\n(line 158)\n* --stringtable-output, msgcat option: msgcat Invocation. (line 138)\n* --stringtable-output, msgcomm option: msgcomm Invocation. (line 120)\n* --stringtable-output, msgconv option: msgconv Invocation. (line 100)\n* --stringtable-output, msgen option: msgen Invocation. (line 103)\n* --stringtable-output, msgfilter option: msgfilter Invocation.\n(line 181)\n* --stringtable-output, msggrep option: msggrep Invocation. (line 172)\n* --stringtable-output, msginit option: msginit Invocation. (line 110)\n* --stringtable-output, msgmerge option: msgmerge Invocation. (line 177)\n* --stringtable-output, msgunfmt option: msgunfmt Invocation. (line 129)\n* --stringtable-output, msguniq option: msguniq Invocation. (line 117)\n* --stringtable-output, xgettext option: xgettext Invocation. (line 390)\n* --style, msgattrib option: msgattrib Invocation.\n(line 123)\n* --style, msgcat option: msgcat Invocation. (line 103)\n* --style, msgcat option <1>: The --style option. (line 6)\n* --style, msgcomm option: msgcomm Invocation. (line 85)\n* --style, msgconv option: msgconv Invocation. (line 65)\n* --style, msgen option: msgen Invocation. (line 68)\n* --style, msgfilter option: msgfilter Invocation.\n(line 142)\n* --style, msggrep option: msggrep Invocation. (line 138)\n* --style, msginit option: msginit Invocation. (line 100)\n* --style, msgmerge option: msgmerge Invocation. (line 142)\n* --style, msgunfmt option: msgunfmt Invocation. (line 107)\n* --style, msguniq option: msguniq Invocation. (line 82)\n* --style, xgettext option: xgettext Invocation. (line 354)\n* --suffix, msgmerge option: msgmerge Invocation. (line 65)\n* --symlink, gettextize option: gettextize Invocation.\n(line 55)\n* --tcl, msgfmt option: msgfmt Invocation. (line 43)\n* --tcl, msgunfmt option: msgunfmt Invocation. (line 26)\n* --template, msgfmt option: msgfmt Invocation. (line 136)\n* --template, msgfmt option <1>: msgfmt Invocation. (line 176)\n* --to-code, msgcat option: msgcat Invocation. (line 86)\n* --to-code, msgconv option: msgconv Invocation. (line 40)\n* --to-code, msguniq option: msguniq Invocation. (line 70)\n* --translated, msgattrib option: msgattrib Invocation.\n(line 39)\n* --trigraphs, xgettext option: xgettext Invocation. (line 316)\n* --unique, msgcat option: msgcat Invocation. (line 66)\n* --unique, msgcomm option: msgcomm Invocation. (line 61)\n* --unique, msguniq option: msguniq Invocation. (line 51)\n* --untranslated, msgattrib option: msgattrib Invocation.\n(line 42)\n* --update, msgmerge option: msgmerge Invocation. (line 44)\n* --use-first, msgcat option: msgcat Invocation. (line 89)\n* --use-first, msguniq option: msguniq Invocation. (line 73)\n* --use-fuzzy, msgcmp option: msgcmp Invocation. (line 43)\n* --use-fuzzy, msgfmt option: msgfmt Invocation. (line 279)\n* --use-untranslated, msgcmp option: msgcmp Invocation. (line 49)\n* --variables, envsubst option: envsubst Invocation. (line 15)\n* --verbose, msgfmt option: msgfmt Invocation. (line 324)\n* --verbose, msgmerge option: msgmerge Invocation. (line 215)\n* --verbose, msgunfmt option: msgunfmt Invocation. (line 163)\n* --verbose, xgettext option: xgettext Invocation. (line 505)\n* --version, autopoint option: autopoint Invocation.\n(line 42)\n* --version, envsubst option: envsubst Invocation. (line 25)\n* --version, gettext option: gettext Invocation. (line 45)\n* --version, gettextize option: gettextize Invocation.\n(line 72)\n* --version, msgattrib option: msgattrib Invocation.\n(line 192)\n* --version, msgcat option: msgcat Invocation. (line 172)\n* --version, msgcmp option: msgcmp Invocation. (line 73)\n* --version, msgcomm option: msgcomm Invocation. (line 157)\n* --version, msgconv option: msgconv Invocation. (line 134)\n* --version, msgen option: msgen Invocation. (line 137)\n* --version, msgexec option: msgexec Invocation. (line 81)\n* --version, msgfilter option: msgfilter Invocation.\n(line 215)\n* --version, msgfmt option: msgfmt Invocation. (line 315)\n* --version, msggrep option: msggrep Invocation. (line 204)\n* --version, msginit option: msginit Invocation. (line 135)\n* --version, msgmerge option: msgmerge Invocation. (line 211)\n* --version, msgunfmt option: msgunfmt Invocation. (line 159)\n* --version, msguniq option: msguniq Invocation. (line 151)\n* --version, ngettext option: ngettext Invocation. (line 40)\n* --version, xgettext option: xgettext Invocation. (line 501)\n* --width, msgattrib option: msgattrib Invocation.\n(line 163)\n* --width, msgcat option: msgcat Invocation. (line 143)\n* --width, msgcomm option: msgcomm Invocation. (line 125)\n* --width, msgconv option: msgconv Invocation. (line 105)\n* --width, msgen option: msgen Invocation. (line 108)\n* --width, msgfilter option: msgfilter Invocation.\n(line 186)\n* --width, msggrep option: msggrep Invocation. (line 177)\n* --width, msginit option: msginit Invocation. (line 115)\n* --width, msgmerge option: msgmerge Invocation. (line 182)\n* --width, msgunfmt option: msgunfmt Invocation. (line 134)\n* --width, msguniq option: msguniq Invocation. (line 122)\n* --width, xgettext option: xgettext Invocation. (line 403)\n* --xml, msgfmt option: msgfmt Invocation. (line 52)\n* -<, msgcat option: msgcat Invocation. (line 56)\n* -<, msgcomm option: msgcomm Invocation. (line 51)\n* ->, msgcat option: msgcat Invocation. (line 61)\n* ->, msgcomm option: msgcomm Invocation. (line 56)\n* -a, msgfmt option: msgfmt Invocation. (line 288)\n* -a, xgettext option: xgettext Invocation. (line 165)\n* -c, gettext option: gettext Invocation. (line 16)\n* -c, msgfmt option: msgfmt Invocation. (line 226)\n* -C, msgfmt option: msgfmt Invocation. (line 263)\n* -C, msggrep option: msggrep Invocation. (line 86)\n* -C, msgmerge option: msgmerge Invocation. (line 36)\n* -c, ngettext option: ngettext Invocation. (line 15)\n* -C, xgettext option: xgettext Invocation. (line 63)\n* -c, xgettext option: xgettext Invocation. (line 94)\n* -d, autopoint option: autopoint Invocation.\n(line 31)\n* -d, gettext option: gettext Invocation. (line 21)\n* -d, gettextize option: gettextize Invocation.\n(line 64)\n* -D, msgattrib option: msgattrib Invocation.\n(line 19)\n* -D, msgcat option: msgcat Invocation. (line 35)\n* -D, msgcmp option: msgcmp Invocation. (line 27)\n* -D, msgcomm option: msgcomm Invocation. (line 30)\n* -D, msgconv option: msgconv Invocation. (line 19)\n* -D, msgen option: msgen Invocation. (line 25)\n* -D, msgexec option: msgexec Invocation. (line 54)\n* -D, msgfilter option: msgfilter Invocation.\n(line 34)\n* -D, msgfmt option: msgfmt Invocation. (line 18)\n* -d, msgfmt option: msgfmt Invocation. (line 88)\n* -d, msgfmt option <1>: msgfmt Invocation. (line 111)\n* -d, msgfmt option <2>: msgfmt Invocation. (line 127)\n* -d, msgfmt option <3>: msgfmt Invocation. (line 151)\n* -d, msgfmt option <4>: msgfmt Invocation. (line 189)\n* -D, msggrep option: msggrep Invocation. (line 19)\n* -D, msgmerge option: msgmerge Invocation. (line 30)\n* -d, msgunfmt option: msgunfmt Invocation. (line 67)\n* -d, msgunfmt option <1>: msgunfmt Invocation. (line 83)\n* -D, msguniq option: msguniq Invocation. (line 26)\n* -d, msguniq option: msguniq Invocation. (line 47)\n* -d, ngettext option: ngettext Invocation. (line 20)\n* -D, xgettext option: xgettext Invocation. (line 24)\n* -d, xgettext option: xgettext Invocation. (line 35)\n* -e, gettext option: gettext Invocation. (line 25)\n* -E, gettext option: gettext Invocation. (line 32)\n* -e, msgfilter option: msgfilter Invocation.\n(line 87)\n* -E, msggrep option: msggrep Invocation. (line 94)\n* -e, msggrep option: msggrep Invocation. (line 102)\n* -e, ngettext option: ngettext Invocation. (line 24)\n* -E, ngettext option: ngettext Invocation. (line 31)\n* -f, autopoint option: autopoint Invocation.\n(line 27)\n* -f, gettextize option: gettextize Invocation.\n(line 40)\n* -F, msgattrib option: msgattrib Invocation.\n(line 181)\n* -f, msgcat option: msgcat Invocation. (line 30)\n* -F, msgcat option: msgcat Invocation. (line 161)\n* -f, msgcomm option: msgcomm Invocation. (line 25)\n* -F, msgcomm option: msgcomm Invocation. (line 143)\n* -F, msgconv option: msgconv Invocation. (line 123)\n* -F, msgen option: msgen Invocation. (line 126)\n* -f, msgfilter option: msgfilter Invocation.\n(line 91)\n* -F, msgfilter option: msgfilter Invocation.\n(line 204)\n* -f, msgfmt option: msgfmt Invocation. (line 279)\n* -F, msggrep option: msggrep Invocation. (line 98)\n* -f, msggrep option: msggrep Invocation. (line 106)\n* -F, msgmerge option: msgmerge Invocation. (line 200)\n* -F, msguniq option: msguniq Invocation. (line 140)\n* -f, xgettext option: xgettext Invocation. (line 19)\n* -F, xgettext option: xgettext Invocation. (line 421)\n* -h, envsubst option: envsubst Invocation. (line 21)\n* -h, gettext option: gettext Invocation. (line 37)\n* -h, msgattrib option: msgattrib Invocation.\n(line 188)\n* -h, msgcat option: msgcat Invocation. (line 168)\n* -h, msgcmp option: msgcmp Invocation. (line 69)\n* -h, msgcomm option: msgcomm Invocation. (line 153)\n* -h, msgconv option: msgconv Invocation. (line 130)\n* -h, msgen option: msgen Invocation. (line 133)\n* -h, msgexec option: msgexec Invocation. (line 77)\n* -h, msgfilter option: msgfilter Invocation.\n(line 211)\n* -h, msgfmt option: msgfmt Invocation. (line 311)\n* -h, msggrep option: msggrep Invocation. (line 200)\n* -h, msginit option: msginit Invocation. (line 131)\n* -h, msgmerge option: msgmerge Invocation. (line 207)\n* -h, msgunfmt option: msgunfmt Invocation. (line 155)\n* -h, msguniq option: msguniq Invocation. (line 147)\n* -h, ngettext option: ngettext Invocation. (line 36)\n* -h, xgettext option: xgettext Invocation. (line 497)\n* -i, msgattrib option: msgattrib Invocation.\n(line 131)\n* -i, msgcat option: msgcat Invocation. (line 111)\n* -i, msgcomm option: msgcomm Invocation. (line 93)\n* -i, msgconv option: msgconv Invocation. (line 73)\n* -i, msgen option: msgen Invocation. (line 76)\n* -i, msgexec option: msgexec Invocation. (line 50)\n* -i, msgfilter option: msgfilter Invocation.\n(line 30)\n* -i, msggrep option: msggrep Invocation. (line 110)\n* -i, msginit option: msginit Invocation. (line 51)\n* -i, msgmerge option: msgmerge Invocation. (line 150)\n* -i, msgunfmt option: msgunfmt Invocation. (line 115)\n* -i, msguniq option: msguniq Invocation. (line 90)\n* -i, xgettext option: xgettext Invocation. (line 362)\n* -j, msgfmt option: msgfmt Invocation. (line 30)\n* -J, msggrep option: msggrep Invocation. (line 74)\n* -j, msgunfmt option: msgunfmt Invocation. (line 16)\n* -j, xgettext option: xgettext Invocation. (line 85)\n* -k, msgfmt option: msgfmt Invocation. (line 140)\n* -K, msggrep option: msggrep Invocation. (line 78)\n* -k, xgettext option: xgettext Invocation. (line 174)\n* -l, msgfmt option: msgfmt Invocation. (line 83)\n* -l, msgfmt option <1>: msgfmt Invocation. (line 106)\n* -l, msgfmt option <2>: msgfmt Invocation. (line 122)\n* -l, msgfmt option <3>: msgfmt Invocation. (line 146)\n* -L, msgfmt option: msgfmt Invocation. (line 180)\n* -l, msgfmt option <4>: msgfmt Invocation. (line 184)\n* -l, msginit option: msginit Invocation. (line 84)\n* -l, msgunfmt option: msgunfmt Invocation. (line 45)\n* -l, msgunfmt option <1>: msgunfmt Invocation. (line 62)\n* -l, msgunfmt option <2>: msgunfmt Invocation. (line 78)\n* -L, xgettext option: xgettext Invocation. (line 54)\n* -m, msgcmp option: msgcmp Invocation. (line 35)\n* -M, msggrep option: msggrep Invocation. (line 70)\n* -m, msgmerge option: msgmerge Invocation. (line 96)\n* -m, xgettext option: xgettext Invocation. (line 486)\n* -M, xgettext option: xgettext Invocation. (line 490)\n* -n, gettext option: gettext Invocation. (line 40)\n* -n, msgattrib option: msgattrib Invocation.\n(line 138)\n* -n, msgcat option: msgcat Invocation. (line 118)\n* -N, msgcmp option: msgcmp Invocation. (line 39)\n* -n, msgcomm option: msgcomm Invocation. (line 100)\n* -n, msgfilter option: msgfilter Invocation.\n(line 96)\n* -N, msggrep option: msggrep Invocation. (line 65)\n* -N, msgmerge option: msgmerge Invocation. (line 107)\n* -n, msguniq option: msguniq Invocation. (line 97)\n* -n, xgettext option: xgettext Invocation. (line 371)\n* -o, msgattrib option: msgattrib Invocation.\n(line 30)\n* -o, msgcat option: msgcat Invocation. (line 46)\n* -o, msgcomm option: msgcomm Invocation. (line 41)\n* -o, msgconv option: msgconv Invocation. (line 30)\n* -o, msgen option: msgen Invocation. (line 36)\n* -o, msgfilter option: msgfilter Invocation.\n(line 45)\n* -o, msgfmt option: msgfmt Invocation. (line 59)\n* -o, msggrep option: msggrep Invocation. (line 30)\n* -o, msginit option: msginit Invocation. (line 61)\n* -o, msgmerge option: msgmerge Invocation. (line 51)\n* -o, msgunfmt option: msgunfmt Invocation. (line 93)\n* -o, msguniq option: msguniq Invocation. (line 37)\n* -o, xgettext option: xgettext Invocation. (line 39)\n* -P, msgattrib option: msgattrib Invocation.\n(line 107)\n* -p, msgattrib option: msgattrib Invocation.\n(line 153)\n* -P, msgcat option: msgcat Invocation. (line 74)\n* -p, msgcat option: msgcat Invocation. (line 133)\n* -P, msgcmp option: msgcmp Invocation. (line 57)\n* -P, msgcomm option: msgcomm Invocation. (line 69)\n* -p, msgcomm option: msgcomm Invocation. (line 115)\n* -P, msgconv option: msgconv Invocation. (line 49)\n* -p, msgconv option: msgconv Invocation. (line 95)\n* -P, msgen option: msgen Invocation. (line 46)\n* -p, msgen option: msgen Invocation. (line 98)\n* -P, msgexec option: msgexec Invocation. (line 65)\n* -P, msgfilter option: msgfilter Invocation.\n(line 126)\n* -p, msgfilter option: msgfilter Invocation.\n(line 176)\n* -P, msgfmt option: msgfmt Invocation. (line 214)\n* -P, msggrep option: msggrep Invocation. (line 122)\n* -p, msggrep option: msggrep Invocation. (line 167)\n* -P, msginit option: msginit Invocation. (line 72)\n* -p, msginit option: msginit Invocation. (line 105)\n* -P, msgmerge option: msgmerge Invocation. (line 119)\n* -p, msgmerge option: msgmerge Invocation. (line 172)\n* -p, msgunfmt option: msgunfmt Invocation. (line 124)\n* -P, msguniq option: msguniq Invocation. (line 58)\n* -p, msguniq option: msguniq Invocation. (line 112)\n* -p, xgettext option: xgettext Invocation. (line 44)\n* -q, msgmerge option: msgmerge Invocation. (line 220)\n* -r, msgfmt option: msgfmt Invocation. (line 79)\n* -r, msgfmt option <1>: msgfmt Invocation. (line 102)\n* -r, msgunfmt option: msgunfmt Invocation. (line 41)\n* -r, msgunfmt option <1>: msgunfmt Invocation. (line 58)\n* -s, msgattrib option: msgattrib Invocation.\n(line 176)\n* -s, msgcat option: msgcat Invocation. (line 156)\n* -s, msgcomm option: msgcomm Invocation. (line 138)\n* -s, msgconv option: msgconv Invocation. (line 118)\n* -s, msgen option: msgen Invocation. (line 121)\n* -s, msgfilter option: msgfilter Invocation.\n(line 199)\n* -s, msgmerge option: msgmerge Invocation. (line 195)\n* -s, msgunfmt option: msgunfmt Invocation. (line 147)\n* -s, msguniq option: msguniq Invocation. (line 135)\n* -s, xgettext option: xgettext Invocation. (line 416)\n* -t, msgcat option: msgcat Invocation. (line 86)\n* -t, msgconv option: msgconv Invocation. (line 40)\n* -T, msggrep option: msggrep Invocation. (line 82)\n* -t, msguniq option: msguniq Invocation. (line 70)\n* -T, xgettext option: xgettext Invocation. (line 316)\n* -u, msgcat option: msgcat Invocation. (line 66)\n* -u, msgcomm option: msgcomm Invocation. (line 61)\n* -U, msgmerge option: msgmerge Invocation. (line 44)\n* -u, msguniq option: msguniq Invocation. (line 51)\n* -v, envsubst option: envsubst Invocation. (line 15)\n* -V, envsubst option: envsubst Invocation. (line 25)\n* -V, gettext option: gettext Invocation. (line 45)\n* -V, msgattrib option: msgattrib Invocation.\n(line 192)\n* -V, msgcat option: msgcat Invocation. (line 172)\n* -V, msgcmp option: msgcmp Invocation. (line 73)\n* -V, msgcomm option: msgcomm Invocation. (line 157)\n* -V, msgconv option: msgconv Invocation. (line 134)\n* -V, msgen option: msgen Invocation. (line 137)\n* -V, msgexec option: msgexec Invocation. (line 81)\n* -V, msgfilter option: msgfilter Invocation.\n(line 215)\n* -V, msgfmt option: msgfmt Invocation. (line 315)\n* -v, msgfmt option: msgfmt Invocation. (line 324)\n* -v, msggrep option: msggrep Invocation. (line 114)\n* -V, msggrep option: msggrep Invocation. (line 204)\n* -V, msginit option: msginit Invocation. (line 135)\n* -V, msgmerge option: msgmerge Invocation. (line 211)\n* -v, msgmerge option: msgmerge Invocation. (line 215)\n* -V, msgunfmt option: msgunfmt Invocation. (line 159)\n* -v, msgunfmt option: msgunfmt Invocation. (line 163)\n* -V, msguniq option: msguniq Invocation. (line 151)\n* -V, ngettext option: ngettext Invocation. (line 40)\n* -V, xgettext option: xgettext Invocation. (line 501)\n* -v, xgettext option: xgettext Invocation. (line 505)\n* -w, msgattrib option: msgattrib Invocation.\n(line 163)\n* -w, msgcat option: msgcat Invocation. (line 143)\n* -w, msgcomm option: msgcomm Invocation. (line 125)\n* -w, msgconv option: msgconv Invocation. (line 105)\n* -w, msgen option: msgen Invocation. (line 108)\n* -w, msgfilter option: msgfilter Invocation.\n(line 186)\n* -w, msggrep option: msggrep Invocation. (line 177)\n* -w, msginit option: msginit Invocation. (line 115)\n* -w, msgmerge option: msgmerge Invocation. (line 182)\n* -w, msgunfmt option: msgunfmt Invocation. (line 134)\n* -w, msguniq option: msguniq Invocation. (line 122)\n* -w, xgettext option: xgettext Invocation. (line 403)\n* -X, msggrep option: msggrep Invocation. (line 90)\n* -x, xgettext option: xgettext Invocation. (line 89)\n\nFile: gettext.info, Node: Variable Index, Next: PO Mode Index, Prev: Option Index, Up: Top\n", "subsections": [] }, "Variable Index": { "content": "* Menu:\n\n* GETTEXTLOGUNTRANSLATED, environment variable: Prioritizing messages.\n(line 22)\n* LANG, environment variable: Locale Environment Variables.\n(line 15)\n* LANG, environment variable <1>: gettext grok. (line 30)\n* LANGUAGE, environment variable: Locale Environment Variables.\n(line 11)\n* LANGUAGE, environment variable <1>: gettext grok. (line 28)\n* LANGUAGE, environment variable <2>: po/Rules-*. (line 11)\n* LCALL, environment variable: Locale Environment Variables.\n(line 11)\n* LCALL, environment variable <1>: gettext grok. (line 28)\n* LCCOLLATE, environment variable: Locale Environment Variables.\n(line 12)\n* LCCOLLATE, environment variable <1>: gettext grok. (line 29)\n* LCCTYPE, environment variable: Locale Environment Variables.\n(line 12)\n* LCCTYPE, environment variable <1>: gettext grok. (line 29)\n* LCMESSAGES, environment variable: Locale Environment Variables.\n(line 12)\n* LCMESSAGES, environment variable <1>: gettext grok. (line 29)\n* LCMONETARY, environment variable: Locale Environment Variables.\n(line 12)\n* LCMONETARY, environment variable <1>: gettext grok. (line 29)\n* LCNUMERIC, environment variable: Locale Environment Variables.\n(line 12)\n* LCNUMERIC, environment variable <1>: gettext grok. (line 29)\n* LCTIME, environment variable: Locale Environment Variables.\n(line 12)\n* LCTIME, environment variable <1>: gettext grok. (line 29)\n* LINGUAS, environment variable: Installers. (line 17)\n* MSGEXECLOCATION, environment variable: msgexec Invocation. (line 21)\n* MSGEXECMSGCTXT, environment variable: msgexec Invocation. (line 21)\n* MSGEXECMSGID, environment variable: msgexec Invocation. (line 21)\n* MSGEXECMSGIDPLURAL, environment variable: msgexec Invocation.\n(line 21)\n* MSGEXECPLURALFORM, environment variable: msgexec Invocation.\n(line 21)\n* MSGEXECPREVMSGCTXT, environment variable: msgexec Invocation.\n(line 21)\n* MSGEXECPREVMSGID, environment variable: msgexec Invocation.\n(line 21)\n* MSGEXECPREVMSGIDPLURAL, environment variable: msgexec Invocation.\n(line 21)\n* MSGFILTERLOCATION, environment variable: msgfilter Invocation.\n(line 11)\n* MSGFILTERMSGCTXT, environment variable: msgfilter Invocation.\n(line 11)\n* MSGFILTERMSGID, environment variable: msgfilter Invocation. (line 11)\n* MSGFILTERMSGIDPLURAL, environment variable: msgfilter Invocation.\n(line 11)\n* MSGFILTERPLURALFORM, environment variable: msgfilter Invocation.\n(line 11)\n* MSGFILTERPREVMSGCTXT, environment variable: msgfilter Invocation.\n(line 11)\n* MSGFILTERPREVMSGID, environment variable: msgfilter Invocation.\n(line 11)\n* MSGFILTERPREVMSGIDPLURAL, environment variable: msgfilter Invocation.\n(line 11)\n* OUTPUTCHARSET, environment variable: Working in a Windows console.\n(line 6)\n* POSTYLE, environment variable: The --style option. (line 10)\n* TERM, environment variable: The TERM variable. (line 6)\n* TEXTDOMAIN, environment variable: sh. (line 27)\n* TEXTDOMAINDIR, environment variable: sh. (line 30)\n\nFile: gettext.info, Node: PO Mode Index, Next: Autoconf Macro Index, Prev: Variable Index, Up: Top\n", "subsections": [] }, "PO Mode Index": { "content": "* Menu:\n\n* #, PO Mode command: Modifying Comments. (line 24)\n* #, PO Mode command <1>: Modifying Comments. (line 45)\n* ,, PO Mode command: Marking. (line 43)\n* ., PO Mode command: Entry Positioning. (line 20)\n* ., PO Mode command <1>: Entry Positioning. (line 45)\n* .emacs customizations: Installation. (line 13)\n* 0, PO Mode command: Main PO Commands. (line 40)\n* 0, PO Mode command <1>: Main PO Commands. (line 72)\n* <, PO Mode command: Entry Positioning. (line 29)\n* <, PO Mode command <1>: Entry Positioning. (line 73)\n* =, PO Mode command: Main PO Commands. (line 47)\n* =, PO Mode command <1>: Main PO Commands. (line 87)\n* >, PO Mode command: Entry Positioning. (line 32)\n* >, PO Mode command <1>: Entry Positioning. (line 73)\n* ?, PO Mode command: Main PO Commands. (line 44)\n* ?, PO Mode command <1>: Main PO Commands. (line 83)\n* , PO Mode command: Main PO Commands. (line 30)\n* , PO Mode command <1>: Main PO Commands. (line 52)\n* a, PO Mode command: Auxiliary. (line 21)\n* A, PO Mode command: Auxiliary. (line 28)\n* A, PO Mode command <1>: Auxiliary. (line 35)\n* a, PO Mode command <1>: Auxiliary. (line 39)\n* auxiliary PO file: Auxiliary. (line 13)\n* C-c C-a, PO Mode command: Subedit. (line 17)\n* C-c C-a, PO Mode command <1>: Subedit. (line 36)\n* C-c C-a, PO Mode command <2>: Auxiliary. (line 25)\n* C-c C-a, PO Mode command <3>: Auxiliary. (line 48)\n* C-c C-c, PO Mode command: Subedit. (line 11)\n* C-c C-c, PO Mode command <1>: Subedit. (line 19)\n* C-c C-k, PO Mode command: Subedit. (line 14)\n* C-c C-k, PO Mode command <1>: Subedit. (line 27)\n* C-j, PO Mode command: Modifying Translations.\n(line 26)\n* C-j, PO Mode command <1>: Modifying Translations.\n(line 52)\n* commands: Main PO Commands. (line 6)\n* comment out PO file entry: Obsolete Entries. (line 46)\n* consulting program sources: C Sources Context. (line 6)\n* consulting translations to other languages: Auxiliary. (line 6)\n* current entry of a PO file: Entry Positioning. (line 6)\n* cut and paste for translated strings: Modifying Translations.\n(line 74)\n* DEL, PO Mode command: Fuzzy Entries. (line 58)\n* DEL, PO Mode command <1>: Obsolete Entries. (line 32)\n* DEL, PO Mode command <2>: Obsolete Entries. (line 46)\n* editing comments: Modifying Comments. (line 6)\n* editing multiple entries: Subedit. (line 64)\n* editing translations: Modifying Translations.\n(line 6)\n* etags, using for marking strings: Marking. (line 17)\n* exiting PO subedit: Subedit. (line 19)\n* f, PO Mode command: Fuzzy Entries. (line 29)\n* F, PO Mode command: Fuzzy Entries. (line 32)\n* f, PO Mode command <1>: Fuzzy Entries. (line 37)\n* F, PO Mode command <1>: Fuzzy Entries. (line 37)\n* find source fragment for a PO file entry: C Sources Context.\n(line 33)\n* h, PO Mode command: Main PO Commands. (line 44)\n* h, PO Mode command <1>: Main PO Commands. (line 83)\n* installing PO mode: Installation. (line 13)\n* k, PO Mode command: Untranslated Entries.\n(line 33)\n* k, PO Mode command <1>: Untranslated Entries.\n(line 40)\n* k, PO Mode command <2>: Modifying Translations.\n(line 30)\n* k, PO Mode command <3>: Modifying Translations.\n(line 74)\n* K, PO Mode command: Modifying Comments. (line 27)\n* K, PO Mode command <1>: Modifying Comments. (line 60)\n* LFD, PO Mode command: Modifying Translations.\n(line 26)\n* LFD, PO Mode command <1>: Modifying Translations.\n(line 52)\n* looking at the source to aid translation: C Sources Context.\n(line 6)\n* m, PO Mode command: Entry Positioning. (line 35)\n* m, PO Mode command <1>: Entry Positioning. (line 91)\n* M-,, PO Mode command: Marking. (line 47)\n* M-., PO Mode command: Marking. (line 50)\n* M-A, PO Mode command: Auxiliary. (line 32)\n* M-A, PO Mode command <1>: Auxiliary. (line 35)\n* M-s, PO Mode command: C Sources Context. (line 41)\n* M-S, PO Mode command: C Sources Context. (line 49)\n* M-s, PO Mode command <1>: C Sources Context. (line 52)\n* M-S, PO Mode command <1>: C Sources Context. (line 88)\n* marking strings for translation: Marking. (line 6)\n* moving by fuzzy entries: Fuzzy Entries. (line 23)\n* moving by obsolete entries: Obsolete Entries. (line 22)\n* moving by translated entries: Translated Entries. (line 12)\n* moving by untranslated entries: Untranslated Entries.\n(line 19)\n* moving through a PO file: Entry Positioning. (line 14)\n* n, PO Mode command: Entry Positioning. (line 23)\n* n, PO Mode command <1>: Entry Positioning. (line 68)\n* next-error, stepping through PO file validation results: Main PO Commands.\n(line 99)\n* normalize, PO Mode command: Auxiliary. (line 63)\n* o, PO Mode command: Obsolete Entries. (line 26)\n* O, PO Mode command: Obsolete Entries. (line 29)\n* o, PO Mode command <1>: Obsolete Entries. (line 35)\n* O, PO Mode command <1>: Obsolete Entries. (line 35)\n* obsolete active entry: Obsolete Entries. (line 46)\n* p, PO Mode command: Entry Positioning. (line 26)\n* p, PO Mode command <1>: Entry Positioning. (line 68)\n* pending subedits: Subedit. (line 75)\n* po-auto-edit-with-msgid, PO Mode variable: Modifying Translations.\n(line 57)\n* po-auto-fuzzy-on-edit, PO Mode variable: Translated Entries.\n(line 27)\n* po-auto-select-on-unfuzzy, PO Mode variable: Fuzzy Entries. (line 42)\n* po-confirm-and-quit, PO Mode command: Main PO Commands. (line 61)\n* po-consider-as-auxiliary, PO Mode command: Auxiliary. (line 35)\n* po-consider-source-path, PO Mode command: C Sources Context.\n(line 88)\n* po-current-entry, PO Mode command: Entry Positioning. (line 45)\n* po-cycle-auxiliary, PO Mode command: Auxiliary. (line 39)\n* po-cycle-source-reference, PO Mode command: C Sources Context.\n(line 52)\n* po-edit-comment, PO Mode command: Modifying Comments. (line 45)\n* po-edit-msgstr, PO Mode command: Modifying Translations.\n(line 41)\n* po-exchange-location, PO Mode command: Entry Positioning. (line 105)\n* po-fade-out-entry, PO Mode command: Fuzzy Entries. (line 58)\n* po-fade-out-entry, PO Mode command <1>: Obsolete Entries. (line 46)\n* po-first-entry, PO Mode command: Entry Positioning. (line 73)\n* po-help, PO Mode command: Main PO Commands. (line 83)\n* po-ignore-as-auxiliary, PO Mode command: Auxiliary. (line 35)\n* po-ignore-source-path, PO Mode command: C Sources Context. (line 88)\n* po-kill-comment, PO Mode command: Modifying Comments. (line 60)\n* po-kill-msgstr, PO Mode command: Untranslated Entries.\n(line 40)\n* po-kill-msgstr, PO Mode command <1>: Modifying Translations.\n(line 74)\n* po-kill-ring-save-comment, PO Mode command: Modifying Comments.\n(line 60)\n* po-kill-ring-save-msgstr, PO Mode command: Modifying Translations.\n(line 74)\n* po-last-entry, PO Mode command: Entry Positioning. (line 73)\n* po-mark-translatable, PO Mode command: Marking. (line 98)\n* po-msgid-to-msgstr, PO Mode command: Modifying Translations.\n(line 52)\n* po-next-entry, PO Mode command: Entry Positioning. (line 68)\n* po-next-fuzzy-entry, PO Mode command: Fuzzy Entries. (line 37)\n* po-next-obsolete-entry, PO Mode command: Obsolete Entries. (line 35)\n* po-next-translated-entry, PO Mode command: Translated Entries.\n(line 22)\n* po-next-untranslated-entry, PO Mode command: Untranslated Entries.\n(line 35)\n* po-normalize, PO Mode command: Normalizing. (line 31)\n* po-other-window, PO Mode command: Main PO Commands. (line 72)\n* po-pop-location, PO Mode command: Entry Positioning. (line 91)\n* po-previous-entry, PO Mode command: Entry Positioning. (line 68)\n* po-previous-fuzzy-entry, PO Mode command: Fuzzy Entries. (line 37)\n* po-previous-obsolete-entry, PO Mode command: Obsolete Entries.\n(line 35)\n* po-previous-translated-entry, PO Mode command: Translated Entries.\n(line 22)\n* po-previous-untransted-entry, PO Mode command: Untranslated Entries.\n(line 35)\n* po-push-location, PO Mode command: Entry Positioning. (line 91)\n* po-quit, PO Mode command: Main PO Commands. (line 61)\n* po-select-auxiliary, PO Mode command: Auxiliary. (line 48)\n* po-select-mark-and-mark, PO Mode command: Marking. (line 98)\n* po-select-source-reference, PO Mode command: C Sources Context.\n(line 52)\n* po-statistics, PO Mode command: Main PO Commands. (line 87)\n* po-subedit-abort, PO Mode command: Subedit. (line 27)\n* po-subedit-cycle-auxiliary, PO Mode command: Subedit. (line 36)\n* po-subedit-exit, PO Mode command: Subedit. (line 19)\n* po-subedit-mode-hook, PO Mode variable: Modifying Comments. (line 57)\n* po-tags-search, PO Mode command: Marking. (line 54)\n* po-undo, PO Mode command: Main PO Commands. (line 52)\n* po-unfuzzy, PO Mode command: Fuzzy Entries. (line 42)\n* po-validate, PO Mode command: Main PO Commands. (line 92)\n* po-yank-comment, PO Mode command: Modifying Comments. (line 60)\n* po-yank-msgstr, PO Mode command: Modifying Translations.\n(line 97)\n* Q, PO Mode command: Main PO Commands. (line 33)\n* q, PO Mode command: Main PO Commands. (line 36)\n* Q, PO Mode command <1>: Main PO Commands. (line 61)\n* q, PO Mode command <1>: Main PO Commands. (line 61)\n* r, PO Mode command: Entry Positioning. (line 39)\n* r, PO Mode command <1>: Entry Positioning. (line 91)\n* RET, PO Mode command: Modifying Translations.\n(line 22)\n* RET, PO Mode command <1>: Modifying Translations.\n(line 41)\n* s, PO Mode command: C Sources Context. (line 37)\n* S, PO Mode command: C Sources Context. (line 45)\n* s, PO Mode command <1>: C Sources Context. (line 52)\n* S, PO Mode command <1>: C Sources Context. (line 88)\n* starting a string translation: Modifying Translations.\n(line 63)\n* string normalization in entries: Normalizing. (line 30)\n* subedit minor mode: Subedit. (line 6)\n* t, PO Mode command: Translated Entries. (line 16)\n* T, PO Mode command: Translated Entries. (line 19)\n* t, PO Mode command <1>: Translated Entries. (line 22)\n* T, PO Mode command <1>: Translated Entries. (line 22)\n* TAB, PO Mode command: Fuzzy Entries. (line 35)\n* TAB, PO Mode command <1>: Fuzzy Entries. (line 42)\n* TAGS, and marking translatable strings: Marking. (line 30)\n* u, PO Mode command: Untranslated Entries.\n(line 26)\n* U, PO Mode command: Untranslated Entries.\n(line 29)\n* u, PO Mode command <1>: Untranslated Entries.\n(line 35)\n* U, PO Mode command <1>: Untranslated Entries.\n(line 35)\n* use the source, Luke: C Sources Context. (line 6)\n* using obsolete translations to make new entries: Modifying Translations.\n(line 123)\n* using translation compendia: Compendium. (line 6)\n* V, PO Mode command: Main PO Commands. (line 50)\n* V, PO Mode command <1>: Main PO Commands. (line 92)\n* w, PO Mode command: Modifying Translations.\n(line 34)\n* w, PO Mode command <1>: Modifying Translations.\n(line 74)\n* W, PO Mode command: Modifying Comments. (line 31)\n* W, PO Mode command <1>: Modifying Comments. (line 60)\n* x, PO Mode command: Entry Positioning. (line 42)\n* x, PO Mode command <1>: Entry Positioning. (line 105)\n* y, PO Mode command: Modifying Translations.\n(line 38)\n* y, PO Mode command <1>: Modifying Translations.\n(line 97)\n* Y, PO Mode command: Modifying Comments. (line 35)\n* Y, PO Mode command <1>: Modifying Comments. (line 60)\n\nFile: gettext.info, Node: Autoconf Macro Index, Next: Index, Prev: PO Mode Index, Up: Top\n", "subsections": [] }, "Autoconf Macro Index": { "content": "* Menu:\n\n* AMGNUGETTEXT: AMGNUGETTEXT. (line 6)\n* AMGNUGETTEXTNEED: AMGNUGETTEXTNEED. (line 6)\n* AMGNUGETTEXTVERSION: AMGNUGETTEXTVERSION.\n(line 6)\n* AMICONV: AMICONV. (line 6)\n* AMPOSUBDIRS: AMPOSUBDIRS. (line 6)\n* AMXGETTEXTOPTION: AMXGETTEXTOPTION. (line 6)\n\nFile: gettext.info, Node: Index, Prev: Autoconf Macro Index, Up: Top\n", "subsections": [] }, "General Index": { "content": "* Menu:\n\n* , a macro to mark strings for translation: Mark Keywords. (line 45)\n* nlmsgcatcntr: gettext grok. (line 59)\n* ABOUT-NLS file: Installing Localizations.\n(line 13)\n* ABOUT-NLS file <1>: The original ABOUT-NLS.\n(line 6)\n* accumulating translations: Creating Compendia. (line 14)\n* aclocal.m4 file: aclocal. (line 6)\n* adding keywords, xgettext: xgettext Invocation. (line 178)\n* ambiguities: Preparing Strings. (line 46)\n* ANSI encoding: Working in a Windows console.\n(line 6)\n* apply a filter to translations: msgfilter Invocation.\n(line 8)\n* apply command to all translations in a catalog: msgexec Invocation.\n(line 8)\n* Arabic digits: c-format. (line 28)\n* attribute manipulation: msgattrib Invocation.\n(line 8)\n* attribute, fuzzy: Fuzzy Entries. (line 6)\n* attributes of a PO file entry: Fuzzy Entries. (line 6)\n* attributes, manipulating: Manipulating. (line 56)\n* autoconf macros for gettext: autoconf macros. (line 6)\n* autopoint program, usage: autopoint Invocation.\n(line 6)\n* auxiliary PO file: Auxiliary. (line 13)\n* available translations: Installing Localizations.\n(line 6)\n* awk: gawk. (line 6)\n* awk-format flag: PO Files. (line 160)\n* backup old file, and msgmerge program: msgmerge Invocation. (line 62)\n* bash: bash. (line 6)\n* bibliography: References. (line 6)\n* big picture: Overview. (line 6)\n* bindtextdomaincodeset: Charset conversion. (line 26)\n* Boost format strings: xgettext Invocation. (line 329)\n* boost-format flag: PO Files. (line 188)\n* bug report address: Introduction. (line 24)\n* C and C-like languages: C. (line 6)\n* C trigraphs: xgettext Invocation. (line 316)\n* C#: C#. (line 6)\n* C# mode, and msgfmt program: msgfmt Invocation. (line 36)\n* C# mode, and msgunfmt program: msgunfmt Invocation. (line 19)\n* C# resources mode, and msgfmt program: msgfmt Invocation. (line 40)\n* C# resources mode, and msgunfmt program: msgunfmt Invocation.\n(line 23)\n* C#, string concatenation: Preparing Strings. (line 182)\n* c-format flag: PO Files. (line 88)\n* c-format, and xgettext: c-format Flag. (line 47)\n* catalog encoding and msgexec output: msgexec Invocation. (line 35)\n* catclose, a catgets function: Interface to catgets.\n(line 44)\n* catgets, a catgets function: Interface to catgets.\n(line 25)\n* catgets, X/Open specification: catgets. (line 6)\n* catopen, a catgets function: Interface to catgets.\n(line 13)\n* character encoding: Aspects. (line 67)\n* charset conversion at runtime: Charset conversion. (line 6)\n* charset of PO files: Header Entry. (line 101)\n* check format strings: msgfmt Invocation. (line 230)\n* checking of translations: Manipulating. (line 41)\n* clisp: Common Lisp. (line 6)\n* clisp C sources: clisp C. (line 6)\n* codeset: Aspects. (line 67)\n* comments in PO files: PO Files. (line 329)\n* comments, automatic: PO Files. (line 36)\n* comments, extracted: PO Files. (line 36)\n* comments, translator: PO Files. (line 36)\n* Common Lisp: Common Lisp. (line 6)\n* compare PO files: msgcmp Invocation. (line 8)\n* comparison of interfaces: Comparison. (line 6)\n* compatibility with X/Open msgfmt: msgfmt Invocation. (line 263)\n* compendium: Compendium. (line 6)\n* compendium, creating: Creating Compendia. (line 6)\n* concatenate PO files: msgcat Invocation. (line 8)\n* concatenating PO files into a compendium: Creating Compendia.\n(line 14)\n* concatenation of strings: Preparing Strings. (line 131)\n* config.h.in file: config.h.in. (line 6)\n* context: Contexts. (line 6)\n* context, argument specification in xgettext: xgettext Invocation.\n(line 178)\n* context, in MO files: MO Files. (line 71)\n* context, in PO files: PO Files. (line 220)\n* control characters: Preparing Strings. (line 230)\n* convert binary message catalog into PO file: msgunfmt Invocation.\n(line 8)\n* convert translations to a different encoding: msgconv Invocation.\n(line 8)\n* converting a package to use gettext: Prerequisites. (line 6)\n* country codes: Country Codes. (line 6)\n* create new PO file: msginit Invocation. (line 8)\n* creating a new PO file: Creating. (line 6)\n* creating compendia: Creating Compendia. (line 6)\n* csharp-format flag: PO Files. (line 128)\n* currency symbols: Aspects. (line 80)\n* date format: Aspects. (line 86)\n* dcngettext: Plural forms. (line 160)\n* dcpgettext: Contexts. (line 56)\n* dcpgettextexpr: Contexts. (line 112)\n* debugging messages marked as format strings: xgettext Invocation.\n(line 333)\n* Desktop Entry mode, and msgfmt program: msgfmt Invocation. (line 49)\n* dialect: Manipulating. (line 28)\n* disabling NLS: lib/gettext.h. (line 6)\n* distribution tarball: Release Management. (line 6)\n* dngettext: Plural forms. (line 152)\n* dollar substitution: envsubst Invocation. (line 8)\n* domain ambiguities: Ambiguities. (line 6)\n* dpgettext: Contexts. (line 56)\n* dpgettextexpr: Contexts. (line 112)\n* duplicate elimination: Manipulating. (line 45)\n* duplicate removal: msguniq Invocation. (line 8)\n* editing comments in PO files: Modifying Comments. (line 6)\n* Editing PO Files: Editing. (line 6)\n* editing translations: Modifying Translations.\n(line 6)\n* elisp-format flag: PO Files. (line 144)\n* Emacs Lisp: Emacs Lisp. (line 6)\n* Emacs PO Mode: PO Mode. (line 6)\n* encoding: Aspects. (line 67)\n* encoding conversion: Manipulating. (line 17)\n* encoding conversion at runtime: Charset conversion. (line 6)\n* encoding for your language: Header Entry. (line 130)\n* encoding list: Header Entry. (line 114)\n* encoding of PO files: Header Entry. (line 101)\n* environment variables: envsubst Invocation. (line 8)\n* envsubst program, usage: envsubst Invocation. (line 6)\n* evalgettext function, usage: evalgettext Invocation.\n(line 6)\n* evalngettext function, usage: evalngettext Invocation.\n(line 6)\n* evalnpgettext function, usage: evalnpgettext Invocation.\n(line 6)\n* evalpgettext function, usage: evalpgettext Invocation.\n(line 6)\n* evolution of packages: Overview. (line 127)\n* extracting parts of a PO file into a compendium: Creating Compendia.\n(line 64)\n* FDL, GNU Free Documentation License: GNU FDL. (line 6)\n* file format, .mo: MO Files. (line 6)\n* file format, .po: PO Files. (line 6)\n* files, .po and .mo: Files. (line 6)\n* files, .pot: Overview. (line 67)\n* filter messages according to attributes: msgattrib Invocation.\n(line 8)\n* find common messages: msgcomm Invocation. (line 8)\n* force use of fuzzy entries: msgfmt Invocation. (line 279)\n* format strings: c-format Flag. (line 6)\n* Free Pascal: Pascal. (line 6)\n* function attribute, formatarg: xgettext Invocation. (line 294)\n* function attribute, format: xgettext Invocation. (line 280)\n* fuzzy entries: Fuzzy Entries. (line 6)\n* fuzzy flag: PO Files. (line 78)\n* gawk: gawk. (line 6)\n* gcc-internal-format flag: PO Files. (line 208)\n* GCC-source: GCC-source. (line 6)\n* generate binary message catalog from PO file: msgfmt Invocation.\n(line 8)\n* generate translation catalog in English: msgen Invocation. (line 8)\n* gettext files: Adjusting Files. (line 6)\n* gettext installation: Installation. (line 6)\n* gettext interface: Interface to gettext.\n(line 6)\n* gettext program, usage: gettext Invocation. (line 6)\n* gettext vs catgets: Comparison. (line 6)\n* gettext, a programmer's view: gettext. (line 6)\n* gettext.h file: lib/gettext.h. (line 6)\n* gettextize program, usage: gettextize Invocation.\n(line 34)\n* gfc-internal-format flag: PO Files. (line 212)\n* GNOME PO file editor: Gtranslator. (line 5)\n* GPL, GNU General Public License: GNU GPL. (line 6)\n* GUI programs: Contexts. (line 6)\n* guile: Scheme. (line 6)\n* hash table, inside MO files: MO Files. (line 55)\n* he, she, and they: Introduction. (line 15)\n* header entry of a PO file: Header Entry. (line 6)\n* help option: Preparing Strings. (line 120)\n* history of GNU gettext: History. (line 6)\n* i18n: Concepts. (line 6)\n* importing PO files: Normalizing. (line 54)\n* include file libintl.h: Overview. (line 57)\n* include file libintl.h <1>: Importing. (line 11)\n* include file libintl.h <2>: Comparison. (line 33)\n* include file libintl.h <3>: lib/gettext.h. (line 28)\n* initialization: Triggering. (line 6)\n* initialize new PO file: msginit Invocation. (line 8)\n* initialize translations from a compendium: Using Compendia. (line 12)\n* installing gettext: Installation. (line 6)\n* interface to catgets: Interface to catgets.\n(line 6)\n* internationalization: Concepts. (line 16)\n* inttypes.h: Preparing Strings. (line 147)\n* ISO 3166: Country Codes. (line 6)\n* ISO 639: Language Codes. (line 6)\n* Java: Java. (line 6)\n* Java mode, and msgfmt program: msgfmt Invocation. (line 30)\n* Java mode, and msgunfmt program: msgunfmt Invocation. (line 16)\n* Java, string concatenation: Preparing Strings. (line 182)\n* java-format flag: PO Files. (line 119)\n* java-printf-format flag: PO Files. (line 124)\n* javascript-format flag: PO Files. (line 132)\n* KDE format strings: xgettext Invocation. (line 325)\n* KDE PO file editor: KBabel. (line 5)\n* kde-format flag: PO Files. (line 184)\n* keyboard accelerator checking: msgfmt Invocation. (line 267)\n* l10n: Concepts. (line 6)\n* language codes: Language Codes. (line 6)\n* language selection: Locale Environment Variables.\n(line 6)\n* language selection at runtime: gettext grok. (line 14)\n* large package: Ambiguities. (line 6)\n* LGPL, GNU Lesser General Public License: GNU LGPL. (line 6)\n* libiconv library: AMICONV. (line 20)\n* libintl for C#: C#. (line 180)\n* libintl for Java: Java. (line 109)\n* libintl library: AMGNUGETTEXT. (line 43)\n* librep Lisp: librep. (line 6)\n* librep-format flag: PO Files. (line 148)\n* License, GNU FDL: GNU FDL. (line 6)\n* License, GNU GPL: GNU GPL. (line 6)\n* License, GNU LGPL: GNU LGPL. (line 6)\n* Licenses: Licenses. (line 6)\n* LINGUAS file: po/LINGUAS. (line 6)\n* link with libintl: Overview. (line 62)\n* Linux: Aspects. (line 129)\n* Linux <1>: Overview. (line 62)\n* Linux <2>: Header Entry. (line 127)\n* Lisp: Common Lisp. (line 6)\n* lisp-format flag: PO Files. (line 140)\n* list of translation teams, where to find: Header Entry. (line 54)\n* locale categories: Aspects. (line 61)\n* locale categories <1>: Aspects. (line 118)\n* locale category, LCALL: Triggering. (line 23)\n* locale category, LCCOLLATE: Triggering. (line 52)\n* locale category, LCCTYPE: Aspects. (line 67)\n* locale category, LCCTYPE <1>: Triggering. (line 23)\n* locale category, LCCTYPE <2>: Triggering. (line 52)\n* locale category, LCMESSAGES: Aspects. (line 112)\n* locale category, LCMESSAGES <1>: Triggering. (line 52)\n* locale category, LCMONETARY: Aspects. (line 80)\n* locale category, LCMONETARY <1>: Triggering. (line 52)\n* locale category, LCNUMERIC: Aspects. (line 97)\n* locale category, LCNUMERIC <1>: Triggering. (line 52)\n* locale category, LCRESPONSES: Triggering. (line 52)\n* locale category, LCTIME: Aspects. (line 86)\n* locale category, LCTIME <1>: Triggering. (line 52)\n* locale program: Header Entry. (line 107)\n* localization: Concepts. (line 26)\n* lookup message translation: gettext Invocation. (line 9)\n* lookup message translation <1>: evalgettext Invocation.\n(line 8)\n* lookup message translation with context: evalpgettext Invocation.\n(line 8)\n* lookup plural message translation: ngettext Invocation. (line 8)\n* lookup plural message translation <1>: evalngettext Invocation.\n(line 8)\n* lookup plural message translation with context: evalnpgettext Invocation.\n(line 8)\n* lua-format flag: PO Files. (line 164)\n* magic signature of MO files: MO Files. (line 9)\n* Makefile.in.in extensions: po/Rules-*. (line 6)\n* Makevars file: po/Makevars. (line 6)\n* manipulating PO files: Manipulating. (line 6)\n* marking Perl sources: Perl. (line 97)\n* marking string initializers: Special cases. (line 6)\n* marking strings that require translation: Mark Keywords. (line 6)\n* marking strings, preparations: Preparing Strings. (line 6)\n* marking translatable strings: Overview. (line 34)\n* markup: Preparing Strings. (line 230)\n* menu entries: Contexts. (line 6)\n* menu, keyboard accelerator support: msgfmt Invocation. (line 267)\n* merge PO files: msgcat Invocation. (line 8)\n* merging two PO files: Manipulating. (line 10)\n* message catalog files location: Locating Catalogs. (line 6)\n* messages: Aspects. (line 112)\n* migration from earlier versions of gettext: Prerequisites. (line 6)\n* mkinstalldirs file: mkinstalldirs. (line 6)\n* mnemonics of menu entries: msgfmt Invocation. (line 267)\n* MO file's format: MO Files. (line 6)\n* modify message attributes: msgattrib Invocation.\n(line 59)\n* msgattrib program, usage: msgattrib Invocation.\n(line 6)\n* msgcat program, usage: msgcat Invocation. (line 6)\n* msgcmp program, usage: msgcmp Invocation. (line 6)\n* msgcomm program, usage: msgcomm Invocation. (line 6)\n* msgconv program, usage: msgconv Invocation. (line 6)\n* msgctxt: PO Files. (line 220)\n* msgen program, usage: msgen Invocation. (line 6)\n* msgexec program, usage: msgexec Invocation. (line 6)\n* msgfilter filter and catalog encoding: msgfilter Invocation.\n(line 62)\n* msgfilter program, usage: msgfilter Invocation.\n(line 6)\n* msgfmt program, usage: msgfmt Invocation. (line 6)\n* msggrep program, usage: msggrep Invocation. (line 6)\n* msgid: PO Files. (line 55)\n* msgidplural: PO Files. (line 240)\n* msginit program, usage: msginit Invocation. (line 6)\n* msgmerge program, usage: msgmerge Invocation. (line 6)\n* msgstr: PO Files. (line 55)\n* msgunfmt program, usage: msgunfmt Invocation. (line 6)\n* msguniq program, usage: msguniq Invocation. (line 6)\n* multi-line strings: Normalizing. (line 64)\n* Native Language Support: Concepts. (line 51)\n* Natural Language Support: Concepts. (line 51)\n* newlines in PO files: PO Files. (line 324)\n* ngettext: Plural forms. (line 82)\n* ngettext program, usage: ngettext Invocation. (line 6)\n* NLS: Concepts. (line 51)\n* no-awk-format flag: PO Files. (line 161)\n* no-boost-format flag: PO Files. (line 189)\n* no-c-format flag: PO Files. (line 89)\n* no-c-format, and xgettext: c-format Flag. (line 47)\n* no-csharp-format flag: PO Files. (line 129)\n* no-elisp-format flag: PO Files. (line 145)\n* no-gcc-internal-format flag: PO Files. (line 209)\n* no-gfc-internal-format flag: PO Files. (line 213)\n* no-java-format flag: PO Files. (line 120)\n* no-java-printf-format flag: PO Files. (line 125)\n* no-javascript-format flag: PO Files. (line 133)\n* no-kde-format flag: PO Files. (line 185)\n* no-librep-format flag: PO Files. (line 149)\n* no-lisp-format flag: PO Files. (line 141)\n* no-lua-format flag: PO Files. (line 165)\n* no-objc-format flag: PO Files. (line 108)\n* no-object-pascal-format flag: PO Files. (line 169)\n* no-perl-brace-format flag: PO Files. (line 201)\n* no-perl-format flag: PO Files. (line 197)\n* no-php-format flag: PO Files. (line 205)\n* no-python-brace-format flag: PO Files. (line 116)\n* no-python-format flag: PO Files. (line 112)\n* no-qt-format flag: PO Files. (line 177)\n* no-qt-plural-format flag: PO Files. (line 181)\n* no-ruby-format flag: PO Files. (line 153)\n* no-scheme-format flag: PO Files. (line 137)\n* no-sh-format flag: PO Files. (line 157)\n* no-smalltalk-format flag: PO Files. (line 173)\n* no-tcl-format flag: PO Files. (line 193)\n* no-ycp-format flag: PO Files. (line 218)\n* nplurals, in a PO file header: Plural forms. (line 179)\n* number format: Aspects. (line 97)\n* N, a convenience macro: Comparison. (line 41)\n* objc-format flag: PO Files. (line 107)\n* Object Pascal: Pascal. (line 6)\n* object-pascal-format flag: PO Files. (line 168)\n* obsolete entries: Obsolete Entries. (line 6)\n* OEM encoding: Working in a Windows console.\n(line 6)\n* optimization of gettext functions: Optimized gettext. (line 6)\n* orthography: Manipulating. (line 28)\n* outdigits: c-format. (line 28)\n* output to stdout, xgettext: xgettext Invocation. (line 46)\n* overview of gettext: Overview. (line 6)\n* package and version declaration in configure.ac: configure.ac.\n(line 9)\n* package build and installation options: Installers. (line 6)\n* package distributor's view of gettext: Installers. (line 6)\n* package installer's view of gettext: Installers. (line 6)\n* package maintainer's view of gettext: Maintainers. (line 6)\n* paragraphs: Preparing Strings. (line 112)\n* Pascal: Pascal. (line 6)\n* Perl: Perl. (line 6)\n* Perl default keywords: Default Keywords. (line 6)\n* Perl invalid string interpolation: Interpolation I. (line 6)\n* Perl long lines: Long Lines. (line 6)\n* Perl parentheses: Parentheses. (line 6)\n* Perl pitfalls: Perl Pitfalls. (line 6)\n* Perl quote-like expressions: Quote-like Expressions.\n(line 6)\n* Perl special keywords for hash-lookups: Special Keywords. (line 6)\n* Perl valid string interpolation: Interpolation II. (line 6)\n* perl-brace-format flag: PO Files. (line 200)\n* perl-format flag: PO Files. (line 196)\n* pgettext: Contexts. (line 33)\n* pgettextexpr: Contexts. (line 112)\n* PHP: PHP. (line 6)\n* php-format flag: PO Files. (line 204)\n* Pike: Pike. (line 6)\n* plural form formulas: Plural forms. (line 199)\n* plural forms: Plural forms. (line 6)\n* plural forms, in MO files: MO Files. (line 74)\n* plural forms, in PO files: PO Files. (line 240)\n* plural forms, translating: Translating plural forms.\n(line 6)\n* plural, in a PO file header: Plural forms. (line 179)\n* PO files' format: PO Files. (line 6)\n* PO mode (Emacs) commands: Main PO Commands. (line 6)\n* PO template file: Template. (line 6)\n* Pology: Other tools. (line 6)\n* portability problems with sed: msgfilter Invocation.\n(line 73)\n* POTFILES.in file: po/POTFILES.in. (line 6)\n* pofilecheckall: Checking API. (line 6)\n* pofilecreate: pofilet API. (line 10)\n* pofiledomains: pofilet API. (line 42)\n* pofiledomainheader: PO Header Entry API. (line 11)\n* pofilefree: pofilet API. (line 37)\n* pofileread: pofilet API. (line 14)\n* pofilewrite: pofilet API. (line 26)\n* poformatlist: Format Type API. (line 6)\n* poformatprettyname: Format Type API. (line 9)\n* poheaderfield: PO Header Entry API. (line 18)\n* poheadersetfield: PO Header Entry API. (line 24)\n* pomessageaddfilepos: pofilepost API. (line 24)\n* pomessagecheckall: Checking API. (line 12)\n* pomessagecheckformat: Checking API. (line 20)\n* pomessagecomments: pomessaget API. (line 83)\n* pomessagecreate: pomessaget API. (line 10)\n* pomessageextractedcomments: pomessaget API. (line 95)\n* pomessagefilepos: pofilepost API. (line 13)\n* pomessageisformat: pomessaget API. (line 167)\n* pomessageisfuzzy: pomessaget API. (line 158)\n* pomessageisobsolete: pomessaget API. (line 149)\n* pomessageisrange: pomessaget API. (line 179)\n* pomessageiterator: pomessageiteratort API.\n(line 10)\n* pomessageiteratorfree: pomessageiteratort API.\n(line 17)\n* pomessagemsgctxt: pomessaget API. (line 19)\n* pomessagemsgid: pomessaget API. (line 31)\n* pomessagemsgidplural: pomessaget API. (line 42)\n* pomessagemsgstr: pomessaget API. (line 56)\n* pomessagemsgstrplural: pomessaget API. (line 68)\n* pomessageprevmsgctxt: pomessaget API. (line 107)\n* pomessageprevmsgid: pomessaget API. (line 121)\n* pomessageprevmsgidplural: pomessaget API. (line 134)\n* pomessageremovefilepos: pofilepost API. (line 19)\n* pomessagesetcomments: pomessaget API. (line 88)\n* pomessagesetextractedcomments: pomessaget API. (line 101)\n* pomessagesetformat: pomessaget API. (line 173)\n* pomessagesetfuzzy: pomessaget API. (line 162)\n* pomessagesetmsgctxt: pomessaget API. (line 24)\n* pomessagesetmsgid: pomessaget API. (line 35)\n* pomessagesetmsgidplural: pomessaget API. (line 48)\n* pomessagesetmsgstr: pomessaget API. (line 61)\n* pomessagesetmsgstrplural: pomessaget API. (line 74)\n* pomessagesetobsolete: pomessaget API. (line 153)\n* pomessagesetprevmsgctxt: pomessaget API. (line 113)\n* pomessagesetprevmsgid: pomessaget API. (line 126)\n* pomessagesetprevmsgidplural: pomessaget API. (line 141)\n* pomessagesetrange: pomessaget API. (line 186)\n* ponextmessage: pomessageiteratort API.\n(line 22)\n* preparing programs for translation: Sources. (line 6)\n* preparing rules for XML translation: Preparing ITS Rules. (line 6)\n* preparing shell scripts for translation: Preparing Shell Scripts.\n(line 6)\n* problems with catgets interface: Problems with catgets.\n(line 6)\n* programming languages: Language Implementors.\n(line 6)\n* Python: Python. (line 6)\n* python-brace-format flag: PO Files. (line 115)\n* python-format flag: PO Files. (line 111)\n* Qt format strings: xgettext Invocation. (line 321)\n* Qt mode, and msgfmt program: msgfmt Invocation. (line 46)\n* qt-format flag: PO Files. (line 176)\n* qt-plural-format flag: PO Files. (line 180)\n* quotation marks: Header Entry. (line 160)\n* quotation marks <1>: po/Rules-*. (line 11)\n* quote characters, use in PO files: Header Entry. (line 160)\n* range: flag: PO Files. (line 271)\n* recode-sr-latin program: msgfilter Invocation.\n(line 101)\n* related reading: References. (line 6)\n* release: Release Management. (line 6)\n* RSJ: RST. (line 6)\n* RST: RST. (line 6)\n* Ruby: Ruby. (line 6)\n* ruby-format flag: PO Files. (line 152)\n* Scheme: Scheme. (line 6)\n* scheme-format flag: PO Files. (line 136)\n* scripting languages: Language Implementors.\n(line 6)\n* search messages in a catalog: msggrep Invocation. (line 8)\n* selecting message language: Locale Environment Variables.\n(line 6)\n* sentence end markers, xgettext: xgettext Invocation. (line 152)\n* sentences: Preparing Strings. (line 52)\n* setting up gettext at build time: Installers. (line 6)\n* setting up gettext at run time: Locale Environment Variables.\n(line 6)\n* several domains: Ambiguities. (line 6)\n* sex: Introduction. (line 15)\n* sh-format flag: PO Files. (line 156)\n* she, he, and they: Introduction. (line 15)\n* shell format string: envsubst Invocation. (line 8)\n* shell scripts: sh. (line 6)\n* Smalltalk: Smalltalk. (line 6)\n* smalltalk-format flag: PO Files. (line 172)\n* sorting msgcat output: msgcat Invocation. (line 156)\n* sorting msgmerge output: msgmerge Invocation. (line 195)\n* sorting msgunfmt output: msgunfmt Invocation. (line 147)\n* sorting output of xgettext: xgettext Invocation. (line 416)\n* specifying plural form in a PO file: Plural forms. (line 179)\n* standard output, and msgcat: msgcat Invocation. (line 48)\n* standard output, and msgmerge program: msgmerge Invocation. (line 53)\n* string concatenation: Preparing Strings. (line 131)\n* string normalization in entries: Normalizing. (line 6)\n* style: Preparing Strings. (line 29)\n* supported languages, msgfmt: msgfmt Invocation. (line 180)\n* supported languages, xgettext: xgettext Invocation. (line 54)\n* supported syntax checks, xgettext: xgettext Invocation. (line 116)\n* Tcl: Tcl. (line 6)\n* Tcl mode, and msgfmt program: msgfmt Invocation. (line 43)\n* Tcl mode, and msgunfmt program: msgunfmt Invocation. (line 26)\n* tcl-format flag: PO Files. (line 192)\n* template PO file: Overview. (line 67)\n* testing .po files for equivalence: xgettext Invocation. (line 426)\n* Tk's scripting language: Tcl. (line 6)\n* translated entries: Translated Entries. (line 6)\n* translating menu entries: Contexts. (line 6)\n* translation aspects: Aspects. (line 6)\n* Translation Matrix: Installing Localizations.\n(line 6)\n* Translation Project: Why. (line 17)\n* turning off NLS support: lib/gettext.h. (line 6)\n* tutorial of gettext usage: Overview. (line 6)\n* unify duplicate translations: msguniq Invocation. (line 8)\n* untranslated entries: Untranslated Entries.\n(line 6)\n* update translations from a compendium: Using Compendia. (line 20)\n* upgrading to new versions of gettext: Prerequisites. (line 6)\n* version control for backup files, msgmerge: msgmerge Invocation.\n(line 67)\n* Windows: Working in a Windows console.\n(line 6)\n* wxWidgets library: wxWidgets. (line 6)\n* xargs, and output from msgexec: msgexec Invocation. (line 14)\n* xerror: Error Handling. (line 15)\n* xerror2: Error Handling. (line 38)\n* xgettext program, usage: xgettext Invocation. (line 6)\n* XML mode, and msgfmt program: msgfmt Invocation. (line 52)\n* xmodmap program, and typing quotation marks: Header Entry. (line 172)\n* YaST2 scripting language: YCP. (line 6)\n* YCP: YCP. (line 6)\n* ycp-format flag: PO Files. (line 217)\n\n", "subsections": [] } }, "flags": [], "examples": [], "see_also": [] }