58 whether the identifier will be extracted into MSG_{INTL,ORIG}_FROM_ORIG
59 or not. If the identifyer are surrounded by _CHKMSG_SKIP_BEGIN_
60 {sparc,i386} and _CHKMSG_SKIP_END_ {sparc,i386}, then the identifiers
61 will not be included in the output set. The architecture being checked
62 should be specified after the key works. These key words should be
63 specified in the comment lines. For example, the input file could
64 contain:
65 # _CHKMSG_SKIP_BEGIN_ sparc
66 @ MSG_ERROR_01 "This identifier is not defined."
67 # _CHKMSG_SKIP_END_ sparc
68
69 It is assumed that the message identifier names are composed of only
70 upper letters.
71
72 OPTIONS
73 -64 Use a 64-bit version of the machine type (i.e. sparc =>
74 sparcv9). Note that this option must be specified first on
75 the command line.
76
77 SEE ALSO
78 gencat(1), ld(1), msgfmt(1), catgets(3C), gettext(3I). sgsmsg(1l).
79
80
81
82 5 Apr 1997 chkmsg(1l)
|
58 whether the identifier will be extracted into MSG_{INTL,ORIG}_FROM_ORIG
59 or not. If the identifyer are surrounded by _CHKMSG_SKIP_BEGIN_
60 {sparc,i386} and _CHKMSG_SKIP_END_ {sparc,i386}, then the identifiers
61 will not be included in the output set. The architecture being checked
62 should be specified after the key works. These key words should be
63 specified in the comment lines. For example, the input file could
64 contain:
65 # _CHKMSG_SKIP_BEGIN_ sparc
66 @ MSG_ERROR_01 "This identifier is not defined."
67 # _CHKMSG_SKIP_END_ sparc
68
69 It is assumed that the message identifier names are composed of only
70 upper letters.
71
72 OPTIONS
73 -64 Use a 64-bit version of the machine type (i.e. sparc =>
74 sparcv9). Note that this option must be specified first on
75 the command line.
76
77 SEE ALSO
78 gencat(1), ld(1), msgfmt(1), catgets(3C), gettext(3C). sgsmsg(1ONBLD).
79
80
81
82 April 5, 1997 chkmsg(1l)
|