Lines Matching +refs:po +refs:mark +refs:string +refs:function

32 searched relative to this list of directories.  The resulting @file{.po}
46 Use @file{@var{name}.po} for output (instead of @file{messages.po}).
52 Write output to specified file (instead of @file{@var{name}.po} or
53 @file{messages.po}).
173 checks for a certain string, you can mark it with an @code{xgettext:}
176 a particular string, add the following comment:
189 than the whole string.  xgettext detects the end of sentence by
233 for strings in the first argument of each call to the function or macro
246 @var{argnum}th argument as a string with context, using the GNOME @code{glib}
252 @var{totalnumargs}.  This is useful for disambiguating overloaded function
358 argument of the function @var{word}.  The possible flags are the possible
359 format string indicators, such as @samp{c-format}, and their negations,
362 @cindex function attribute, __format__
363 The meaning of @code{--flag=@var{function}:@var{arg}:@var{lang}-format}
364 is that in language @var{lang}, the specified @var{function} expects as
365 @var{arg}th argument a format string.  (For those of you familiar with
366 GCC function attributes, @code{--flag=@var{function}:@var{arg}:c-format} is
369 to @var{function} in a C source file.)
370 For example, if you use the @samp{error} function from GNU libc, you can
372 this specification is that @code{xgettext} will mark as format strings all
374 @var{function}.
375 This is useful when such strings contain no format string directives:
377 translators cannot accidentally use format string directives that would
380 @cindex function attribute, __format_arg__
381 The meaning of @code{--flag=@var{function}:@var{arg}:pass-@var{lang}-format}
382 is that in language @var{lang}, if the @var{function} call occurs in a
383 position that must yield a format string, then its @var{arg}th argument
384 must yield a format string of the same type as well.  (If you know GCC
385 function attributes, the @code{--flag=@var{function}:@var{arg}:pass-c-format}
387 @samp{__attribute__ ((__format_arg__ (@var{arg})))} attached to @var{function}
389 For example, if you use the @samp{_} shortcut for the @code{gettext} function,
391 specification is that @code{xgettext} will propagate a format string
392 requirement for a @code{_("string")} call to its first argument, the literal
393 @code{"string"}, and thus mark it as a format string.
394 This is useful when such strings contain no format string directives:
396 translators cannot accidentally use format string directives that would
437 responsible for marking a message as a format string.  The latter form is
466 @item --force-po
467 @opindex --force-po@r{, @code{xgettext} option}
474 Write the .po file using indented style.
553 @cindex testing @file{.po} files for equivalence
562 @item --copyright-holder=@var{string}
564 Set the copyright holder in the output.  @var{string} should be the
569 distribute them without legal risk.  If @var{string} is empty, the output
574 The default value for @var{string} is the Free Software Foundation, Inc.,
616 @item -m[@var{string}]
617 @itemx --msgstr-prefix[=@var{string}]
620 Use @var{string} (or "" if not specified) as prefix for msgstr values.
622 @item -M[@var{string}]
623 @itemx --msgstr-suffix[=@var{string}]
626 Use @var{string} (or "" if not specified) as suffix for msgstr values.