OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [gnu-old/] [gcc-4.2.2/] [gcc/] [ABOUT-GCC-NLS] - Diff between revs 154 and 816

Go to most recent revision | Only display areas with differences | Details | Blame | View Log

Rev 154 Rev 816
Notes on GCC's Native Language Support
Notes on GCC's Native Language Support
By and large, only diagnostic messages have been internationalized.
By and large, only diagnostic messages have been internationalized.
Some work remains in other areas; for example, GCC does not yet allow
Some work remains in other areas; for example, GCC does not yet allow
non-ASCII letters in identifiers.
non-ASCII letters in identifiers.
Not all of GCC's diagnostic messages have been internationalized. Programs
Not all of GCC's diagnostic messages have been internationalized. Programs
like `genattr' (in fact all gen* programs) are not internationalized, as
like `genattr' (in fact all gen* programs) are not internationalized, as
their users are GCC maintainers who typically need to be able to read
their users are GCC maintainers who typically need to be able to read
English anyway; internationalizing them would thus entail needless work for
English anyway; internationalizing them would thus entail needless work for
the human translators. Messages used for debugging, such as used in dumped
the human translators. Messages used for debugging, such as used in dumped
tables, should also not be translated.
tables, should also not be translated.
The GCC library should not contain any messages that need
The GCC library should not contain any messages that need
internationalization, because it operates below the internationalization
internationalization, because it operates below the internationalization
library.
library.
Unlike some other GNU programs, the GCC sources contain few instances
Unlike some other GNU programs, the GCC sources contain few instances
of explicit translation calls like _("string").  Instead, the
of explicit translation calls like _("string").  Instead, the
diagnostic printing routines automatically translate their arguments.
diagnostic printing routines automatically translate their arguments.
For example, GCC source code should not contain calls like `error
For example, GCC source code should not contain calls like `error
(_("unterminated comment"))'; it should contain calls like `error
(_("unterminated comment"))'; it should contain calls like `error
("unterminated comment")' instead, as it is the `error' function's
("unterminated comment")' instead, as it is the `error' function's
responsibility to translate the message before the user sees it.
responsibility to translate the message before the user sees it.
By convention, any function parameter in the GCC sources whose name
By convention, any function parameter in the GCC sources whose name
ends in `msgid' is expected to be a message requiring translation.
ends in `msgid' is expected to be a message requiring translation.
If the parameter name ends with `gmsgid', it is assumed to be a GCC
If the parameter name ends with `gmsgid', it is assumed to be a GCC
diagnostics format string requiring translation, if it ends with
diagnostics format string requiring translation, if it ends with
`cmsgid', it is assumed to be a format string for `printf' family
`cmsgid', it is assumed to be a format string for `printf' family
of functions, requiring a translation.
of functions, requiring a translation.
For example, the `error' function's first parameter is named `gmsgid'.
For example, the `error' function's first parameter is named `gmsgid'.
GCC's exgettext script uses this convention to determine which
GCC's exgettext script uses this convention to determine which
function parameter strings need to be translated.  The exgettext
function parameter strings need to be translated.  The exgettext
script also assumes that any occurrence of `%eMSGID}' on a source
script also assumes that any occurrence of `%eMSGID}' on a source
line, where MSGID does not contain `%' or `}', corresponds to a
line, where MSGID does not contain `%' or `}', corresponds to a
message MSGID that requires translation; this is needed to identify
message MSGID that requires translation; this is needed to identify
diagnostics in GCC spec strings.
diagnostics in GCC spec strings.
The `G_(GMSGID)' macro defined in intl.h can be used to mark GCC diagnostics
The `G_(GMSGID)' macro defined in intl.h can be used to mark GCC diagnostics
format strings as requiring translation, but other than that it is a
format strings as requiring translation, but other than that it is a
no-op at runtime.
no-op at runtime.
If you modify source files, you'll need at least version 0.14.15 of the
If you modify source files, you'll need at least version 0.14.15 of the
GNU gettext package to propagate the modifications to the translation
GNU gettext package to propagate the modifications to the translation
tables.
tables.
After having built and installed these gettext tools, you have to
After having built and installed these gettext tools, you have to
configure GCC with --enable-maintainer-mode to get the master catalog
configure GCC with --enable-maintainer-mode to get the master catalog
rebuilt.
rebuilt.
 
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.