On 06/18/2014 03:53 PM, Martin Perina wrote:
----- Original Message -----
From: "Yuko Katabami" <[email protected]>
To: "Martin Perina" <[email protected]>
Cc: "Einav Cohen" <[email protected]>, "Dima Kuznetsov" <[email protected]>,
[email protected]
Sent: Wednesday, June 18, 2014 7:49:22 AM
Subject: Re: [ovirt-devel] [oVirt 3.5 Localization Question #1] "Permissive"
On 06/18/2014 03:39 PM, Martin Perina wrote:
----- Original Message -----
From: "Yuko Katabami" <[email protected]>
To: "Einav Cohen" <[email protected]>, "Martin Perina"
<[email protected]>, "Dima Kuznetsov" <[email protected]>
Cc: [email protected]
Sent: Wednesday, June 18, 2014 4:05:42 AM
Subject: Re: [ovirt-devel] [oVirt 3.5 Localization Question #1]
"Permissive"
On 06/18/2014 11:38 AM, Einav Cohen wrote:
----- Original Message -----
From: "Yuko Katabami" <[email protected]>
Sent: Tuesday, June 17, 2014 9:32:27 PM
In the same file, I found more statuses and they are for Kdump and
SElinux.
Could anyone please tell me if all of these should be translated or
should
be
left in English?
Kdump:
Unknown
Enabled
Disabled
adding Martin.
Hi,
kdump is the name of kexec based crash dumping mechansim for Linux [1],
so I wouldn't translate it. But kdump configuration statuses can be
translated easily.
Thanks
Martin
[1] http://lse.sourceforge.net/kdump/
Hi Martin,
Thank you very much for your reply and informaiton.
Yes, we will leave kdump itself untranslated as it is a proper noun.
With statuses, are these same as SELinux statuses -- the values in this
field map directly to what is shown on host's terminal?
(and if so, better to leave them English, so that users can recognize
them easily?)
Kind regards,
Yuko
No sure, that I understand, but those statuses are oVirt specific. Theys just
inform webadmin user about:
1) Enabled - kdump on host is configured and works fine
2) Disabled - kdump on is not configured properly
3) Unknown - VDSM didn't report anything about kdump config (probably
too old version of VDSM)
So personally I would translate them.
Martin
Hi Martin,
Thank you very much for your prompt reply. That's very clear and yes, we
should translate these.
I will share this with other translators.
Kind regards,
Yuko
SELinux:
Enforcing
Permissive
Disabled
as Dima mentioned in his previous e-mail: all values for the SELinux
field
map
directly to what is shown on host's terminal. Therefore, I would say that
these
values should be left in English.
Thanks Einav for your clarification.
I just realized that I did not subscribe the new mailing list properly
and did not receive the previous email. I just checked it in the archive.
@Dima, thank you very much for your reply. I share this with other
translators.
Yuko
On 06/18/2014 09:00 AM, Yuko Katabami wrote:
Hello all,
I am a Brisbane-based translator working on oVirt 3.5 localization
project
along with 5 other translators, each specialized in a different locale.
Our localization cycle is just kicked off and I would like to post our
questions to this mailing list, just as I did for 3.4.
It would be greatly appreciated if you could help us by answering
questions,
so that we can ensure accuracy of our translations, based on the
context.
Here is our first question.
File: LocalizedEnums
Resource ID: SELinuxMode___PERMISSIVE
Strings: Permissive
Question: Could someone explain to us how this appears in the Admin
Portal?
(we currently do not have a demo environment and cannot check it on the
screen). Translators usually leave SELinux modes untranslated as they
appear
in the command line in English, however this string starts with the
uppercase letter "P". We just wonder if this is used as descriptive or
it
refers exactly the "permissive" mode as shown in the terminal.
Kind regards,
Yuko Katabami
_______________________________________________
Devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/devel
