Hello again :)
As I have requested before, please encourage GNU developers to fill
in the Report-Msgid-Bugs-To header , so we translator do have an
accurate contact address for reports like these.
I have noticed that more GNU PO files do have this header filled
in, so we're heading in the right direction. Slowly. ;)
About the ld-2.17.90 PO file:
1. There are some duplicate strings, varying only in whitespace.
You may want to reduce these: they can also result in varying
translations (I only noticed them because I was reviewing the whole
msgid " --support-old-code Support interworking with old code\n"
msgid " --support-old-code Support interworking
with old code\n"
msgid " --thumb-entry=<sym> Set the entry point to be Thumb
msgid " --thumb-entry=<symbol> Set the entry point to
be Thumb <symbol>\n"
msgid "Errors encountered processing file %s"
msgid "Errors encountered processing file %s\n"
(There is a line-break difference between these two strings, so I'm
unsure if they both have utility, or not. With two sets duplicate
strings, it seemed worth mentioning this one as well.)
msgid "%F%S nonconstant expression for %s\n"
msgid "%F%S: nonconstant expression for %s\n"
(A colon is the only difference, which again might be useful, or not.)
msgid "%P: warning: connot find thumb start symbol %s\n"
msgid "built in linker script:%u
Should there be a space after the colon?
I don't know if you want to abbreviate these as much as possible,
or if you would prefer that they were correct English:
msgid "Specify target for following input files"
"Specific the target for the following input files"
Other strings where "the following" could be substituted for just
"Set DT_NEEDED tags for DT_NEEDED entries in\n"
"\t\t\t\tfollowing dynamic libs"
"Do not set DT_NEEDED tags for DT_NEEDED entries\n"
"\t\t\t\tin following dynamic libs"
msgid "Only set DT_NEEDED for following dynamic libs if used"
msgid "Always set DT_NEEDED for following dynamic libs"
I hope this is useful.
from Clytie (vi-VN, Vietnamese free-software translation team /
nhóm Việt hóa phần mềm tự do)
As the gettext documentation says:
This has already been filled in by `xgettext'.
The developer thus needs to pass the option --msgid-bugs-address=...
to xgettext. With recent gettext infrastructure this is a field in
po/Makevars that the developer fills in; the rest is automatic.
(in short for programmers: put a C-style
comment immediately _before_ the gettext (macro) invocation).
address@hidden set report address for msgid