12:31 a.m.
This is a multi-part message in MIME format.
--------------010601010100070903030301
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hello,
Sorry to bother you again.
I have one more question.
*
File:***AppErrors*
**Resource ID:* start with"VAR__VM_STATUS_"*
**Strings:***start with "$vmStatus"
*Question: *I would like to check to see if those VM statues should be
translated. In the previous releases, we were advised that the statuses
included in the listhere
<https://gerrit.eng.lab.tlv.redhat.com/gitweb?p=ovirt-engine.git;a=blob_pl...
were untranslated (and these were not pushed to translation). The new
strings starting with "$vmStatus" seem to be mostly the same list, but
maybe for a different usage? (thus should be translated?)
Kind regards,
Yuko
--------------010601010100070903030301
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
Sorry to bother you again. <br>
I have one more question.<br>
<b><br>
File:</b><b> </b>AppErrors<b><br>
</b><b>Resource ID:</b>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
start with"VAR__VM_STATUS_"<b><br>
</b><b>Strings:</b><b> </b>start with
"$vmStatus"<br>
<b>Question: </b>I would like to check to see if those VM statues
should be translated. In the previous releases, we were advised that
the statuses included in the list<a
href="https://gerrit.eng.lab.tlv.redhat.com/gitweb?p=ovirt-engine.gi...
here</a> were untranslated (and these were not pushed to
translation). The new strings starting with "$vmStatus" seem to be
mostly the same list, but maybe for a different usage? (thus should
be translated?)<br>
<br>
Kind regards,<br>
<br>
Yuko<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</body>
</html>
--------------010601010100070903030301--
2:23 a.m.
New subject: [Engine-devel] [oVirt 3.4 Localization Question #4] "$vmStatus"
----- Original Message -----
From: "Yuko Katabami" <ykatabam(a)redhat.com>
To: engine-devel(a)ovirt.org
Sent: Thursday, February 13, 2014 6:31:59 AM
Subject: [Engine-devel] [oVirt 3.4 Localization Question #4] "$vmStatus"
Hello,
Sorry to bother you again.
I have one more question.
File: AppErrors
Resource ID: start with"VAR__VM_STATUS_"
Strings: start with "$vmStatus"
Question: I would like to check to see if those VM statues should be
translated. In the previous releases, we were advised that the statuses
included in the list here were untranslated (and these were not pushed to
translation). The new strings starting with "$vmStatus" seem to be mostly
the same list, but maybe for a different usage? (thus should be translated?)
There was a request (https://bugzilla.redhat.com/show_bug.cgi?id=1000068) to change the
message "Cannot run VM. The VM status is illegal" to "Cannot run VM because
it is in ${status} status."
while the ${status} part is the localized name of the status of the VM (e.g. the
VAR__VM_STATUS_*).
So this statuses should be localized.
Tomas
Kind regards,
Yuko
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
4:29 a.m.
New subject: [Engine-devel] [oVirt 3.4 Localization Question #4] "$vmStatus"
This is a multi-part message in MIME format.
--------------010405060703070706070900
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
On 02/13/2014 05:23 PM, Tomas Jelinek wrote:
----- Original Message -----
> From: "Yuko Katabami" <ykatabam(a)redhat.com>
> To: engine-devel(a)ovirt.org
> Sent: Thursday, February 13, 2014 6:31:59 AM
> Subject: [Engine-devel] [oVirt 3.4 Localization Question #4] "$vmStatus"
>
> Hello,
>
> Sorry to bother you again.
> I have one more question.
>
> File: AppErrors
> Resource ID: start with"VAR__VM_STATUS_"
> Strings: start with "$vmStatus"
> Question: I would like to check to see if those VM statues should be
> translated. In the previous releases, we were advised that the statuses
> included in the list here were untranslated (and these were not pushed to
> translation). The new strings starting with "$vmStatus" seem to be mostly
> the same list, but maybe for a different usage? (thus should be translated?)
>
There was a request (https://bugzilla.redhat.com/show_bug.cgi?id=1000068) to change the
message "Cannot run VM. The VM status is illegal" to "Cannot run VM
because it is in ${status} status."
while the ${status} part is the localized name of the status of the VM (e.g. the
VAR__VM_STATUS_*).
So this statuses should be localized.
Hi Tomas,
Thank you again for your help.
I will share this with other translators.
Kind regards,
Yuko
Tomas
> Kind regards,
>
> Yuko
>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
-
--------------010405060703070706070900
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 02/13/2014 05:23 PM, Tomas Jelinek
wrote:<br>
</div>
<blockquote
cite="mid:1210168834.2345149.1392276216768.JavaMail.zimbra@redhat.com"
type="cite">
<pre wrap="">
----- Original Message -----
</pre>
<blockquote type="cite">
<pre wrap="">From: "Yuko Katabami" <a
class="moz-txt-link-rfc2396E"
href="mailto:ykatabam@redhat.com"><ykatabam@redhat.com></a>
To: <a class="moz-txt-link-abbreviated"
href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a>
Sent: Thursday, February 13, 2014 6:31:59 AM
Subject: [Engine-devel] [oVirt 3.4 Localization Question #4] "$vmStatus"
Hello,
Sorry to bother you again.
I have one more question.
File: AppErrors
Resource ID: start with"VAR__VM_STATUS_"
Strings: start with "$vmStatus"
Question: I would like to check to see if those VM statues should be
translated. In the previous releases, we were advised that the statuses
included in the list here were untranslated (and these were not pushed to
translation). The new strings starting with "$vmStatus" seem to be mostly
the same list, but maybe for a different usage? (thus should be translated?)
</pre>
</blockquote>
<pre wrap="">
There was a request (<a class="moz-txt-link-freetext"
href="https://bugzilla.redhat.com/show_bug.cgi?id=1000068">h...>)
to change the
message "Cannot run VM. The VM status is illegal" to "Cannot run VM because
it is in ${status} status."
while the ${status} part is the localized name of the status of the VM (e.g. the
VAR__VM_STATUS_*).
So this statuses should be localized.</pre>
</blockquote>
Hi Tomas,<br>
Thank you again for your help. <br>
I will share this with other translators.<br>
<br>
Kind regards,<br>
<br>
Yuko<br>
<blockquote
cite="mid:1210168834.2345149.1392276216768.JavaMail.zimbra@redhat.com"
type="cite">
<pre wrap="">
Tomas
</pre>
<blockquote type="cite">
<pre wrap="">Kind regards,
Yuko
_______________________________________________
Engine-devel mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/engine-devel">...
</pre>
</blockquote>
</blockquote>
<br>
<div class="moz-signature">-<font color="#000000"
face="arial,
sans-serif" size="2"></font>
</div>
</body>
</html>
--------------010405060703070706070900--
3966
days inactive
3966
days old
2 comments
2 participants
participants (2)
-
Tomas Jelinek -
Yuko Katabami