Lines Matching refs:message
11 choose among the variants every time a message has to be printed. This is
14 really big with dozens of message sets.
16 A better solution is to keep the message sets for each language
21 message translation. The problem is that neither of the interfaces is
27 As mentioned above, the message catalog handling provides easy
28 extendability by using external data files which contain the message
31 of the message handling functions are
39 map a given key to the translated message
57 Associate every message to translate in the source code with a unique
58 identifier. To retrieve a message from a catalog file solely the
64 message catalogs is always the same.
66 Before a message can be translated the catalog file must be located.
76 * The message catalog files:: Format of the message catalog files.
77 * The gencat program:: How to generate message catalogs files which
113 The @code{catopen} function tries to locate the message data file named
129 The first problem is to find out where all the message catalogs are
188 message catalogs while still allowing different languages to be used.
202 First of all the user can specify a path in the message catalog name
230 it is a translation from a message catalog or it is the same as the
251 The set/message tuple does not name an existing element in the
252 message catalog.
257 problem if the original, untranslated message is printed. Either the
269 @deftypefun {char *} catgets (nl_catd @var{catalog_desc}, int @var{set}, int @var{message}, const c…
271 The function @code{catgets} has to be used to access the message catalog
276 The next two parameters, @var{set} and @var{message}, reflect the
277 internal organization of the message catalog files. This will be
281 message number must be consecutive. They can be arbitrarily chosen.
282 But each message (unless equal to another one) must have its own unique
283 pair of set and message numbers.
285 Since it is not guaranteed that the message catalog for the language
302 set/message number tuple must be unique the programmer must keep lists
315 associated with a message catalog which previously was opened by a call
324 @node The message catalog files
325 @subsection Format of the message catalog files
328 store the result in a message catalog file which can be read by the
329 @code{catopen} function is to write all the message text to the
331 file with entries which associate the set/message tuple with a specific
406 which gets associated with the currently selected set and the message
409 If the start of the line is a number the message number is obvious. It
410 is an error if the same message number already appeared for this set.
412 If the leading token was an identifier the message number gets
413 automatically assigned. The value is the current maximum message
415 already used for a message in this set. It is OK to reuse the
416 identifier for a message in another thread. How to use the symbolic
430 X/Open specification do not have this feature. An example for a message
453 message definition would have to be omitted and in this case the
454 message with the identifier @code{two} would lose its leading whitespace.
518 then @strong{merging} the resulting collection of message sets with a
520 with set/message number tuples matching any of the generated messages
537 Print a usage message listing all available options, then exit successfully.
567 Since the X/Open format of the message catalog files does not allow
580 message numbers.
617 has to write a complete message catalog file while s/he is writing the
623 E.g., for the example message file given in the last section we could
651 the name of the message set plus the name of the message or the special
653 access the translation with identifier @code{two} in the message set
656 The other names denote the names of the message sets. The special
657 string @code{Set} is used in the place of the message identifier.
667 Writing the function this way will allow to change the message number
689 Now we want to internationalize the message and therefore replace the
690 message with whatever the user wants.
715 message. To get the actual definitions which match the information in
716 the catalog file we have to create the message catalog source file and
727 Now we can start building the program (assume the message catalog source
745 @file{msgnrs.h} as well as the message catalog binary. The former is
755 Sun Microsystems tried to standardize a different approach to message
779 * Helper programs for gettext:: Programs to handle message catalogs
787 The paradigms underlying the @code{gettext} approach to message
793 * Translation with gettext:: What has to be done to translate a message.
805 @subsubsection What has to be done to translate a message?
815 be selected based on the original string. The message catalogs must
836 The @code{gettext} function searches the currently selected message
846 Please note that above we wrote ``message catalogs'' (plural). This is
848 say more about this when we talk about the ways message catalogs are
862 called) we would get a wrong message.
864 So there is no easy way to detect a missing message catalog besides
867 when a message catalog is really necessary since for a user who speaks
868 the language the program was developed in, the message does not need any translation.
871 The remaining two functions to access the message catalog add some
872 functionality to select a message catalog which is not the default one.
874 Every part can have its own message catalog and all of them can be used
877 currently selected default message catalog it must specify all ambiguous
886 which guides the selection of the message catalogs which are searched
995 piece of information needed to localize the message catalog. I.e., the
996 domain name and the locale category exactly specify which message
1034 as long as no new message catalog is loaded the translation of a message
1042 The functions to retrieve the translations for a given message have a
1055 Locate the set of message catalogs. There are a number of files for
1085 that a message catalog matching this exactly is not available. But
1088 later message catalog should not be used. (We call this @dfn{message
1094 simply not translate any message. Instead a user might be better able
1162 which contains the message catalogs for domain @var{domainname} for the
1260 value in case no message catalog is found (similar to the normal
1278 as it finds the message catalogs in the same way. But it takes two
1283 message catalog is found @var{msgid1} is returned if @code{n == 1},
1302 way the message catalog is selected. The difference is that it takes
1312 way the message catalog is selected. The difference is that it takes
1544 @code{gettext} not only looks up a translation in a message catalog, it
1547 than the translator who created the message catalog, because it avoids
1548 distributing variants of message catalogs which differ only in the
1570 output character set for message catalogs for domain @var{domainname}.
1711 character not often used in message strings.
1713 But what if the character is used in message strings. Or if the chose
1731 the user to select the message s/he wants to see. S/He must understand
1742 message catalog. It is composed as follows:
1758 message catalogs are system independent, so all systems can use the same
1760 the message domain that is currently handled, the @code{dir_name}
1831 @code{LC_MESSAGES} locale (for looking up the message catalog) and
1835 the message catalogs for the domain @code{test-package} can be found
1920 mentioned the character set as a factor in the selection of the message
1925 message catalogs there are files for the same language but coded using
1930 @subsection Programs to handle message catalogs for @code{gettext}
1933 handle message catalogs for the @code{gettext} functions. As part of
1941 -editable form of the message catalog a binary file which can be used by
1956 is possible to @emph{completely} automate the handling of message