Keyword argument should be used in translation strings

Bug #1422106 reported by Erkin Alp Güney
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Translations
New
Undecided
Unassigned
command-not-found
New
Undecided
Unassigned
command-not-found (Ubuntu)
New
Undecided
Unassigned

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.

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for reporting this issue.

This should be possible to fix in the Ubuntu translations:
https://translations.launchpad.net/ubuntu/vivid/+source/command-not-found/+pots/command-not-found/tr/+translate
or the upstream ones:
https://translations.launchpad.net/command-not-found/trunk/+pots/command-not-found/tr/+translate

It looks like they are connected though, so hopefully a fix in one place should apply in the other as well (though please double-check).

Revision history for this message
Erkin Alp Güney (erkinalp9035) wrote : Re: [Bug 1422106] Re: Keyword argument should be used in translation strings

I cannot. It keeps me from saving my translation due to missing argument.
Original needs to be keyword argument, too, in order to be able to use
keyword argument.

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

>It keeps me from saving my translation due to missing argument.

Hm, I'm not sure why that would happen. I suppose the arguments might refer to the %s placeholders where the name of the package etc. will be inserted.

I don't speak Turkish, but could you add your suggestion in a comment here, and I'll take a look if there's anything which would explain why it doesn't work. (This would be the string in question, right https://translations.launchpad.net/ubuntu/vivid/+source/command-not-found/+pots/command-not-found/tr/3/+translate?)

Revision history for this message
Erkin Alp Güney (erkinalp9035) wrote :

21 Tem 2015 12:25 tarihinde "Hans Joachim Desserud" <
<email address hidden>> yazdı:
>
> >It keeps me from saving my translation due to missing argument.
>
> I don't speak Turkish, but could you add your suggestion in a comment
> here, and I'll take a look if there's anything which would explain why
> it doesn't work.
> --
>

Original text:
'Command "{command}" from "{package}"'
In Turkish:
'"{package}" paketinden "{command}" komutu'

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

I'm not quite sure I follow...

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.

Or.. are you saying you need more control over the arguments in order to rearrange them, because the current order won't make sense in your language?

Revision history for this message
Erkin Alp Güney (erkinalp9035) wrote :

> 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.
> Or.. are you saying you need more control over the arguments in order to
> rearrange them, because the current order won't make sense in your
> language?
>
> --

This. ^

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

>> 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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.