[TASK] XLIFF: Add translation hint to labels, which must not be
[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 <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 effectively as they appear arranged in columns and languages.
31 A Content Element has a large editing form with many options. The "Type" determines which options are visible.
32 In the frontend - on the webpage - a Content Element like the above could look like this.</source>
33 <target>The Page module is used to manage Content Elements effectively as they appear arranged in columns and languages.
34 A Content Element has a large editing form with many options. The "Type" determines which options are visible.
35 In the frontend - on the webpage - 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 you have in the editform, so make sure to save the record before you make 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 insert a standard content element header and nothing more.
48 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.
49
50 &lt;strong&gt;Text&lt;/strong&gt;
51 The Text type allows you to insert regular page content.
52
53 &lt;strong&gt;Text w/image&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 same as Text w/image but without the text field - so only images.
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 line in the bulletlist.
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 tablerow and vertical bars '|' separates each column.
64
65 &lt;strong&gt;Filelinks&lt;/strong&gt;
66 Allows you to present a list of files for download. You can have thumbnails attached to the list including filesize.
67
68 &lt;strong&gt;Multimedia&lt;/strong&gt;
69 Lets you insert multimedia elements such as sound, video, java applets and flash animations.
70
71 &lt;strong&gt;Form&lt;/strong&gt;
72 Lets you create mail forms. There is a special syntax to use when you wish to create form fields.
73
74 &lt;strong&gt;Search&lt;/strong&gt;
75 This inserts a search box and it will also display the search result if a query is performed to the page.
76
77 &lt;strong&gt;Login&lt;/strong&gt;
78 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.
79
80 &lt;strong&gt;Textbox&lt;/strong&gt;
81 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.
82 Use only if instructed to.
83
84 &lt;strong&gt;Menu/Sitemap&lt;/strong&gt;
85 Offers a selection of various link menus and a sitemap you can insert on a page.
86
87 &lt;strong&gt;Insert records&lt;/strong&gt;
88 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.
89
90 &lt;strong&gt;Insert plugin&lt;/strong&gt;
91 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.
92
93 &lt;strong&gt;Script&lt;/strong&gt;
94 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.
95
96 &lt;strong&gt;HTML&lt;/strong&gt;
97 This is plain HTML content. Everything put here will be displayed directly on the page without any preprocessing.</source>
98 <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.
99
100 This is a description of the various types:
101
102 &lt;strong&gt;Header&lt;/strong&gt;
103 This type allows you insert a standard content element header and nothing more.
104 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.
105
106 &lt;strong&gt;Text&lt;/strong&gt;
107 The Text type allows you to insert regular page content.
108
109 &lt;strong&gt;Text w/image&lt;/strong&gt;
110 This is the same as the Text type (regular page content) but with the option of attaching images.
111
112 &lt;strong&gt;Image&lt;/strong&gt;
113 The same as Text w/image but without the text field - so only images.
114
115 &lt;strong&gt;Bullet list&lt;/strong&gt;
116 Lets you create a bullet list. Each line in the text-field will appear as a single line in the bulletlist.
117
118 &lt;strong&gt;Table&lt;/strong&gt;
119 Lets you create &lt;em&gt;simple&lt;/em&gt; tables. Each line represents a tablerow and vertical bars '|' separates each column.
120
121 &lt;strong&gt;Filelinks&lt;/strong&gt;
122 Allows you to present a list of files for download. You can have thumbnails attached to the list including filesize.
123
124 &lt;strong&gt;Multimedia&lt;/strong&gt;
125 Lets you insert multimedia elements such as sound, video, java applets and flash animations.
126
127 &lt;strong&gt;Form&lt;/strong&gt;
128 Lets you create mail forms. There is a special syntax to use when you wish to create form fields.
129
130 &lt;strong&gt;Search&lt;/strong&gt;
131 This inserts a search box and it will also display the search result if a query is performed to the page.
132
133 &lt;strong&gt;Login&lt;/strong&gt;
134 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.
135
136 &lt;strong&gt;Textbox&lt;/strong&gt;
137 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.
138 Use only if instructed to.
139
140 &lt;strong&gt;Menu/Sitemap&lt;/strong&gt;
141 Offers a selection of various link menus and a sitemap you can insert on a page.
142
143 &lt;strong&gt;Insert records&lt;/strong&gt;
144 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.
145
146 &lt;strong&gt;Insert plugin&lt;/strong&gt;
147 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.
148
149 &lt;strong&gt;Script&lt;/strong&gt;
150 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.
151
152 &lt;strong&gt;HTML&lt;/strong&gt;
153 This is plain HTML content. Everything put here will be displayed directly on the page without any preprocessing.</target>
154 </trans-unit>
155 <trans-unit id="_CType.seeAlso" approved="yes">
156 <source>tt_content:colPos,
157 tt_content:sys_language_uid,
158 About Content Elements | http://typo3.org/documentation/document-library/doc_tut_quickstart/Content_element_type/</source>
159 <target>tt_content:colPos,
160 tt_content:sys_language_uid,
161 About Content Elements | http://typo3.org/documentation/document-library/doc_tut_quickstart/Content_element_type/</target>
162 <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>
163 </trans-unit>
164 <trans-unit id="_CType.image" approved="yes">
165 <source>EXT:context_help/cshimages/ttcontent_4.png</source>
166 <target>EXT:context_help/cshimages/ttcontent_4.png</target>
167 <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>
168 </trans-unit>
169 <trans-unit id="hidden.description" approved="yes">
170 <source>Check this box if you wish to hide the content element from being displayed.</source>
171 <target>Check this box if you wish to hide the content element from being displayed.</target>
172 </trans-unit>
173 <trans-unit id="_hidden.seeAlso" approved="yes">
174 <source>tt_content:starttime,
175 tt_content:endtime,
176 tt_content:fe_group,
177 tt_content:colPos,
178 tt_content:sys_language_uid</source>
179 <target>tt_content:starttime,
180 tt_content:endtime,
181 tt_content:fe_group,
182 tt_content:colPos,
183 tt_content:sys_language_uid</target>
184 <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>
185 </trans-unit>
186 <trans-unit id="starttime.description" approved="yes">
187 <source>Enter the date from which the content element will be visible.</source>
188 <target>Enter the date from which the content element will be visible.</target>
189 </trans-unit>
190 <trans-unit id="_starttime.seeAlso" approved="yes">
191 <source>pages:starttime,
192 tt_content:endtime,
193 tt_content:hidden,
194 tt_content:fe_group</source>
195 <target>pages:starttime,
196 tt_content:endtime,
197 tt_content:hidden,
198 tt_content:fe_group</target>
199 <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>
200 </trans-unit>
201 <trans-unit id="endtime.description" approved="yes">
202 <source>Enter the date from which the content element will disappear from the website.</source>
203 <target>Enter the date from which the content element will disappear from the website.</target>
204 </trans-unit>
205 <trans-unit id="_endtime.seeAlso" approved="yes">
206 <source>pages:endtime,
207 tt_content:starttime,
208 tt_content:hidden,
209 tt_content:fe_group</source>
210 <target>pages:endtime,
211 tt_content:starttime,
212 tt_content:hidden,
213 tt_content:fe_group</target>
214 <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>
215 </trans-unit>
216 <trans-unit id="fe_group.description" approved="yes">
217 <source>Select a Website usergroup which is exclusively allowed to view the element.</source>
218 <target>Select a Website usergroup which is exclusively allowed to view the element.</target>
219 </trans-unit>
220 <trans-unit id="fe_group.details" approved="yes">
221 <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.
222 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>
223 <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.
224 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>
225 </trans-unit>
226 <trans-unit id="_fe_group.seeAlso" approved="yes">
227 <source>tt_content:hidden,
228 tt_content:starttime,
229 tt_content:endtime,
230 pages:fe_group,
231 fe_users,
232 fe_groups</source>
233 <target>tt_content:hidden,
234 tt_content:starttime,
235 tt_content:endtime,
236 pages:fe_group,
237 fe_users,
238 fe_groups</target>
239 <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>
240 </trans-unit>
241 <trans-unit id="sys_language_uid.description" approved="yes">
242 <source>Select the system language of this element. &lt;strong&gt;Notice&lt;/strong&gt; this will affect whether the element is visible.</source>
243 <target>Select the system language of this element. &lt;strong&gt;Notice&lt;/strong&gt; this will affect whether the element is visible.</target>
244 </trans-unit>
245 <trans-unit id="sys_language_uid.details" approved="yes">
246 <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.
247 The available system languages are created by the administrator.</source>
248 <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.
249 The available system languages are created by the administrator.</target>
250 </trans-unit>
251 <trans-unit id="_sys_language_uid.seeAlso" approved="yes">
252 <source>tt_content:colPos,
253 sys_language,
254 Localization concepts [Technical] | http://typo3.org/documentation/tips-tricks/multi-language-sites-in-typo3/,
255 _MOD_web_layout:language_list</source>
256 <target>tt_content:colPos,
257 sys_language,
258 Localization concepts [Technical] | http://typo3.org/documentation/tips-tricks/multi-language-sites-in-typo3/,
259 _MOD_web_layout:language_list</target>
260 <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>
261 </trans-unit>
262 <trans-unit id="layout.description" approved="yes">
263 <source>Select a layout.</source>
264 <target>Select a layout.</target>
265 </trans-unit>
266 <trans-unit id="layout.details" approved="yes">
267 <source>This option is not used in the default templates but may be used by any custom rendering.
268
269 There are a number of default implementations depending on the content element type:
270
271 &lt;b&gt;"Filelinks":&lt;/b&gt;
272 "Normal" will provide a list of filelinks with no thumbnail.
273 "Layout 1" adds a file icon to the left of the link
274 "Layout 2" adds a thumbnail if the file is an image file and if not an icon. A black border is wrapped around.
275 "Layout 3" is like Layout 2, but without the black border.</source>
276 <target>This option is not used in the default templates but may be used by any custom rendering.
277
278 There are a number of default implementations depending on the content element type:
279
280 &lt;b&gt;"Filelinks":&lt;/b&gt;
281 "Normal" will provide a list of filelinks with no thumbnail.
282 "Layout 1" adds a file icon to the left of the link
283 "Layout 2" adds a thumbnail if the file is an image file and if not an icon. A black border is wrapped around.
284 "Layout 3" is like Layout 2, but without the black border.</target>
285 </trans-unit>
286 <trans-unit id="colPos.description" approved="yes">
287 <source>Select the column position this element. &lt;strong&gt;Notice&lt;/strong&gt; this will affect whether the element is visible.</source>
288 <target>Select the column position this element. &lt;strong&gt;Notice&lt;/strong&gt; this will affect whether the element is visible.</target>
289 </trans-unit>
290 <trans-unit id="colPos.details" approved="yes">
291 <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.
292
293 &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>
294 <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.
295
296 &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>
297 </trans-unit>
298 <trans-unit id="_colPos.seeAlso" approved="yes">
299 <source>tt_content:sys_language_uid,
300 _MOD_web_layout:columns_multi,
301 _MOD_web_layout:columns_single</source>
302 <target>tt_content:sys_language_uid,
303 _MOD_web_layout:columns_multi,
304 _MOD_web_layout:columns_single</target>
305 <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>
306 </trans-unit>
307 <trans-unit id="date.description" approved="yes">
308 <source>Enter a date to be displayed above the header.</source>
309 <target>Enter a date to be displayed above the header.</target>
310 </trans-unit>
311 <trans-unit id="header.description" approved="yes">
312 <source>Enter a headline for the content element.</source>
313 <target>Enter a headline for the content element.</target>
314 </trans-unit>
315 <trans-unit id="header.details" approved="yes">
316 <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.
317
318 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>
319 <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.
320
321 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>
322 </trans-unit>
323 <trans-unit id="_header.seeAlso" approved="yes">
324 <source>tt_content:header_position,
325 tt_content:header_link,
326 tt_content:header_layout,
327 tt_content:date,</source>
328 <target>tt_content:header_position,
329 tt_content:header_link,
330 tt_content:header_layout,
331 tt_content:date,</target>
332 <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>
333 </trans-unit>
334 <trans-unit id="_header.image" approved="yes">
335 <source>EXT:context_help/cshimages/ttcontent_6.png</source>
336 <target>EXT:context_help/cshimages/ttcontent_6.png</target>
337 <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>
338 </trans-unit>
339 <trans-unit id="header_position.description" approved="yes">
340 <source>Places the header to the left, centered or to the right.</source>
341 <target>Places the header to the left, centered or to the right.</target>
342 </trans-unit>
343 <trans-unit id="_header_position.seeAlso" approved="yes">
344 <source>tt_content:header</source>
345 <target>tt_content:header</target>
346 <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>
347 </trans-unit>
348 <trans-unit id="header_link.description" approved="yes">
349 <source>Creates a link from the header. Insert a page id, email address or URL.</source>
350 <target>Creates a link from the header. Insert a page id, email address or URL.</target>
351 </trans-unit>
352 <trans-unit id="header_link.syntax" approved="yes">
353 <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.
354 If you insert an email address, eg. "name@my-domain.test", the link will point to that email address.
355 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>
356 <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.
357 If you insert an email address, eg. "name@my-domain.test", the link will point to that email address.
358 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>
359 </trans-unit>
360 <trans-unit id="_header_link.seeAlso" approved="yes">
361 <source>tt_content:header</source>
362 <target>tt_content:header</target>
363 <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>
364 </trans-unit>
365 <trans-unit id="header_layout.description" approved="yes">
366 <source>Select a visual design for the header.</source>
367 <target>Select a visual design for the header.</target>
368 </trans-unit>
369 <trans-unit id="header_layout.details" approved="yes">
370 <source>If you select "Default" the standard design (which is one of the layouts 1-5) will be used.
371 Alternatively you can select from Layout 1 through 5 which are configured in the website template with individual visual designs.
372 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>
373 <target>If you select "Default" the standard design (which is one of the layouts 1-5) will be used.
374 Alternatively you can select from Layout 1 through 5 which are configured in the website template with individual visual designs.
375 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>
376 </trans-unit>
377 <trans-unit id="_header_layout.seeAlso" approved="yes">
378 <source>tt_content:header</source>
379 <target>tt_content:header</target>
380 <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>
381 </trans-unit>
382 <trans-unit id="subheader.description" approved="yes">
383 <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>
384 <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>
385 </trans-unit>
386 <trans-unit id="subheader.details" approved="yes">
387 <source>A subheader is displayed only with the "Header" content element type.
388
389 &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>
390 <target>A subheader is displayed only with the "Header" content element type.
391
392 &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>
393 </trans-unit>
394 <trans-unit id="_subheader.seeAlso" approved="yes">
395 <source>tt_content:header
396 tt_content:bodytext</source>
397 <target>tt_content:header
398 tt_content:bodytext</target>
399 <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>
400 </trans-unit>
401 <trans-unit id="bodytext.description" approved="yes">
402 <source>Enter the body text.</source>
403 <target>Enter the body text.</target>
404 </trans-unit>
405 <trans-unit id="bodytext.details" approved="yes">
406 <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.
407 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.
408
409 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.
410
411 &lt;b&gt;Bulletlists:&lt;/b&gt;
412 If the type is "Bulletlist" each line in this field is a bulletlist entry.
413
414 &lt;b&gt;Tables:&lt;/b&gt;
415 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.
416
417 &lt;b&gt;Parameters:&lt;/b&gt;
418 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.
419
420 &lt;strong&gt;Rich Text Editor:&lt;/strong&gt;
421 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.
422
423 &lt;b&gt;Making a mail form:&lt;/b&gt;
424 When you have selected the content element type "Form" you should enter lines of parameters into this field. This is a brief example:
425
426 Your name: | *name=input,40 | [Enter name!]
427 Your email: | *email=input,40
428 Your address: | address=textarea,40,10
429 Your haircolor: |hair=radio|Blue=blue, Red=red
430
431 |formtype_mail = submit | Send form
432 |subject=hidden| Enter a subject here!
433 |html_enabled=hidden | 1
434
435 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!]".
436 The third line is a text box and the fourth makes radiobuttons to select haircolor.
437 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.
438 It is much easier to use the Form Wizard for creating forms.
439
440 &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>
441 <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.
442 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.
443
444 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.
445
446 &lt;b&gt;Bulletlists:&lt;/b&gt;
447 If the type is "Bulletlist" each line in this field is a bulletlist entry.
448
449 &lt;b&gt;Tables:&lt;/b&gt;
450 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.
451
452 &lt;b&gt;Parameters:&lt;/b&gt;
453 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.
454
455 &lt;strong&gt;Rich Text Editor:&lt;/strong&gt;
456 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.
457
458 &lt;b&gt;Making a mail form:&lt;/b&gt;
459 When you have selected the content element type "Form" you should enter lines of parameters into this field. This is a brief example:
460
461 Your name: | *name=input,40 | [Enter name!]
462 Your email: | *email=input,40
463 Your address: | address=textarea,40,10
464 Your haircolor: |hair=radio|Blue=blue, Red=red
465
466 |formtype_mail = submit | Send form
467 |subject=hidden| Enter a subject here!
468 |html_enabled=hidden | 1
469
470 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!]".
471 The third line is a text box and the fourth makes radiobuttons to select haircolor.
472 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.
473 It is much easier to use the Form Wizard for creating forms.
474
475 &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>
476 </trans-unit>
477 <trans-unit id="_bodytext.seeAlso" approved="yes">
478 <source>tt_content:CType,
479 tt_content:subheader,
480 xMOD_csh_corebe:wizard_forms_wiz,
481 xMOD_csh_corebe:wizard_table_wiz</source>
482 <target>tt_content:CType,
483 tt_content:subheader,
484 xMOD_csh_corebe:wizard_forms_wiz,
485 xMOD_csh_corebe:wizard_table_wiz</target>
486 <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>
487 </trans-unit>
488 <trans-unit id="text_align.description" approved="yes">
489 <source>Places the body text to the left, centered or to the right.</source>
490 <target>Places the body text to the left, centered or to the right.</target>
491 </trans-unit>
492 <trans-unit id="text_align.details" approved="yes">
493 <source>See Pagecontent / Fontface for comments.
494 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
495 <target>See Pagecontent / Fontface for comments.
496 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
497 </trans-unit>
498 <trans-unit id="_text_align.seeAlso" approved="yes">
499 <source>tt_content:text_face,
500 tt_content:bodytext</source>
501 <target>tt_content:text_face,
502 tt_content:bodytext</target>
503 <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>
504 </trans-unit>
505 <trans-unit id="text_face.description" approved="yes">
506 <source>Select a font fact family for the body text.</source>
507 <target>Select a font fact family for the body text.</target>
508 </trans-unit>
509 <trans-unit id="text_face.details" approved="yes">
510 <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>
511 <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>
512 </trans-unit>
513 <trans-unit id="_text_face.seeAlso" approved="yes">
514 <source>tt_content:text_face,
515 tt_content:bodytext</source>
516 <target>tt_content:text_face,
517 tt_content:bodytext</target>
518 <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>
519 </trans-unit>
520 <trans-unit id="text_size.description" approved="yes">
521 <source>Select a font size for the body text.</source>
522 <target>Select a font size for the body text.</target>
523 </trans-unit>
524 <trans-unit id="text_size.details" approved="yes">
525 <source>See Pagecontent / Fontface for comments.
526 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
527 <target>See Pagecontent / Fontface for comments.
528 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
529 </trans-unit>
530 <trans-unit id="_text_size.seeAlso" approved="yes">
531 <source>tt_content:text_face,
532 tt_content:bodytext</source>
533 <target>tt_content:text_face,
534 tt_content:bodytext</target>
535 <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>
536 </trans-unit>
537 <trans-unit id="text_color.description" approved="yes">
538 <source>Select a color for the body text.</source>
539 <target>Select a color for the body text.</target>
540 </trans-unit>
541 <trans-unit id="text_color.details" approved="yes">
542 <source>See Pagecontent / Fontface for comments.
543 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
544 <target>See Pagecontent / Fontface for comments.
545 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
546 </trans-unit>
547 <trans-unit id="_text_color.seeAlso" approved="yes">
548 <source>tt_content:text_face,
549 tt_content:bodytext</source>
550 <target>tt_content:text_face,
551 tt_content:bodytext</target>
552 <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>
553 </trans-unit>
554 <trans-unit id="text_properties.description" approved="yes">
555 <source>Select additional font properties.</source>
556 <target>Select additional font properties.</target>
557 </trans-unit>
558 <trans-unit id="text_properties.details" approved="yes">
559 <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:
560
561 &amp;lt;b&amp;gt;&lt;strong&gt;This is bold&lt;/strong&gt;&amp;lt;b&amp;gt;
562 &amp;lt;i&amp;gt;&lt;em&gt;This is italics&lt;/em&gt;&amp;lt;i&amp;gt;
563 &amp;lt;u&amp;gt;&lt;u&gt;This is underlined&lt;/u&gt;&amp;lt;u&amp;gt;
564
565 See Pagecontent / Fontface for comments.
566 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</source>
567 <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:
568
569 &amp;lt;b&amp;gt;&lt;strong&gt;This is bold&lt;/strong&gt;&amp;lt;b&amp;gt;
570 &amp;lt;i&amp;gt;&lt;em&gt;This is italics&lt;/em&gt;&amp;lt;i&amp;gt;
571 &amp;lt;u&amp;gt;&lt;u&gt;This is underlined&lt;/u&gt;&amp;lt;u&amp;gt;
572
573 See Pagecontent / Fontface for comments.
574 &lt;b&gt;Notice:&lt;/b&gt; This option is obsolete when you are using CSS for rendering.</target>
575 </trans-unit>
576 <trans-unit id="_text_properties.seeAlso" approved="yes">
577 <source>tt_content:text_face,
578 tt_content:bodytext</source>
579 <target>tt_content:text_face,
580 tt_content:bodytext</target>
581 <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>
582 </trans-unit>
583 <trans-unit id="image.description" approved="yes">
584 <source>Insert one or more images.</source>
585 <target>Insert one or more images.</target>
586 </trans-unit>
587 <trans-unit id="image.details" approved="yes">
588 <source>You can attach images to the content element and almost as many as you like.
589 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.
590
591 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.
592 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.
593 Most likely you don't have all options available. This depends on your permissions in the system.</source>
594 <target>You can attach images to the content element and almost as many as you like.
595 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.
596
597 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.
598 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.
599 Most likely you don't have all options available. This depends on your permissions in the system.</target>
600 </trans-unit>
601 <trans-unit id="_image.seeAlso" approved="yes">
602 <source>tt_content:imagewidth,
603 tt_content:imageheight,
604 tt_content:imageorient,
605 tt_content:imageborder,
606 tt_content:image_noRows,
607 tt_content:image_link,
608 tt_content:image_zoom,
609 tt_content:imagecols,
610 tt_content:imagecaption,
611 tt_content:image_effects,
612 tt_content:image_frames,
613 tt_content:image_compression,
614 Using images ("Getting Started") | http://typo3.org/documentation/document-library/doc_tut_quickstart/Managing_files_in_TY/
615 Using images (Animation) | FILE:EXT:welcome/modsub/ani_10.gif</source>
616 <target>tt_content:imagewidth,
617 tt_content:imageheight,
618 tt_content:imageorient,
619 tt_content:imageborder,
620 tt_content:image_noRows,
621 tt_content:image_link,
622 tt_content:image_zoom,
623 tt_content:imagecols,
624 tt_content:imagecaption,
625 tt_content:image_effects,
626 tt_content:image_frames,
627 tt_content:image_compression,
628 Using images ("Getting Started") | http://typo3.org/documentation/document-library/doc_tut_quickstart/Managing_files_in_TY/
629 Using images (Animation) | FILE:EXT:welcome/modsub/ani_10.gif</target>
630 <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>
631 </trans-unit>
632 <trans-unit id="_image.image" approved="yes">
633 <source>EXT:context_help/cshimages/ttcontent_5.png</source>
634 <target>EXT:context_help/cshimages/ttcontent_5.png</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="image.image_descr" approved="yes">
638 <source>This shows all the options related to inserting images in Content Elements. You might not be able to use all of them.</source>
639 <target>This shows all the options related to inserting images in Content Elements. You might not be able to use all of them.</target>
640 </trans-unit>
641 <trans-unit id="imagewidth.description" approved="yes">
642 <source>Enter the width in pixels of the image.</source>
643 <target>Enter the width in pixels of the image.</target>
644 </trans-unit>
645 <trans-unit id="imagewidth.details" approved="yes">
646 <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>
647 <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>
648 </trans-unit>
649 <trans-unit id="_imagewidth.seeAlso" approved="yes">
650 <source>tt_content:imageheight,
651 tt_content:image</source>
652 <target>tt_content:imageheight,
653 tt_content:image</target>
654 <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>
655 </trans-unit>
656 <trans-unit id="imageheight.description" approved="yes">
657 <source>Enter the height of the image in pixels.</source>
658 <target>Enter the height of the image in pixels.</target>
659 </trans-unit>
660 <trans-unit id="_imageheight.seeAlso" approved="yes">
661 <source>tt_content:imagewidth,
662 tt_content:image</source>
663 <target>tt_content:imagewidth,
664 tt_content:image</target>
665 <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>
666 </trans-unit>
667 <trans-unit id="imageorient.description" approved="yes">
668 <source>Select the position of the imageblock relative to the body text.</source>
669 <target>Select the position of the imageblock relative to the body text.</target>
670 </trans-unit>
671 <trans-unit id="imageorient.details" approved="yes">
672 <source>The position above and below the body text is pretty straight forward.
673 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.
674 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.
675 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>
676 <target>The position above and below the body text is pretty straight forward.
677 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.
678 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.
679 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>
680 </trans-unit>
681 <trans-unit id="imageborder.description" approved="yes">
682 <source>Check this, if you wish a colored border around the images.</source>
683 <target>Check this, if you wish a colored border around the images.</target>
684 </trans-unit>
685 <trans-unit id="_imageborder.seeAlso" approved="yes">
686 <source>tt_content:imagecols,
687 tt_content:image</source>
688 <target>tt_content:imagecols,
689 tt_content:image</target>
690 <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>
691 </trans-unit>
692 <trans-unit id="image_noRows.description" approved="yes">
693 <source>Disables strict tablerows in the image block.</source>
694 <target>Disables strict tablerows in the image block.</target>
695 </trans-unit>
696 <trans-unit id="image_noRows.details" approved="yes">
697 <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.
698 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>
699 <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.
700 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>
701 </trans-unit>
702 <trans-unit id="_image_noRows.seeAlso" approved="yes">
703 <source>tt_content:imagecols,
704 tt_content:image</source>
705 <target>tt_content:imagecols,
706 tt_content:image</target>
707 <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>
708 </trans-unit>
709 <trans-unit id="image_link.description" approved="yes">
710 <source>Enter a link for the images.</source>
711 <target>Enter a link for the images.</target>
712 </trans-unit>
713 <trans-unit id="image_link.details" approved="yes">
714 <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.
715
716 See Pagecontent&gt;Link below for details on syntax.</source>
717 <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.
718
719 See Pagecontent&gt;Link below for details on syntax.</target>
720 </trans-unit>
721 <trans-unit id="_image_link.seeAlso" approved="yes">
722 <source>tt_content:header_link,
723 tt_content:image_zoom,
724 tt_content:image</source>
725 <target>tt_content:header_link,
726 tt_content:image_zoom,
727 tt_content:image</target>
728 <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>
729 </trans-unit>
730 <trans-unit id="image_zoom.description" approved="yes">
731 <source>Check this option, and the image will link to a new window with a bigger version.</source>
732 <target>Check this option, and the image will link to a new window with a bigger version.</target>
733 </trans-unit>
734 <trans-unit id="image_zoom.details" approved="yes">
735 <source>This option overrides the value in the Link-field.</source>
736 <target>This option overrides the value in the Link-field.</target>
737 </trans-unit>
738 <trans-unit id="_image_zoom.seeAlso" approved="yes">
739 <source>tt_content:image_link,
740 tt_content:image</source>
741 <target>tt_content:image_link,
742 tt_content:image</target>
743 <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>
744 </trans-unit>
745 <trans-unit id="image_effects.description" approved="yes">
746 <source>Select special image processing effects.</source>
747 <target>Select special image processing effects.</target>
748 </trans-unit>
749 <trans-unit id="_image_effects.seeAlso" approved="yes">
750 <source>tt_content:image_compression,
751 tt_content:image_frames,
752 tt_content:image</source>
753 <target>tt_content:image_compression,
754 tt_content:image_frames,
755 tt_content:image</target>
756 <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>
757 </trans-unit>
758 <trans-unit id="image_frames.description" approved="yes">
759 <source>Select special image framing options.</source>
760 <target>Select special image framing options.</target>
761 </trans-unit>
762 <trans-unit id="_image_frames.seeAlso" approved="yes">
763 <source>tt_content:image_compression,
764 tt_content:image_effects,
765 tt_content:image</source>
766 <target>tt_content:image_compression,
767 tt_content:image_effects,
768 tt_content:image</target>
769 <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>
770 </trans-unit>
771 <trans-unit id="image_compression.description" approved="yes">
772 <source>Select compression/quality options.</source>
773 <target>Select compression/quality options.</target>
774 </trans-unit>
775 <trans-unit id="_image_compression.seeAlso" approved="yes">
776 <source>tt_content:image_frames,
777 tt_content:image_effects,
778 tt_content:image</source>
779 <target>tt_content:image_frames,
780 tt_content:image_effects,
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="imagecols.description" approved="yes">
785 <source>Select the number of columns in the image block.</source>
786 <target>Select the number of columns in the image block.</target>
787 </trans-unit>
788 <trans-unit id="_imagecols.seeAlso" approved="yes">
789 <source>tt_content:image_noRows,
790 tt_content:image</source>
791 <target>tt_content:image_noRows,
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="imagecaption.description" approved="yes">
796 <source>Enter a caption for the image block</source>
797 <target>Enter a caption for the image block</target>
798 </trans-unit>
799 <trans-unit id="imagecaption.details" approved="yes">
800 <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.
801 In that case each line in this field will be the image caption of the corresponding image in the list.
802
803 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>
804 <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.
805 In that case each line in this field will be the image caption of the corresponding image in the list.
806
807 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>
808 </trans-unit>
809 <trans-unit id="_imagecaption.seeAlso" approved="yes">
810 <source>tt_content:imagecaption_position,
811 tt_content:image</source>
812 <target>tt_content:imagecaption_position,
813 tt_content:image</target>
814 <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>
815 </trans-unit>
816 <trans-unit id="imagecaption_position.description" approved="yes">
817 <source>Places the image caption to the left, centered or to the right.</source>
818 <target>Places the image caption to the left, centered or to the right.</target>
819 </trans-unit>
820 <trans-unit id="_imagecaption_position.seeAlso" approved="yes">
821 <source>tt_content:imagecaption,
822 tt_content:image</source>
823 <target>tt_content:imagecaption,
824 tt_content:image</target>
825 <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>
826 </trans-unit>
827 <trans-unit id="cols.description" approved="yes">
828 <source>Select a fixed number of table columns</source>
829 <target>Select a fixed number of table columns</target>
830 </trans-unit>
831 <trans-unit id="pages.description" approved="yes">
832 <source>Insert page(s)</source>
833 <target>Insert page(s)</target>
834 </trans-unit>
835 <trans-unit id="pages.details" approved="yes">
836 <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.
837
838 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.
839
840 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!
841 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.
842 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.
843
844 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.
845
846 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>
847 <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.
848
849 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.
850
851 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!
852 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.
853 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.
854
855 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.
856
857 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>
858 </trans-unit>
859 <trans-unit id="_pages.seeAlso" approved="yes">
860 <source>tt_content:CType,
861 tt_content:recursive</source>
862 <target>tt_content:CType,
863 tt_content:recursive</target>
864 <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>
865 </trans-unit>
866 <trans-unit id="recursive.description" approved="yes">
867 <source>Select how many subleves should be additionally selected for each page in the list.</source>
868 <target>Select how many subleves should be additionally selected for each page in the list.</target>
869 </trans-unit>
870 <trans-unit id="recursive.details" approved="yes">
871 <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!
872
873 &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>
874 <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!
875
876 &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>
877 </trans-unit>
878 <trans-unit id="_recursive.seeAlso" approved="yes">
879 <source>tt_content:pages</source>
880 <target>tt_content:pages</target>
881 <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>
882 </trans-unit>
883 <trans-unit id="menu_type.description" approved="yes">
884 <source>Select which kind of menu you wish to create.</source>
885 <target>Select which kind of menu you wish to create.</target>
886 </trans-unit>
887 <trans-unit id="menu_type.details" approved="yes">
888 <source>This is a short description of each type:
889
890 &lt;strong&gt;Menu of these pages&lt;/strong&gt;
891 This will create a list of links to the pages you insert in the Startingpoint list.
892
893 &lt;strong&gt;Menu of subpages to these pages&lt;/strong&gt;
894 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.
895
896 &lt;strong&gt;Menu of subpages to these pages (with abstract)&lt;/strong&gt;
897 Like the previous, but this will include the content of the Abstract field of the pages.
898
899 &lt;strong&gt;Menu of subpages to these pages + sections&lt;/strong&gt;
900 Like the previous, but including 'submenu' links to all content elements on the page which has the "Index" checkbox set.
901
902 &lt;strong&gt;Sitemap&lt;/strong&gt;
903 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.
904
905 &lt;strong&gt;Section index (pagecontent w/Index checked)&lt;/strong&gt;
906 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.
907 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.
908
909 &lt;strong&gt;Recently updated pages&lt;/strong&gt;
910 This displays the 10 most recently updated pages.
911 &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.
912
913 &lt;strong&gt;Related pages (based on keywords)&lt;/strong&gt;
914 Displays other related pages based on the keywords set for this page matched up with the keywords on other pages.
915
916
917 &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>
918 <target>This is a short description of each type:
919
920 &lt;strong&gt;Menu of these pages&lt;/strong&gt;
921 This will create a list of links to the pages you insert in the Startingpoint list.
922
923 &lt;strong&gt;Menu of subpages to these pages&lt;/strong&gt;
924 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.
925
926 &lt;strong&gt;Menu of subpages to these pages (with abstract)&lt;/strong&gt;
927 Like the previous, but this will include the content of the Abstract field of the pages.
928
929 &lt;strong&gt;Menu of subpages to these pages + sections&lt;/strong&gt;
930 Like the previous, but including 'submenu' links to all content elements on the page which has the "Index" checkbox set.
931
932 &lt;strong&gt;Sitemap&lt;/strong&gt;
933 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.
934
935 &lt;strong&gt;Section index (pagecontent w/Index checked)&lt;/strong&gt;
936 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.
937 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.
938
939 &lt;strong&gt;Recently updated pages&lt;/strong&gt;
940 This displays the 10 most recently updated pages.
941 &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.
942
943 &lt;strong&gt;Related pages (based on keywords)&lt;/strong&gt;
944 Displays other related pages based on the keywords set for this page matched up with the keywords on other pages.
945
946
947 &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>
948 </trans-unit>
949 <trans-unit id="_menu_type.seeAlso" approved="yes">
950 <source>tt_content:pages,
951 tt_content:sectionIndex</source>
952 <target>tt_content:pages,
953 tt_content:sectionIndex</target>
954 <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>
955 </trans-unit>
956 <trans-unit id="list_type.description" approved="yes">
957 <source>Select a plugin to insert.</source>
958 <target>Select a plugin to insert.</target>
959 </trans-unit>
960 <trans-unit id="list_type.details" approved="yes">
961 <source>The list of plugins you can insert on a page. The available plugins depends on which extensions are installed.</source>
962 <target>The list of plugins you can insert on a page. The available plugins depends on which extensions are installed.</target>
963 </trans-unit>
964 <trans-unit id="_list_type.seeAlso" approved="yes">
965 <source>_MOD_tools_em</source>
966 <target>_MOD_tools_em</target>
967 <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>
968 </trans-unit>
969 <trans-unit id="_list_type.image" approved="yes">
970 <source>EXT:context_help/cshimages/ttcontent_7.png</source>
971 <target>EXT:context_help/cshimages/ttcontent_7.png</target>
972 <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>
973 </trans-unit>
974 <trans-unit id="select_key.description" approved="yes">
975 <source>Enter a code string.</source>
976 <target>Enter a code string.</target>
977 </trans-unit>
978 <trans-unit id="select_key.details" approved="yes">
979 <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>
980 <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>
981 </trans-unit>
982 <trans-unit id="_select_key.seeAlso" approved="yes">
983 <source>tt_content:list_type</source>
984 <target>tt_content:list_type</target>
985 <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>
986 </trans-unit>
987 <trans-unit id="table_bgColor.description" approved="yes">
988 <source>Select table background color.</source>
989 <target>Select table background color.</target>
990 </trans-unit>
991 <trans-unit id="table_border.description" approved="yes">
992 <source>Select table border thickness.</source>
993 <target>Select table border thickness.</target>
994 </trans-unit>
995 <trans-unit id="table_cellspacing.description" approved="yes">
996 <source>Select table cell spacing.</source>
997 <target>Select table cell spacing.</target>
998 </trans-unit>
999 <trans-unit id="table_cellspacing.details" approved="yes">
1000 <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>
1001 <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>
1002 </trans-unit>
1003 <trans-unit id="table_cellpadding.description" approved="yes">
1004 <source>Select table cellpadding.</source>
1005 <target>Select table cellpadding.</target>
1006 </trans-unit>
1007 <trans-unit id="table_cellpadding.details" approved="yes">
1008 <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>
1009 <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>
1010 </trans-unit>
1011 <trans-unit id="media.description" approved="yes">
1012 <source>Add files to the list here.</source>
1013 <target>Add files to the list here.</target>
1014 </trans-unit>
1015 <trans-unit id="multimedia.description" approved="yes">
1016 <source>Insert the multimedia element, eg. a flash movie here.</source>
1017 <target>Insert the multimedia element, eg. a flash movie here.</target>
1018 </trans-unit>
1019 <trans-unit id="filelink_size.description" approved="yes">
1020 <source>Check this, if you wish the filesizes to be displayed.</source>
1021 <target>Check this, if you wish the filesizes to be displayed.</target>
1022 </trans-unit>
1023 <trans-unit id="records.description" approved="yes">
1024 <source>Insert relations to records.</source>
1025 <target>Insert relations to records.</target>
1026 </trans-unit>
1027 <trans-unit id="spaceBefore.description" approved="yes">
1028 <source>Enter the amount of whitespace (in pixels) to insert &lt;em&gt;before&lt;/em&gt; this content element.</source>
1029 <target>Enter the amount of whitespace (in pixels) to insert &lt;em&gt;before&lt;/em&gt; this content element.</target>
1030 </trans-unit>
1031 <trans-unit id="_spaceBefore.seeAlso" approved="yes">
1032 <source>tt_content:spaceAfter,
1033 tt_content:section_frame</source>
1034 <target>tt_content:spaceAfter,
1035 tt_content:section_frame</target>
1036 <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>
1037 </trans-unit>
1038 <trans-unit id="spaceAfter.description" approved="yes">
1039 <source>Enter the amount of whitespace (in pixels) to insert &lt;em&gt;after&lt;/em&gt; this content element.</source>
1040 <target>Enter the amount of whitespace (in pixels) to insert &lt;em&gt;after&lt;/em&gt; this content element.</target>
1041 </trans-unit>
1042 <trans-unit id="_spaceAfter.seeAlso" approved="yes">
1043 <source>tt_content:spaceBefore,
1044 tt_content:section_frame</source>
1045 <target>tt_content:spaceBefore,
1046 tt_content:section_frame</target>
1047 <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>
1048 </trans-unit>
1049 <trans-unit id="section_frame.description" approved="yes">
1050 <source>Select a framing option for the content element.</source>
1051 <target>Select a framing option for the content element.</target>
1052 </trans-unit>
1053 <trans-unit id="_section_frame.seeAlso" approved="yes">
1054 <source>tt_content:spaceAfter,
1055 tt_content:spaceBefore</source>
1056 <target>tt_content:spaceAfter,
1057 tt_content:spaceBefore</target>
1058 <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>
1059 </trans-unit>
1060 <trans-unit id="splash_layout.description" approved="yes">
1061 <source>Select the design for the Text box.</source>
1062 <target>Select the design for the Text box.</target>
1063 </trans-unit>
1064 <trans-unit id="splash_layout.details" approved="yes">
1065 <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>
1066 <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>
1067 </trans-unit>
1068 <trans-unit id="_splash_layout.seeAlso" approved="yes">
1069 <source>tt_content:CType</source>
1070 <target>tt_content:CType</target>
1071 <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>
1072 </trans-unit>
1073 <trans-unit id="sectionIndex.description" approved="yes">
1074 <source>If set, the content element will appear in section indices.</source>
1075 <target>If set, the content element will appear in section indices.</target>
1076 </trans-unit>
1077 <trans-unit id="sectionIndex.details" approved="yes">
1078 <source>See details for the Menu-type selector (click below).</source>
1079 <target>See details for the Menu-type selector (click below).</target>
1080 </trans-unit>
1081 <trans-unit id="_sectionIndex.seeAlso" approved="yes">
1082 <source>tt_content:menu_type</source>
1083 <target>tt_content:menu_type</target>
1084 <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>
1085 </trans-unit>
1086 <trans-unit id="linkToTop.description" approved="yes">
1087 <source>If checked, a little "To top" link will be inserted after the content element.</source>
1088 <target>If checked, a little "To top" link will be inserted after the content element.</target>
1089 </trans-unit>
1090 <trans-unit id="rte_enabled.description" approved="yes">
1091 <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>
1092 <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>
1093 </trans-unit>
1094 <trans-unit id="_rte_enabled.seeAlso" approved="yes">
1095 <source>tt_content:bodytext</source>
1096 <target>tt_content:bodytext</target>
1097 <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>
1098 </trans-unit>
1099 <trans-unit id="pi_flexform.description" approved="yes">
1100 <source>FlexForm Configuration of Plugins</source>
1101 <target>FlexForm Configuration of Plugins</target>
1102 </trans-unit>
1103 <trans-unit id="pi_flexform.details" approved="yes">
1104 <source>Some plugins may require configuration of their options. They may use this field for FlexForm based configuration settings (stored as XML).</source>
1105 <target>Some plugins may require configuration of their options. They may use this field for FlexForm based configuration settings (stored as XML).</target>
1106 </trans-unit>
1107 <trans-unit id="_pi_flexform.seeAlso" approved="yes">
1108 <source>tt_content:list_type</source>
1109 <target>tt_content:list_type</target>
1110 <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>
1111 </trans-unit>
1112 </body>
1113 </file>
1114 </xliff>