| [ Index ] |
PHP Cross Reference of Drupal 6 (yi-drupal) |
[Summary view] [Print] [Text view]
1 # $Id: content.pot,v 1.1.2.11 2009/06/16 17:05:11 hass Exp $ 2 # 3 # LANGUAGE translation of Drupal (root) 4 # Copyright YEAR NAME <EMAIL@ADDRESS> 5 # Generated from files: 6 # content.module,v 1.301.2.106 2009/06/02 12:24:04 yched 7 # content.install,v 1.85.2.31 2009/04/23 18:37:10 yched 8 # content.info,v 1.6 2007/07/04 23:46:29 yched 9 # content.rules.inc,v 1.1.2.6 2009/04/30 09:56:07 fago 10 # content.views.inc,v 1.1.2.25 2009/04/11 14:50:53 yched 11 # content_copy.info,v 1.6 2008/04/23 18:01:48 dww 12 # content_permissions.info,v 1.2 2008/04/23 18:01:52 dww 13 # fieldgroup.info,v 1.6.2.1 2008/09/22 18:25:21 karens 14 # nodereference.info,v 1.8 2008/04/23 18:02:07 dww 15 # number.info,v 1.7 2008/04/23 18:02:16 dww 16 # optionwidgets.info,v 1.7 2008/04/23 18:02:24 dww 17 # text.info,v 1.9 2008/04/23 18:02:31 dww 18 # userreference.info,v 1.8 2008/04/23 18:02:38 dww 19 # 20 #, fuzzy 21 msgid "" 22 msgstr "" 23 "Project-Id-Version: PROJECT VERSION\n" 24 "POT-Creation-Date: 2009-06-16 19:00+0200\n" 25 "PO-Revision-Date: YYYY-mm-DD HH:MM+ZZZZ\n" 26 "Last-Translator: NAME <EMAIL@ADDRESS>\n" 27 "Language-Team: LANGUAGE <EMAIL@ADDRESS>\n" 28 "MIME-Version: 1.0\n" 29 "Content-Type: text/plain; charset=utf-8\n" 30 "Content-Transfer-Encoding: 8bit\n" 31 "Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n" 32 33 #: content.module:21 34 msgid "The content module, a required component of the Content Construction Kit (CCK), allows administrators to associate custom fields with content types. In Drupal, content types are used to define the characteristics of a post, including the title and description of the fields displayed on its add and edit pages. Using the content module (and the other helper modules included in CCK), custom fields beyond the default \"Title\" and \"Body\" may be added. CCK features are accessible through tabs on the <a href=\"@content-types\">content types administration page</a>. (See the <a href=\"@node-help\">node module help page</a> for more information about content types.)" 35 msgstr "" 36 37 #: content.module:22 38 msgid "When adding a custom field to a content type, you determine its type (whether it will contain text, numbers, or references to other objects) and how it will be displayed (either as a text field or area, a select box, checkbox, radio button, or autocompleting field). A field may have multiple values (i.e., a \"person\" may have multiple e-mail addresses) or a single value (i.e., an \"employee\" has a single employee identification number). As you add and edit fields, CCK automatically adjusts the structure of the database as necessary. CCK also provides a number of other features, including intelligent caching for your custom data, an import and export facility for content type definitions, and integration with other contributed modules." 39 msgstr "" 40 41 #: content.module:23 42 msgid "Custom field types are provided by a set of optional modules included with CCK (each module provides a different type). The <a href=\"@modules\">modules page</a> allows you to enable or disable CCK components. A default installation of CCK includes:" 43 msgstr "" 44 45 #: content.module:25 46 msgid "<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." 47 msgstr "" 48 49 #: content.module:26 50 msgid "<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." 51 msgstr "" 52 53 #: content.module:27 54 msgid "<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)." 55 msgstr "" 56 57 #: content.module:28 58 msgid "<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." 59 msgstr "" 60 61 #: content.module:29 62 msgid "<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." 63 msgstr "" 64 65 #: content.module:31 66 msgid "For more information, see the online handbook entry for <a href=\"@handbook-cck\">CCK</a> or the <a href=\"@project-cck\">CCK project page</a>." 67 msgstr "" 68 69 #: content.module:492 70 msgid "This field is required." 71 msgstr "" 72 73 #: content.module:496 74 msgid "!title: !required" 75 msgstr "" 76 77 #: content.module:1854 78 msgid "Basic" 79 msgstr "" 80 81 #: content.module:1867;1870 82 msgid "RSS" 83 msgstr "" 84 85 #: content.module:1880 86 msgid "Search" 87 msgstr "" 88 89 #: content.module:1883 90 msgid "Search Index" 91 msgstr "" 92 93 #: content.module:1887 94 msgid "Search Result" 95 msgstr "" 96 97 #: content.module:1897;1900 98 msgid "Print" 99 msgstr "" 100 101 #: content.module:2348;2355 102 msgid "Node module form." 103 msgstr "" 104 105 #: content.module:2362 106 msgid "Language" 107 msgstr "" 108 109 #: content.module:2363 110 msgid "Locale module form." 111 msgstr "" 112 113 #: content.module:2369 114 msgid "Menu settings" 115 msgstr "" 116 117 #: content.module:2370 118 msgid "Menu module form." 119 msgstr "" 120 121 #: content.module:2376 122 msgid "Taxonomy" 123 msgstr "" 124 125 #: content.module:2377 126 msgid "Taxonomy module form." 127 msgstr "" 128 129 #: content.module:2383 130 msgid "Book" 131 msgstr "" 132 133 #: content.module:2384 134 msgid "Book module form." 135 msgstr "" 136 137 #: content.module:2390 138 msgid "Poll title" 139 msgstr "" 140 141 #: content.module:2391 142 msgid "Poll module title." 143 msgstr "" 144 145 #: content.module:2395 146 msgid "Poll choices" 147 msgstr "" 148 149 #: content.module:2396 150 msgid "Poll module choices." 151 msgstr "" 152 153 #: content.module:2400 154 msgid "Poll settings" 155 msgstr "" 156 157 #: content.module:2401 158 msgid "Poll module settings." 159 msgstr "" 160 161 #: content.module:2407 162 msgid "File attachments" 163 msgstr "" 164 165 #: content.module:2408 166 msgid "Upload module form." 167 msgstr "" 168 169 #: content.module:595 170 msgid "Updating field type %type with module %module." 171 msgstr "" 172 173 #: content.module:602 174 msgid "Updating widget type %type with module %module." 175 msgstr "" 176 177 #: content.module:60 178 msgid "Use PHP input for field settings (dangerous - grant with care)" 179 msgstr "" 180 181 #: content.module:79 182 msgid "Fields" 183 msgstr "" 184 185 #: content.module:101 186 msgid "Manage fields" 187 msgstr "" 188 189 #: content.module:110 190 msgid "Display fields" 191 msgstr "" 192 193 #: content.module:141 194 msgid "Remove field" 195 msgstr "" 196 197 #: content.install:236 198 msgid "Updates for CCK-related modules are not run until the modules are enabled on the <a href=\"@admin-modules-path\">administer modules page</a>. When you enable them, you'll need to return to <a href=\"@update-php\">update.php</a> and run the remaining updates." 199 msgstr "" 200 201 #: content.install:239 202 msgid "!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." 203 msgstr "" 204 205 #: content.install:244 206 msgid "!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." 207 msgstr "" 208 209 #: content.install:251 210 msgid "Some updates are still pending. Please return to <a href=\"@update-php\">update.php</a> and run the remaining updates." 211 msgstr "" 212 213 #: content.install:252 214 msgid "Some updates are still pending.<br/>Please re-run the update script." 215 msgstr "" 216 217 #: (duplicate) content.install:10 218 msgid "CCK - No Views integration" 219 msgstr "" 220 221 #: (duplicate) content.install:11 222 msgid "CCK integration with Views module requires Views 6.x-2.0-rc2 or greater." 223 msgstr "" 224 225 #: content.info:0 includes/content.rules.inc:19;212 includes/views/content.views.inc:180;261 226 msgid "Content" 227 msgstr "" 228 229 #: content.info:0 230 msgid "Allows administrators to define new content types." 231 msgstr "" 232 233 #: content.info:0 modules/content_copy/content_copy.info:0 modules/content_permissions/content_permissions.info:0 modules/fieldgroup/fieldgroup.info:0 modules/nodereference/nodereference.info:0 modules/number/number.info:0 modules/optionwidgets/optionwidgets.info:0 modules/text/text.info:0 modules/userreference/userreference.info:0 234 msgid "CCK" 235 msgstr "" 236
title
Description
Body
title
Description
Body
title
Description
Body
title
Body
| Generated: Mon Jul 9 18:01:44 2012 | Cross-referenced by PHPXref 0.7 |