mirror/gcc
2
0
Fork 0
mirror of git://gcc.gnu.org/git/gcc.git synced 2024-12-13 00:20:55 +08:00
Code Issues Packages Projects Releases Wiki Activity

ABOUT-GCC-NLS: add usage guidance

Browse Source 
gcc/ChangeLog:

	* ABOUT-GCC-NLS: Add usage guidance.
This commit is contained in:
Jason Merrill 2023-10-19 11:07:18 -04:00
parent 1ec36bcda3
commit 00e7c49fa0
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
gcc/ABOUT-GCC-NLS
View File

@ -23,6 +23,22 @@ For example, GCC source code should not contain calls like `error
("unterminated comment")' instead, as it is the `error' function's
responsibility to translate the message before the user sees it.
In general, use no markup for strings that are the immediate format string
argument of a diagnostic function. Use G_("str") for strings that will be
used as the format string for a diagnostic but are e.g. assigned to a
variable first. Use N_("str") for strings that are not diagnostic format
strings, but will still be translated later. Use _("str") for strings that
will not be translated elsewhere. It's important not to use _("str") in
the initializer of a statically allocated variable; use one of the others
instead and make sure that uses of that variable translate the string,
whether directly with _(msg) or by passing it to a diagnostic or other
function that performs the translation.
Avoid using %s to compose a diagnostic message from multiple translatable
strings; instead, write out the full diagnostic message for each variant.
Only use %s for message components that do not need translation, such as
keywords.
By convention, any function parameter in the GCC sources whose name
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