Traduzir expressões

A expressão original
!day-abbreviation SU|MO|TU|WE|TH|FR|SA
!description date (numeric representation of the day of the week)
!description date in 'small' format. (%date)
!description day (abbreviation)
!description day (full word)
!description day (one or two digits without leading zeros)
!description day (two digits with leading zeros)
!description in 'time-since' format. (%date)
!description in UNIX timestamp format (%date)
!description month (abbreviated)
!description month (full word)
!description month (one or two digits without leading zeros)
!description month (two digits with leading zeros)
!description week (two digits with leading zeros)
!description year (four digit)
!description year (two digit)
!field (!field_name) is an inactive !field_type field that uses a !widget_type widget.
!module.module has updates and is available in the modules folder but is not enabled.<br />If and when it is enabled, you will need to re-run the update script. You will continue to see this message until the module is enabled and updates are run.
!module.module has updates but cannot be updated because content.module is not enabled.<br />If and when content.module is enabled, you will need to re-run the update script. You will continue to see this message until the module is enabled and updates are run.
!type
!type nodes beginning with "!term"
!type nodes classified with !term
"$arg" is no longer supported. Use % instead.
"%" may not be used for the first segment of a path.
"@s" field group: @group in @type
"@s" field: @widget_label (@field_name) - @field_type
%name: found no valid user with that name.
%type basic information
&lt;none&gt;
'@column' => value for @column
(@field) <strong>Exposed</strong> @widget @format
(File not found, in folder @template-path)
(Sticky header effects will not be active for preview below, only on live output.)
(first item is 0)
(highest)
(lowest)
(normal)
(start from last values)
, of which @count are unpublished.
, of which one is unpublished.
- none -
-Any-
0.0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1.0
< Prev
<Hidden>
<em>fieldgroup</em>, which creates collapsible fieldsets to hold a group of related fields. A fieldset may either be open or closed by default. The order of your fieldsets, and the order of fields within a fieldset, is managed via a drag-and-drop interface provided by content module.
<em>nodereference</em>, which creates custom references between Drupal nodes. By adding a <em>nodereference</em> field and two different content types, for instance, you can easily create complex parent/child relationships between data (multiple "employee" nodes may contain a <em>nodereference</em> field linking to an "employer" node).
<em>number</em>, which adds numeric field types, in integer, decimal or floating point form. You may define a set of allowed inputs, or specify an allowable range of values. A variety of common formats for displaying numeric data are available.
<em>text</em>, which adds text field types. A text field may contain plain text only, or optionally, may use Drupal's input format filters to securely manage rich text input. Text input fields may be either a single line (text field), multiple lines (text area), or for greater input control, a select box, checkbox, or radio buttons. If desired, CCK can validate the input to a set of allowed values.
<em>userreference</em>, which creates custom references to your sites' user accounts. By adding a <em>userreference</em> field, you can create complex relationships between your site's users and posts. To track user involvement in a post beyond Drupal's standard <em>Authored by</em> field, for instance, add a <em>userreference</em> field named "Edited by" to a content type to store a link to an editor's user account page.
<p>Choose the "Views module" view that selects the nodes that can be referenced.<br />Note:</p>
<p>Choose the "Views module" view that selects the users that can be referenced.<br />Note:</p>
<p>DB maintenance performs an optimization query on selected tables.</p> <p>For MyISAM tables, OPTIMIZE TABLE repairs a table if it has deleted or split rows, sorts table indexes, and updates table statistics. For BDB and InnoDB, OPTIMIZE rebuilds the table. Note, MySQL locks tables during the time OPTIMIZE TABLE is running. OPTIMIZE works best on tables with large deletions (e.g. cache or watchdog), however MySQL will reuse old record positions, therefore in most setups, OPTIMIZE TABLE is unnecessary unless you just like defragmenting.</p> <p>The Overhead column in phpMyAdmin's database view is the most common way to determine the need of an OPTIMIZE TABLE query. It essentially shows the amount of disk space you would recover by running an optimize/defragmentation query.</p> <p>For PostgreSQL tables, VACUUM reclaims storage occupied by deleted tuples. In normal PostgreSQL operation, tuples that are deleted or obsoleted by an update are not physically removed from their table; they remain present until a VACUUM is done. Therefore it's necessary to do VACUUM periodically, especially on frequently-updated tables.</p>
<p>Endere&ccedil;o : Av.Vladimir Lenine,1935, Maputo - Mo&ccedil;ambique</p> <p>Telefone Fixo : <span class="skype_pnh_print_container">+258 21414743</span><span class="skype_pnh_container" dir="ltr" tabindex="-1"><strong><font size="2"><font color="#49535a"><font face="Tahoma"><span class="skype_pnh_mark"> </span></font></font></font></strong></span></p> <p>Telem&oacute;vel Celular : <span class="skype_pnh_print_container">+258 82 3038218</span><span class="skype_pnh_container" dir="ltr" tabindex="-1"><strong><font size="2"><font color="#49535a"><font face="Tahoma"><span class="skype_pnh_mark"> </span></font></font></font></strong></span></p> <p>Fax : +258 21414744</p> <p>E-mail:geral@oamoz.org</p>
<p>Provides a mechanism for modules to automatically generate aliases for the content they manage.</p> <h2>Settings</h2> <p>The <strong>Maximum Alias Length</strong> and <strong>Maximum component length</strong> values default to 100 and have a limit of 128 from pathauto. This length is limited by the length of the dst column of the url_alias database table. The default database schema for this column is 128. If you set a length that is equal to that of the one set in the dst column it will cause problems in situations where the system needs to append additional words to the aliased URL. For example... URLs generated for feeds will have "/feed" added to the end. You should enter a value that is the length of the dst column minus the length of any strings that might get added to the end of the URL. The length of strings that might get added to the end of your URLs depends on which modules you have enabled and on your Pathauto settings. The recommended and default value is 100.</p> <p><strong>Raw Tokens</strong> In Pathauto it is appropriate to use the -raw form of tokens. Paths are sent through a filtering system which ensures that raw user content is filtered. Failure to use -raw tokens can cause problems with the Pathauto punctuation filtering system.</p>
<p>The following substitution patterns are available for this display. Use the pattern shown on the left to display the value indicated on the right. Note that due to rendering order, you cannot use fields that come after this field; if you need a field not listed here, rearrange your fields.</p>
<p>The list of nodes that can be referenced can be based on a "Views module" view but no appropriate views were found. <br />Note:</p>
<p>The list of user that can be referenced can be based on a "Views module" view but no appropriate views were found. <br />Note:</p>
<p>You must add some additional fields to this display before using this field. These fields may be marked as <em>Exclude from display</em> if you prefer. Note that due to rendering order, you cannot use fields that come after this field; if you need a field not listed here, rearrange your fields.</p>
<strong>Important!</strong> When adding, removing, or renaming template files, it is necessary to make Drupal aware of the changes by making it rescan the files on your system. By clicking this button you clear Drupal's theme registry and thereby trigger this rescanning process. The highlighted templates above will then reflect the new state of your system.
<ul> <li>Check if your spelling is correct, or try removing filters.</li> <li>Remove quotes around phrases to match each word individually: <em>"blue drop"</em> will match less than <em>blue drop</em>.</li> <li>You can require or exclude terms using + and -: <em>big +blue drop</em> will require a match on <em>blue</em> while <em>big blue -drop</em> will exclude results that contain <em>drop</em>.</li> </ul>
<ul><li>Only views that have fields will work for this purpose.</li><li>This will discard the "Content types" settings above. Use the view's "filters" section instead.</li><li>Use the view's "fields" section to display additional informations about candidate nodes on node creation/edition form.</li><li>Use the view's "sort criteria" section to determine the order in which candidate nodes will be displayed.</li></ul>
<ul><li>Only views that have fields will work for this purpose.</li><li>This will discard the "Referenceable Roles" and "Referenceable Status" settings above. Use the view's "filters" section instead.</li><li>Use the view's "fields" section to display additional informations about candidate users on user creation/edition form.</li><li>Use the view's "sort criteria" section to determine the order in which candidate users will be displayed.</li></ul>
@field-name
@label (!name) - !column
@label (!name) - delta
@label-truncated - !column
@label-truncated - delta
@node's field '@field' has been changed
@node's field '@field' has value
@origin translation
@type handler @table.@field is not available.
A date in any machine readable format. CCYY-MM-DD HH:MM:SS is preferred.
A description of the location or context of the string.
A display whose path ends with a % cannot be a tab.
A file has been pre-loaded for import.
A human-readable name to be used as the label for this field in the %type content type.
A randomly generated SHA1 hash.
A randomly generated single-digit number.
A randomly generated ten-digit number.
A randomly generated three-digit number.
A source string for translation, in English or the default site language.
A view by that name already exists; please choose a different name
About taxonomy_import services
Above Left
Above Right
Above content
Absolute path alias to the referenced node.
Absolute path alias to the referenced user.
custom_search
default
!day-abbreviation SU|MO|TU|WE|TH|FR|SAdefault
!description date (numeric representation of the day of the week)default
!description date in 'small' format. (%date)default
!description day (abbreviation)default
!description day (full word)default
!description day (one or two digits without leading zeros)default
!description day (two digits with leading zeros)default
!description in 'time-since' format. (%date)default
!description in UNIX timestamp format (%date)default
!description month (abbreviated)default
!description month (full word)default
!description month (one or two digits without leading zeros)default
!description month (two digits with leading zeros)default
!description week (two digits with leading zeros)default
!description year (four digit)default
!description year (two digit)default
!field (!field_name) is an inactive !field_type field that uses a !widget_type widget.default
!module.module has updates and is available in the modules folder but is not enabled.<br />If and when it is enabled, you will need to re-run the update script. You will continue to see this message until the module is enabled and updates are run.default
!module.module has updates but cannot be updated because content.module is not enabled.<br />If and when content.module is enabled, you will need to re-run the update script. You will continue to see this message until the module is enabled and updates are run.default
!typedefault
!type nodes beginning with "!term"default
!type nodes classified with !termdefault
"$arg" is no longer supported. Use % instead.default
"%" may not be used for the first segment of a path.default
"@s" field group: @group in @typedefault
"@s" field: @widget_label (@field_name) - @field_typedefault
%name: found no valid user with that name.default
%type basic informationdefault
&lt;none&gt;default
'@column' => value for @columndefault
(@field) <strong>Exposed</strong> @widget @formatdefault
(File not found, in folder @template-path)default
(Sticky header effects will not be active for preview below, only on live output.)default
(first item is 0)default
(highest)default
(lowest)default
(normal)default
(start from last values)default
, of which @count are unpublished.default
, of which one is unpublished.default
- none -default
-Any-default
0.0default
0.1default
0.2default
0.3default
0.4default
0.5default
0.6default
0.7default
0.8default
0.9default
1.0default
< Prevdefault
<Hidden>default
<em>fieldgroup</em>, which creates collapsible fieldsets to hold a group of related fields. A fieldset may either be open or closed by default. The order of your fieldsets, and the order of fields within a fieldset, is managed via a drag-and-drop interface provided by content module.default
<em>nodereference</em>, which creates custom references between Drupal nodes. By adding a <em>nodereference</em> field and two different content types, for instance, you can easily create complex parent/child relationships between data (multiple "employee" nodes may contain a <em>nodereference</em> field linking to an "employer" node).default
<em>number</em>, which adds numeric field types, in integer, decimal or floating point form. You may define a set of allowed inputs, or specify an allowable range of values. A variety of common formats for displaying numeric data are available.default
<em>text</em>, which adds text field types. A text field may contain plain text only, or optionally, may use Drupal's input format filters to securely manage rich text input. Text input fields may be either a single line (text field), multiple lines (text area), or for greater input control, a select box, checkbox, or radio buttons. If desired, CCK can validate the input to a set of allowed values.default
<em>userreference</em>, which creates custom references to your sites' user accounts. By adding a <em>userreference</em> field, you can create complex relationships between your site's users and posts. To track user involvement in a post beyond Drupal's standard <em>Authored by</em> field, for instance, add a <em>userreference</em> field named "Edited by" to a content type to store a link to an editor's user account page.default
<p>Choose the "Views module" view that selects the nodes that can be referenced.<br />Note:</p>default
<p>Choose the "Views module" view that selects the users that can be referenced.<br />Note:</p>default
<p>DB maintenance performs an optimization query on selected tables.</p> <p>For MyISAM tables, OPTIMIZE TABLE repairs a table if it has deleted or split rows, sorts table indexes, and updates table statistics. For BDB and InnoDB, OPTIMIZE rebuilds the table. Note, MySQL locks tables during the time OPTIMIZE TABLE is running. OPTIMIZE works best on tables with large deletions (e.g. cache or watchdog), however MySQL will reuse old record positions, therefore in most setups, OPTIMIZE TABLE is unnecessary unless you just like defragmenting.</p> <p>The Overhead column in phpMyAdmin's database view is the most common way to determine the need of an OPTIMIZE TABLE query. It essentially shows the amount of disk space you would recover by running an optimize/defragmentation query.</p> <p>For PostgreSQL tables, VACUUM reclaims storage occupied by deleted tuples. In normal PostgreSQL operation, tuples that are deleted or obsoleted by an update are not physically removed from their table; they remain present until a VACUUM is done. Therefore it's necessary to do VACUUM periodically, especially on frequently-updated tables.</p>default
<p>Endere&ccedil;o : Av.Vladimir Lenine,1935, Maputo - Mo&ccedil;ambique</p> <p>Telefone Fixo : <span class="skype_pnh_print_container">+258 21414743</span><span class="skype_pnh_container" dir="ltr" tabindex="-1"><strong><font size="2"><font color="#49535a"><font face="Tahoma"><span class="skype_pnh_mark"> </span></font></font></font></strong></span></p> <p>Telem&oacute;vel Celular : <span class="skype_pnh_print_container">+258 82 3038218</span><span class="skype_pnh_container" dir="ltr" tabindex="-1"><strong><font size="2"><font color="#49535a"><font face="Tahoma"><span class="skype_pnh_mark"> </span></font></font></font></strong></span></p> <p>Fax : +258 21414744</p> <p>E-mail:geral@oamoz.org</p>default
<p>Provides a mechanism for modules to automatically generate aliases for the content they manage.</p> <h2>Settings</h2> <p>The <strong>Maximum Alias Length</strong> and <strong>Maximum component length</strong> values default to 100 and have a limit of 128 from pathauto. This length is limited by the length of the dst column of the url_alias database table. The default database schema for this column is 128. If you set a length that is equal to that of the one set in the dst column it will cause problems in situations where the system needs to append additional words to the aliased URL. For example... URLs generated for feeds will have "/feed" added to the end. You should enter a value that is the length of the dst column minus the length of any strings that might get added to the end of the URL. The length of strings that might get added to the end of your URLs depends on which modules you have enabled and on your Pathauto settings. The recommended and default value is 100.</p> <p><strong>Raw Tokens</strong> In Pathauto it is appropriate to use the -raw form of tokens. Paths are sent through a filtering system which ensures that raw user content is filtered. Failure to use -raw tokens can cause problems with the Pathauto punctuation filtering system.</p>default
<p>The following substitution patterns are available for this display. Use the pattern shown on the left to display the value indicated on the right. Note that due to rendering order, you cannot use fields that come after this field; if you need a field not listed here, rearrange your fields.</p>default
<p>The list of nodes that can be referenced can be based on a "Views module" view but no appropriate views were found. <br />Note:</p>default
<p>The list of user that can be referenced can be based on a "Views module" view but no appropriate views were found. <br />Note:</p>default
<p>You must add some additional fields to this display before using this field. These fields may be marked as <em>Exclude from display</em> if you prefer. Note that due to rendering order, you cannot use fields that come after this field; if you need a field not listed here, rearrange your fields.</p>default
<strong>Important!</strong> When adding, removing, or renaming template files, it is necessary to make Drupal aware of the changes by making it rescan the files on your system. By clicking this button you clear Drupal's theme registry and thereby trigger this rescanning process. The highlighted templates above will then reflect the new state of your system.default
<ul> <li>Check if your spelling is correct, or try removing filters.</li> <li>Remove quotes around phrases to match each word individually: <em>"blue drop"</em> will match less than <em>blue drop</em>.</li> <li>You can require or exclude terms using + and -: <em>big +blue drop</em> will require a match on <em>blue</em> while <em>big blue -drop</em> will exclude results that contain <em>drop</em>.</li> </ul>default
<ul><li>Only views that have fields will work for this purpose.</li><li>This will discard the "Content types" settings above. Use the view's "filters" section instead.</li><li>Use the view's "fields" section to display additional informations about candidate nodes on node creation/edition form.</li><li>Use the view's "sort criteria" section to determine the order in which candidate nodes will be displayed.</li></ul>default
<ul><li>Only views that have fields will work for this purpose.</li><li>This will discard the "Referenceable Roles" and "Referenceable Status" settings above. Use the view's "filters" section instead.</li><li>Use the view's "fields" section to display additional informations about candidate users on user creation/edition form.</li><li>Use the view's "sort criteria" section to determine the order in which candidate users will be displayed.</li></ul>default
@field-namedefault
@label (!name) - !columndefault
@label (!name) - deltadefault
@label-truncated - !columndefault
@label-truncated - deltadefault
@node's field '@field' has been changeddefault
@node's field '@field' has valuedefault
@origin translationdefault
@type handler @table.@field is not available.default
A date in any machine readable format. CCYY-MM-DD HH:MM:SS is preferred.default
A description of the location or context of the string.default
A display whose path ends with a % cannot be a tab.default
A file has been pre-loaded for import.default
A human-readable name to be used as the label for this field in the %type content type.default
A randomly generated SHA1 hash.default
A randomly generated single-digit number.default
A randomly generated ten-digit number.default
A randomly generated three-digit number.default
A source string for translation, in English or the default site language.default
A view by that name already exists; please choose a different namedefault
About taxonomy_import servicesdefault
Above Leftdefault
Above Rightdefault
Above contentdefault
Absolute path alias to the referenced node.default
Absolute path alias to the referenced user.default
Acordãomenu
All legal informationcustom_search
Avisomenu
Boletins da Republica de Moçambiquemenu
Comunicadomenu
Conselho Constitucionalmenu
Decretomenu
Deliberaçãomenu
Despachomenu
Despacho Ministerialmenu
Despacho Presidencialmenu
Enter keywordscustom_search
Homemenu
Judicial-Courtmenu
Legislação por Sectormenu
Leimenu
Página Inicialmenu
Rectificaçãomenu
Resoluçãomenu
Searchcustom_search
Search forcustom_search
Tribunal Supremomenu