'Access Denied' message should be translatable
Bug #612608 reported by
Christophe CHAUVET
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) | Status tracked in Trunk | |||||
5.0 |
Invalid
|
Medium
|
Unassigned | |||
Trunk |
Invalid
|
Low
|
OpenERP's Framework R&D |
Bug Description
OpenObject: 5.0
Server revno: 2085
Addons revno: 2790
Client revno: 1085
Web revno: 2887
I use intensive rules for a project, and often i see this message "// Access Denied //" and it's normal ;)
But i can't translate it because there's missing _(....)
See the relate branch to correct this issue
Distribution: Ubuntu
Version: 9.10 (karmic)
Python 2.6.4
Locale:
LANG=fr_FR.UTF-8
Related branches
lp:~christophe-chauvet/openobject-server/5.0-access_denied-translatable
Rejected
for merging
into
lp:openobject-server/5.0
- Olivier Dony (Odoo): Disapprove
-
Diff: 12 lines (+1/-1)1 file modifiedbin/osv/fields.py (+1/-1)
lp:~christophe-chauvet/openobject-server/trunk-access_denied-translatable
Rejected
for merging
into
lp:openobject-server
- Olivier Dony (Odoo): Disapprove
-
Diff: 12 lines (+1/-1)1 file modifiedbin/osv/fields.py (+1/-1)
Changed in openobject-server: | |
assignee: | nobody → Christophe Chauvet - http://www.syleam.fr/ (christophe-chauvet) |
Changed in openobject-server: | |
assignee: | Christophe Chauvet - http://www.syleam.fr/ (christophe-chauvet) → nobody |
status: | Confirmed → In Progress |
To post a comment you must log in.
On Tuesday 03 August 2010, you wrote: server/ 5.0 server/ 5.0 server/ 5.0 server/ 5.0
> ** Also affects: openobject-
> Importance: Undecided
> Status: New
>
> ** Changed in: openobject-
> Status: New => In Progress
>
> ** Changed in: openobject-
> Importance: Undecided => Medium
>
> ** Changed in: openobject-
> Milestone: None => 5.0.13
Please, such changes should NOT be done against 5.0. Anything that alters the
behaviour, is not for the stable branch. String changes, too. Consider also
that no new translations should be done against 5.0, and that a localized
message (such as this one) /may/ trigger utf8 bugs.
My vote: Invalid for 5.0