[BUGFIX] High CPU load in IE8/9 when using context menu in htmlArea RTE
[Packages/TYPO3.CMS.git] / typo3 / sysext / context_help / 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 in TYPO3 is typically made by "Pagecontent" records. They are typically referred to as "Content Elements". Often Content Elements are managed by the "Page" module which is designed to handle Content Elements in multiple columns and languages.</source>
8 <target>All visible content on webpages in TYPO3 is typically made by "Pagecontent" records. They are typically referred to as "Content Elements". Often Content Elements are managed by the "Page" module which is designed to handle Content Elements in multiple columns and languages.</target>
9 </trans-unit>
10 <trans-unit id=".details" approved="yes">
11 <source>"Pagecontent" records is ordered and can thus be rearranged. Also notice that the "Language" and "Column" selector of the "Pagecontent" records determines where and in which situation they appear. If you do not change the value of the "Language" and "Column" selectors you are most sure that the element will appear by default.</source>
12 <target>"Pagecontent" records is ordered and can thus be rearranged. Also notice that the "Language" and "Column" selector of the "Pagecontent" records determines where and in which situation they appear. If you do not change the value of the "Language" and "Column" selectors you are most sure that the element will appear by default.</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 </trans-unit>
28 <trans-unit id=".image_descr" approved="yes">
29 <source>The Page module is used to manage Content Elements effectively as they appear arranged in columns and languages.
30 A Content Element has a large editing form with many options. The "Type" determines which options are visible.
31 In the frontend - on the webpage - a Content Element like the above could look like this.</source>
32 <target>The Page module is used to manage Content Elements effectively as they appear arranged in columns and languages.
33 A Content Element has a large editing form with many options. The "Type" determines which options are visible.
34 In the frontend - on the webpage - a Content Element like the above could look like this.</target>
35 </trans-unit>
36 <trans-unit id="CType.description" approved="yes">
37 <source>Select the kind of page content this element represents. New options will appear when you save the record.</source>
38 <target>Select the kind of page content this element represents. New options will appear when you save the record.</target>
39 </trans-unit>
40 <trans-unit id="CType.details" approved="yes">
41 <source>The 'Type' of content you select determines which options you have in the editform, so make sure to save the record before you make changes.
42
43 This is a description of the various types:
44
45 &lt;strong&gt;Header&lt;/strong&gt;
46 This type allows you insert a standard content element header and nothing more.
47 Almost all the other types described below also includes the header with the exact same options. So the Header type just provides a way to insert a header &lt;em&gt;only&lt;/em&gt; without anything else.
48
49 &lt;strong&gt;Text&lt;/strong&gt;
50 The Text type allows you to insert regular page content.
51
52 &lt;strong&gt;Text w/image&lt;/strong&gt;
53 This is the same as the Text type (regular page content) but with the option of attaching images.
54
55 &lt;strong&gt;Image&lt;/strong&gt;
56 The same as Text w/image but without the text field - so only images.
57
58 &lt;strong&gt;Bullet list&lt;/strong&gt;
59 Lets you create a bullet list. Each line in the text-field will appear as a single line in the bulletlist.
60
61 &lt;strong&gt;Table&lt;/strong&gt;
62 Lets you create &lt;em&gt;simple&lt;/em&gt; tables. Each line represents a tablerow and vertical bars '|' separates each column.
63
64 &lt;strong&gt;Filelinks&lt;/strong&gt;
65 Allows you to present a list of files for download. You can have thumbnails attached to the list including filesize.
66
67 &lt;strong&gt;Multimedia&lt;/strong&gt;
68 Lets you insert multimedia elements such as sound, video, java applets and flash animations.
69
70 &lt;strong&gt;Form&lt;/strong&gt;
71 Lets you create mail forms. There is a special syntax to use when you wish to create form fields.
72
73 &lt;strong&gt;Search&lt;/strong&gt;
74 This inserts a search box and it will also display the search result if a query is performed to the page.
75
76 &lt;strong&gt;Login&lt;/strong&gt;
77 Displays a login box for website users. You must create at least one Website user and user group before this makes any sense to use.
78
79 &lt;strong&gt;Textbox&lt;/strong&gt;
80 This is mainly for customly defined design which includes typically some text and an image. So in other words the function is not generally defined. However the default subtypes will let you choose various ways to display some text with an image.
81 Use only if instructed to.
82
83 &lt;strong&gt;Menu/Sitemap&lt;/strong&gt;
84 Offers a selection of various link menus and a sitemap you can insert on a page.
85
86 &lt;strong&gt;Insert records&lt;/strong&gt;
87 This is a placeholder for other records. In other words, by this element you can attach other content elements from elsewhere and thus insert them this page.
88
89 &lt;strong&gt;Insert plugin&lt;/strong&gt;
90 This will allow you to insert a forum, guestbook, list of addresses, shopping basket etc. The various features are available &lt;em&gt;only&lt;/em&gt; if they are configured correctly in the template of your website. So before you use it, make sure this is the case.
91
92 &lt;strong&gt;Script&lt;/strong&gt;
93 This is reserved for custom purposes where the template developer can allow you to insert specialized page content by this element type along with a code to identify which special content you want.
94
95 &lt;strong&gt;HTML&lt;/strong&gt;
96 This is plain HTML content. Everything put here will be displayed directly on the page without any preprocessing.</source>
97 <target>The 'Type' of content you select determines which options you have in the editform, so make sure to save the record before you make changes.
98
99 This is a description of the various types:
100
101 &lt;strong&gt;Header&lt;/strong&gt;
102 This type allows you insert a standard content element header and nothing more.
103 Almost all the other types described below also includes the header with the exact same options. So the Header type just provides a way to insert a header &lt;em&gt;only&lt;/em&gt; without anything else.
104
105 &lt;strong&gt;Text&lt;/strong&gt;
106 The Text type allows you to insert regular page content.
107
108 &lt;strong&gt;Text w/image&lt;/strong&gt;
109 This is the same as the Text type (regular page content) but with the option of attaching images.
110
111 &lt;strong&gt;Image&lt;/strong&gt;
112 The same as Text w/image but without the text field - so only images.
113
114 &lt;strong&gt;Bullet list&lt;/strong&gt;
115 Lets you create a bullet list. Each line in the text-field will appear as a single line in the bulletlist.
116
117 &lt;strong&gt;Table&lt;/strong&gt;
118 Lets you create &lt;em&gt;simple&lt;/em&gt; tables. Each line represents a tablerow and vertical bars '|' separates each column.
119
120 &lt;strong&gt;Filelinks&lt;/strong&gt;
121 Allows you to present a list of files for download. You can have thumbnails attached to the list including filesize.
122
123 &lt;strong&gt;Multimedia&lt;/strong&gt;
124 Lets you insert multimedia elements such as sound, video, java applets and flash animations.
125
126 &lt;strong&gt;Form&lt;/strong&gt;
127 Lets you create mail forms. There is a special syntax to use when you wish to create form fields.
128
129 &lt;strong&gt;Search&lt;/strong&gt;
130 This inserts a search box and it will also display the search result if a query is performed to the page.
131
132 &lt;strong&gt;Login&lt;/strong&gt;
133 Displays a login box for website users. You must create at least one Website user and user group before this makes any sense to use.
134
135 &lt;strong&gt;Textbox&lt;/strong&gt;
136 This is mainly for customly defined design which includes typically some text and an image. So in other words the function is not generally defined. However the default subtypes will let you choose various ways to display some text with an image.
137 Use only if instructed to.
138
139 &lt;strong&gt;Menu/Sitemap&lt;/strong&gt;
140 Offers a selection of various link menus and a sitemap you can insert on a page.
141
142 &lt;strong&gt;Insert records&lt;/strong&gt;
143 This is a placeholder for other records. In other words, by this element you can attach other content elements from elsewhere and thus insert them this page.
144
145 &lt;strong&gt;Insert plugin&lt;/strong&gt;
146 This will allow you to insert a forum, guestbook, list of addresses, shopping basket etc. The various features are available &lt;em&gt;only&lt;/em&gt; if they are configured correctly in the template of your website. So before you use it, make sure this is the case.
147
148 &lt;strong&gt;Script&lt;/strong&gt;
149 This is reserved for custom purposes where the template developer can allow you to insert specialized page content by this element type along with a code to identify which special content you want.
150
151 &lt;strong&gt;HTML&lt;/strong&gt;
152 This is plain HTML content. Everything put here will be displayed directly on the page without any preprocessing.</target>
153 </trans-unit>
154 <trans-unit id="_CType.seeAlso" approved="yes">
155 <source>tt_content:colPos,
156 tt_content:sys_language_uid,
157 About Content Elements | http://typo3.org/documentation/document-library/doc_tut_quickstart/Content_element_type/</source>
158 <target>tt_content:colPos,
159 tt_content:sys_language_uid,
160 About Content Elements | http://typo3.org/documentation/document-library/doc_tut_quickstart/Content_element_type/</target>
161 </trans-unit>
162 <trans-unit id="_CType.image" approved="yes">
163 <source>EXT:context_help/cshimages/ttcontent_4.png</source>
164 <target>EXT:context_help/cshimages/ttcontent_4.png</target>
165 </trans-unit>
166 <trans-unit id="hidden.description" approved="yes">
167 <source>Check this box if you wish to hide the content element from being displayed.</source>
168 <target>Check this box if you wish to hide the content element from being displayed.</target>
169 </trans-unit>
170 <trans-unit id="_hidden.seeAlso" approved="yes">
171 <source>tt_content:starttime,
172 tt_content:endtime,
173 tt_content:fe_group,
174 tt_content:colPos,
175 tt_content:sys_language_uid</source>
176 <target>tt_content:starttime,
177 tt_content:endtime,
178 tt_content:fe_group,
179 tt_content:colPos,
180 tt_content:sys_language_uid</target>
181 </trans-unit>
182 <trans-unit id="starttime.description" approved="yes">
183 <source>Enter the date from which the content element will be visible.</source>
184 <target>Enter the date from which the content element will be visible.</target>
185 </trans-unit>
186 <trans-unit id="_starttime.seeAlso" approved="yes">
187 <source>pages:starttime,
188 tt_content:endtime,
189 tt_content:hidden,
190 tt_content:fe_group</source>
191 <target>pages:starttime,
192 tt_content:endtime,
193 tt_content:hidden,
194 tt_content:fe_group</target>
195 </trans-unit>
196 <trans-unit id="endtime.description" approved="yes">
197 <source>Enter the date from which the content element will disappear from the website.</source>
198 <target>Enter the date from which the content element will disappear from the website.</target>
199 </trans-unit>
200 <trans-unit id="_endtime.seeAlso" approved="yes">
201 <source>pages:endtime,
202 tt_content:starttime,
203 tt_content:hidden,
204 tt_content:fe_group</source>
205 <target>pages:endtime,
206 tt_content:starttime,
207 tt_content:hidden,
208 tt_content:fe_group</target>
209 </trans-unit>
210 <trans-unit id="fe_group.description" approved="yes">
211 <source>Select a Website usergroup which is exclusively allowed to view the element.</source>
212 <target>Select a Website usergroup which is exclusively allowed to view the element.</target>
213 </trans-unit>
214 <trans-unit id="fe_group.details" approved="yes">
215 <source>The options in this box depends on which Website usergroups are created and available for you. When you select a user group here, the content element will no longer be visible to users which are not logged in. Only Website users which are logged in and members of the group you selected will be allowed to see the element.
216 If you select "Hide at login" the effect is kind of reversed in that the element &lt;em&gt;disappears&lt;/em&gt; if &lt;em&gt;any&lt;/em&gt; Website user is logged in. This is useful if you want to present information like "How to login" and such which is irrelevant if a user is finally logged in.</source>
217 <target>The options in this box depends on which Website usergroups are created and available for you. When you select a user group here, the content element will no longer be visible to users which are not logged in. Only Website users which are logged in and members of the group you selected will be allowed to see the element.
218 If you select "Hide at login" the effect is kind of reversed in that the element &lt;em&gt;disappears&lt;/em&gt; if &lt;em&gt;any&lt;/em&gt; Website user is logged in. This is useful if you want to present information like "How to login" and such which is irrelevant if a user is finally logged in.</target>
219 </trans-unit>
220 <trans-unit id="_fe_group.seeAlso" approved="yes">
221 <source>tt_content:hidden,
222 tt_content:starttime,
223 tt_content:endtime,
224 pages:fe_group,
225 fe_users,
226 fe_groups</source>
227 <target>tt_content:hidden,
228 tt_content:starttime,
229 tt_content:endtime,
230 pages:fe_group,
231 fe_users,
232 fe_groups</target>
233 </trans-unit>
234 <trans-unit id="sys_language_uid.description" approved="yes">
235 <source>Select the system language of this element. &lt;strong&gt;Notice&lt;/strong&gt; this will affect whether the element is visible.</source>
236 <target>Select the system language of this element. &lt;strong&gt;Notice&lt;/strong&gt; this will affect whether the element is visible.</target>
237 </trans-unit>
238 <trans-unit id="sys_language_uid.details" approved="yes">
239 <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.
240 The available system languages are created by the administrator.</source>
241 <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.
242 The available system languages are created by the administrator.</target>
243 </trans-unit>
244 <trans-unit id="_sys_language_uid.seeAlso" approved="yes">
245 <source>tt_content:colPos,
246 sys_language,
247 Localization concepts [Technical] | http://typo3.org/documentation/tips-tricks/multi-language-sites-in-typo3/,
248 _MOD_web_layout:language_list</source>
249 <target>tt_content:colPos,
250 sys_language,
251 Localization concepts [Technical] | http://typo3.org/documentation/tips-tricks/multi-language-sites-in-typo3/,
252 _MOD_web_layout:language_list</target>
253 </trans-unit>
254 <trans-unit id="layout.description" approved="yes">
255 <source>Select a layout.</source>
256 <target>Select a layout.</target>
257 </trans-unit>
258 <trans-unit id="layout.details" approved="yes">
259 <source>This option is not used in the default templates but may be used by any custom rendering.
260
261 There are a number of default implementations depending on the content element type:
262
263 &lt;b&gt;"Filelinks":&lt;/b&gt;
264 "Normal" will provide a list of filelinks with no thumbnail.
265 "Layout 1" adds a file icon to the left of the link
266 "Layout 2" adds a thumbnail if the file is an image file and if not an icon. A black border is wrapped around.
267 "Layout 3" is like Layout 2, but without the black border.</source>
268 <target>This option is not used in the default templates but may be used by any custom rendering.
269
270 There are a number of default implementations depending on the content element type:
271
272 &lt;b&gt;"Filelinks":&lt;/b&gt;
273 "Normal" will provide a list of filelinks with no thumbnail.
274 "Layout 1" adds a file icon to the left of the link
275 "Layout 2" adds a thumbnail if the file is an image file and if not an icon. A black border is wrapped around.
276 "Layout 3" is like Layout 2, but without the black border.</target>
277 </trans-unit>
278 <trans-unit id="colPos.description" approved="yes">
279 <source>Select the column position this element. &lt;strong&gt;Notice&lt;/strong&gt; this will affect whether the element is visible.</source>
280 <target>Select the column position this element. &lt;strong&gt;Notice&lt;/strong&gt; this will affect whether the element is visible.</target>
281 </trans-unit>
282 <trans-unit id="colPos.details" approved="yes">
283 <source>Most websites use only one column of content. However some templates lets you put content in multiple columns and this option allows you to select another column for the element.
284
285 &lt;strong&gt;Notice&lt;/strong&gt; that selecting another column than "Normal" will make the content element disappear unless that column is also displayed in the website template. If your content element is 'strangely' not visible please make sure the Column and Language selectors are set correctly.</source>
286 <target>Most websites use only one column of content. However some templates lets you put content in multiple columns and this option allows you to select another column for the element.
287
288 &lt;strong&gt;Notice&lt;/strong&gt; that selecting another column than "Normal" will make the content element disappear unless that column is also displayed in the website template. If your content element is 'strangely' not visible please make sure the Column and Language selectors are set correctly.</target>
289 </trans-unit>
290 <trans-unit id="_colPos.seeAlso" approved="yes">
291 <source>tt_content:sys_language_uid,
292 _MOD_web_layout:columns_multi,
293 _MOD_web_layout:columns_single</source>
294 <target>tt_content:sys_language_uid,
295 _MOD_web_layout:columns_multi,
296 _MOD_web_layout:columns_single</target>
297 </trans-unit>
298 <trans-unit id="date.description" approved="yes">
299 <source>Enter a date to be displayed above the header.</source>
300 <target>Enter a date to be displayed above the header.</target>
301 </trans-unit>
302 <trans-unit id="header.description" approved="yes">
303 <source>Enter a headline for the content element.</source>
304 <target>Enter a headline for the content element.</target>
305 </trans-unit>
306 <trans-unit id="header.details" approved="yes">
307 <source>Almost all content elements (except the HTML type for instance) will display this header above the content. If you don't want a header displayed, select the header Layout to "Hidden". Alternatively you can choose not to enter any content in this field.
308
309 Some content element types do not display the header by default. In those cases the Header field is typically labeled "Name" instead. One of these are the HTML type content element.</source>
310 <target>Almost all content elements (except the HTML type for instance) will display this header above the content. If you don't want a header displayed, select the header Layout to "Hidden". Alternatively you can choose not to enter any content in this field.
311
312 Some content element types do not display the header by default. In those cases the Header field is typically labeled "Name" instead. One of these are the HTML type content element.</target>
313 </trans-unit>
314 <trans-unit id="_header.seeAlso" approved="yes">
315 <source>tt_content:header_position,
316 tt_content:header_link,
317 tt_content:header_layout,
318 tt_content:date,</source>
319 <target>tt_content:header_position,
320 tt_content:header_link,
321 tt_content:header_layout,
322 tt_content:date,</target>
323 </trans-unit>
324 <trans-unit id="_header.image" approved="yes">
325 <source>EXT:context_help/cshimages/ttcontent_6.png</source>
326 <target>EXT:context_help/cshimages/ttcontent_6.png</target>
327 </trans-unit>
328 <trans-unit id="header_position.description" approved="yes">
329 <source>Places the header to the left, centered or to the right.</source>
330 <target>Places the header to the left, centered or to the right.</target>
331 </trans-unit>
332 <trans-unit id="_header_position.seeAlso" approved="yes">
333 <source>tt_content:header</source>
334 <target>tt_content:header</target>
335 </trans-unit>
336 <trans-unit id="header_link.description" approved="yes">
337 <source>Creates a link from the header. Insert a page id, email address or URL.</source>
338 <target>Creates a link from the header. Insert a page id, email address or URL.</target>
339 </trans-unit>
340 <trans-unit id="header_link.syntax" approved="yes">
341 <source>If you insert an id-number, eg. "51", the link will refer to page with id=51 &lt;em&gt;inside&lt;/em&gt; TYPO3.
342 If you insert an email address, eg. "name@my-domain.test", the link will point to that email address.
343 If you insert an URL or domain, eg. "www.typo3.com" or "http://www.my-domain.org", the link will point to that website.</source>
344 <target>If you insert an id-number, eg. "51", the link will refer to page with id=51 &lt;em&gt;inside&lt;/em&gt; TYPO3.
345 If you insert an email address, eg. "name@my-domain.test", the link will point to that email address.
346 If you insert an URL or domain, eg. "www.typo3.com" or "http://www.my-domain.org", the link will point to that website.</target>
347 </trans-unit>
348 <trans-unit id="_header_link.seeAlso" approved="yes">
349 <source>tt_content:header</source>
350 <target>tt_content:header</target>
351 </trans-unit>
352 <trans-unit id="header_layout.description" approved="yes">
353 <source>Select a visual design for the header.</source>
354 <target>Select a visual design for the header.</target>
355 </trans-unit>
356 <trans-unit id="header_layout.details" approved="yes">
357 <source>If you select "Default" the standard design (which is one of the layouts 1-5) will be used.
358 Alternatively you can select from Layout 1 through 5 which are configured in the website template with individual visual designs.
359 If you select "Hidden" the header will simply not appear. This is usefull if you wish a header for the content element (in order to identify it in the backend) but do not wish the header to be displayed on the website.</source>
360 <target>If you select "Default" the standard design (which is one of the layouts 1-5) will be used.
361 Alternatively you can select from Layout 1 through 5 which are configured in the website template with individual visual designs.
362 If you select "Hidden" the header will simply not appear. This is usefull if you wish a header for the content element (in order to identify it in the backend) but do not wish the header to be displayed on the website.</target>
363 </trans-unit>
364 <trans-unit id="_header_layout.seeAlso" approved="yes">
365 <source>tt_content:header</source>
366 <target>tt_content:header</target>
367 </trans-unit>
368 <trans-unit id="subheader.description" approved="yes">
369 <source>Enter a subheader. This is displayed below the ordinary headline. If the content element type is "Form" this field is the recipient email.</source>
370 <target>Enter a subheader. This is displayed below the ordinary headline. If the content element type is "Form" this field is the recipient email.</target>
371 </trans-unit>
372 <trans-unit id="subheader.details" approved="yes">
373 <source>A subheader is displayed only with the "Header" content element type.
374
375 &lt;b&gt;Notice:&lt;/b&gt; When using the content element type "Form", this field is named 'Recipient-email:' and contains the email address of the form mail recipient. It's therefore important to allow access to this field for the users.</source>
376 <target>A subheader is displayed only with the "Header" content element type.
377
378 &lt;b&gt;Notice:&lt;/b&gt; When using the content element type "Form", this field is named 'Recipient-email:' and contains the email address of the form mail recipient. It's therefore important to allow access to this field for the users.</target>
379 </trans-unit>
380 <trans-unit id="_subheader.seeAlso" approved="yes">
381 <source>tt_content:header
382 tt_content:bodytext</source>
383 <target>tt_content:header
384 tt_content:bodytext</target>
385 </trans-unit>
386 <trans-unit id="bodytext.description" approved="yes">
387 <source>Enter the body text.</source>
388 <target>Enter the body text.</target>
389 </trans-unit>
390 <trans-unit id="bodytext.details" approved="yes">
391 <source>Here you enter the body text of the content element. Usually you can use some HTML formatting tags, if you're using Internet Explorer you can even format the content visually.
392 The field is reused in most other types and so switching between the content element types will bring the value of this field with it.
393
394 When you're using this field with the "Text" and "Text w/image" types, the content is used as ordinary body text. Each linebreak normally 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 as well. This will depend on the implementation.
395
396 &lt;b&gt;Bulletlists:&lt;/b&gt;
397 If the type is "Bulletlist" each line in this field is a bulletlist entry.
398
399 &lt;b&gt;Tables:&lt;/b&gt;
400 If the type is "Table" each line represents a table row. Within each line you divide the columns by inserting a vertical bar, |. So making a table row with 3 columns could look like "This is column 1 | Column 2 here | Third column!". Use the table wizard for creating tables - that is much easier than "coding" them.
401
402 &lt;b&gt;Parameters:&lt;/b&gt;
403 Types like "Script", "Form" and "Multimedia" use this field for parameters you can pass to the element. And the "HTML" type accepts any input as raw HTML which is simply displayed on the website without any preprocessing.
404
405 &lt;strong&gt;Rich Text Editor:&lt;/strong&gt;
406 With the types "Text" and "Text w/image" the Rich Text editor is used for editing if your browser supports it and the editor is generally enabled in the system. Be aware that the content is "cleansed" before it goes into the database when you're using the "Text" and "Text w/image" types.
407
408 &lt;b&gt;Making a mail form:&lt;/b&gt;
409 When you have selected the content element type "Form" you should enter lines of parameters into this field. This is a brief example:
410
411 Your name: | *name=input,40 | [Enter name!]
412 Your email: | *email=input,40
413 Your address: | address=textarea,40,10
414 Your haircolor: |hair=radio|Blue=blue, Red=red
415
416 |formtype_mail = submit | Send form
417 |subject=hidden| Enter a subject here!
418 |html_enabled=hidden | 1
419
420 The first two lines makes input-fields for name and email, both are marked "required" by the * and the name field has a default value of "[Enter name!]".
421 The third line is a text box and the fourth makes radiobuttons to select haircolor.
422 Then 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 makes the form result render in an HTML-table.
423 It is much easier to use the Form Wizard for creating forms.
424
425 &lt;b&gt;Notice:&lt;/b&gt; Before any form will ever work, you must enter a recipient email address. The "Recipient-email:" field is used for that (this is in fact the Subheader field used!).</source>
426 <target>Here you enter the body text of the content element. Usually you can use some HTML formatting tags, if you're using Internet Explorer you can even format the content visually.
427 The field is reused in most other types and so switching between the content element types will bring the value of this field with it.
428
429 When you're using this field with the "Text" and "Text w/image" types, the content is used as ordinary body text. Each linebreak normally 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 as well. This will depend on the implementation.
430
431 &lt;b&gt;Bulletlists:&lt;/b&gt;
432 If the type is "Bulletlist" each line in this field is a bulletlist entry.
433
434 &lt;b&gt;Tables:&lt;/b&gt;
435 If the type is "Table" each line represents a table row. Within each line you divide the columns by inserting a vertical bar, |. So making a table row with 3 columns could look like "This is column 1 | Column 2 here | Third column!". Use the table wizard for creating tables - that is much easier than "coding" them.
436
437 &lt;b&gt;Parameters:&lt;/b&gt;
438 Types like "Script", "Form" and "Multimedia" use this field for parameters you can pass to the element. And the "HTML" type accepts any input as raw HTML which is simply displayed on the website without any preprocessing.
439
440 &lt;strong&gt;Rich Text Editor:&lt;/strong&gt;
441 With the types "Text" and "Text w/image" the Rich Text editor is used for editing if your browser supports it and the editor is generally enabled in the system. Be aware that the content is "cleansed" before it goes into the database when you're using the "Text" and "Text w/image" types.
442
443 &lt;b&gt;Making a mail form:&lt;/b&gt;
444 When you have selected the content element type "Form" you should enter lines of parameters into this field. This is a brief example:
445
446 Your name: | *name=input,40 | [Enter name!]
447 Your email: | *email=input,40
448 Your address: | address=textarea,40,10
449 Your haircolor: |hair=radio|Blue=blue, Red=red
450
451 |formtype_mail = submit | Send form
452 |subject=hidden| Enter a subject here!
453 |html_enabled=hidden | 1
454
455 The first two lines makes input-fields for name and email, both are marked "required" by the * and the name field has a default value of "[Enter name!]".
456 The third line is a text box and the fourth makes radiobuttons to select haircolor.
457 Then 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 makes the form result render in an HTML-table.
458 It is much easier to use the Form Wizard for creating forms.
459
460 &lt;b&gt;Notice:&lt;/b&gt; Before any form will ever work, you must enter a recipient email address. The "Recipient-email:" field is used for that (this is in fact the Subheader field used!).</target>
461 </trans-unit>
462 <trans-unit id="_bodytext.seeAlso" approved="yes">
463 <source>tt_content:CType,
464 tt_content:subheader,
465 xMOD_csh_corebe:wizard_forms_wiz,
466 xMOD_csh_corebe:wizard_table_wiz</source>
467 <target>tt_content:CType,
468 tt_content:subheader,
469 xMOD_csh_corebe:wizard_forms_wiz,
470 xMOD_csh_corebe:wizard_table_wiz</target>
471 </trans-unit>
472 <trans-unit id="text_align.description" approved="yes">
473 <source>Places the body text to the left, centered or to the right.</source>
474 <target>Places the body text to the left, centered or to the right.</target>
475 </trans-unit>
476 <trans-unit id="text_align.details" approved="yes">
477 <source>See Pagecontent / Fontface for comments.
478 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
479 <target>See Pagecontent / Fontface for comments.
480 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
481 </trans-unit>
482 <trans-unit id="_text_align.seeAlso" approved="yes">
483 <source>tt_content:text_face,
484 tt_content:bodytext</source>
485 <target>tt_content:text_face,
486 tt_content:bodytext</target>
487 </trans-unit>
488 <trans-unit id="text_face.description" approved="yes">
489 <source>Select a font fact family for the body text.</source>
490 <target>Select a font fact family for the body text.</target>
491 </trans-unit>
492 <trans-unit id="text_face.details" approved="yes">
493 <source>&lt;strong&gt;Notice&lt;/strong&gt; that these options are only 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>
494 <target>&lt;strong&gt;Notice&lt;/strong&gt; that these options are only 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>
495 </trans-unit>
496 <trans-unit id="_text_face.seeAlso" approved="yes">
497 <source>tt_content:text_face,
498 tt_content:bodytext</source>
499 <target>tt_content:text_face,
500 tt_content:bodytext</target>
501 </trans-unit>
502 <trans-unit id="text_size.description" approved="yes">
503 <source>Select a font size for the body text.</source>
504 <target>Select a font size for the body text.</target>
505 </trans-unit>
506 <trans-unit id="text_size.details" approved="yes">
507 <source>See Pagecontent / Fontface for comments.
508 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
509 <target>See Pagecontent / Fontface for comments.
510 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
511 </trans-unit>
512 <trans-unit id="_text_size.seeAlso" approved="yes">
513 <source>tt_content:text_face,
514 tt_content:bodytext</source>
515 <target>tt_content:text_face,
516 tt_content:bodytext</target>
517 </trans-unit>
518 <trans-unit id="text_color.description" approved="yes">
519 <source>Select a color for the body text.</source>
520 <target>Select a color for the body text.</target>
521 </trans-unit>
522 <trans-unit id="text_color.details" approved="yes">
523 <source>See Pagecontent / Fontface for comments.
524 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
525 <target>See Pagecontent / Fontface for comments.
526 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
527 </trans-unit>
528 <trans-unit id="_text_color.seeAlso" approved="yes">
529 <source>tt_content:text_face,
530 tt_content:bodytext</source>
531 <target>tt_content:text_face,
532 tt_content:bodytext</target>
533 </trans-unit>
534 <trans-unit id="text_properties.description" approved="yes">
535 <source>Select additional font properties.</source>
536 <target>Select additional font properties.</target>
537 </trans-unit>
538 <trans-unit id="text_properties.details" approved="yes">
539 <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:
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 Pagecontent / Fontface for comments.
546 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
547 <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:
548
549 &amp;lt;b&amp;gt;&lt;strong&gt;This is bold&lt;/strong&gt;&amp;lt;b&amp;gt;
550 &amp;lt;i&amp;gt;&lt;em&gt;This is italics&lt;/em&gt;&amp;lt;i&amp;gt;
551 &amp;lt;u&amp;gt;&lt;u&gt;This is underlined&lt;/u&gt;&amp;lt;u&amp;gt;
552
553 See Pagecontent / Fontface for comments.
554 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
555 </trans-unit>
556 <trans-unit id="_text_properties.seeAlso" approved="yes">
557 <source>tt_content:text_face,
558 tt_content:bodytext</source>
559 <target>tt_content:text_face,
560 tt_content:bodytext</target>
561 </trans-unit>
562 <trans-unit id="image.description" approved="yes">
563 <source>Insert one or more images.</source>
564 <target>Insert one or more images.</target>
565 </trans-unit>
566 <trans-unit id="image.details" approved="yes">
567 <source>You can attach images to the content element and almost as many as you like.
568 Depending on the configuration of TYPO3 you can even attach them in any format you like. Especially you do not need to worry about size and compression because these factors are normally handled by TYPO3 internally.
569
570 When you use the "Text w/image" type, it's important to select a proper position of the imageblock. For this purpose, use the Position selector which is displayed below (or if you click in the image list field in the Classic backend). See link to "Pagecontent / Position" below.
571 You can also display images in multiple columns and enable an option which enables a link so you can click the image and see a bigger version. Just to name a few options.
572 Most likely you don't have all options available. This depends on your permissions in the system.</source>
573 <target>You can attach images to the content element and almost as many as you like.
574 Depending on the configuration of TYPO3 you can even attach them in any format you like. Especially you do not need to worry about size and compression because these factors are normally handled by TYPO3 internally.
575
576 When you use the "Text w/image" type, it's important to select a proper position of the imageblock. For this purpose, use the Position selector which is displayed below (or if you click in the image list field in the Classic backend). See link to "Pagecontent / Position" below.
577 You can also display images in multiple columns and enable an option which enables a link so you can click the image and see a bigger version. Just to name a few options.
578 Most likely you don't have all options available. This depends on your permissions in the system.</target>
579 </trans-unit>
580 <trans-unit id="_image.seeAlso" approved="yes">
581 <source>tt_content:imagewidth,
582 tt_content:imageheight,
583 tt_content:imageorient,
584 tt_content:imageborder,
585 tt_content:image_noRows,
586 tt_content:image_link,
587 tt_content:image_zoom,
588 tt_content:imagecols,
589 tt_content:imagecaption,
590 tt_content:image_effects,
591 tt_content:image_frames,
592 tt_content:image_compression,
593 Using images ("Getting Started") | http://typo3.org/documentation/document-library/doc_tut_quickstart/Managing_files_in_TY/
594 Using images (Animation) | FILE:EXT:welcome/modsub/ani_10.gif</source>
595 <target>tt_content:imagewidth,
596 tt_content:imageheight,
597 tt_content:imageorient,
598 tt_content:imageborder,
599 tt_content:image_noRows,
600 tt_content:image_link,
601 tt_content:image_zoom,
602 tt_content:imagecols,
603 tt_content:imagecaption,
604 tt_content:image_effects,
605 tt_content:image_frames,
606 tt_content:image_compression,
607 Using images ("Getting Started") | http://typo3.org/documentation/document-library/doc_tut_quickstart/Managing_files_in_TY/
608 Using images (Animation) | FILE:EXT:welcome/modsub/ani_10.gif</target>
609 </trans-unit>
610 <trans-unit id="_image.image" approved="yes">
611 <source>EXT:context_help/cshimages/ttcontent_5.png</source>
612 <target>EXT:context_help/cshimages/ttcontent_5.png</target>
613 </trans-unit>
614 <trans-unit id="image.image_descr" approved="yes">
615 <source>This shows all the options related to inserting images in Content Elements. You might not be able to use all of them.</source>
616 <target>This shows all the options related to inserting images in Content Elements. You might not be able to use all of them.</target>
617 </trans-unit>
618 <trans-unit id="imagewidth.description" approved="yes">
619 <source>Enter the width in pixels of the image.</source>
620 <target>Enter the width in pixels of the image.</target>
621 </trans-unit>
622 <trans-unit id="imagewidth.details" approved="yes">
623 <source>The template is normally configured to a max width of an image and so you don't need to specify the width if the image fits perfectly into those dimensions. However this does give you an opportunity to specify a specific width.</source>
624 <target>The template is normally configured to a max width of an image and so you don't need to specify the width if the image fits perfectly into those dimensions. However this does give you an opportunity to specify a specific width.</target>
625 </trans-unit>
626 <trans-unit id="_imagewidth.seeAlso" approved="yes">
627 <source>tt_content:imageheight,
628 tt_content:image</source>
629 <target>tt_content:imageheight,
630 tt_content:image</target>
631 </trans-unit>
632 <trans-unit id="imageheight.description" approved="yes">
633 <source>Enter the height of the image in pixels.</source>
634 <target>Enter the height of the image in pixels.</target>
635 </trans-unit>
636 <trans-unit id="_imageheight.seeAlso" approved="yes">
637 <source>tt_content:imagewidth,
638 tt_content:image</source>
639 <target>tt_content:imagewidth,
640 tt_content:image</target>
641 </trans-unit>
642 <trans-unit id="imageorient.description" approved="yes">
643 <source>Select the position of the imageblock relative to the body text.</source>
644 <target>Select the position of the imageblock relative to the body text.</target>
645 </trans-unit>
646 <trans-unit id="imageorient.details" approved="yes">
647 <source>The position above and below the body text is pretty straight forward.
648 The options "In text" means that the image block is displayed with text aside it. When you select this option the template will probably force the images into smaller dimensions because they cannot take up the same space when text is supposed to float around them.
649 When you select "In text" you can choose the options either above or below the divider "No wrap". If you select the "In text" option above, the bodytext will float &lt;em&gt;under&lt;/em&gt; the image block when the bodytext reaches the end of the image block. So 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.
650 Apart from the visual difference there is a technical aspect as well. Because 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: You experience that the subsequent content elements on the page is somehow layered on top of the image block - and this certainly looks like a bug. However it's easily solved by changing the "In text" position to the equal value but below the "No wrap" divider.</source>
651 <target>The position above and below the body text is pretty straight forward.
652 The options "In text" means that the image block is displayed with text aside it. When you select this option the template will probably force the images into smaller dimensions because they cannot take up the same space when text is supposed to float around them.
653 When you select "In text" you can choose the options either above or below the divider "No wrap". If you select the "In text" option above, the bodytext will float &lt;em&gt;under&lt;/em&gt; the image block when the bodytext reaches the end of the image block. So 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.
654 Apart from the visual difference there is a technical aspect as well. Because 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: You experience that the subsequent content elements on the page is somehow layered on top of the image block - and this certainly looks like a bug. However it's easily solved by changing the "In text" position to the equal value but below the "No wrap" divider.</target>
655 </trans-unit>
656 <trans-unit id="imageborder.description" approved="yes">
657 <source>Check this, if you wish a colored border around the images.</source>
658 <target>Check this, if you wish a colored border around the images.</target>
659 </trans-unit>
660 <trans-unit id="_imageborder.seeAlso" approved="yes">
661 <source>tt_content:imagecols,
662 tt_content:image</source>
663 <target>tt_content:imagecols,
664 tt_content:image</target>
665 </trans-unit>
666 <trans-unit id="image_noRows.description" approved="yes">
667 <source>Disables strict tablerows in the image block.</source>
668 <target>Disables strict tablerows in the image block.</target>
669 </trans-unit>
670 <trans-unit id="image_noRows.details" approved="yes">
671 <source>This options is kind of hard to explain, but 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 a bit taller than the second this will generate an empty extra space beneath the second image. This is due to the normal procedure in which the images are placed in a table cell each.
672 If you set this option, the table will place all images in a column in a single table cell which make the distance between them vertically identical throughout. This may provide a better look if the alternative looks stupid.</source>
673 <target>This options is kind of hard to explain, but 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 a bit taller than the second this will generate an empty extra space beneath the second image. This is due to the normal procedure in which the images are placed in a table cell each.
674 If you set this option, the table will place all images in a column in a single table cell which make the distance between them vertically identical throughout. This may provide a better look if the alternative looks stupid.</target>
675 </trans-unit>
676 <trans-unit id="_image_noRows.seeAlso" approved="yes">
677 <source>tt_content:imagecols,
678 tt_content:image</source>
679 <target>tt_content:imagecols,
680 tt_content:image</target>
681 </trans-unit>
682 <trans-unit id="image_link.description" approved="yes">
683 <source>Enter a link for the images.</source>
684 <target>Enter a link for the images.</target>
685 </trans-unit>
686 <trans-unit id="image_link.details" approved="yes">
687 <source>By default all images share the same link. However you may ask the administrator to configure the TypoScript template to allow a separate link for each image. If this is the case, you simply separate the link values by a comma.
688
689 See Pagecontent&gt;Link below for details on syntax.</source>
690 <target>By default all images share the same link. However you may ask the administrator to configure the TypoScript template to allow a separate link for each image. If this is the case, you simply separate the link values by a comma.
691
692 See Pagecontent&gt;Link below for details on syntax.</target>
693 </trans-unit>
694 <trans-unit id="_image_link.seeAlso" approved="yes">
695 <source>tt_content:header_link,
696 tt_content:image_zoom,
697 tt_content:image</source>
698 <target>tt_content:header_link,
699 tt_content:image_zoom,
700 tt_content:image</target>
701 </trans-unit>
702 <trans-unit id="image_zoom.description" approved="yes">
703 <source>Check this option, and the image will link to a new window with a bigger version.</source>
704 <target>Check this option, and the image will link to a new window with a bigger version.</target>
705 </trans-unit>
706 <trans-unit id="image_zoom.details" approved="yes">
707 <source>This option overrides the value in the Link-field.</source>
708 <target>This option overrides the value in the Link-field.</target>
709 </trans-unit>
710 <trans-unit id="_image_zoom.seeAlso" approved="yes">
711 <source>tt_content:image_link,
712 tt_content:image</source>
713 <target>tt_content:image_link,
714 tt_content:image</target>
715 </trans-unit>
716 <trans-unit id="image_effects.description" approved="yes">
717 <source>Select special image processing effects.</source>
718 <target>Select special image processing effects.</target>
719 </trans-unit>
720 <trans-unit id="_image_effects.seeAlso" approved="yes">
721 <source>tt_content:image_compression,
722 tt_content:image_frames,
723 tt_content:image</source>
724 <target>tt_content:image_compression,
725 tt_content:image_frames,
726 tt_content:image</target>
727 </trans-unit>
728 <trans-unit id="image_frames.description" approved="yes">
729 <source>Select special image framing options.</source>
730 <target>Select special image framing options.</target>
731 </trans-unit>
732 <trans-unit id="_image_frames.seeAlso" approved="yes">
733 <source>tt_content:image_compression,
734 tt_content:image_effects,
735 tt_content:image</source>
736 <target>tt_content:image_compression,
737 tt_content:image_effects,
738 tt_content:image</target>
739 </trans-unit>
740 <trans-unit id="image_compression.description" approved="yes">
741 <source>Select compression/quality options.</source>
742 <target>Select compression/quality options.</target>
743 </trans-unit>
744 <trans-unit id="_image_compression.seeAlso" approved="yes">
745 <source>tt_content:image_frames,
746 tt_content:image_effects,
747 tt_content:image</source>
748 <target>tt_content:image_frames,
749 tt_content:image_effects,
750 tt_content:image</target>
751 </trans-unit>
752 <trans-unit id="imagecols.description" approved="yes">
753 <source>Select the number of columns in the image block.</source>
754 <target>Select the number of columns in the image block.</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 </trans-unit>
762 <trans-unit id="imagecaption.description" approved="yes">
763 <source>Enter a caption for the image block</source>
764 <target>Enter a caption for the image block</target>
765 </trans-unit>
766 <trans-unit id="imagecaption.details" approved="yes">
767 <source>By default the caption is positioned below the whole image block. However your website template may be configured to allow individual image captions by setting "styles.content.imgtext.captionSplit=1" in your template constants.
768 In that case each line in this field will be the image caption of the corresponding image in the list.
769
770 The caption text field is also used by the content element type "Filelinks" where each line represents a description of a file in the list.</source>
771 <target>By default the caption is positioned below the whole image block. However your website template may be configured to allow individual image captions by setting "styles.content.imgtext.captionSplit=1" in your template constants.
772 In that case each line in this field will be the image caption of the corresponding image in the list.
773
774 The caption text field is also used by the content element type "Filelinks" where each line represents a description of a file in the list.</target>
775 </trans-unit>
776 <trans-unit id="_imagecaption.seeAlso" approved="yes">
777 <source>tt_content:imagecaption_position,
778 tt_content:image</source>
779 <target>tt_content:imagecaption_position,
780 tt_content:image</target>
781 </trans-unit>
782 <trans-unit id="imagecaption_position.description" approved="yes">
783 <source>Places the image caption to the left, centered or to the right.</source>
784 <target>Places the image caption to the left, centered or to the right.</target>
785 </trans-unit>
786 <trans-unit id="_imagecaption_position.seeAlso" approved="yes">
787 <source>tt_content:imagecaption,
788 tt_content:image</source>
789 <target>tt_content:imagecaption,
790 tt_content:image</target>
791 </trans-unit>
792 <trans-unit id="cols.description" approved="yes">
793 <source>Select a fixed number of table columns</source>
794 <target>Select a fixed number of table columns</target>
795 </trans-unit>
796 <trans-unit id="pages.description" approved="yes">
797 <source>Insert page(s)</source>
798 <target>Insert page(s)</target>
799 </trans-unit>
800 <trans-unit id="pages.details" approved="yes">
801 <source>With this field you can generally create a relation to a page (or more) in TYPO3. This field is used by many of the content element types. If you don't specify a page here, the current page will generally be used.
802
803 Using the "Search" type, the page you insert will be the page to which the search is targeted. You must make sure that this page has a similar "Search" content element (or something similar) to render a search result. Else it makes no sense.
804
805 The "Login" type content element also uses this field to direct the login to a certain page. However that page does not need to contain a Login content element in order to perform the authentication - you can in fact submit a login request to any TYPO3 page and it will be evaluated!
806 If you specify a second page in this list, the id will be passed to the login system as being the page inside TYPO3 where the database of users to look up is found. You should use this only if your template is not configured to pass this value on.
807 In order for the login procedure to work, you must make sure that 1) you have created at least one Website user and member usergroup and is using the correct username and password, 2) you have configured in your TypoScript template on which page (typically a SysFolder) the users can be found - or alternatively have specified this by the second page in the this page list, 3) cookies must be enabled.
808
809 The "Menu/Sitemap" element also uses this field. In that case the page(s) will determine from which point the menu is drawn or maybe even represent the actual pages to which the menu links. All this depends on the subtype of Menu/Sitemap you have selected.
810
811 Finally the "Form" element uses this field as the page to which the form is submitted. You might thus insert a page which is the "Thank you" page of the form mail.</source>
812 <target>With this field you can generally create a relation to a page (or more) in TYPO3. This field is used by many of the content element types. If you don't specify a page here, the current page will generally be used.
813
814 Using the "Search" type, the page you insert will be the page to which the search is targeted. You must make sure that this page has a similar "Search" content element (or something similar) to render a search result. Else it makes no sense.
815
816 The "Login" type content element also uses this field to direct the login to a certain page. However that page does not need to contain a Login content element in order to perform the authentication - you can in fact submit a login request to any TYPO3 page and it will be evaluated!
817 If you specify a second page in this list, the id will be passed to the login system as being the page inside TYPO3 where the database of users to look up is found. You should use this only if your template is not configured to pass this value on.
818 In order for the login procedure to work, you must make sure that 1) you have created at least one Website user and member usergroup and is using the correct username and password, 2) you have configured in your TypoScript template on which page (typically a SysFolder) the users can be found - or alternatively have specified this by the second page in the this page list, 3) cookies must be enabled.
819
820 The "Menu/Sitemap" element also uses this field. In that case the page(s) will determine from which point the menu is drawn or maybe even represent the actual pages to which the menu links. All this depends on the subtype of Menu/Sitemap you have selected.
821
822 Finally the "Form" element uses this field as the page to which the form is submitted. You might thus insert a page which is the "Thank you" page of the form mail.</target>
823 </trans-unit>
824 <trans-unit id="_pages.seeAlso" approved="yes">
825 <source>tt_content:CType,
826 tt_content:recursive</source>
827 <target>tt_content:CType,
828 tt_content:recursive</target>
829 </trans-unit>
830 <trans-unit id="recursive.description" approved="yes">
831 <source>Select how many subleves should be additionally selected for each page in the list.</source>
832 <target>Select how many subleves should be additionally selected for each page in the list.</target>
833 </trans-unit>
834 <trans-unit id="recursive.details" approved="yes">
835 <source>Whether this feature makes sense or not depends solely on the template implementation and/or content element type. But basically if this feature is enabled it means that for each page listed in the "Send to page/Starting point" box subpages - to the depth specified here - will &lt;em&gt;also&lt;/em&gt; be selected!
836
837 &lt;strong&gt;Warning:&lt;/strong&gt; If there are many subpages, be aware of this option. It may select an incredible amount of pages then!</source>
838 <target>Whether this feature makes sense or not depends solely on the template implementation and/or content element type. But basically if this feature is enabled it means that for each page listed in the "Send to page/Starting point" box subpages - to the depth specified here - will &lt;em&gt;also&lt;/em&gt; be selected!
839
840 &lt;strong&gt;Warning:&lt;/strong&gt; If there are many subpages, be aware of this option. It may select an incredible amount of pages then!</target>
841 </trans-unit>
842 <trans-unit id="_recursive.seeAlso" approved="yes">
843 <source>tt_content:pages</source>
844 <target>tt_content:pages</target>
845 </trans-unit>
846 <trans-unit id="menu_type.description" approved="yes">
847 <source>Select which kind of menu you wish to create.</source>
848 <target>Select which kind of menu you wish to create.</target>
849 </trans-unit>
850 <trans-unit id="menu_type.details" approved="yes">
851 <source>This is a short description of each type:
852
853 &lt;strong&gt;Menu of these pages&lt;/strong&gt;
854 This will create a list of links to the pages you insert in the Startingpoint list.
855
856 &lt;strong&gt;Menu of subpages to these pages&lt;/strong&gt;
857 This results in a list of links to the subpages of the pages in the Startingpoint list. If you do not specify a startingpoint, subpages to the current page will be selected.
858
859 &lt;strong&gt;Menu of subpages to these pages (with abstract)&lt;/strong&gt;
860 Like the previous, but this will include the content of the Abstract field of the pages.
861
862 &lt;strong&gt;Menu of subpages to these pages + sections&lt;/strong&gt;
863 Like the previous, but including 'submenu' links to all content elements on the page which has the "Index" checkbox set.
864
865 &lt;strong&gt;Sitemap&lt;/strong&gt;
866 Generates a classic tree sitemap. Maybe your TypoScript template is configured to another design of the sitemap, but anyhow you'll get a sitemap out of this. Notice that the sitemap will begin from the current page unless you specify another "Startingpoint" page in the list below.
867
868 &lt;strong&gt;Section index (pagecontent w/Index checked)&lt;/strong&gt;
869 This makes a menu to the content elements on this page (or the page specified in the Starting point list). Great way to make an index in the top of the page.
870 Notice that all content elements with the "Index" checkbox set is selected. So if you don't want certain content elements to appear in the list, just un-check the Index checkbox for those elements.
871
872 &lt;strong&gt;Recently updated pages&lt;/strong&gt;
873 This displays the 10 most recently updated pages.
874 &lt;strong&gt;Notice:&lt;/strong&gt; If you update a page and this list seems not to be updated instantly, just clear the cache of the page and the problem is solved.
875
876 &lt;strong&gt;Related pages (based on keywords)&lt;/strong&gt;
877 Displays other related pages based on the keywords set for this page matched up with the keywords on other pages.
878
879
880 &lt;b&gt;Notice:&lt;/b&gt; With many of the above menu types, the default starting point is the current page. However you can specify another startingpoint (or more than one in fact!) by adding pages to the "Startingpoint" list. See link below.</source>
881 <target>This is a short description of each type:
882
883 &lt;strong&gt;Menu of these pages&lt;/strong&gt;
884 This will create a list of links to the pages you insert in the Startingpoint list.
885
886 &lt;strong&gt;Menu of subpages to these pages&lt;/strong&gt;
887 This results in a list of links to the subpages of the pages in the Startingpoint list. If you do not specify a startingpoint, subpages to the current page will be selected.
888
889 &lt;strong&gt;Menu of subpages to these pages (with abstract)&lt;/strong&gt;
890 Like the previous, but this will include the content of the Abstract field of the pages.
891
892 &lt;strong&gt;Menu of subpages to these pages + sections&lt;/strong&gt;
893 Like the previous, but including 'submenu' links to all content elements on the page which has the "Index" checkbox set.
894
895 &lt;strong&gt;Sitemap&lt;/strong&gt;
896 Generates a classic tree sitemap. Maybe your TypoScript template is configured to another design of the sitemap, but anyhow you'll get a sitemap out of this. Notice that the sitemap will begin from the current page unless you specify another "Startingpoint" page in the list below.
897
898 &lt;strong&gt;Section index (pagecontent w/Index checked)&lt;/strong&gt;
899 This makes a menu to the content elements on this page (or the page specified in the Starting point list). Great way to make an index in the top of the page.
900 Notice that all content elements with the "Index" checkbox set is selected. So if you don't want certain content elements to appear in the list, just un-check the Index checkbox for those elements.
901
902 &lt;strong&gt;Recently updated pages&lt;/strong&gt;
903 This displays the 10 most recently updated pages.
904 &lt;strong&gt;Notice:&lt;/strong&gt; If you update a page and this list seems not to be updated instantly, just clear the cache of the page and the problem is solved.
905
906 &lt;strong&gt;Related pages (based on keywords)&lt;/strong&gt;
907 Displays other related pages based on the keywords set for this page matched up with the keywords on other pages.
908
909
910 &lt;b&gt;Notice:&lt;/b&gt; With many of the above menu types, the default starting point is the current page. However you can specify another startingpoint (or more than one in fact!) by adding pages to the "Startingpoint" list. See link below.</target>
911 </trans-unit>
912 <trans-unit id="_menu_type.seeAlso" approved="yes">
913 <source>tt_content:pages,
914 tt_content:sectionIndex</source>
915 <target>tt_content:pages,
916 tt_content:sectionIndex</target>
917 </trans-unit>
918 <trans-unit id="list_type.description" approved="yes">
919 <source>Select a plugin to insert.</source>
920 <target>Select a plugin to insert.</target>
921 </trans-unit>
922 <trans-unit id="list_type.details" approved="yes">
923 <source>The list of plugins you can insert on a page. The available plugins depends on which extensions are installed.</source>
924 <target>The list of plugins you can insert on a page. The available plugins depends on which extensions are installed.</target>
925 </trans-unit>
926 <trans-unit id="_list_type.seeAlso" approved="yes">
927 <source>_MOD_tools_em</source>
928 <target>_MOD_tools_em</target>
929 </trans-unit>
930 <trans-unit id="_list_type.image" approved="yes">
931 <source>EXT:context_help/cshimages/ttcontent_7.png</source>
932 <target>EXT:context_help/cshimages/ttcontent_7.png</target>
933 </trans-unit>
934 <trans-unit id="select_key.description" approved="yes">
935 <source>Enter a code string.</source>
936 <target>Enter a code string.</target>
937 </trans-unit>
938 <trans-unit id="select_key.details" approved="yes">
939 <source>Whether or not the content of this field is used and how it's intepreted depends on the context. It is considered obsolete today.</source>
940 <target>Whether or not the content of this field is used and how it's intepreted depends on the context. It is considered obsolete today.</target>
941 </trans-unit>
942 <trans-unit id="_select_key.seeAlso" approved="yes">
943 <source>tt_content:list_type</source>
944 <target>tt_content:list_type</target>
945 </trans-unit>
946 <trans-unit id="table_bgColor.description" approved="yes">
947 <source>Select table background color.</source>
948 <target>Select table background color.</target>
949 </trans-unit>
950 <trans-unit id="table_border.description" approved="yes">
951 <source>Select table border thickness.</source>
952 <target>Select table border thickness.</target>
953 </trans-unit>
954 <trans-unit id="table_cellspacing.description" approved="yes">
955 <source>Select table cell spacing.</source>
956 <target>Select table cell spacing.</target>
957 </trans-unit>
958 <trans-unit id="table_cellspacing.details" approved="yes">
959 <source>Cell spacing is the distance between table cells in rows an columns. The distance is equally applied in all directions, top, bottom, left and right.</source>
960 <target>Cell spacing is the distance between table cells in rows an columns. The distance is equally applied in all directions, top, bottom, left and right.</target>
961 </trans-unit>
962 <trans-unit id="table_cellpadding.description" approved="yes">
963 <source>Select table cellpadding.</source>
964 <target>Select table cellpadding.</target>
965 </trans-unit>
966 <trans-unit id="table_cellpadding.details" approved="yes">
967 <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>
968 <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>
969 </trans-unit>
970 <trans-unit id="media.description" approved="yes">
971 <source>Add files to the list here.</source>
972 <target>Add files to the list here.</target>
973 </trans-unit>
974 <trans-unit id="multimedia.description" approved="yes">
975 <source>Insert the multimedia element, eg. a flash movie here.</source>
976 <target>Insert the multimedia element, eg. a flash movie here.</target>
977 </trans-unit>
978 <trans-unit id="filelink_size.description" approved="yes">
979 <source>Check this, if you wish the filesizes to be displayed.</source>
980 <target>Check this, if you wish the filesizes to be displayed.</target>
981 </trans-unit>
982 <trans-unit id="records.description" approved="yes">
983 <source>Insert relations to records.</source>
984 <target>Insert relations to records.</target>
985 </trans-unit>
986 <trans-unit id="spaceBefore.description" approved="yes">
987 <source>Enter the amount of whitespace (in pixels) to insert &lt;em&gt;before&lt;/em&gt; this content element.</source>
988 <target>Enter the amount of whitespace (in pixels) to insert &lt;em&gt;before&lt;/em&gt; this content element.</target>
989 </trans-unit>
990 <trans-unit id="_spaceBefore.seeAlso" approved="yes">
991 <source>tt_content:spaceAfter,
992 tt_content:section_frame</source>
993 <target>tt_content:spaceAfter,
994 tt_content:section_frame</target>
995 </trans-unit>
996 <trans-unit id="spaceAfter.description" approved="yes">
997 <source>Enter the amount of whitespace (in pixels) to insert &lt;em&gt;after&lt;/em&gt; this content element.</source>
998 <target>Enter the amount of whitespace (in pixels) to insert &lt;em&gt;after&lt;/em&gt; this content element.</target>
999 </trans-unit>
1000 <trans-unit id="_spaceAfter.seeAlso" approved="yes">
1001 <source>tt_content:spaceBefore,
1002 tt_content:section_frame</source>
1003 <target>tt_content:spaceBefore,
1004 tt_content:section_frame</target>
1005 </trans-unit>
1006 <trans-unit id="section_frame.description" approved="yes">
1007 <source>Select a framing option for the content element.</source>
1008 <target>Select a framing option for the content element.</target>
1009 </trans-unit>
1010 <trans-unit id="_section_frame.seeAlso" approved="yes">
1011 <source>tt_content:spaceAfter,
1012 tt_content:spaceBefore</source>
1013 <target>tt_content:spaceAfter,
1014 tt_content:spaceBefore</target>
1015 </trans-unit>
1016 <trans-unit id="splash_layout.description" approved="yes">
1017 <source>Select the design for the Text box.</source>
1018 <target>Select the design for the Text box.</target>
1019 </trans-unit>
1020 <trans-unit id="splash_layout.details" approved="yes">
1021 <source>&lt;strong&gt;Notice:&lt;/strong&gt; The Textbox type has a few default renderings but are primarily designed to be used for custom purposes. Therefore the availability of features will depend on the current website template.</source>
1022 <target>&lt;strong&gt;Notice:&lt;/strong&gt; The Textbox type has a few default renderings but are primarily designed to be used for custom purposes. Therefore the availability of features will depend on the current website template.</target>
1023 </trans-unit>
1024 <trans-unit id="_splash_layout.seeAlso" approved="yes">
1025 <source>tt_content:CType</source>
1026 <target>tt_content:CType</target>
1027 </trans-unit>
1028 <trans-unit id="sectionIndex.description" approved="yes">
1029 <source>If set, the content element will appear in section indices.</source>
1030 <target>If set, the content element will appear in section indices.</target>
1031 </trans-unit>
1032 <trans-unit id="sectionIndex.details" approved="yes">
1033 <source>See details for the Menu-type selector (click below).</source>
1034 <target>See details for the Menu-type selector (click below).</target>
1035 </trans-unit>
1036 <trans-unit id="_sectionIndex.seeAlso" approved="yes">
1037 <source>tt_content:menu_type</source>
1038 <target>tt_content:menu_type</target>
1039 </trans-unit>
1040 <trans-unit id="linkToTop.description" approved="yes">
1041 <source>If checked, a little "To top" link will be inserted after the content element.</source>
1042 <target>If checked, a little "To top" link will be inserted after the content element.</target>
1043 </trans-unit>
1044 <trans-unit id="rte_enabled.description" approved="yes">
1045 <source>If checked, the Rich Text Editor will be disabled for the "Text" and "Text w/Image" types (&lt;em&gt;in this element only&lt;/em&gt;).</source>
1046 <target>If checked, the Rich Text Editor will be disabled for the "Text" and "Text w/Image" types (&lt;em&gt;in this element only&lt;/em&gt;).</target>
1047 </trans-unit>
1048 <trans-unit id="_rte_enabled.seeAlso" approved="yes">
1049 <source>tt_content:bodytext</source>
1050 <target>tt_content:bodytext</target>
1051 </trans-unit>
1052 <trans-unit id="pi_flexform.description" approved="yes">
1053 <source>FlexForm Configuration of Plugins</source>
1054 <target>FlexForm Configuration of Plugins</target>
1055 </trans-unit>
1056 <trans-unit id="pi_flexform.details" approved="yes">
1057 <source>Some plugins may require configuration of their options. They may use this field for FlexForm based configuration settings (stored as XML).</source>
1058 <target>Some plugins may require configuration of their options. They may use this field for FlexForm based configuration settings (stored as XML).</target>
1059 </trans-unit>
1060 <trans-unit id="_pi_flexform.seeAlso" approved="yes">
1061 <source>tt_content:list_type</source>
1062 <target>tt_content:list_type</target>
1063 </trans-unit>
1064 </body>
1065 </file>
1066 </xliff>