Some errors in text strings

[Tommy Pettersson]

Hello,

I'm the Swedish translator of binutils.po.  When I updated the
Swedish po file, I found some things worth reporting.  (Line
numbers are from a fresh cvs checkout, files in src/binutils/.)


strings.c:657:  -t --radix={o,x,d}        Print the location of the string in 
base 8, 10 or 16\n\
        The flag arguments are listed in order o,x,d (same
        as on line 36), but the explanation lists the
        corresponding bases in wrong order: 8, 10, 16.


There are some messages of the form "<filename>: something
bad happened at line <lineno>".  I would prefer the form
"<filename>:<lineno> something bad happened", or "something bad
happened in file <filename>:<lineno>".  Ok, this might call
for a really good motivation.  I don't have one.  It's just
that my text editor recognizes filename:lineno in any output,
and it's very handy for quickly jumping to that file and line.
I just thought I'd give it a try.  Here are the lines:
        objcopy.c:703:      non_fatal (_("Ignoring rubbish found on line %d of 
%s"),
        objcopy.c:1071: fatal (_("%s: garbage at end of line %d"), filename, 
lineno);
        objcopy.c:1074: fatal (_("%s: missing new symbol name at line %d"), 
filename, lineno);
        objcopy.c:1084:    fatal (_("%s: premature end of file at line %d"), 
filename, lineno);


srconv.c:1859:  -q --quick       (Obsolete - ignoerd)\n\
        ignoERd is a typo.  (This was discovered by Jan D of
        the Swedish translation team.)


windres.c:623:  fatal (_("can not determine type of file `%s'; use the -I 
option"),
        This leads to: "Option -I is deprecated for setting
        the input format, please use -J instead."  Might want
        to suggest -J right away.  :-)


-- 
Tommy Pettersson <address@hidden>