networkOperationMessage is built dynamically in the run-time (e.g. "Attach
<NetworkName> to <InterfaceName>"). The final message depends on
operation type and its argument(s) (1 or 2).
The possible networkOperationMessage does not include '.' (dot sign) at the end so
that was added in order to separate the warning from the operation description.
Regards,
Yevgeny
----- Original Message -----
From: "Dan Kenigsberg" <danken(a)redhat.com>
To: yzaspits(a)redhat.com
Cc: lvernia(a)redhat.com
Sent: Friday, June 20, 2014 3:39:47 PM
Subject: Re: [ovirt-devel] [oVirt 3.5 Localization Question #8]
"moveDisplayNetworkWarning"
Hi Yevgeny, I think you are the best to answer this question.
On Fri, Jun 20, 2014 at 10:08:18PM +1000, Yuko Katabami wrote:
>
> On 06/19/2014 06:28 PM, Yuko Katabami wrote:
> >Hello,
> >
> >This is our last question for today.
> >
> >*File:***ApplicationMessages
> >*Resource IDs:*** moveDisplayNetworkWarning
> >*String:***{0}. Moving the display network will drop VM console
> >connectivity until they are restarted.
> >*Question:* From the source comment "0=networkOperationMessage" I can
see
> >that {0} will be replaced with network operation messages. I wonder if
> >each of those messages already contains a fullstop. If so, it will have
> >two full stops. Could you please give me the example of those messages, so
> >that we can check our corresponding translation in Zanata (whether
> >fullstops are included or not).
> Is the variable {0} going to be replaced with messages that start
> with"$detailMessage"?
> I found them newly added to the current project we are translating.
>
> Kind regards,
>
> Yuko
> >
> >
> >Kind regards,
> >
> >Yuko
> >
> >
> >_______________________________________________
> >Devel mailing list
> >Devel(a)ovirt.org
> >http://lists.ovirt.org/mailman/listinfo/devel
>
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/devel