Bug 871393 - [es_ES]Under Events tab the column "Message" shows all messages in English
Summary: [es_ES]Under Events tab the column "Message" shows all messages in English
Keywords:
Status: CLOSED DUPLICATE of bug 870294
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.1.0
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Einav Cohen
QA Contact: Pavel Stehlik
URL:
Whiteboard: ux
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-30 11:30 UTC by A S Alam
Modified: 2013-07-03 01:11 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-27 04:25:36 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
The claimed content is in en_US, actually seems already fixed. (87.99 KB, image/png)
2012-11-09 10:35 UTC, Satyabrata Maitra 		no flags Details
View All

Comment 2 Satyabrata Maitra 2012-11-09 10:35:47 UTC 
Created attachment 641454 [details]
The claimed content is in en_US, actually seems already fixed.

I have tested this bug. But it seems the claimed content "Message" was showing in English, is actually now showing in Spanish - es_ES. So, I think, this bug is Fixed.
Version of the component tested :
Red Hat Enterprise Virtualization Manager-3.1.0-26.el6ev
Comment 3 Einav Cohen 2012-12-27 04:22:01 UTC 
(In reply to comment #2)
> Created attachment 641454 [details]
> The claimed content is in en_US, actually seems already fixed.
> 
> I have tested this bug. But it seems the claimed content "Message" was
> showing in English, is actually now showing in Spanish - es_ES. So, I think,
> this bug is Fixed.

The bug is not on the "Message" column title (which is indeed localized), but on the "Message" column *content* (i.e. actual messages), which is not localized.
Comment 4 Einav Cohen 2012-12-27 04:25:36 UTC 

*** This bug has been marked as a duplicate of bug 870294 ***
Note You need to log in before you can comment on or make changes to this bug.