Fwd: Duplicate strings in the ld-2.17.90 PO file

[Clytie Siddall]

It turns out that the binutils mailing list is the contact address for this package, as well. So here's another well-travelled email.

Begin forwarded message:

Hello again :)





About the ld-2.17.90 PO file:
___



(a)
#: emultempl/armcoff.em:72
#, c-format
msgid "  --support-old-code   Support interworking with old code\n"

#: emultempl/pe.em:325
#, c-format


(b)
#: emultempl/armcoff.em:73
#, c-format


#: emultempl/pe.em:326
#, c-format


(c)
#: emultempl/armcoff.em:121
#, c-format
msgid "Errors encountered processing file %s"

#: emultempl/pe.em:1334
#, c-format
msgid "Errors encountered processing file %s\n"



(d)
#: ldexp.c:1054
#: ldexp.c:1079
#, c-format
msgid "%F%S nonconstant expression for %s\n"

#: ldexp.c:1138
#, c-format
msgid "%F%S: nonconstant expression for %s\n"

(A colon is the only difference, which again might be useful, or not.)



2.
#: emultempl/armcoff.em:194
#: emultempl/pe.em:1533
msgid "%P: warning: connot find thumb start symbol %s\n"

- connot
+ cannot


3.
#: ldmisc.c:245
#, c-format
msgid "built in linker script:%u

Should there be a space after the colon?


4.


(a)
#: lexsup.c:210
msgid "Specify target for following input files"

"Specific the target for the following input files"



#: lexsup.c:329
msgid ""
"Set DT_NEEDED tags for DT_NEEDED entries in\n"
"\t\t\t\tfollowing dynamic libs"

#: lexsup.c:332
msgid ""
"Do not set DT_NEEDED tags for DT_NEEDED entries\n"
"\t\t\t\tin following dynamic libs"

#: lexsup.c:335
msgid "Only set DT_NEEDED for following dynamic libs if used"

#: lexsup.c:338
msgid "Always set DT_NEEDED for following dynamic libs"


I hope this is useful.


http://groups-beta.google.com/group/vi-VN

[1]
As the gettext documentation says:

   Report-Msgid-Bugs-To
     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).
___

As I have requested before, please encourage GNU developers to fill in the Report-Msgid-Bugs-To header [1], 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. ;) 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 file). msgid " --support-old-code Support interworking with old code\n" msgid " --thumb-entry=<sym> Set the entry point to be Thumb symbol <sym>\n" msgid " --thumb-entry=<symbol> Set the entry point to be Thumb <symbol>\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.) I don't know if you want to abbreviate these as much as possible, or if you would prefer that they were correct English: Other strings where "the following" could be substituted for just "following": from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) [EMAIL PROTECTED] set report address for msgid bugs\n

PGP.sig
Description: This is a digitally signed message part

_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils