Add ':' inside translatable (Part 2 of 2)

Punctuation needs to be included in translation since punctuation differs
depending on the language.  Along with moving ':' also replaced   with
blank space insde trans or transblock tag.The initial review grew too large,
so this patch has been broken into 2 reviews.  Part 2 will cover the files in
openstack_dashboard/dashboard/project while Part 1 coverered the rest.

Change-Id: Ibf2036d5bbc4c478fcb912f6335104356e8f1317
Partially-Closes-Bug: #1369445
This commit is contained in:
Aaron Sahlin 2014-09-30 16:25:04 -05:00
parent 6f2c431130
commit a1e770dc10
41 changed files with 85 additions and 67 deletions

View File

@ -14,7 +14,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Key pairs are ssh credentials which are injected into images when they are launched. Creating a new key pair registers the public key and downloads the private key (a .pem file)." %}</p>
<p>{% trans "Protect and use the key as you would any normal ssh private key." %}</p>
</div>

View File

@ -14,7 +14,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Key Pairs are how you login to your instance after it is launched." %}</p>
<p>{% trans "Choose a key pair name you will recognise and paste your SSH public key into the space provided." %}</p>
<p>{% trans "SSH key pairs can be generated with the ssh-keygen command:" %}</p>

View File

@ -15,11 +15,11 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% blocktrans %}Rules define which traffic is allowed to instances assigned to the security group. A security group rule consists of three main parts:{% endblocktrans %}</p>
<p><strong>{% trans "Rule" %}</strong>: {% blocktrans %}You can specify the desired rule template or use custom rules, the options are Custom TCP Rule, Custom UDP Rule, or Custom ICMP Rule.{% endblocktrans %}</p>
<p><strong>{% trans "Open Port/Port Range" %}</strong>: {% blocktrans %}For TCP and UDP rules you may choose to open either a single port or a range of ports. Selecting the "Port Range" option will provide you with space to provide both the starting and ending ports for the range. For ICMP rules you instead specify an ICMP type and code in the spaces provided.{% endblocktrans %}</p>
<p><strong>{% trans "Remote" %}</strong>: {% blocktrans %}You must specify the source of the traffic to be allowed via this rule. You may do so either in the form of an IP address block (CIDR) or via a source group (Security Group). Selecting a security group as the source will allow any other instance in that security group access to any other instance via this rule.{% endblocktrans %}</p>
<p><strong>{% trans "Rule:" %}</strong> {% blocktrans %}You can specify the desired rule template or use custom rules, the options are Custom TCP Rule, Custom UDP Rule, or Custom ICMP Rule.{% endblocktrans %}</p>
<p><strong>{% trans "Open Port/Port Range:" %}</strong> {% blocktrans %}For TCP and UDP rules you may choose to open either a single port or a range of ports. Selecting the "Port Range" option will provide you with space to provide both the starting and ending ports for the range. For ICMP rules you instead specify an ICMP type and code in the spaces provided.{% endblocktrans %}</p>
<p><strong>{% trans "Remote:" %}</strong> {% blocktrans %}You must specify the source of the traffic to be allowed via this rule. You may do so either in the form of an IP address block (CIDR) or via a source group (Security Group). Selecting a security group as the source will allow any other instance in that security group access to any other instance via this rule.{% endblocktrans %}</p>
</div>
{% endblock %}

View File

@ -15,7 +15,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Security groups are sets of IP filter rules that are applied to the network settings for the VM. After the security group is created, you can add rules to the security group." %}</p>
</div>
{% endblock %}

View File

@ -15,7 +15,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Security groups are sets of IP filter rules that are applied to the network settings for the VM. Edit the security group to add and change the rules." %}</p>
</div>
{% endblock %}

View File

@ -5,7 +5,7 @@
{% block form_id %}copy_object_form{% endblock %}
{% block form_action %}{% url 'horizon:project:containers:object_copy' container_name object_name %}{% endblock %}
{% block modal-header %}{% trans "Copy Object" %}: {{ object_name }}{% endblock %}
{% block modal-header %}{% blocktrans %}Copy Object: {{ object_name }}{% endblocktrans %}{% endblock %}
{% block modal-body %}
<div class="left">
@ -14,7 +14,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Make a new copy of an existing object to store in this or another container. You may additionally specify the path within the selected container where the new copy should be stored." %}</p>
</div>
{% endblock %}

View File

@ -14,7 +14,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "A container is a storage compartment for your data and provides a way for you to organize your data. You can think of a container as a folder in Windows &reg; or a directory in UNIX &reg;. The primary difference between a container and these other file system concepts is that containers cannot be nested. You can, however, create an unlimited number of containers within your account. Data must be stored in a container so you must have at least one container defined in your account prior to uploading data." %}</p>
<p>{% trans "Note: A Public Container will allow anyone with the Public URL to gain access to your objects in the container." %}</p>
</div>

View File

@ -14,8 +14,8 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<p><strong>{% trans "Pseudo-folder" %}</strong>: {% trans "Within a container you can group your objects into pseudo-folders, which behave similarly to folders in your desktop operating system, with the exception that they are virtual collections defined by a common prefix on the object's name. A slash (/) character is used as the delimiter for pseudo-folders in the Object Store." %}</p>
<h3>{% trans "Description: %}</h3>
<p><strong>{% trans "Pseudo-folder:" %}</strong> {% trans "Within a container you can group your objects into pseudo-folders, which behave similarly to folders in your desktop operating system, with the exception that they are virtual collections defined by a common prefix on the object's name. A slash (/) character is used as the delimiter for pseudo-folders in the Object Store." %}</p>
</div>
{% endblock %}

View File

@ -17,9 +17,9 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<p><strong>{% trans "Object" %}</strong>: {% trans "An object is the basic storage entity that represents a file you store in the OpenStack Object Storage system. When you upload data to OpenStack Object Storage, the data is stored as-is (no compression or encryption) and consists of a location (container), the object's name, and any metadata consisting of key/value pairs." %}</p>
<p><strong>{% trans "File" %}</strong>: {% trans "A new uploaded file will replace the content of the current object" %}</p>
<h3>{% trans "Description:" %}</h3>
<p><strong>{% trans "Object:" %}</strong> {% trans "An object is the basic storage entity that represents a file you store in the OpenStack Object Storage system. When you upload data to OpenStack Object Storage, the data is stored as-is (no compression or encryption) and consists of a location (container), the object's name, and any metadata consisting of key/value pairs." %}</p>
<p><strong>{% trans "File:" %}</strong> {% trans "A new uploaded file will replace the content of the current object" %}</p>
</div>
{% endblock %}

View File

@ -7,7 +7,9 @@
{% block form_action %}{% url 'horizon:project:containers:object_upload' container_name %}{% endblock %}
{% block form_attrs %}enctype="multipart/form-data"{% endblock %}
{% block modal-header %}{% trans "Upload Object To Container" %}: {{ container_name }}{% endblock %}
{% block modal-header %}
{% blocktrans %}Upload Object To Container: {{ container_name }}{% endblocktrans %}
{% endblock %}
{% block modal-body %}
<div class="left">
@ -16,9 +18,9 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<p><strong>{% trans "Object" %}</strong>: {% trans "An object is the basic storage entity that represents a file you store in the OpenStack Object Storage system. When you upload data to OpenStack Object Storage, the data is stored as-is (no compression or encryption) and consists of a location (container), the object's name, and any metadata consisting of key/value pairs." %}</p>
<p><strong>{% trans "Pseudo-folder" %}</strong>: {% trans "Within a container you can group your objects into pseudo-folders, which behave similarly to folders in your desktop operating system, with the exception that they are virtual collections defined by a common prefix on the object's name. A slash (/) character is used as the delimiter for pseudo-folders in the Object Store." %}</p>
<h3>{% trans "Description:" %}</h3>
<p><strong>{% trans "Object:" %}</strong> {% trans "An object is the basic storage entity that represents a file you store in the OpenStack Object Storage system. When you upload data to OpenStack Object Storage, the data is stored as-is (no compression or encryption) and consists of a location (container), the object's name, and any metadata consisting of key/value pairs." %}</p>
<p><strong>{% trans "Pseudo-folder:" %}</strong> {% trans "Within a container you can group your objects into pseudo-folders, which behave similarly to folders in your desktop operating system, with the exception that they are virtual collections defined by a common prefix on the object's name. A slash (/) character is used as the delimiter for pseudo-folders in the Object Store." %}</p>
</div>
{% endblock %}

View File

@ -39,7 +39,7 @@
{% if service_conf %}
<ul>
{% for conf_name, conf_value in service_conf.items %}
<li>{{ conf_name }}:&nbsp{{ conf_value }}</li>
<li>{% blocktrans %}{{ conf_name }}: {{ conf_value }}{% endblocktrans %}</li>
{% endfor %}
</ul>
{% else %}

View File

@ -4,7 +4,7 @@
<div class="status row detail">
{% for node_group in template.node_groups %}
<dl class="well">
<h4>{% trans "Node Group" %}: {{ node_group.name }}</h4>
<h4>{% blocktrans with node_group_name=node_group.name %}Node Group: {{ node_group_name }}{% endblocktrans %}</h4>
<dt>{% trans "Nodes Count" %}</dt>
<dd>{{ node_group.count }}</dd>
@ -51,7 +51,7 @@
{% if service_conf %}
<ul>
{% for conf_name, conf_value in service_conf.items %}
<li>{{ conf_name }}:&nbsp{{ conf_value }}</li>
<li>{% blocktrans %}{{ conf_name }}: {{ conf_value }}{% endblocktrans %}</li>
{% endfor %}
</ul>
{% else %}

View File

@ -92,7 +92,7 @@
$("#node-templates").hide();
</script>
<input type="hidden" value="[]" name="forms_ids" id="forms_ids">
<label for="template_id">{% trans "Select a Node Group Template to add" %}:</label>
<label for="template_id">{% trans "Select a Node Group Template to add:" %}</label>
<span class="row">
<span class="input-group col-sm-4">
<select id="template_id" name="template" class="form-control">

View File

@ -65,7 +65,7 @@
{% if service_conf %}
<ul>
{% for conf_name, conf_value in service_conf.items %}
<li>{{ conf_name }}:&nbsp{{ conf_value }}</li>
<li>{% blocktrans %}{{ conf_name }}: {{ conf_value }}{% endblocktrans %}</li>
{% endfor %}
</ul>
{% else %}
@ -82,7 +82,9 @@
{% for info_key, info_val in cluster.info.items %}
<dt>{{ info_key }}</dt>
{% for key, val in info_val.items %}
<dd>{{ key }}:&nbsp{% autoescape off %}{{ val }}{% endautoescape %}</dd>
<dd>
{% blocktrans %}{{ key }}: {% autoescape off %}{{ val }}{% endautoescape %}{% endblocktrans %}
</dd>
{% endfor %}
{% endfor %}
</dl>

View File

@ -7,7 +7,7 @@
<div class="status row detail">
{% for node_group in cluster.node_groups %}
<dl class="well">
<h4>{% trans "Name" %}: {{ node_group.name }}</h4>
<h4>{% blocktrans with node_group_name=node_group.name %}Name: {{ node_group_name }}{% endblocktrans %}</h4>
<dt>{% trans "Number of Nodes" %}</dt>
<dd>{{ node_group.count }}</dd>
@ -59,7 +59,7 @@
{% if service_conf %}
<ul>
{% for conf_name, conf_value in service_conf.items %}
<li>{{ conf_name }}:&nbsp{{ conf_value }}</li>
<li>{% blocktrans %}{{ conf_name }}: {{ conf_value }}{% endblocktrans %}</li>
{% endfor %}
</ul>
{% else %}

View File

@ -29,7 +29,7 @@
<dd>{{ job_execution.created_at }}</dd>
<dt>{% trans "Job Configuration" %}</dt>
<dd>{% for group, vals in job_execution.job_configs.iteritems %}
<ul><li><span style="font-weight:bold">{{ group }}:</span>
<ul><li><span style="font-weight:bold">{% blocktrans %}{{ group }}:{% endblocktrans %}</span>
{%if group == "args" %}
<ul>{% for val in vals %} <li>{{ val }}</li> {% endfor %}</ul>
{% else %}

View File

@ -9,7 +9,7 @@
<ul>
{% for conf_name, conf_val in config.items %}
<li>
{{ conf_name }}:&nbsp{{ conf_val }}
{% blocktrans %}{{ conf_name }}: {{ conf_value }}{% endblocktrans %}
</li>
{% endfor %}
</ul>

View File

@ -17,7 +17,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "To decrypt your password you will need the private key of your key pair for this instance. Select the private key file, or copy and paste the content of your private key file into the text area below, then click Decrypt Password."%}</p>
<p><b>{% trans "Note: " %} </b> {% trans "The private key will be only used in your browser and will not be sent to the server" %}</p>
</div>

View File

@ -5,7 +5,7 @@
<tr><th>{% trans 'RAM' %}</th><td>{{ size_ram }}</td></tr>
<tr><th>{% trans 'Size' %}</th><td>{{ size_disk }}</td></tr>
</table>
" data-original-title="{% trans "Flavor Details" %}: {{ name }}">{{ name }}</a>
" data-original-title="{% blocktrans %}Flavor Details: {{ name }}">{{ name }}{% endblocktrans %}</a>
<script type="text/javascript" charset="utf-8">
$(function ()
{ $("#flavor_details_{{ id }}").popover({html:true});

View File

@ -15,7 +15,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Select the image to rebuild your instance." %}</p>
{% if can_set_server_password %}
<p>{% trans "You may optionally set a password on the rebuilt instance." %}</p>

View File

@ -38,12 +38,17 @@
<dt>{% trans "Session Persistence" %}</dt>
{% if vip.session_persistence %}
<dd>{% trans "Type" %}: {{ vip.session_persistence.type }}</dd>
<dd>
{% blocktrans with persistence_type=vip.session_persistence.type %}Type: {{ persistence_type }}{% endblocktrans %}
</dd>
{% if vip.session_persistence.cookie_name %}
<dd>{% trans "Cookie Name" %}: {{ vip.session_persistence.cookie_name }}</dd>
<dd>
{% blocktrans with cookie_name=vip.session_persistence.cookie_name %}Cookie Name: {{ cookie_name }}{% endblocktrans %}
</dd>
{% endif %}
{% else %}
<dd>{% trans "None" %}</dd>
<dd>{% trans "None" %}</dd>
{% endif %}
<dt>{% trans "Connection Limit" %}</dt>

View File

@ -14,7 +14,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Select a name for your network."%}</p>
</div>
{% endblock %}

View File

@ -20,9 +20,9 @@
<dd>{{ network.router__external|yesno|capfirst }}</dd>
{% if network.provider__network_type %}
<dt>{% trans "Provider Network" %}</dt>
<dd>{% trans "Network Type" %}: {{ network.provider__network_type|default:_("Unknown") }}</dd>
<dd>{% trans "Physical Network" %}: {{ network.provider__physical_network|default:"-" }}</dd>
<dd>{% trans "Segmentation ID" %}: {{ network.provider__segmentation_id|default:"-" }}</dd>
<dd>{% trans "Network Type:" %} {{ network.provider__network_type|default:_("Unknown") }}</dd>
<dd>{% trans "Physical Network:" %} {{ network.provider__physical_network|default:"-" }}</dd>
<dd>{% trans "Segmentation ID:" %} {{ network.provider__segmentation_id|default:"-" }}</dd>
{% endif %}
</dl>
</div>

View File

@ -1,6 +1,8 @@
{% load i18n sizeformat parse_date %}
<h3>{% trans "Router Overview" %}: {{router.name|default:_("None") }}</h3>
<h3>
{% blocktrans with router_name=router.name|default:_("None") %}Router Overview: {{ router_name }}{% endblocktrans %}
</h3>
<div class="info detail">
<dl>
@ -22,7 +24,7 @@
{% endif %}
{% if router.external_gateway_info %}
<dt>{% trans "External Gateway Information" %}</dt>
<dd>{% trans "Connected External Network" %}:
<dd>{% trans "Connected External Network:" %}
{{ router.external_gateway_info.network }}</dd>
{% endif %}
</dl>

View File

@ -15,7 +15,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>
{% trans "Routing rules to apply to router. Rules are matched by most specific source first and then by most specific destination." %}<br/>
{% trans "The next hop addresses can be used to override the router used by the client." %}

View File

@ -27,7 +27,7 @@
<th>
{{ dest.networkname }}<br/>
{% if dest.subnetname|length > 0 %}
{% trans "Subnet" %}: {{ dest.subnetname }}</br>
{% blocktrans with dest_subnetname=dest.subnetname %}Subnet: {{ dest_subnetname }}{% endblocktrans %}</br>
{% endif %}
{{ dest.cidr }}
</th>
@ -41,7 +41,8 @@
<td>
<b>{{ row.source.networkname }}
{% if row.source.subnetname|length > 0 %}
<br/>{% trans "Subnet" %}: {{ row.source.subnetname }}
<br/>
{% blocktrans with row_source_subnetname=row.source.subnetname %}Subnet: {{ row_source_subnetname }}{% endblocktrans %}
{% endif %}
<br/>
{{ row.source.cidr }}
@ -95,9 +96,9 @@
<p>{% blocktrans %}A more specific rule affects a portion of this traffic so a rule cannot be automatically generated to control the behavior of the entire source/destination combination.{% endblocktrans %}</p>
<hr>
<h4>{% trans "Conflicting Rule" %}</h4>
<b>{% trans "Source" %}:</b> {{ dest.conflicting_rule.source }}<br>
<b>{% trans "Destination" %}:</b> {{ dest.conflicting_rule.destination }}<br>
<b>{% trans "Action" %}:</b> {{ dest.conflicting_rule.action }}<br>
<b>{% trans "Source:" %}</b> {{ dest.conflicting_rule.source }}<br>
<b>{% trans "Destination:" %}</b> {{ dest.conflicting_rule.destination }}<br>
<b>{% trans "Action:" %}</b> {{ dest.conflicting_rule.action }}<br>
</div>
<div class="modal-footer">
<a href="#" class="btn" data-dismiss="modal">{% trans "Close" %}</a>

View File

@ -15,7 +15,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>
{% trans "You can connect a specified subnet to the router." %}
</p>

View File

@ -15,7 +15,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "You can connect a specified external network to the router. The external network is regarded as a default route of the router and the router acts as a gateway for external connectivity." %}</p>
</div>
{% endblock %}

View File

@ -16,7 +16,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Use one of the available template source options to specify the template to be used in creating this stack." %}</p>
</div>
{% endblock %}

View File

@ -15,7 +15,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Create a new stack with the provided values." %}</p>
</div>
{% endblock %}

View File

@ -24,7 +24,9 @@
<dt>{% trans "Last Updated" %}</dt>
<dd>{{ stack.updated_time|parse_isotime|timesince_or_never }}</dd>
<dt>{% trans "Status" %}</dt>
<dd>{{ stack.stack_status|title }}: {{ stack.stack_status_reason }}</dd>
<dd>
{% blocktrans with stack_status_title=stack.stack_status|title stack_status_reason=stack.stack_status_reason %}{{ stack_status_title }}: {{ stack_status_reason }}{% endblocktrans %}
</dd>
</dl>
</div>

View File

@ -38,7 +38,9 @@
<dt>{% trans "Last Updated" %}</dt>
<dd>{{ resource.updated_time|parse_isotime|timesince_or_never }}</dd>
<dt>{% trans "Status" %}</dt>
<dd>{{ resource.resource_status|title|replace_underscores }}: {{ resource.resource_status_reason }}</dd>
<dd>
{% blocktrans with resource_status=resource.resource_status|title|replace_underscores resource_status_reason=resource.resource_status_reason % }{{ resource_status }}: {{ resource_status_reason }}{% endblocktrans %}
</dd>
</dl>
</div>

View File

@ -16,7 +16,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Use one of the available template source options to specify the template to be used in creating this stack." %}</p>
</div>
{% endblock %}

View File

@ -15,7 +15,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Update a stack with the provided values. Please note that any encrypted parameters, such as passwords, will be reset to default if you do not change them here." %}</p>
</div>
{% endblock %}

View File

@ -15,7 +15,7 @@
</fieldset>
</div>
<div class="right">
<p><strong>{% trans "Volume Backup" %}</strong>: {% trans "Volume Backups are stored using the Object Storage service. You must have this service activated in order to create a backup." %}</p>
<p><strong>{% trans "Volume Backup:" %}</strong> {% trans "Volume Backups are stored using the Object Storage service. You must have this service activated in order to create a backup." %}</p>
<p>{% trans "If no container name is provided, a default container named volumebackups will be provisioned for you. Backups will be the same size as the volume they originate from." %}</p>
</div>
{% endblock %}

View File

@ -1,7 +1,9 @@
{% load i18n sizeformat parse_date %}
{% load url from future %}
<h3>{% trans "Volume Backup Overview" %}: {{backup.display_name }}</h3>
<h3>
{% blocktrans with backup_display_name=backup.display_name %}Volume Backup Overview: {{ backup_display_name }}{% endblocktrans %}
</h3>
<div class="info row-fluid detail">
<h4>{% trans "Info" %}</h4>

View File

@ -15,7 +15,7 @@
</fieldset>
</div>
<div class="right">
<p><strong>{% trans "Restore Backup" %}</strong>: {% trans "Select a volume to restore to." %}</p>
<p><strong>{% trans "Restore Backup:" %}</strong> {% trans "Select a volume to restore to." %}</p>
<p>{% trans "Optionally, you may choose to create a new volume." %}</p>
</div>
{% endblock %}

View File

@ -1,6 +1,6 @@
{% load i18n horizon humanize %}
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Extend the size of a volume." %}</p>

View File

@ -1,6 +1,6 @@
{% load i18n horizon humanize %}
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% block title %}{% trans "Volumes are block devices that can be attached to instances." %}{% endblock %}</p>

View File

@ -15,7 +15,7 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<h3>{% trans "Description:" %}</h3>
<p>{% trans "Modify name and description of a volume." %}</p>
</div>
{% endblock %}

View File

@ -15,11 +15,11 @@
</fieldset>
</div>
<div class="right">
<h3>{% trans "Description" %}:</h3>
<p><strong>{% trans "Name" %}</strong>: {% blocktrans %} Select a name for your network profile.{% endblocktrans %}</p>
<p><strong>{% trans "Segment Type" %}</strong>: {% blocktrans %} Segment types available are VLAN, Overlay and Trunk.{% endblocktrans %}</p>
<p><strong>{% trans "Segment Sub Type" %}</strong>: {% blocktrans %} Sub types available are for the Overlay and Trunk segments. Available sub-types for Overlay are: Native-VXLAN, Enhanced-VXLAN or 'Other' (eg. GRE) which can be manually inputed as a text parameter for subtype. Available sub-type for Trunk is: VLAN.{% endblocktrans %}</p>
<p><strong>{% trans "Segment Range" %}</strong>: {% blocktrans %} Segment Ranges are 1-4093 for VLAN and above 5000 for Enhanced-VXLAN Overlay.{% endblocktrans %}</p>
<h3>{% trans "Description:" %}</h3>
<p><strong>{% trans "Name:" %}</strong> {% blocktrans %} Select a name for your network profile.{% endblocktrans %}</p>
<p><strong>{% trans "Segment Type:" %}</strong> {% blocktrans %} Segment types available are VLAN, Overlay and Trunk.{% endblocktrans %}</p>
<p><strong>{% trans "Segment Sub Type:" %}</strong> {% blocktrans %} Sub types available are for the Overlay and Trunk segments. Available sub-types for Overlay are: Native-VXLAN, Enhanced-VXLAN or 'Other' (eg. GRE) which can be manually inputed as a text parameter for subtype. Available sub-type for Trunk is: VLAN.{% endblocktrans %}</p>
<p><strong>{% trans "Segment Range:" %}</strong> {% blocktrans %} Segment Ranges are 1-4093 for VLAN and above 5000 for Enhanced-VXLAN Overlay.{% endblocktrans %}</p>
</div>
{% endblock %}