ubuntu-translations-coordinators team mailing list archive

[Hans Joachim Desserud <1422106@xxxxxxxxxxxxxxxxxx>]

>> The original string is:
>> Command '%s' from package '%s' (%s)
>> And the three %s will be replaced by the appropriate command name,
package name and main/universe/multiverse, respectively. So presumably the
error message about missing argument comes when if a translator leave any
of these out.

>No, component names are untranslatable and should stay that way.

I may have been to quick here. Allow me to rephrase; they will be
replaced when the program is running, and it displays whichever
suggestions are relevant. The inserted content should of course not be
translated, but the translated string will need the same amount of
placeholders as the original.

In any case, it looks like a proper fix here would require named in the
translation template, which I guess will need to be addressed upstream.
I've marked the upstream project as also affected.

** Also affects: command-not-found
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1422106

Title:
  Keyword argument should be used in translation strings

Status in command-not-found:
  New
Status in Ubuntu Translations:
  New
Status in command-not-found package in Ubuntu:
  New

Bug description:
  Command-not-found gives such a result in Turkish: 
  'kar' paketinden 'sra-toolkit' komutu (universe)
   'ken' paketinden 'filters' komutu (universe)
   'key' paketinden 'donkey' komutu (universe)
  Package and command needs to be swapped in Turkish translation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/command-not-found/+bug/1422106/+subscriptions