Исходный текст | Переводы |
---|---|
<p>Example Mappings:</p> <ul> <li><em>taxonomy/page/or/52,97</em> to <em>taxonomy/term/52+97</em>.</li> <li><em>taxonomy/feed/or/52,97</em> to <em>taxonomy/term/52+97/0/feed</em>.</li> <li><em>blog/feed/52</em> to <em>blog/52/feed</em>.</li> <li><em>node/view/52</em> to <em>node/52</em>.</li> <li><em>book/view/52</em> to <em>node/52</em>.</li> <li><em>user/view/52</em> to <em>user/52</em>.</li> </ul> | |
For more information please read the configuration and customization handbook <a href="@legacy">Legacy page</a>. | |
Taxonomy | Таксономия |
Legacy filter | |
Replaces URLs from Drupal 4.1 (and lower) with updated equivalents. | |
legacy | |
Provides legacy handlers for upgrades from older Drupal installations. | |
The locale module provides two options for providing translations. The first is the integrated web interface, via which you can search for untranslated strings, and specify their translations. An easier and less time-consuming method is to import existing translations for your language. These translations are available as <em>GNU gettext Portable Object files</em> (<em>.po</em> files for short). Translations for many languages are available for download from the translation page. | |
If an existing translation does not meet your needs, the <em>.po</em> files are easily edited with special editing tools. The locale module's import feature allows you to add strings from such files into your site's database. The export functionality enables you to share your translations with others, generating Portable Object files from your site strings. | |
For more information please read the configuration and customization handbook <a href="@locale">Locale page</a>. |