i18n: Fix untranslated messages
trunk-subports.help.html: The <p translate> tag was not closed appropriately. This confused angular-gettext and as a result translations are not used properly. launch-instance/networkports/ports.html: "on subnet" was marked as translation string in bug 1745873, but one "on subnet" is forgot to mark. This commit fixes it. Related-Bug: #1745873 Change-Id: I01c653161c9a91d499bf493590bb5f511901f31a
This commit is contained in:
parent
439c3e578d
commit
6294494163
|
@ -117,7 +117,11 @@
|
|||
<td class="rsp-p1 word-break">{$ ctrl.nameOrID(item) $}</td>
|
||||
<td class="rsp-p2">
|
||||
<div ng-repeat="ip in item.fixed_ips">
|
||||
{$ ip.ip_address $} on subnet: {$ item.subnet_names[ip.ip_address] $}
|
||||
<span translate
|
||||
translate-params-address="ip.ip_address"
|
||||
translate-params-subnet="item.subnet_names[ip.ip_address]">
|
||||
{$ address $} on subnet {$ subnet $}
|
||||
</span>
|
||||
</div>
|
||||
</td>
|
||||
<td class="rsp-p1">{$ item.admin_state | decode:ctrl.portAdminStates $}</td>
|
||||
|
|
|
@ -5,7 +5,7 @@
|
|||
<p translate>An arbitrary amount (0, 1, 2, ...) of regular Neutron
|
||||
ports with segmentation details (ie. type and ID). May be provided
|
||||
when the trunk is created. Also may be attached or detached later
|
||||
during the trunk's (and the instance's) life.
|
||||
during the trunk's (and the instance's) life.</p>
|
||||
|
||||
<p translate>Inside the instance a particular subport's network will
|
||||
be presented as tagged frames transmitted and received on the vNIC
|
||||
|
|
Loading…
Reference in New Issue