bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug 294348] Re: ubuntu directing users to coreutils mailing list fo


From: Eric Blake
Subject: Re: [Bug 294348] Re: ubuntu directing users to coreutils mailing list for general problems
Date: Sun, 09 Nov 2008 13:56:49 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080914 Thunderbird/2.0.0.17 Mnenhy/0.7.5.666

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Jim Meyering on 11/9/2008 9:09 AM:
>>> -  printf (_("\nReport bugs to <%s>.\n"), PACKAGE_BUGREPORT);
>>> +  printf (_("\nReport %s bugs to <%s>.\n"), last_component (program_name),
>>> +     PACKAGE_BUGREPORT);
>> And where would the second line's %s be filled in from?  You would need to
>> add another last_component call as an additional printf argument before
>> you could suggest that.

I stand corrected; with $1 notation, you can reuse a printf argument in
more than one % specifier.  So we could possibly suggest:

Report %$1s bugs to <%$2s>.
Report %$1s translation bugs to <...>.

>>
>> Doesn't it just suffice to have the text read:
>>
>> Report ls bugs to <address@hidden>.
>> Report translation bugs to <...>.
> 
> Good catch.
> I started to write the first patch below,
> but then saw that very few translators have heeded the instructions.

Indeed; but that seems like a generic problem where the translation
project needs to do a better job of instructing all the teams, as it
affects more than just coreutils.

>     Print the "Report translation bugs to <...>." diagnostic
>     for all but the C/POSIX locale.
> 
> Though I'm not sure I want to print such a line in an English locale.
> In spite of that, I have a slight preference for this approach.
> Note: if I go that route, then I'll have to remove all other
> hard-locale.h inclusions to get past make syntax-check.
> 
> Opinions?

Making it a separate diagnostic would indeed make it more obvious that it
needs to be translated; but unless all projects adopt this approach, the
translated --help strings are not common between projects.  I could also
go either way on this.

> +  /* TRANSLATORS: Replace LANG_CODE in this URL with your language code
> +     <http://translationproject.org/team/LANG_CODE.html> to form one of
> +     the URLs at http://translationproject.org/team/.  Otherwise, replace
> +     the entire URL with your team's email address.  */
> +  if (hard_locale (LC_MESSAGES))
> +    fputs (_("Report translation bugs to "
> +          "<http://translationproject.org/team/>\n"), stdout);

Do you want LANG_CODE in the string and not just the comment, to make it
more obvious when the string has not been translated?

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkXTpAACgkQ84KuGfSFAYAFHACfWKzEoktxyzfiVnYdxWmLQtxq
YYIAnimT+3Vjsw+2X7hHw245ZHMlbVEO
=V2K1
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]