>> 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.
>> The original string is: multiverse, respectively. So presumably the
>> Command '%s' from package '%s' (%s)
>> And the three %s will be replaced by the appropriate command name,
package name and main/universe/
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.