[TASK] XLIFF: Add translation hint to labels, which must not be
[Packages/TYPO3.CMS.git] / typo3 / sysext / context_help / 4.5 / locallang_csh_ttcontent.xlf
1 <?xml version="1.0" encoding="UTF-8"?>
2 <xliff version="1.0">
3 <file source-language="EN" target-language="en" datatype="plaintext" original="messages" date="Lun 1 aoĆ» 2011 20:03:23 UTC" product-name="context_help">
4 <header/>
5 <body>
6 <trans-unit id=".description" approved="yes">
7 <source>All visible content on webpages is typically made by "Page Content" records, often referred to as "Content Elements". Content Elements are managed by the "Page" Module which organizes Content Elements in multiple columns and languages.</source>
8 <target>All visible content on webpages is typically made by "Page Content" records, often referred to as "Content Elements". Content Elements are managed by the "Page" Module which organizes Content Elements in multiple columns and languages.</target>
9 </trans-unit>
10 <trans-unit id=".details" approved="yes">
11 <source>"Page Content" records are sortable and can be rearranged. The "Language" and "Column" selectors of the "Page Content" records determines when and where they appear. If you do not change the value of the "Language" and "Column" selectors the Content Element will appear in the default configuration.</source>
12 <target>"Page Content" records are sortable and can be rearranged. The "Language" and "Column" selectors of the "Page Content" records determines when and where they appear. If you do not change the value of the "Language" and "Column" selectors the Content Element will appear in the default configuration.</target>
13 </trans-unit>
14 <trans-unit id="_.seeAlso" approved="yes">
15 <source>Page Content Principles | http://typo3.org/documentation/document-library/doc_tut_quickstart/Page_content/,
16 _MOD_web_layout</source>
17 <target>Page Content Principles | http://typo3.org/documentation/document-library/doc_tut_quickstart/Page_content/,
18 _MOD_web_layout</target>
19 </trans-unit>
20 <trans-unit id="_.image" approved="yes">
21 <source>EXT:context_help/cshimages/ttcontent_1.png,
22 EXT:context_help/cshimages/ttcontent_2.png,
23 EXT:context_help/cshimages/ttcontent_3.png</source>
24 <target>EXT:context_help/cshimages/ttcontent_1.png,
25 EXT:context_help/cshimages/ttcontent_2.png,
26 EXT:context_help/cshimages/ttcontent_3.png</target>
27 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
28 </trans-unit>
29 <trans-unit id=".image_descr" approved="yes">
30 <source>The Page Module is used to manage Content Elements arranged in columns and languages.
31 A Content Element has an editing form with many options. The "Type" determines which options are visible.
32 In the Frontend, a Content Element like the above could look like this.</source>
33 <target>The Page Module is used to manage Content Elements arranged in columns and languages.
34 A Content Element has an editing form with many options. The "Type" determines which options are visible.
35 In the Frontend, a Content Element like the above could look like this.</target>
36 </trans-unit>
37 <trans-unit id="CType.description" approved="yes">
38 <source>Select the kind of Page Content this element represents. New options will appear when you save the record.</source>
39 <target>Select the kind of Page Content this element represents. New options will appear when you save the record.</target>
40 </trans-unit>
41 <trans-unit id="CType.details" approved="yes">
42 <source>The 'Type' of content you select determines which options are available in the editing form so be sure to save the record before making other changes.
43
44 This is a description of the various types:
45
46 &lt;strong&gt;Header&lt;/strong&gt;
47 This type allows you to insert a standard Content Element header and nothing more.
48 Almost all the other types described below also include the Header and its options. The Header type provides a way to insert a header without any other content.
49
50 &lt;strong&gt;Text&lt;/strong&gt;
51 The Text type allows you to insert regular page content. It is generally used for text only content.
52
53 &lt;strong&gt;Text &amp; Images&lt;/strong&gt;
54 This is the same as the Text type (regular page content) but with the option of attaching images.
55
56 &lt;strong&gt;Image&lt;/strong&gt;
57 The Image type allows you to insert image only page content.
58
59 &lt;strong&gt;Bullet List&lt;/strong&gt;
60 Lets you create a bullet list. Each line in the text field will appear as a single bullet.
61
62 &lt;strong&gt;Table&lt;/strong&gt;
63 Lets you create &lt;em&gt;simple&lt;/em&gt; tables. Each line represents a row in the table and vertical bars ('|') separate each column. A popup wizard is also available.
64
65 &lt;strong&gt;File Links&lt;/strong&gt;
66 Allows you to present a list of files for download. Thumbnails can be attached to the list and you can also display the file size.
67
68 &lt;strong&gt;Form&lt;/strong&gt;
69 Lets you create mail forms using a special syntax or a popup wizard.
70
71 &lt;strong&gt;Search&lt;/strong&gt;
72 This inserts a search box and also shows the search results when a search is performed on the page.
73
74 &lt;strong&gt;Login&lt;/strong&gt;
75 Displays a login box for website users. This is only useful if you have already created website users and usergroups.
76
77 &lt;strong&gt;Menu/Sitemap&lt;/strong&gt;
78 Offers a selection of menus and a sitemap you can insert on a page.
79
80 &lt;strong&gt;Insert records&lt;/strong&gt;
81 This acts as placeholder for other records. With this Content Element, you can resuse multiple content elements from other pages.
82
83 &lt;strong&gt;Insert plugin&lt;/strong&gt;
84 This will allows you to insert news, forums, guestbooks, lists of addresses, and other functionality. Plugins are typically provided by TYPO3 extensions. The available fields and required configuration depend on the extension.
85
86 &lt;strong&gt;Divider&lt;/strong&gt;
87 This inserts a simple horizontal rule on a page.
88
89 &lt;strong&gt;HTML&lt;/strong&gt;
90 This is plain HTML content. Anything added in the HTML Code of this Content Element will be displayed directly on the page without any preprocessing.</source>
91 <target>The 'Type' of content you select determines which options are available in the editing form so be sure to save the record before making other changes.
92
93 This is a description of the various types:
94
95 &lt;strong&gt;Header&lt;/strong&gt;
96 This type allows you to insert a standard Content Element header and nothing more.
97 Almost all the other types described below also include the Header and its options. The Header type provides a way to insert a header without any other content.
98
99 &lt;strong&gt;Text&lt;/strong&gt;
100 The Text type allows you to insert regular page content. It is generally used for text only content.
101
102 &lt;strong&gt;Text &amp; Images&lt;/strong&gt;
103 This is the same as the Text type (regular page content) but with the option of attaching images.
104
105 &lt;strong&gt;Image&lt;/strong&gt;
106 The Image type allows you to insert image only page content.
107
108 &lt;strong&gt;Bullet List&lt;/strong&gt;
109 Lets you create a bullet list. Each line in the text field will appear as a single bullet.
110
111 &lt;strong&gt;Table&lt;/strong&gt;
112 Lets you create &lt;em&gt;simple&lt;/em&gt; tables. Each line represents a row in the table and vertical bars ('|') separate each column. A popup wizard is also available.
113
114 &lt;strong&gt;File Links&lt;/strong&gt;
115 Allows you to present a list of files for download. Thumbnails can be attached to the list and you can also display the file size.
116
117 &lt;strong&gt;Form&lt;/strong&gt;
118 Lets you create mail forms using a special syntax or a popup wizard.
119
120 &lt;strong&gt;Search&lt;/strong&gt;
121 This inserts a search box and also shows the search results when a search is performed on the page.
122
123 &lt;strong&gt;Login&lt;/strong&gt;
124 Displays a login box for website users. This is only useful if you have already created website users and usergroups.
125
126 &lt;strong&gt;Menu/Sitemap&lt;/strong&gt;
127 Offers a selection of menus and a sitemap you can insert on a page.
128
129 &lt;strong&gt;Insert records&lt;/strong&gt;
130 This acts as placeholder for other records. With this Content Element, you can resuse multiple content elements from other pages.
131
132 &lt;strong&gt;Insert plugin&lt;/strong&gt;
133 This will allows you to insert news, forums, guestbooks, lists of addresses, and other functionality. Plugins are typically provided by TYPO3 extensions. The available fields and required configuration depend on the extension.
134
135 &lt;strong&gt;Divider&lt;/strong&gt;
136 This inserts a simple horizontal rule on a page.
137
138 &lt;strong&gt;HTML&lt;/strong&gt;
139 This is plain HTML content. Anything added in the HTML Code of this Content Element will be displayed directly on the page without any preprocessing.</target>
140 </trans-unit>
141 <trans-unit id="_CType.seeAlso" approved="yes">
142 <source>tt_content:colPos,
143 tt_content:sys_language_uid,
144 About Content Elements | http://typo3.org/documentation/document-library/doc_tut_quickstart/Content_element_type/</source>
145 <target>tt_content:colPos,
146 tt_content:sys_language_uid,
147 About Content Elements | http://typo3.org/documentation/document-library/doc_tut_quickstart/Content_element_type/</target>
148 <note from="developer">A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note>
149 </trans-unit>
150 <trans-unit id="_CType.image" approved="yes">
151 <source>EXT:context_help/cshimages/ttcontent_4.png</source>
152 <target>EXT:context_help/cshimages/ttcontent_4.png</target>
153 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
154 </trans-unit>
155 <trans-unit id="hidden.description" approved="yes">
156 <source>Check this box if you wish to disable the Content Element and keep it from being displayed on the website.</source>
157 <target>Check this box if you wish to disable the Content Element and keep it from being displayed on the website.</target>
158 </trans-unit>
159 <trans-unit id="_hidden.seeAlso" approved="yes">
160 <source>tt_content:starttime,
161 tt_content:endtime,
162 tt_content:fe_group,
163 tt_content:colPos,
164 tt_content:sys_language_uid</source>
165 <target>tt_content:starttime,
166 tt_content:endtime,
167 tt_content:fe_group,
168 tt_content:colPos,
169 tt_content:sys_language_uid</target>
170 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
171 </trans-unit>
172 <trans-unit id="starttime.description" approved="yes">
173 <source>Enter the date when the Content Element should be published and displayed on the website.</source>
174 <target>Enter the date when the Content Element should be published and displayed on the website.</target>
175 </trans-unit>
176 <trans-unit id="_starttime.seeAlso" approved="yes">
177 <source>pages:starttime,
178 tt_content:endtime,
179 tt_content:hidden,
180 tt_content:fe_group</source>
181 <target>pages:starttime,
182 tt_content:endtime,
183 tt_content:hidden,
184 tt_content:fe_group</target>
185 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
186 </trans-unit>
187 <trans-unit id="endtime.description" approved="yes">
188 <source>Enter the date when the Content Element should expire and disappear from the website.</source>
189 <target>Enter the date when the Content Element should expire and disappear from the website.</target>
190 </trans-unit>
191 <trans-unit id="_endtime.seeAlso" approved="yes">
192 <source>pages:endtime,
193 tt_content:starttime,
194 tt_content:hidden,
195 tt_content:fe_group</source>
196 <target>pages:endtime,
197 tt_content:starttime,
198 tt_content:hidden,
199 tt_content:fe_group</target>
200 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
201 </trans-unit>
202 <trans-unit id="fe_group.description" approved="yes">
203 <source>If Usergroup Access Rights are set to a usergroup name, only website users who are logged in and members of the selected usergroup will be able to view the Content Element. The special option 'Hide at Login' means the Content Element will &lt;em&gt;not&lt;/em&gt; be visible for any website users that are logged in. Likewise "Show at Any Login" will make the Content Element visible for any logged in website user.</source>
204 <target>If Usergroup Access Rights are set to a usergroup name, only website users who are logged in and members of the selected usergroup will be able to view the Content Element. The special option 'Hide at Login' means the Content Element will &lt;em&gt;not&lt;/em&gt; be visible for any website users that are logged in. Likewise "Show at Any Login" will make the Content Element visible for any logged in website user.</target>
205 </trans-unit>
206 <trans-unit id="fe_group.details" approved="yes">
207 <source>The 'Hide at Login' option is is useful if you want to present information like "How to Login" that becomes irrelevant when a website user is actually logged in.</source>
208 <target>The 'Hide at Login' option is is useful if you want to present information like "How to Login" that becomes irrelevant when a website user is actually logged in.</target>
209 </trans-unit>
210 <trans-unit id="_fe_group.seeAlso" approved="yes">
211 <source>tt_content:hidden,
212 tt_content:starttime,
213 tt_content:endtime,
214 pages:fe_group,
215 fe_users,
216 fe_groups</source>
217 <target>tt_content:hidden,
218 tt_content:starttime,
219 tt_content:endtime,
220 pages:fe_group,
221 fe_users,
222 fe_groups</target>
223 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
224 </trans-unit>
225 <trans-unit id="sys_language_uid.description" approved="yes">
226 <source>Select the system language of this Content Element. &lt;strong&gt;Notice:&lt;/strong&gt; This will affect the Content Element visibility by limiting it to a certain language.</source>
227 <target>Select the system language of this Content Element. &lt;strong&gt;Notice:&lt;/strong&gt; This will affect the Content Element visibility by limiting it to a certain language.</target>
228 </trans-unit>
229 <trans-unit id="sys_language_uid.details" approved="yes">
230 <source>This allows you to assign a specific language to the Content Element. If you select anything but the default value, the element will &lt;em&gt;not&lt;/em&gt; be visible unless the language assigned is also configured by the TypoScript template.
231 The available system languages are created by the administrator.</source>
232 <target>This allows you to assign a specific language to the Content Element. If you select anything but the default value, the element will &lt;em&gt;not&lt;/em&gt; be visible unless the language assigned is also configured by the TypoScript template.
233 The available system languages are created by the administrator.</target>
234 </trans-unit>
235 <trans-unit id="_sys_language_uid.seeAlso" approved="yes">
236 <source>tt_content:colPos,
237 sys_language,
238 Localization concepts [Technical] | http://typo3.org/documentation/tips-tricks/multi-language-sites-in-typo3/,
239 _MOD_web_layout:language_list</source>
240 <target>tt_content:colPos,
241 sys_language,
242 Localization concepts [Technical] | http://typo3.org/documentation/tips-tricks/multi-language-sites-in-typo3/,
243 _MOD_web_layout:language_list</target>
244 <note from="developer">A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note>
245 </trans-unit>
246 <trans-unit id="layout.description" approved="yes">
247 <source>Select a Layout.</source>
248 <target>Select a Layout.</target>
249 </trans-unit>
250 <trans-unit id="layout.details" approved="yes">
251 <source>This option does not work by default for all Content Elements but your website may display Content Elements differently depending on the layout.
252
253 The File Links Content Element does make use of the Layout field by default:
254 "Normal" will provide a list of file links with no thumbnail.
255 "Layout 1" adds a file icon to the left of the link
256 "Layout 2" adds a thumbnail for image files and an icon for other files. A black border is wrapped around the icon.
257 "Layout 3" is similar to Layout 2, but without the black border.</source>
258 <target>This option does not work by default for all Content Elements but your website may display Content Elements differently depending on the layout.
259
260 The File Links Content Element does make use of the Layout field by default:
261 "Normal" will provide a list of file links with no thumbnail.
262 "Layout 1" adds a file icon to the left of the link
263 "Layout 2" adds a thumbnail for image files and an icon for other files. A black border is wrapped around the icon.
264 "Layout 3" is similar to Layout 2, but without the black border.</target>
265 </trans-unit>
266 <trans-unit id="colPos.description" approved="yes">
267 <source>Select the column position of this element. &lt;strong&gt;Notice:&lt;/strong&gt; This may affect whether the Content Element is visible depending on your website template.</source>
268 <target>Select the column position of this element. &lt;strong&gt;Notice:&lt;/strong&gt; This may affect whether the Content Element is visible depending on your website template.</target>
269 </trans-unit>
270 <trans-unit id="colPos.details" approved="yes">
271 <source>Many websites only use one column of content. Some templates, however, let you put content in multiple columns using the Column option.
272
273 &lt;strong&gt;Notice:&lt;/strong&gt; Selecting a column other than "Normal" may cause the Content Element to disappear if the website template does not use that column. If your Content Element mysteriously disappears make sure the Column and Language selectors are set correctly.</source>
274 <target>Many websites only use one column of content. Some templates, however, let you put content in multiple columns using the Column option.
275
276 &lt;strong&gt;Notice:&lt;/strong&gt; Selecting a column other than "Normal" may cause the Content Element to disappear if the website template does not use that column. If your Content Element mysteriously disappears make sure the Column and Language selectors are set correctly.</target>
277 </trans-unit>
278 <trans-unit id="_colPos.seeAlso" approved="yes">
279 <source>tt_content:sys_language_uid,
280 _MOD_web_layout:columns_multi,
281 _MOD_web_layout:columns_single</source>
282 <target>tt_content:sys_language_uid,
283 _MOD_web_layout:columns_multi,
284 _MOD_web_layout:columns_single</target>
285 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
286 </trans-unit>
287 <trans-unit id="date.description" approved="yes">
288 <source>Enter a date to be displayed above the header.</source>
289 <target>Enter a date to be displayed above the header.</target>
290 </trans-unit>
291 <trans-unit id="header.description" approved="yes">
292 <source>Enter header text for the Content Element.</source>
293 <target>Enter header text for the Content Element.</target>
294 </trans-unit>
295 <trans-unit id="header.details" approved="yes">
296 <source>Almost all Content Elements will display this header above the content. If you don't want the header displayed, set the header Layout to "Hidden". You can also choose not to enter any content in this field.
297
298 Some content element types do not display the header by default. In those cases the Header field is typically labeled "Name" instead. One example is the HTML Content Element.</source>
299 <target>Almost all Content Elements will display this header above the content. If you don't want the header displayed, set the header Layout to "Hidden". You can also choose not to enter any content in this field.
300
301 Some content element types do not display the header by default. In those cases the Header field is typically labeled "Name" instead. One example is the HTML Content Element.</target>
302 </trans-unit>
303 <trans-unit id="_header.seeAlso" approved="yes">
304 <source>tt_content:header_position,
305 tt_content:header_link,
306 tt_content:header_layout,
307 tt_content:date,</source>
308 <target>tt_content:header_position,
309 tt_content:header_link,
310 tt_content:header_layout,
311 tt_content:date,</target>
312 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
313 </trans-unit>
314 <trans-unit id="_header.image" approved="yes">
315 <source>EXT:context_help/cshimages/ttcontent_6.png</source>
316 <target>EXT:context_help/cshimages/ttcontent_6.png</target>
317 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
318 </trans-unit>
319 <trans-unit id="header_position.description" approved="yes">
320 <source>Aligns the header to the left, center, or right.</source>
321 <target>Aligns the header to the left, center, or right.</target>
322 </trans-unit>
323 <trans-unit id="_header_position.seeAlso" approved="yes">
324 <source>tt_content:header</source>
325 <target>tt_content:header</target>
326 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
327 </trans-unit>
328 <trans-unit id="header_link.description" approved="yes">
329 <source>Creates a link from the header to a Page ID, email address, or URL.</source>
330 <target>Creates a link from the header to a Page ID, email address, or URL.</target>
331 </trans-unit>
332 <trans-unit id="header_link.syntax" approved="yes">
333 <source>If you insert a Page ID (ex. 51), the link will point to the page with id=51 &lt;em&gt;inside&lt;/em&gt; TYPO3.
334 If you insert an email address (ex. name@my-domain.test), the link will point to that email address.
335 If you insert an URL or domain, (ex. www.typo3.com or http://www.my-domain.org), the link will point to that website.</source>
336 <target>If you insert a Page ID (ex. 51), the link will point to the page with id=51 &lt;em&gt;inside&lt;/em&gt; TYPO3.
337 If you insert an email address (ex. name@my-domain.test), the link will point to that email address.
338 If you insert an URL or domain, (ex. www.typo3.com or http://www.my-domain.org), the link will point to that website.</target>
339 </trans-unit>
340 <trans-unit id="_header_link.seeAlso" approved="yes">
341 <source>tt_content:header</source>
342 <target>tt_content:header</target>
343 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
344 </trans-unit>
345 <trans-unit id="header_layout.description" approved="yes">
346 <source>Select a visual design for the header.</source>
347 <target>Select a visual design for the header.</target>
348 </trans-unit>
349 <trans-unit id="header_layout.details" approved="yes">
350 <source>If you select "Default" the standard design (which is one of the layouts 1-5) will be used.
351 Alternatively you can select from Layout 1 through 5 which are configured in the website template with individual visual designs.
352 If you select "Hidden" the header will simply not appear. This is useful when you don't need a header to display on the website but still want to identify the Content Element in the Backend.</source>
353 <target>If you select "Default" the standard design (which is one of the layouts 1-5) will be used.
354 Alternatively you can select from Layout 1 through 5 which are configured in the website template with individual visual designs.
355 If you select "Hidden" the header will simply not appear. This is useful when you don't need a header to display on the website but still want to identify the Content Element in the Backend.</target>
356 </trans-unit>
357 <trans-unit id="_header_layout.seeAlso" approved="yes">
358 <source>tt_content:header</source>
359 <target>tt_content:header</target>
360 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
361 </trans-unit>
362 <trans-unit id="subheader.description" approved="yes">
363 <source>Enter a subheader to be displayed below the main header. If the Content Element is a "Form" this field is instead used as the Recipient Email.</source>
364 <target>Enter a subheader to be displayed below the main header. If the Content Element is a "Form" this field is instead used as the Recipient Email.</target>
365 </trans-unit>
366 <trans-unit id="subheader.details" approved="yes">
367 <source>A subheader is displayed only with "Header" Content Elements and with "Form" Content Elements (as the Recipient Email).</source>
368 <target>A subheader is displayed only with "Header" Content Elements and with "Form" Content Elements (as the Recipient Email).</target>
369 </trans-unit>
370 <trans-unit id="_subheader.seeAlso" approved="yes">
371 <source>tt_content:header
372 tt_content:bodytext</source>
373 <target>tt_content:header
374 tt_content:bodytext</target>
375 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
376 </trans-unit>
377 <trans-unit id="bodytext.description" approved="yes">
378 <source>Enter the main text.</source>
379 <target>Enter the main text.</target>
380 </trans-unit>
381 <trans-unit id="bodytext.details" approved="yes">
382 <source>The main text of the Content Element is entered here and can be formatted with HTML or a Rich Text Editor.
383 The field is reused in other Content Element types so changing the type will cause any text to be reused in that new Content Element type.
384
385 When you're using this field with the "Text" and "Text &amp; Images" types, the content is normal body text. Each linebreak signifies a new paragraph, you can use the special TYPO3 tag, &amp;lt;LINK&amp;gt;, for making links. You can use many HTML tags but there are limitations depending on your website configuration.
386 A Rich Text Editor is commonly used to add a visual editing interface for 'Text' and 'Text &amp; Images' Content Elements.
387
388 &lt;b&gt;Bullet Lists:&lt;/b&gt;
389 If the type is "Bullet List" each line in this field is a bullet item.
390
391 &lt;b&gt;Tables:&lt;/b&gt;
392 If the type is "Table" each line represents a table row. Within each line, columns are divided by a vertical bar ('|'). A table row with 3 columns could look like "This is column 1 | Column 2 here | Third column!". The table wizard can also be used for creating tables and is much easier than hand coding them.
393
394 &lt;b&gt;Parameters:&lt;/b&gt;
395 Types like "Form" and "Multimedia" use this field for parameters than can be passed to the Content Element. The "HTML" type expects raw HTML which is simply displayed on the website without any processing.
396
397 &lt;b&gt;Making a mail form:&lt;/b&gt;
398 When you have selected the "Form" Content Element you can enter form field and other options. This is a brief example:
399
400 Your name: | *name=input,40 | [Enter name!]
401 Your email: | *email=input,40
402 Your address: | address=textarea,40,10
403 Your haircolor: |hair=radio|Blue=blue, Red=red
404
405 |formtype_mail = submit | Send Form
406 |subject=hidden| Enter a subject here!
407 |html_enabled=hidden | 1
408
409 The first two lines makes input fields for name and email. Both are marked as "required" and are designated by the *, and the name field has a default value of "[Enter name!]".
410 The third line is a text box and the fourth makes radio buttons to select a hair color.
411 After the input fields, there are three important lines in the end. The first makes a submit button with the label "Send Form", the second line is the subject of the email the receiver gets, and the third line formats the email using HTML.
412 Like the table wizard, it is easier to use the form wizard rather than hand coding the forms.
413
414 &lt;b&gt;Note:&lt;/b&gt; For a form to work you must add an email address for the Recipient Email in its field.</source>
415 <target>The main text of the Content Element is entered here and can be formatted with HTML or a Rich Text Editor.
416 The field is reused in other Content Element types so changing the type will cause any text to be reused in that new Content Element type.
417
418 When you're using this field with the "Text" and "Text &amp; Images" types, the content is normal body text. Each linebreak signifies a new paragraph, you can use the special TYPO3 tag, &amp;lt;LINK&amp;gt;, for making links. You can use many HTML tags but there are limitations depending on your website configuration.
419 A Rich Text Editor is commonly used to add a visual editing interface for 'Text' and 'Text &amp; Images' Content Elements.
420
421 &lt;b&gt;Bullet Lists:&lt;/b&gt;
422 If the type is "Bullet List" each line in this field is a bullet item.
423
424 &lt;b&gt;Tables:&lt;/b&gt;
425 If the type is "Table" each line represents a table row. Within each line, columns are divided by a vertical bar ('|'). A table row with 3 columns could look like "This is column 1 | Column 2 here | Third column!". The table wizard can also be used for creating tables and is much easier than hand coding them.
426
427 &lt;b&gt;Parameters:&lt;/b&gt;
428 Types like "Form" and "Multimedia" use this field for parameters than can be passed to the Content Element. The "HTML" type expects raw HTML which is simply displayed on the website without any processing.
429
430 &lt;b&gt;Making a mail form:&lt;/b&gt;
431 When you have selected the "Form" Content Element you can enter form field and other options. This is a brief example:
432
433 Your name: | *name=input,40 | [Enter name!]
434 Your email: | *email=input,40
435 Your address: | address=textarea,40,10
436 Your haircolor: |hair=radio|Blue=blue, Red=red
437
438 |formtype_mail = submit | Send Form
439 |subject=hidden| Enter a subject here!
440 |html_enabled=hidden | 1
441
442 The first two lines makes input fields for name and email. Both are marked as "required" and are designated by the *, and the name field has a default value of "[Enter name!]".
443 The third line is a text box and the fourth makes radio buttons to select a hair color.
444 After the input fields, there are three important lines in the end. The first makes a submit button with the label "Send Form", the second line is the subject of the email the receiver gets, and the third line formats the email using HTML.
445 Like the table wizard, it is easier to use the form wizard rather than hand coding the forms.
446
447 &lt;b&gt;Note:&lt;/b&gt; For a form to work you must add an email address for the Recipient Email in its field.</target>
448 </trans-unit>
449 <trans-unit id="_bodytext.seeAlso" approved="yes">
450 <source>tt_content:CType,
451 tt_content:subheader,
452 xMOD_csh_corebe:wizard_forms_wiz,
453 xMOD_csh_corebe:wizard_table_wiz</source>
454 <target>tt_content:CType,
455 tt_content:subheader,
456 xMOD_csh_corebe:wizard_forms_wiz,
457 xMOD_csh_corebe:wizard_table_wiz</target>
458 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
459 </trans-unit>
460 <trans-unit id="text_align.description" approved="yes">
461 <source>Aligns the body text to the left, center, or right.</source>
462 <target>Aligns the body text to the left, center, or right.</target>
463 </trans-unit>
464 <trans-unit id="text_align.details" approved="yes">
465 <source>See Page Content / Fontface for comments.
466 &lt;b&gt;Note:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
467 <target>See Page Content / Fontface for comments.
468 &lt;b&gt;Note:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
469 </trans-unit>
470 <trans-unit id="_text_align.seeAlso" approved="yes">
471 <source>tt_content:text_face,
472 tt_content:bodytext</source>
473 <target>tt_content:text_face,
474 tt_content:bodytext</target>
475 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
476 </trans-unit>
477 <trans-unit id="text_face.description" approved="yes">
478 <source>Select a font face family for the body text.</source>
479 <target>Select a font face family for the body text.</target>
480 </trans-unit>
481 <trans-unit id="text_face.details" approved="yes">
482 <source>&lt;strong&gt;Notice:&lt;/strong&gt; These options are meant for special design. The general (default) design should be configured in the template instead. Furthermore you should NOT use these options if your template implements stylesheets and are based on using styles in general.</source>
483 <target>&lt;strong&gt;Notice:&lt;/strong&gt; These options are meant for special design. The general (default) design should be configured in the template instead. Furthermore you should NOT use these options if your template implements stylesheets and are based on using styles in general.</target>
484 </trans-unit>
485 <trans-unit id="_text_face.seeAlso" approved="yes">
486 <source>tt_content:text_face,
487 tt_content:bodytext</source>
488 <target>tt_content:text_face,
489 tt_content:bodytext</target>
490 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
491 </trans-unit>
492 <trans-unit id="text_size.description" approved="yes">
493 <source>Select a font size for the body text.</source>
494 <target>Select a font size for the body text.</target>
495 </trans-unit>
496 <trans-unit id="text_size.details" approved="yes">
497 <source>See Page Content / Fontface for comments.
498 &lt;b&gt;Note:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
499 <target>See Page Content / Fontface for comments.
500 &lt;b&gt;Note:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
501 </trans-unit>
502 <trans-unit id="_text_size.seeAlso" approved="yes">
503 <source>tt_content:text_face,
504 tt_content:bodytext</source>
505 <target>tt_content:text_face,
506 tt_content:bodytext</target>
507 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
508 </trans-unit>
509 <trans-unit id="text_color.description" approved="yes">
510 <source>Select a color for the body text.</source>
511 <target>Select a color for the body text.</target>
512 </trans-unit>
513 <trans-unit id="text_color.details" approved="yes">
514 <source>See Page Content / Fontface for comments.
515 &lt;b&gt;Note:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
516 <target>See Page Content / Fontface for comments.
517 &lt;b&gt;Note:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
518 </trans-unit>
519 <trans-unit id="_text_color.seeAlso" approved="yes">
520 <source>tt_content:text_face,
521 tt_content:bodytext</source>
522 <target>tt_content:text_face,
523 tt_content:bodytext</target>
524 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
525 </trans-unit>
526 <trans-unit id="text_properties.description" approved="yes">
527 <source>Select additional font properties.</source>
528 <target>Select additional font properties.</target>
529 </trans-unit>
530 <trans-unit id="text_properties.details" approved="yes">
531 <source>These options will select font properties for all the body text. However you may wish to mark only a part of the bodytext as bold or underline in which case you should use the formatting options in the Rich Text Editor. Alternatively you can use the HTML tags here:
532
533 &amp;lt;b&amp;gt;&lt;strong&gt;This is bold&lt;/strong&gt;&amp;lt;b&amp;gt;
534 &amp;lt;i&amp;gt;&lt;em&gt;This is italics&lt;/em&gt;&amp;lt;i&amp;gt;
535 &amp;lt;u&amp;gt;&lt;u&gt;This is underlined&lt;/u&gt;&amp;lt;u&amp;gt;
536
537 See Page Content / Fontface for comments.
538 &lt;b&gt;Note:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
539 <target>These options will select font properties for all the body text. However you may wish to mark only a part of the bodytext as bold or underline in which case you should use the formatting options in the Rich Text Editor. Alternatively you can use the HTML tags here:
540
541 &amp;lt;b&amp;gt;&lt;strong&gt;This is bold&lt;/strong&gt;&amp;lt;b&amp;gt;
542 &amp;lt;i&amp;gt;&lt;em&gt;This is italics&lt;/em&gt;&amp;lt;i&amp;gt;
543 &amp;lt;u&amp;gt;&lt;u&gt;This is underlined&lt;/u&gt;&amp;lt;u&amp;gt;
544
545 See Page Content / Fontface for comments.
546 &lt;b&gt;Note:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
547 </trans-unit>
548 <trans-unit id="_text_properties.seeAlso" approved="yes">
549 <source>tt_content:text_face,
550 tt_content:bodytext</source>
551 <target>tt_content:text_face,
552 tt_content:bodytext</target>
553 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
554 </trans-unit>
555 <trans-unit id="image.description" approved="yes">
556 <source>Insert one or more images.</source>
557 <target>Insert one or more images.</target>
558 </trans-unit>
559 <trans-unit id="image.details" approved="yes">
560 <source>You can attach multiple images to the Content Element.
561 Depending on the configuration of TYPO3, you can attach images in many formats without worrying about size and compression. TYPO3's graphics processing handles these details for you.
562
563 When you use the "Text &amp; Images" type, it's important to select a proper position for images. For this purpose, use the Position and Aligment selector. See link to "Page Content / Position" below.
564 You can also display images in multiple columns and even enable an option that opens full size images when thumbnails are clicked.</source>
565 <target>You can attach multiple images to the Content Element.
566 Depending on the configuration of TYPO3, you can attach images in many formats without worrying about size and compression. TYPO3's graphics processing handles these details for you.
567
568 When you use the "Text &amp; Images" type, it's important to select a proper position for images. For this purpose, use the Position and Aligment selector. See link to "Page Content / Position" below.
569 You can also display images in multiple columns and even enable an option that opens full size images when thumbnails are clicked.</target>
570 </trans-unit>
571 <trans-unit id="_image.seeAlso" approved="yes">
572 <source>tt_content:imagewidth,
573 tt_content:imageheight,
574 tt_content:imageorient,
575 tt_content:imageborder,
576 tt_content:image_noRows,
577 tt_content:image_link,
578 tt_content:image_zoom,
579 tt_content:imagecols,
580 tt_content:imagecaption,
581 tt_content:image_effects,
582 tt_content:image_frames,
583 tt_content:image_compression,
584 Using images ("Getting Started") | http://typo3.org/documentation/document-library/doc_tut_quickstart/Managing_files_in_TY/
585 Using images (Animation) | FILE:EXT:welcome/modsub/ani_10.gif</source>
586 <target>tt_content:imagewidth,
587 tt_content:imageheight,
588 tt_content:imageorient,
589 tt_content:imageborder,
590 tt_content:image_noRows,
591 tt_content:image_link,
592 tt_content:image_zoom,
593 tt_content:imagecols,
594 tt_content:imagecaption,
595 tt_content:image_effects,
596 tt_content:image_frames,
597 tt_content:image_compression,
598 Using images ("Getting Started") | http://typo3.org/documentation/document-library/doc_tut_quickstart/Managing_files_in_TY/
599 Using images (Animation) | FILE:EXT:welcome/modsub/ani_10.gif</target>
600 <note from="developer">A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note>
601 </trans-unit>
602 <trans-unit id="_image.image" approved="yes">
603 <source>EXT:context_help/cshimages/ttcontent_5.png</source>
604 <target>EXT:context_help/cshimages/ttcontent_5.png</target>
605 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
606 </trans-unit>
607 <trans-unit id="image.image_descr" approved="yes">
608 <source>This shows all the options related to inserting images in Content Elements. Depending on user permissions, you may not be able to use all of them.</source>
609 <target>This shows all the options related to inserting images in Content Elements. Depending on user permissions, you may not be able to use all of them.</target>
610 </trans-unit>
611 <trans-unit id="imagewidth.description" approved="yes">
612 <source>Enter the width (in pixels) for displaying the image in the Frontend of your website.</source>
613 <target>Enter the width (in pixels) for displaying the image in the Frontend of your website.</target>
614 </trans-unit>
615 <trans-unit id="imagewidth.details" approved="yes">
616 <source>The TypoScript template is normally configured with maximum image width so you shouldn't need to specify a width. In unique cases, this provides additional flexibility though.</source>
617 <target>The TypoScript template is normally configured with maximum image width so you shouldn't need to specify a width. In unique cases, this provides additional flexibility though.</target>
618 </trans-unit>
619 <trans-unit id="_imagewidth.seeAlso" approved="yes">
620 <source>tt_content:imageheight,
621 tt_content:image</source>
622 <target>tt_content:imageheight,
623 tt_content:image</target>
624 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
625 </trans-unit>
626 <trans-unit id="imageheight.description" approved="yes">
627 <source>Enter the height (in pixels) for displaying the images in the Frontend of your website.</source>
628 <target>Enter the height (in pixels) for displaying the images in the Frontend of your website.</target>
629 </trans-unit>
630 <trans-unit id="_imageheight.seeAlso" approved="yes">
631 <source>tt_content:imagewidth,
632 tt_content:image</source>
633 <target>tt_content:imagewidth,
634 tt_content:image</target>
635 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
636 </trans-unit>
637 <trans-unit id="imageorient.description" approved="yes">
638 <source>Select the position and alignment of the images relative to the body text.</source>
639 <target>Select the position and alignment of the images relative to the body text.</target>
640 </trans-unit>
641 <trans-unit id="imageorient.details" approved="yes">
642 <source>The positions above and below the body text are pretty straight forward.
643 The options for "In text" mean that images are displayed with text wrapped around them. When you select this option the template will probably force the images into smaller dimensions to accomodate the width of the template and the width of the text. The bodytext will float &lt;em&gt;under&lt;/em&gt; the image block when it reaches the end of the image block. In other words, the body text &lt;em&gt;wraps around&lt;/em&gt; the image block. If you select "In text" below the "No wrap" divider, the body text will not float under the image block, but simply continue in its column.
644 Apart from the visual difference there is a technical aspect as well. If you choose to allow the content to wrap the image block you will experience a strange phenomenon when you do not have enough bodytext to make it float around the image: subsequent content elements on the page will appear to be layered on top of the image block. However it's easily solved by changing the "In text" position to the equal value but below the "No wrap" divider.</source>
645 <target>The positions above and below the body text are pretty straight forward.
646 The options for "In text" mean that images are displayed with text wrapped around them. When you select this option the template will probably force the images into smaller dimensions to accomodate the width of the template and the width of the text. The bodytext will float &lt;em&gt;under&lt;/em&gt; the image block when it reaches the end of the image block. In other words, the body text &lt;em&gt;wraps around&lt;/em&gt; the image block. If you select "In text" below the "No wrap" divider, the body text will not float under the image block, but simply continue in its column.
647 Apart from the visual difference there is a technical aspect as well. If you choose to allow the content to wrap the image block you will experience a strange phenomenon when you do not have enough bodytext to make it float around the image: subsequent content elements on the page will appear to be layered on top of the image block. However it's easily solved by changing the "In text" position to the equal value but below the "No wrap" divider.</target>
648 </trans-unit>
649 <trans-unit id="imageborder.description" approved="yes">
650 <source>Displays a colored border around the images.</source>
651 <target>Displays a colored border around the images.</target>
652 </trans-unit>
653 <trans-unit id="_imageborder.seeAlso" approved="yes">
654 <source>tt_content:imagecols,
655 tt_content:image</source>
656 <target>tt_content:imagecols,
657 tt_content:image</target>
658 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
659 </trans-unit>
660 <trans-unit id="image_noRows.description" approved="yes">
661 <source>Disables tablerows in the image block.</source>
662 <target>Disables tablerows in the image block.</target>
663 </trans-unit>
664 <trans-unit id="image_noRows.details" approved="yes">
665 <source>To illustrate, imagine you have 2 or more columns &lt;em&gt;and&lt;/em&gt; rows of images. If one image in the upper row is taller than the second this will generate empty space beneath the second image. This is due to the normal flow in which the images are placed in table cells.
666 If you enable the No Rows option, the table will place the images in a column into a single table cell which make the distance between them vertically identical throughout. This may provide a better look if the alternative is unacceptable.</source>
667 <target>To illustrate, imagine you have 2 or more columns &lt;em&gt;and&lt;/em&gt; rows of images. If one image in the upper row is taller than the second this will generate empty space beneath the second image. This is due to the normal flow in which the images are placed in table cells.
668 If you enable the No Rows option, the table will place the images in a column into a single table cell which make the distance between them vertically identical throughout. This may provide a better look if the alternative is unacceptable.</target>
669 </trans-unit>
670 <trans-unit id="_image_noRows.seeAlso" approved="yes">
671 <source>tt_content:imagecols,
672 tt_content:image</source>
673 <target>tt_content:imagecols,
674 tt_content:image</target>
675 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
676 </trans-unit>
677 <trans-unit id="image_link.description" approved="yes">
678 <source>Enter a link for the image. For multiple images, separate the links with commas.</source>
679 <target>Enter a link for the image. For multiple images, separate the links with commas.</target>
680 </trans-unit>
681 <trans-unit id="image_link.details" approved="yes">
682 <source>By default all images share the same link. Your TypoScript template may be configured to allow a separate link for each image. If this is the case, you simply separate the links with a comma.
683
684 See Page Content&gt;Link below for details on syntax.</source>
685 <target>By default all images share the same link. Your TypoScript template may be configured to allow a separate link for each image. If this is the case, you simply separate the links with a comma.
686
687 See Page Content&gt;Link below for details on syntax.</target>
688 </trans-unit>
689 <trans-unit id="_image_link.seeAlso" approved="yes">
690 <source>tt_content:header_link,
691 tt_content:image_zoom,
692 tt_content:image</source>
693 <target>tt_content:header_link,
694 tt_content:image_zoom,
695 tt_content:image</target>
696 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
697 </trans-unit>
698 <trans-unit id="image_zoom.description" approved="yes">
699 <source>When enabled, clicking an image will open a larger version in a popup window.</source>
700 <target>When enabled, clicking an image will open a larger version in a popup window.</target>
701 </trans-unit>
702 <trans-unit id="image_zoom.details" approved="yes">
703 <source>This option overrides the value in the Links field.</source>
704 <target>This option overrides the value in the Links field.</target>
705 </trans-unit>
706 <trans-unit id="_image_zoom.seeAlso" approved="yes">
707 <source>tt_content:image_link,
708 tt_content:image</source>
709 <target>tt_content:image_link,
710 tt_content:image</target>
711 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
712 </trans-unit>
713 <trans-unit id="image_effects.description" approved="yes">
714 <source>Select special image processing effects, such as rotation and color adjustments.</source>
715 <target>Select special image processing effects, such as rotation and color adjustments.</target>
716 </trans-unit>
717 <trans-unit id="_image_effects.seeAlso" approved="yes">
718 <source>tt_content:image_compression,
719 tt_content:image_frames,
720 tt_content:image</source>
721 <target>tt_content:image_compression,
722 tt_content:image_frames,
723 tt_content:image</target>
724 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
725 </trans-unit>
726 <trans-unit id="image_frames.description" approved="yes">
727 <source>Select special image framing options.</source>
728 <target>Select special image framing options.</target>
729 </trans-unit>
730 <trans-unit id="_image_frames.seeAlso" approved="yes">
731 <source>tt_content:image_compression,
732 tt_content:image_effects,
733 tt_content:image</source>
734 <target>tt_content:image_compression,
735 tt_content:image_effects,
736 tt_content:image</target>
737 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
738 </trans-unit>
739 <trans-unit id="image_compression.description" approved="yes">
740 <source>Select image quality and image type options.</source>
741 <target>Select image quality and image type options.</target>
742 </trans-unit>
743 <trans-unit id="_image_compression.seeAlso" approved="yes">
744 <source>tt_content:image_frames,
745 tt_content:image_effects,
746 tt_content:image</source>
747 <target>tt_content:image_frames,
748 tt_content:image_effects,
749 tt_content:image</target>
750 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
751 </trans-unit>
752 <trans-unit id="imagecols.description" approved="yes">
753 <source>Set the number of columns when the images are displayed in the Frontend of the website.</source>
754 <target>Set the number of columns when the images are displayed in the Frontend of the website.</target>
755 </trans-unit>
756 <trans-unit id="_imagecols.seeAlso" approved="yes">
757 <source>tt_content:image_noRows,
758 tt_content:image</source>
759 <target>tt_content:image_noRows,
760 tt_content:image</target>
761 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
762 </trans-unit>
763 <trans-unit id="imagecaption.description" approved="yes">
764 <source>Enter captions for the images. For multiple images, enter one caption per line.</source>
765 <target>Enter captions for the images. For multiple images, enter one caption per line.</target>
766 </trans-unit>
767 <trans-unit id="imagecaption.details" approved="yes">
768 <source>By default, the caption is positioned below the images. However, your TypoScript template may be configured to allow individual image captions by setting "styles.content.imgtext.captionSplit=1" in your template constants.
769 In this case, each line in this field will be the image caption of the corresponding image in the list.
770
771 The caption text field is also used by the Content Element type "File Links" where each line represents a description of a file in the list.</source>
772 <target>By default, the caption is positioned below the images. However, your TypoScript template may be configured to allow individual image captions by setting "styles.content.imgtext.captionSplit=1" in your template constants.
773 In this case, each line in this field will be the image caption of the corresponding image in the list.
774
775 The caption text field is also used by the Content Element type "File Links" where each line represents a description of a file in the list.</target>
776 </trans-unit>
777 <trans-unit id="_imagecaption.seeAlso" approved="yes">
778 <source>tt_content:imagecaption_position,
779 tt_content:image</source>
780 <target>tt_content:imagecaption_position,
781 tt_content:image</target>
782 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
783 </trans-unit>
784 <trans-unit id="imagecaption_position.description" approved="yes">
785 <source>Aligns the image captions to the left, center, or right.</source>
786 <target>Aligns the image captions to the left, center, or right.</target>
787 </trans-unit>
788 <trans-unit id="_imagecaption_position.seeAlso" approved="yes">
789 <source>tt_content:imagecaption,
790 tt_content:image</source>
791 <target>tt_content:imagecaption,
792 tt_content:image</target>
793 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
794 </trans-unit>
795 <trans-unit id="cols.description" approved="yes">
796 <source>Select a fixed number of table columns</source>
797 <target>Select a fixed number of table columns</target>
798 </trans-unit>
799 <trans-unit id="pages.description" approved="yes">
800 <source>Select a target page or multiple target pages.</source>
801 <target>Select a target page or multiple target pages.</target>
802 </trans-unit>
803 <trans-unit id="pages.details" approved="yes">
804 <source>This field is used by many of the Content Element types to create a relation to either a single target page or multiple target pages. If no target page is specified, the current page will generally be used.
805
806 Using the "Search" Content Element, the target page is where search results will appear. You must make sure that this page has a similar "Search" Content Element to display the results.
807
808 The "Login" Content Element (not to be confused with the Login plugin available when the felogin extension is installed) also uses this field to redirect the login to a certain page. That page does not need to contain a "Login" Content Element in order to perform the authentication since any TYPO3 page can handle a login request.
809 If you specify a second page in this list, the ID will be passed to the login system as the page inside TYPO3 where website users are found. You should use this only if your template is not already configured to pass this value on.
810 In order for the login procedure to work you must make sure that you have created website users and website usergroups, have specified where these website users can be found (typically a SysFolder), a page ID in the page list, and ensured that cookies are enabled for the site.
811
812 The "Menu/Sitemap" Content Elements also use this field. In this case the page will determine the starting point for the menu or the actual pages shown in the menu. This behavior depends on the menu type you have selected.
813
814 Finally the "Form" element uses this field as the target page to which the form is submitted. A common use is the "Thank you" page after the form is completed.</source>
815 <target>This field is used by many of the Content Element types to create a relation to either a single target page or multiple target pages. If no target page is specified, the current page will generally be used.
816
817 Using the "Search" Content Element, the target page is where search results will appear. You must make sure that this page has a similar "Search" Content Element to display the results.
818
819 The "Login" Content Element (not to be confused with the Login plugin available when the felogin extension is installed) also uses this field to redirect the login to a certain page. That page does not need to contain a "Login" Content Element in order to perform the authentication since any TYPO3 page can handle a login request.
820 If you specify a second page in this list, the ID will be passed to the login system as the page inside TYPO3 where website users are found. You should use this only if your template is not already configured to pass this value on.
821 In order for the login procedure to work you must make sure that you have created website users and website usergroups, have specified where these website users can be found (typically a SysFolder), a page ID in the page list, and ensured that cookies are enabled for the site.
822
823 The "Menu/Sitemap" Content Elements also use this field. In this case the page will determine the starting point for the menu or the actual pages shown in the menu. This behavior depends on the menu type you have selected.
824
825 Finally the "Form" element uses this field as the target page to which the form is submitted. A common use is the "Thank you" page after the form is completed.</target>
826 </trans-unit>
827 <trans-unit id="_pages.seeAlso" approved="yes">
828 <source>tt_content:CType,
829 tt_content:recursive</source>
830 <target>tt_content:CType,
831 tt_content:recursive</target>
832 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
833 </trans-unit>
834 <trans-unit id="recursive.description" approved="yes">
835 <source>The number of subpage levels that should also be included for each page in the list.</source>
836 <target>The number of subpage levels that should also be included for each page in the list.</target>
837 </trans-unit>
838 <trans-unit id="recursive.details" approved="yes">
839 <source>This feature depends on the TypoScript template configuration and Content Element type. If enabled, each page listed in the "Pages" field will also have its subpages included to the specified depth.
840
841 &lt;strong&gt;Warning:&lt;/strong&gt; If there are many subpages, be aware that this option may return a large number of results</source>
842 <target>This feature depends on the TypoScript template configuration and Content Element type. If enabled, each page listed in the "Pages" field will also have its subpages included to the specified depth.
843
844 &lt;strong&gt;Warning:&lt;/strong&gt; If there are many subpages, be aware that this option may return a large number of results</target>
845 </trans-unit>
846 <trans-unit id="_recursive.seeAlso" approved="yes">
847 <source>tt_content:pages</source>
848 <target>tt_content:pages</target>
849 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
850 </trans-unit>
851 <trans-unit id="menu_type.description" approved="yes">
852 <source>Select the type of menu you wish to create.</source>
853 <target>Select the type of menu you wish to create.</target>
854 </trans-unit>
855 <trans-unit id="menu_type.details" approved="yes">
856 <source>This is a short description of each type:
857
858 &lt;strong&gt;Menu of selected pages&lt;/strong&gt;
859 This will create a menu with links to the pages in the Selected Pages list.
860
861 &lt;strong&gt;Menu of subpages of selected pages&lt;/strong&gt;
862 This will create in a menu with links to the subpages of the pages in the Selected Pages list. If you do not specify any pages, the subpages to the current page will be used.
863
864 &lt;strong&gt;Menu of subpages of selected pages (with abstract)&lt;/strong&gt;
865 Like the previous option, but also displays the content of the Abstract field (or the Description field) for each page in the menu. The Abstract field is given priority over the Description field if both are complete.
866
867 &lt;strong&gt;Menu of subpages of selected pages + sections&lt;/strong&gt;
868 Like the previous option, but includes links to all Content Elements on the page that are marked to Show In Section Menus.
869
870 &lt;strong&gt;Sitemap&lt;/strong&gt;
871 Generates a classic tree sitemap. Notice that the sitemap will begin from the current page unless you select another page instead.
872
873 &lt;strong&gt;Section index (page content marked for section menus)&lt;/strong&gt;
874 This makes a menu of Content Elements on the selected pages for all Content Elements marked to Show In Section Menu. This is a great way to make an index at the top of the page.
875 If you don't want certain Content Elements to appear in the list, just uncheck the Show in Section Menus checkbox for those elements.
876
877 &lt;strong&gt;Recently updated pages&lt;/strong&gt;
878 This displays the 10 most recently updated pages.
879 &lt;strong&gt;Notice:&lt;/strong&gt; If you update a page and the updated page is not included in this list, clearing the Page Cache will resolve the issue.
880
881 &lt;strong&gt;Related pages (based on keywords)&lt;/strong&gt;
882 Displays other related pages based on the keywords of the selected pages matched against the keywords of other pages.
883 </source>
884 <target>This is a short description of each type:
885
886 &lt;strong&gt;Menu of selected pages&lt;/strong&gt;
887 This will create a menu with links to the pages in the Selected Pages list.
888
889 &lt;strong&gt;Menu of subpages of selected pages&lt;/strong&gt;
890 This will create in a menu with links to the subpages of the pages in the Selected Pages list. If you do not specify any pages, the subpages to the current page will be used.
891
892 &lt;strong&gt;Menu of subpages of selected pages (with abstract)&lt;/strong&gt;
893 Like the previous option, but also displays the content of the Abstract field (or the Description field) for each page in the menu. The Abstract field is given priority over the Description field if both are complete.
894
895 &lt;strong&gt;Menu of subpages of selected pages + sections&lt;/strong&gt;
896 Like the previous option, but includes links to all Content Elements on the page that are marked to Show In Section Menus.
897
898 &lt;strong&gt;Sitemap&lt;/strong&gt;
899 Generates a classic tree sitemap. Notice that the sitemap will begin from the current page unless you select another page instead.
900
901 &lt;strong&gt;Section index (page content marked for section menus)&lt;/strong&gt;
902 This makes a menu of Content Elements on the selected pages for all Content Elements marked to Show In Section Menu. This is a great way to make an index at the top of the page.
903 If you don't want certain Content Elements to appear in the list, just uncheck the Show in Section Menus checkbox for those elements.
904
905 &lt;strong&gt;Recently updated pages&lt;/strong&gt;
906 This displays the 10 most recently updated pages.
907 &lt;strong&gt;Notice:&lt;/strong&gt; If you update a page and the updated page is not included in this list, clearing the Page Cache will resolve the issue.
908
909 &lt;strong&gt;Related pages (based on keywords)&lt;/strong&gt;
910 Displays other related pages based on the keywords of the selected pages matched against the keywords of other pages.
911 </target>
912 </trans-unit>
913 <trans-unit id="_menu_type.seeAlso" approved="yes">
914 <source>tt_content:pages,
915 tt_content:sectionIndex</source>
916 <target>tt_content:pages,
917 tt_content:sectionIndex</target>
918 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
919 </trans-unit>
920 <trans-unit id="list_type.description" approved="yes">
921 <source>Select a plugin to insert.</source>
922 <target>Select a plugin to insert.</target>
923 </trans-unit>
924 <trans-unit id="list_type.details" approved="yes">
925 <source>The list of plugins you can insert on a page. The available plugins depend on which extensions are installed.</source>
926 <target>The list of plugins you can insert on a page. The available plugins depend on which extensions are installed.</target>
927 </trans-unit>
928 <trans-unit id="_list_type.seeAlso" approved="yes">
929 <source>_MOD_tools_em</source>
930 <target>_MOD_tools_em</target>
931 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
932 </trans-unit>
933 <trans-unit id="_list_type.image" approved="yes">
934 <source>EXT:context_help/cshimages/ttcontent_7.png</source>
935 <target>EXT:context_help/cshimages/ttcontent_7.png</target>
936 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
937 </trans-unit>
938 <trans-unit id="select_key.description" approved="yes">
939 <source>Enter a special string to define the Content Element's operation or leave it blank for the default mode. Possible values depend on the Content Element being used.</source>
940 <target>Enter a special string to define the Content Element's operation or leave it blank for the default mode. Possible values depend on the Content Element being used.</target>
941 </trans-unit>
942 <trans-unit id="select_key.details" approved="yes">
943 <source>Whether or not the content of this field is used and how it's intepreted depends on the Content Element and/or plugin being used. It is considered obsolete for plugins today, but is used in some Content Elements such as File Links.</source>
944 <target>Whether or not the content of this field is used and how it's intepreted depends on the Content Element and/or plugin being used. It is considered obsolete for plugins today, but is used in some Content Elements such as File Links.</target>
945 </trans-unit>
946 <trans-unit id="_select_key.seeAlso" approved="yes">
947 <source>tt_content:list_type</source>
948 <target>tt_content:list_type</target>
949 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
950 </trans-unit>
951 <trans-unit id="table_bgColor.description" approved="yes">
952 <source>Select the table background color.</source>
953 <target>Select the table background color.</target>
954 </trans-unit>
955 <trans-unit id="table_border.description" approved="yes">
956 <source>Select the table border thickness.</source>
957 <target>Select the table border thickness.</target>
958 </trans-unit>
959 <trans-unit id="table_cellspacing.description" approved="yes">
960 <source>Select the table cell spacing.</source>
961 <target>Select the table cell spacing.</target>
962 </trans-unit>
963 <trans-unit id="table_cellspacing.details" approved="yes">
964 <source>Cell spacing is the distance between table cells in rows and columns. The distance is equally applied in all directions, top, bottom, left, and right.</source>
965 <target>Cell spacing is the distance between table cells in rows and columns. The distance is equally applied in all directions, top, bottom, left, and right.</target>
966 </trans-unit>
967 <trans-unit id="table_cellpadding.description" approved="yes">
968 <source>Select the table cellpadding.</source>
969 <target>Select the table cellpadding.</target>
970 </trans-unit>
971 <trans-unit id="table_cellpadding.details" approved="yes">
972 <source>Cell padding is the 'internal' margin of a table cell. The distance is equally applied in all directions, top, bottom, left, and right.</source>
973 <target>Cell padding is the 'internal' margin of a table cell. The distance is equally applied in all directions, top, bottom, left, and right.</target>
974 </trans-unit>
975 <trans-unit id="media.description" approved="yes">
976 <source>Files can be added to the list here.</source>
977 <target>Files can be added to the list here.</target>
978 </trans-unit>
979 <trans-unit id="multimedia.description" approved="yes">
980 <source>Insert a multimedia element here (ex. Flash movie)</source>
981 <target>Insert a multimedia element here (ex. Flash movie)</target>
982 </trans-unit>
983 <trans-unit id="filelink_size.description" approved="yes">
984 <source>Enable the display of file sizes.</source>
985 <target>Enable the display of file sizes.</target>
986 </trans-unit>
987 <trans-unit id="records.description" approved="yes">
988 <source>Insert records to be displayed on this page.</source>
989 <target>Insert records to be displayed on this page.</target>
990 </trans-unit>
991 <trans-unit id="spaceBefore.description" approved="yes">
992 <source>Top Margin (in pixels) inserts whitespace &lt;em&gt;before&lt;/em&gt; this Content Element.</source>
993 <target>Top Margin (in pixels) inserts whitespace &lt;em&gt;before&lt;/em&gt; this Content Element.</target>
994 </trans-unit>
995 <trans-unit id="_spaceBefore.seeAlso" approved="yes">
996 <source>tt_content:spaceAfter,
997 tt_content:section_frame</source>
998 <target>tt_content:spaceAfter,
999 tt_content:section_frame</target>
1000 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
1001 </trans-unit>
1002 <trans-unit id="spaceAfter.description" approved="yes">
1003 <source>Bottom Margin (in pixels) inserts whitespace &lt;em&gt;after&lt;/em&gt; this Content Element.</source>
1004 <target>Bottom Margin (in pixels) inserts whitespace &lt;em&gt;after&lt;/em&gt; this Content Element.</target>
1005 </trans-unit>
1006 <trans-unit id="_spaceAfter.seeAlso" approved="yes">
1007 <source>tt_content:spaceBefore,
1008 tt_content:section_frame</source>
1009 <target>tt_content:spaceBefore,
1010 tt_content:section_frame</target>
1011 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
1012 </trans-unit>
1013 <trans-unit id="section_frame.description" approved="yes">
1014 <source>Select indention or framing options for the Content Element.</source>
1015 <target>Select indention or framing options for the Content Element.</target>
1016 </trans-unit>
1017 <trans-unit id="_section_frame.seeAlso" approved="yes">
1018 <source>tt_content:spaceAfter,
1019 tt_content:spaceBefore</source>
1020 <target>tt_content:spaceAfter,
1021 tt_content:spaceBefore</target>
1022 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
1023 </trans-unit>
1024 <trans-unit id="sectionIndex.description" approved="yes">
1025 <source>If set, the Content Element will appear in Section Menus.</source>
1026 <target>If set, the Content Element will appear in Section Menus.</target>
1027 </trans-unit>
1028 <trans-unit id="sectionIndex.details" approved="yes">
1029 <source>See more details about Section Menus by clicking below.</source>
1030 <target>See more details about Section Menus by clicking below.</target>
1031 </trans-unit>
1032 <trans-unit id="_sectionIndex.seeAlso" approved="yes">
1033 <source>tt_content:menu_type</source>
1034 <target>tt_content:menu_type</target>
1035 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
1036 </trans-unit>
1037 <trans-unit id="linkToTop.description" approved="yes">
1038 <source>If checked, a small "To Top" link will be added after the Content Element, linking back to the top of the page.</source>
1039 <target>If checked, a small "To Top" link will be added after the Content Element, linking back to the top of the page.</target>
1040 </trans-unit>
1041 <trans-unit id="rte_enabled.description" approved="yes">
1042 <source>If checked, the Rich Text Editor will be disabled for the "Text" and "Text &amp; Image" types (&lt;em&gt;in this Content Element only&lt;/em&gt;).</source>
1043 <target>If checked, the Rich Text Editor will be disabled for the "Text" and "Text &amp; Image" types (&lt;em&gt;in this Content Element only&lt;/em&gt;).</target>
1044 </trans-unit>
1045 <trans-unit id="_rte_enabled.seeAlso" approved="yes">
1046 <source>tt_content:bodytext</source>
1047 <target>tt_content:bodytext</target>
1048 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
1049 </trans-unit>
1050 <trans-unit id="pi_flexform.description" approved="yes">
1051 <source>Plugin Configuration</source>
1052 <target>Plugin Configuration</target>
1053 </trans-unit>
1054 <trans-unit id="pi_flexform.details" approved="yes">
1055 <source>Some plugins may provide configuration options, but the actual options vary based on the plugin. Behind the scenes, these are based on FlexForms and stored as XML.</source>
1056 <target>Some plugins may provide configuration options, but the actual options vary based on the plugin. Behind the scenes, these are based on FlexForms and stored as XML.</target>
1057 </trans-unit>
1058 <trans-unit id="_pi_flexform.seeAlso" approved="yes">
1059 <source>tt_content:list_type</source>
1060 <target>tt_content:list_type</target>
1061 <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
1062 </trans-unit>
1063 </body>
1064 </file>
1065 </xliff>