| 2010-03-26 20:35:29 |
Ricardo Pérez López |
bug |
|
|
added bug |
| 2010-03-26 20:35:45 |
Ricardo Pérez López |
bug task added |
|
ubuntu-translations |
|
| 2010-03-26 20:46:10 |
Victor Vargas |
command-not-found (Ubuntu): importance |
Undecided |
Low |
|
| 2010-03-30 10:44:45 |
David Planella |
bug task added |
|
command-not-found |
|
| 2010-03-30 10:45:31 |
David Planella |
ubuntu-translations: status |
New |
Triaged |
|
| 2010-03-30 10:45:34 |
David Planella |
ubuntu-translations: importance |
Undecided |
Low |
|
| 2010-04-01 06:18:24 |
David Planella |
command-not-found: status |
New |
Invalid |
|
| 2010-04-01 06:18:58 |
David Planella |
summary |
Some strings shows untranslated, and can't be translated via Launchpad |
The command-not-found package needs to create a POT template on build |
|
| 2010-04-01 06:19:14 |
David Planella |
tags |
|
needs-pot-on-build |
|
| 2010-04-01 06:24:47 |
David Planella |
description |
Binary package hint: command-not-found
command-not-found shows some untranslated strings in my Spanish desktop, and can't be translated because these strings aren't in the Launchpad template.
Example:
ricardo@kadath:~$ xplane
No command 'xplane' found, did you mean:
Command 'xplanet' from package 'xplanet' (universe)
xplane: command not found
ricardo@kadath:~$ xplanet
El programa «xplanet» no está instalado actualmente. Puede instalarlo escribiendo:
sudo apt-get install xplanet
ricardo@kadath:~$
As you can see, some strings are translated into Spanish, but some others don't, and can't be translated because there aren't here:
https://translations.launchpad.net/ubuntu/lucid/+source/command-not-found/+pots/command-not-found/es/+translate |
Binary package hint: command-not-found
command-not-found needs to generate a POT template on build for its translatable messages to be exposed in Launchpad.
In this way, on every upload the template will be refreshed in Launchpad. Right now, the template is present in Launchpad, but it's outdated, making it impossible to translate e.g. the "No command '%s' found, did you mean:" message, because it's not in Launchpad.
This is because the package contains an outdated po/command-not-found.pot file, and that's the one that gets imported. An easy fix is to simply add the following to debian/rules, just below the './setup.py build' line in the build-stamp rule:
cd po; intltool-update -p -g command-not-found
In the meantime, I've manually uploaded an updated template in Launchpad, which should be available shortly
For more info on this:
* https://wiki.ubuntu.com/UbuntuDevelopment/Internationalisation/Packaging#Translation%20templates
* https://wiki.ubuntu.com/UbuntuDevelopment/Internationalisation/RecipeVerifyingTranslationUploads
|
|
| 2010-08-06 18:40:58 |
David Planella |
attachment added |
|
Generate command-not-found.pot on build http://launchpadlibrarian.net/53183784/c-n-f-pot-on-build.diff |
|
| 2010-08-06 22:58:46 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2010-08-06 22:58:53 |
Brian Murray |
tags |
needs-pot-on-build |
needs-pot-on-build patch |
|
| 2010-08-13 10:24:31 |
Michael Vogt |
command-not-found (Ubuntu): status |
New |
Fix Committed |
|
| 2010-08-13 10:25:34 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/command-not-found/ubuntu |
|
| 2010-08-13 10:30:10 |
Launchpad Janitor |
command-not-found (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2010-08-13 11:14:27 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/command-not-found |
|
| 2010-08-13 11:31:01 |
David Planella |
ubuntu-translations: status |
Triaged |
Fix Released |
|
| 2020-10-14 16:36:44 |
Noah Gorny |
branch unlinked |
lp:command-not-found |
|
|
