Eric Blake <[EMAIL PROTECTED]> wrote: > 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 <...>.
Good to know, in case we ever go back. > 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. Converting coreutils' 100+ programs is a good start, and the untranslated URL (without LANG_CODE) should be useful. So I'm going ahead. >> + /* 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? I did that at first, but chose to make it so the default URL will be usable, while we wait for translations to catch up. _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils