ubuntu-translations-coordinators team mailing list archive

[Gabor Kelemen <kelemeng@xxxxxxxx>]

This string is not in Gwibber anymore.

** Changed in: ubuntu-translations
       Status: Triaged => Invalid

** Changed in: gwibber (Ubuntu)
       Status: Triaged => Invalid

** Changed in: gwibber
       Status: Confirmed => Invalid

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

Title:
  "{0} ({1}) - Disabled" string needs a translator comment

Status in Gwibber:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in “gwibber” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gwibber

  Currently the "{0} ({1}) - Disabled" string at e.g.
  https://translations.launchpad.net/ubuntu/lucid/+source/gwibber/+pots/gwibber/ca/+translate?batch=10&show=all&search=disabled
  has no translator comment and translators must resort to going to the
  source code or asking someone else to find out what {0} and {1} mean
  to properly translate the message or reorder the arguments.

  This is not in the usual translation workflow, since most translators
  are not familiar with coding.

  It would be good to have a translator comment to indicate what the
  string means, an explanation of what each argument is, or use Python
  named arguments.

  Usually in plain Python adding a translator comment is just a matter
  of writing a comment on the line immediately preceeding the string
  marked for translation in the code, I'm not sure how this is handled
  in mako templates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/567123/+subscriptions