i18n: nested <translate> tag does not work
rule.description.html in network QoS panel used <translated> tag in a nested way. As a result, strings used when looking up in a PO file does not match strings extracted into POT file. See [1] for details. This commit adjusts the help message without nested <translate> tag. [1] https://bugs.launchpad.net/horizon/+bug/2037875/comments/2 Closes-Bug: #2037875 Change-Id: I146e45681a29cb264fa40898cfc5f636143b2701
This commit is contained in:
parent
f988217c94
commit
d31bf68579
|
@ -6,13 +6,13 @@
|
|||
<p translate>
|
||||
The maximum KBPS (kilobits per second) value.
|
||||
If you specify this value, must be greater than 0 otherwise max_kbps will have no value.
|
||||
<p translate>
|
||||
The maximum burst size (in kilobits). Default is 0.
|
||||
</p>
|
||||
</p>
|
||||
<p translate>
|
||||
The maximum burst size (in kilobits). Default is 0.
|
||||
</p>
|
||||
<p translate>
|
||||
The minimum KBPS (kilobits per second) value which should be available for port.
|
||||
</p>
|
||||
<p translate>
|
||||
The minimum kpps (kilo(1000) packets per second) value which should be available for port.
|
||||
</p>
|
||||
</p>
|
||||
|
|
Loading…
Reference in New Issue