wrong translation text direction

[norberto]

LIBDBUSMENU-GLIB-WARNING **: Translation has an invalid value 'I-->D' for default text direction. Defaulting to left-to-right.
Running global cleanup code from study base classes.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: apport 1.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportLog:

ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Mon Feb 20 15:23:10 2012
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to precise on 2012-02-16 (4 days ago)

[Roman Yepishev (rye)]

Reproducible with ES_es locale.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Gabor Kelemen (kelemeng)]

This is a translation error, made here:
https://translations.launchpad.net/ubuntu/precise/+source/libdbusmenu/+pots/libdbusmenu/es/+translate?batch=10&show=all&search=ltr

[Adolfo Jayme Barrientos (fitojb)]

Correction made.

[Juan Simón (simonbcn)]

Same problem on Ubuntu 13.04 upgraded from 12.10.

[Adolfo Jayme Barrientos (fitojb)]

I committed the fix again...

[Juan Simón (simonbcn)]

Fix released? My Ubuntu 13.04 hasn't received this update. The error remains.

[Ivan Baldo (ibaldo)]

I still see the error, is a bit distracting when using the console, which happens a lot when I develop software for example....

[Juan Simón (simonbcn)]

¿Cuales son los paquetes afectados por este error? ¿Qué versión o versiones corrigen este error? Hace casi 2 meses que supuestamente se liberó la corrección y a mi me sigue mostrando el error.

[Adolfo Jayme Barrientos (fitojb)]

Espero que sepan disculparme por la confusión que he creado al no cambiar el estado a "Fix Committed" anteriormente... :/

[faustus69 (aclbros14)]

Hi, this bug still exists in raring.

Is there a workaround until it's fixed?

Gracias!

[Adolfo Jayme Barrientos (fitojb)]

There will be no more language packs for raring, but the fixed translation is available in saucy and up. Anyway, this is a harmless bug, it just causes that warning to show up on terminal but that's it...