[BUGFIX] High CPU load in IE8/9 when using context menu in htmlArea RTE
[Packages/TYPO3.CMS.git] / typo3 / sysext / context_help / locallang_csh_pages.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="layout.description" approved="yes">
7 <source>Select a layout for the page. Any effect depends on the website template.</source>
8 <target>Select a layout for the page. Any effect depends on the website template.</target>
9 </trans-unit>
10 <trans-unit id="layout.details" approved="yes">
11 <source>This option may not have any impact on the page design since it depends on how (and if) the front end template uses it. In most default templates it's not used.</source>
12 <target>This option may not have any impact on the page design since it depends on how (and if) the front end template uses it. In most default templates it's not used.</target>
13 </trans-unit>
14 <trans-unit id="doktype.description" approved="yes">
15 <source>Select a page type affects whether the page represents a visible webpage or is used for other purposes.</source>
16 <target>Select a page type affects whether the page represents a visible webpage or is used for other purposes.</target>
17 </trans-unit>
18 <trans-unit id="doktype.details" approved="yes">
19 <source>'Standard' and 'Advanced' types are regular webpages, just differing in the number of options.
20 'External URL' and 'Shortcut' types allows you to let a page be a shortcut to either an external URL or in the latter case a page in the page tree.
21 'Not in menu' is also a regular page, but will not be shown in the navigation. &lt;em&gt;This page type is deprecated! Please use the "Hide in menu" option!&lt;/em&gt;
22 'Backend User Section' is an option which requires a backend user to be logged in for the page to be visible.
23
24 &lt;b&gt;Special types:&lt;/b&gt;
25 'Spacer' is only meaningfull if your frontend navigation is programmed to use it. In this case it does not represent a page with content but is intended to be a non-clickable placeholder in the navigation.
26 'SysFolder' is a page type which cannot be shown as a webpage but is rather acting as a storage for records of your choice.
27 'Recycler' is a garbage can. Pages and records in a recycler are not visible in the frontend.
28
29 &lt;b&gt;Notice:&lt;/b&gt; Each type usually has a specific icon attached. Also certain types may not be available for a user (so you may experience that some of the options are not available for you!). And finally each type is configured to allow only certain table records in the page (SysFolder will allow any record if you have any problems).</source>
30 <target>'Standard' and 'Advanced' types are regular webpages, just differing in the number of options.
31 'External URL' and 'Shortcut' types allows you to let a page be a shortcut to either an external URL or in the latter case a page in the page tree.
32 'Not in menu' is also a regular page, but will not be shown in the navigation. &lt;em&gt;This page type is deprecated! Please use the "Hide in menu" option!&lt;/em&gt;
33 'Backend User Section' is an option which requires a backend user to be logged in for the page to be visible.
34
35 &lt;b&gt;Special types:&lt;/b&gt;
36 'Spacer' is only meaningfull if your frontend navigation is programmed to use it. In this case it does not represent a page with content but is intended to be a non-clickable placeholder in the navigation.
37 'SysFolder' is a page type which cannot be shown as a webpage but is rather acting as a storage for records of your choice.
38 'Recycler' is a garbage can. Pages and records in a recycler are not visible in the frontend.
39
40 &lt;b&gt;Notice:&lt;/b&gt; Each type usually has a specific icon attached. Also certain types may not be available for a user (so you may experience that some of the options are not available for you!). And finally each type is configured to allow only certain table records in the page (SysFolder will allow any record if you have any problems).</target>
41 </trans-unit>
42 <trans-unit id="_doktype.seeAlso" approved="yes">
43 <source>pages:shortcut,
44 pages:url</source>
45 <target>pages:shortcut,
46 pages:url</target>
47 </trans-unit>
48 <trans-unit id="hidden.description" approved="yes">
49 <source>If this is checked, the page will be hidden on the website.</source>
50 <target>If this is checked, the page will be hidden on the website.</target>
51 </trans-unit>
52 <trans-unit id="hidden.details" approved="yes">
53 <source>The 'Hidden', 'Start', 'Stop' and 'Access' options are all about limiting access to pages and thus they are related in functionality. In any case where a page is not visible due to one of these options, the page will not show up in the site navigation.
54 Notice, these options are related &lt;em&gt;only&lt;/em&gt; to the page for which they are set. If you want their effect to cover the subpages as well, you must enable the 'Include subpages' option.
55 When you're logged in as a backend user you can preview hidden pages if you have read access to them.</source>
56 <target>The 'Hidden', 'Start', 'Stop' and 'Access' options are all about limiting access to pages and thus they are related in functionality. In any case where a page is not visible due to one of these options, the page will not show up in the site navigation.
57 Notice, these options are related &lt;em&gt;only&lt;/em&gt; to the page for which they are set. If you want their effect to cover the subpages as well, you must enable the 'Include subpages' option.
58 When you're logged in as a backend user you can preview hidden pages if you have read access to them.</target>
59 </trans-unit>
60 <trans-unit id="_hidden.seeAlso" approved="yes">
61 <source>pages:starttime,pages:endtime,pages:fe_group,pages:extendToSubpages</source>
62 <target>pages:starttime,pages:endtime,pages:fe_group,pages:extendToSubpages</target>
63 </trans-unit>
64 <trans-unit id="_hidden.image" approved="yes">
65 <source>EXT:context_help/cshimages/hidden_page.gif,
66 EXT:context_help/cshimages/pages_1.png</source>
67 <target>EXT:context_help/cshimages/hidden_page.gif,
68 EXT:context_help/cshimages/pages_1.png</target>
69 </trans-unit>
70 <trans-unit id="hidden.image_descr" approved="yes">
71 <source>The page icon of a hidden page is dimmed and a red X is added.
72 If you view a page that is hidden and you are logged in into the backend you will still be able to see the page. The red "Preview" box will tell you that this page is visible to you because of this special circumstance.</source>
73 <target>The page icon of a hidden page is dimmed and a red X is added.
74 If you view a page that is hidden and you are logged in into the backend you will still be able to see the page. The red "Preview" box will tell you that this page is visible to you because of this special circumstance.</target>
75 </trans-unit>
76 <trans-unit id="starttime.description" approved="yes">
77 <source>The 'Start' time determines the date from which the page will be visible online. Use this to 'publish' the page on a certain date. If 'Start' time is not set, the page will be online instantly (unless the page is hidden otherwise).</source>
78 <target>The 'Start' time determines the date from which the page will be visible online. Use this to 'publish' the page on a certain date. If 'Start' time is not set, the page will be online instantly (unless the page is hidden otherwise).</target>
79 </trans-unit>
80 <trans-unit id="starttime.syntax" approved="yes">
81 <source>Format is DD-MM-YYYY. You may enter the value in other ways - it will be evaluated immediately.
82 If you insert eg. a 'd' the current date is inserted. You can also append any value in the field with eg. '+10' which will add 10 days to the current value. For instance setting the value to 'd+10' would select a date 10 days from now.</source>
83 <target>Format is DD-MM-YYYY. You may enter the value in other ways - it will be evaluated immediately.
84 If you insert eg. a 'd' the current date is inserted. You can also append any value in the field with eg. '+10' which will add 10 days to the current value. For instance setting the value to 'd+10' would select a date 10 days from now.</target>
85 </trans-unit>
86 <trans-unit id="_starttime.seeAlso" approved="yes">
87 <source>pages:endtime,pages:hidden</source>
88 <target>pages:endtime,pages:hidden</target>
89 </trans-unit>
90 <trans-unit id="_.seeAlso" approved="yes">
91 <source>tt_content</source>
92 <target>tt_content</target>
93 </trans-unit>
94 <trans-unit id="endtime.description" approved="yes">
95 <source>The 'Stop' time is the date from which the page will not be online anymore.</source>
96 <target>The 'Stop' time is the date from which the page will not be online anymore.</target>
97 </trans-unit>
98 <trans-unit id="endtime.syntax" approved="yes">
99 <source>See Page / Start (click below)</source>
100 <target>See Page / Start (click below)</target>
101 </trans-unit>
102 <trans-unit id="_endtime.seeAlso" approved="yes">
103 <source>pages:starttime</source>
104 <target>pages:starttime</target>
105 </trans-unit>
106 <trans-unit id="fe_group.description" approved="yes">
107 <source>If 'Access' is set to a usergroup name, only website users which are members of the selected usergroup will be able to view the page when they are logged in. The special option 'Hide at login' means the page will &lt;em&gt;not&lt;/em&gt; be visible for website users that are logged in. Likewise "Show at login" will make the page visible for any logged in frontend user.</source>
108 <target>If 'Access' is set to a usergroup name, only website users which are members of the selected usergroup will be able to view the page when they are logged in. The special option 'Hide at login' means the page will &lt;em&gt;not&lt;/em&gt; be visible for website users that are logged in. Likewise "Show at login" will make the page visible for any logged in frontend user.</target>
109 </trans-unit>
110 <trans-unit id="_fe_group.seeAlso" approved="yes">
111 <source>fe_groups</source>
112 <target>fe_groups</target>
113 </trans-unit>
114 <trans-unit id="_fe_group.image" approved="yes">
115 <source>EXT:context_help/cshimages/fegroups_4.png</source>
116 <target>EXT:context_help/cshimages/fegroups_4.png</target>
117 </trans-unit>
118 <trans-unit id="extendToSubpages.description" approved="yes">
119 <source>By default the Start, Stop, Access and Hidden options are effective &lt;em&gt;only&lt;/em&gt; for the page on which they are set. If the option 'Include subpages' is checked for the page, then their effect is inherited by all subpages to that page.</source>
120 <target>By default the Start, Stop, Access and Hidden options are effective &lt;em&gt;only&lt;/em&gt; for the page on which they are set. If the option 'Include subpages' is checked for the page, then their effect is inherited by all subpages to that page.</target>
121 </trans-unit>
122 <trans-unit id="extendToSubpages.details" approved="yes">
123 <source>Consider a scenario where you want to create a whole section of subpages only visible for users which are logged in. Setting the 'Access' option for the top page in the section would affect access to that page only. So the page would not show up in the navigation unless you are logged in.
124 However the subpages would still be visible if one could guess the id-number of the pages and enter it manually in the URL. But setting this option would extend the effect of the top page setting to cover all subpages as well.</source>
125 <target>Consider a scenario where you want to create a whole section of subpages only visible for users which are logged in. Setting the 'Access' option for the top page in the section would affect access to that page only. So the page would not show up in the navigation unless you are logged in.
126 However the subpages would still be visible if one could guess the id-number of the pages and enter it manually in the URL. But setting this option would extend the effect of the top page setting to cover all subpages as well.</target>
127 </trans-unit>
128 <trans-unit id="_extendToSubpages.seeAlso" approved="yes">
129 <source>pages:hidden,
130 pages:starttime,
131 pages:endtime,
132 pages:fe_group</source>
133 <target>pages:hidden,
134 pages:starttime,
135 pages:endtime,
136 pages:fe_group</target>
137 </trans-unit>
138 <trans-unit id="_extendToSubpages.image" approved="yes">
139 <source>EXT:context_help/cshimages/pages_2.png</source>
140 <target>EXT:context_help/cshimages/pages_2.png</target>
141 </trans-unit>
142 <trans-unit id="extendToSubpages.image_descr" approved="yes">
143 <source>This page icon has access restricted to a certain group and "Include subpages" set as well. This is reflected in the way the icon changed look.</source>
144 <target>This page icon has access restricted to a certain group and "Include subpages" set as well. This is reflected in the way the icon changed look.</target>
145 </trans-unit>
146 <trans-unit id="alias.description" approved="yes">
147 <source>An 'alias' is a unique identification string for a page. You can use this string instead of the id-number to refer to the page.</source>
148 <target>An 'alias' is a unique identification string for a page. You can use this string instead of the id-number to refer to the page.</target>
149 </trans-unit>
150 <trans-unit id="alias.details" approved="yes">
151 <source>Ultimately a page is identified by its id-number. For instance you may refer to a page in TYPO3 by '.../?id=123'. If the page with id '123' has the alias 'one_two_three', then the URL '.../?id=one_two_three' would display exactly the same page, because 'one_two_three' is an alias for the id '123'.
152 Normally you should assign aliases only to a limited number of pages, preferably those you need to link to a lot. In most TYPO3 configurations you would be able to use the syntax '.. &amp;lt;link one_two_three&amp;gt;go to the page&amp;lt;/link&amp;gt; ..' to create a link to the page. This is easier to remember.
153 Another use is if you need to change which page such a link is referring to. In that case you can delete the alias for one page and enter it for another and all links pointing to the alias would now refer to another id-number.</source>
154 <target>Ultimately a page is identified by its id-number. For instance you may refer to a page in TYPO3 by '.../?id=123'. If the page with id '123' has the alias 'one_two_three', then the URL '.../?id=one_two_three' would display exactly the same page, because 'one_two_three' is an alias for the id '123'.
155 Normally you should assign aliases only to a limited number of pages, preferably those you need to link to a lot. In most TYPO3 configurations you would be able to use the syntax '.. &amp;lt;link one_two_three&amp;gt;go to the page&amp;lt;/link&amp;gt; ..' to create a link to the page. This is easier to remember.
156 Another use is if you need to change which page such a link is referring to. In that case you can delete the alias for one page and enter it for another and all links pointing to the alias would now refer to another id-number.</target>
157 </trans-unit>
158 <trans-unit id="alias.syntax" approved="yes">
159 <source>An alias can contain only lowercase alphanumeric characters and must be unique.
160 Please notice: If the entered value was not unique, it will automatically be prepended with a number.</source>
161 <target>An alias can contain only lowercase alphanumeric characters and must be unique.
162 Please notice: If the entered value was not unique, it will automatically be prepended with a number.</target>
163 </trans-unit>
164 <trans-unit id="target.description" approved="yes">
165 <source>The HTML target of menu items linking to this page. Also can be used for open page in popup.</source>
166 <target>The HTML target of menu items linking to this page. Also can be used for open page in popup.</target>
167 </trans-unit>
168 <trans-unit id="target.details" approved="yes">
169 <source>Set this value only to overrule the default link, which should be configured correctly for most pages in the website TypoScript template.
170 There are more options with the target field
171
172 Setting an integer value at the start of the field adds it as the default type for the page.
173 For example, if an RSS feed is configured in Typoscript as typeNum=100, setting the target to 100 could be used to add an RSS link in the menu.
174
175 For open in popup use following syntax:
176 400x200 - this opens page in a popup of size 400x200
177 230x450:resizable=0,location=1 - opens page in popup with parameters
178
179 Combined:
180 100 600x350 - opens page in popup with type 100
181 2 _blank - opens page with target "_blank" and type 2
182 </source>
183 <target>Set this value only to overrule the default link, which should be configured correctly for most pages in the website TypoScript template.
184 There are more options with the target field
185
186 Setting an integer value at the start of the field adds it as the default type for the page.
187 For example, if an RSS feed is configured in Typoscript as typeNum=100, setting the target to 100 could be used to add an RSS link in the menu.
188
189 For open in popup use following syntax:
190 400x200 - this opens page in a popup of size 400x200
191 230x450:resizable=0,location=1 - opens page in popup with parameters
192
193 Combined:
194 100 600x350 - opens page in popup with type 100
195 2 _blank - opens page with target "_blank" and type 2
196 </target>
197 </trans-unit>
198 <trans-unit id="no_cache.description" approved="yes">
199 <source>This option disables server caching of the page.</source>
200 <target>This option disables server caching of the page.</target>
201 </trans-unit>
202 <trans-unit id="no_cache.details" approved="yes">
203 <source>Normally pages in TYPO3 are cached on the server after being constructed for the first time. This means a page is displayed much faster the second time it's requested.
204 For most pages this presents no problems - rather it's boosting the performance of the website.
205 However you may need to disable caching for a page if it contains dynamic content which must not be cached under any circumstances. Normally the PHP-code rendering such content is programmed to disable the caching automatically. But in any case you can force the page not to be cached via this option.</source>
206 <target>Normally pages in TYPO3 are cached on the server after being constructed for the first time. This means a page is displayed much faster the second time it's requested.
207 For most pages this presents no problems - rather it's boosting the performance of the website.
208 However you may need to disable caching for a page if it contains dynamic content which must not be cached under any circumstances. Normally the PHP-code rendering such content is programmed to disable the caching automatically. But in any case you can force the page not to be cached via this option.</target>
209 </trans-unit>
210 <trans-unit id="_no_cache.seeAlso" approved="yes">
211 <source>pages:cache_timeout</source>
212 <target>pages:cache_timeout</target>
213 </trans-unit>
214 <trans-unit id="cache_timeout.description" approved="yes">
215 <source>Sets the cache timeout for the page.</source>
216 <target>Sets the cache timeout for the page.</target>
217 </trans-unit>
218 <trans-unit id="cache_timeout.details" approved="yes">
219 <source>By default pages last for 24 hours in the cache. After that period the page is constructed again and rewritten to the cache. Depending on your configuration, the cache may also be cleared at midnight.
220 Anyhow you may here set another timeout time for the page in cache if you need to.
221 This option is used quite rarely.</source>
222 <target>By default pages last for 24 hours in the cache. After that period the page is constructed again and rewritten to the cache. Depending on your configuration, the cache may also be cleared at midnight.
223 Anyhow you may here set another timeout time for the page in cache if you need to.
224 This option is used quite rarely.</target>
225 </trans-unit>
226 <trans-unit id="_cache_timeout.seeAlso" approved="yes">
227 <source>pages:no_cache</source>
228 <target>pages:no_cache</target>
229 </trans-unit>
230 <trans-unit id="no_search.description" approved="yes">
231 <source>If enabled, this option excludes the page from searching operations on the website.</source>
232 <target>If enabled, this option excludes the page from searching operations on the website.</target>
233 </trans-unit>
234 <trans-unit id="author.description" approved="yes">
235 <source>Enter the page authors name.</source>
236 <target>Enter the page authors name.</target>
237 </trans-unit>
238 <trans-unit id="author.details" approved="yes">
239 <source>Whether the author name is used or not depends on the setup of your TypoScript template.
240
241 - You may use it in a meta-tag.
242 - If you're using TYPO3 pages as 'articles' then you could use this field to display the name of the page (article) author.</source>
243 <target>Whether the author name is used or not depends on the setup of your TypoScript template.
244
245 - You may use it in a meta-tag.
246 - If you're using TYPO3 pages as 'articles' then you could use this field to display the name of the page (article) author.</target>
247 </trans-unit>
248 <trans-unit id="_author.seeAlso" approved="yes">
249 <source>pages:author_email</source>
250 <target>pages:author_email</target>
251 </trans-unit>
252 <trans-unit id="author_email.description" approved="yes">
253 <source>Enter the page authors email address.</source>
254 <target>Enter the page authors email address.</target>
255 </trans-unit>
256 <trans-unit id="_author_email.seeAlso" approved="yes">
257 <source>pages:author</source>
258 <target>pages:author</target>
259 </trans-unit>
260 <trans-unit id="module.description" approved="yes">
261 <source>Define the page as a frontend 'module'.</source>
262 <target>Define the page as a frontend 'module'.</target>
263 </trans-unit>
264 <trans-unit id="module.details" approved="yes">
265 <source>In the backend there is a module called 'Web&gt;Modules' as well as a header 'Modules' in the 'User&gt;Task Center'. Both functions list the available 'Frontend modules' to which the user has access.
266 Basically, setting this option just marks the page so the backend knows this page contains eg. a forum or is the root page of a shopping section on the website. And based on this knowledge the backend is able to display a shortcut list as well as relevant functionality in the 'Web&gt;Modules' module. The frontend display is - largely - not affected.
267 So in effect, by 'marking' a page to be a 'Shop' module simply means it'll show up in the shortcut list of modules in the backend.
268
269 There may be a little more to it than this, but for details on the subject, you must refer to the administration documentation.
270
271 It's recommended that only admin-users are allowed access to this field!</source>
272 <target>In the backend there is a module called 'Web&gt;Modules' as well as a header 'Modules' in the 'User&gt;Task Center'. Both functions list the available 'Frontend modules' to which the user has access.
273 Basically, setting this option just marks the page so the backend knows this page contains eg. a forum or is the root page of a shopping section on the website. And based on this knowledge the backend is able to display a shortcut list as well as relevant functionality in the 'Web&gt;Modules' module. The frontend display is - largely - not affected.
274 So in effect, by 'marking' a page to be a 'Shop' module simply means it'll show up in the shortcut list of modules in the backend.
275
276 There may be a little more to it than this, but for details on the subject, you must refer to the administration documentation.
277
278 It's recommended that only admin-users are allowed access to this field!</target>
279 </trans-unit>
280 <trans-unit id="media.description" approved="yes">
281 <source>Attach media files related to the page.</source>
282 <target>Attach media files related to the page.</target>
283 </trans-unit>
284 <trans-unit id="media.details" approved="yes">
285 <source>This fields allows you to attach various files to the page record.
286 If and how these files are used depends on your template. So basically which files you attach here and in which order they must be listed is determined by your specific website template and thus you should seek instructions in the documentation for your specific website.
287 As an example this field could be used from the template to allow you to attach a logo-image to the page. Or the template might be programmed to expect the first file to be an image used as a link in the navigation menu. But remember, this totally depends on how this field is used in the programming of the template.</source>
288 <target>This fields allows you to attach various files to the page record.
289 If and how these files are used depends on your template. So basically which files you attach here and in which order they must be listed is determined by your specific website template and thus you should seek instructions in the documentation for your specific website.
290 As an example this field could be used from the template to allow you to attach a logo-image to the page. Or the template might be programmed to expect the first file to be an image used as a link in the navigation menu. But remember, this totally depends on how this field is used in the programming of the template.</target>
291 </trans-unit>
292 <trans-unit id="subtitle.description" approved="yes">
293 <source>Enter a subtitle if needed.</source>
294 <target>Enter a subtitle if needed.</target>
295 </trans-unit>
296 <trans-unit id="subtitle.details" approved="yes">
297 <source>Whether this field is used or not depends on the template. In most cases it's not used.
298 You may use this field as you like in your own templates.</source>
299 <target>Whether this field is used or not depends on the template. In most cases it's not used.
300 You may use this field as you like in your own templates.</target>
301 </trans-unit>
302 <trans-unit id="url.description" approved="yes">
303 <source>Enter the URL to which this page is supposed to link.</source>
304 <target>Enter the URL to which this page is supposed to link.</target>
305 </trans-unit>
306 <trans-unit id="url.details" approved="yes">
307 <source>Example: 'http://www.typo3.com' or just 'www.typo3.com' provided the 'Type' selector is set to 'http://'.
308 Use the 'Type' selector to select a prefix for the URL.
309
310 This option is used only if the page 'Type' is set to 'External URL'.</source>
311 <target>Example: 'http://www.typo3.com' or just 'www.typo3.com' provided the 'Type' selector is set to 'http://'.
312 Use the 'Type' selector to select a prefix for the URL.
313
314 This option is used only if the page 'Type' is set to 'External URL'.</target>
315 </trans-unit>
316 <trans-unit id="_url.seeAlso" approved="yes">
317 <source>pages:urltype</source>
318 <target>pages:urltype</target>
319 </trans-unit>
320 <trans-unit id="shortcut.description" approved="yes">
321 <source>Insert a reference to the page to which this page is supposed to be a shortcut. Requesting this ID in the frontend will redirect people to the page referred to by this value.</source>
322 <target>Insert a reference to the page to which this page is supposed to be a shortcut. Requesting this ID in the frontend will redirect people to the page referred to by this value.</target>
323 </trans-unit>
324 <trans-unit id="shortcut.details" approved="yes">
325 <source>Click the 'Browse for records' icon and a new window will appear in which you can easily select the page to which the shortcut is supposed to link.
326
327 This option is used only if the page 'Type' is set to 'Shortcut'.</source>
328 <target>Click the 'Browse for records' icon and a new window will appear in which you can easily select the page to which the shortcut is supposed to link.
329
330 This option is used only if the page 'Type' is set to 'Shortcut'.</target>
331 </trans-unit>
332 <trans-unit id="_shortcut.seeAlso" approved="yes">
333 <source>pages:doktype,
334 pages:shortcut_mode</source>
335 <target>pages:doktype,
336 pages:shortcut_mode</target>
337 </trans-unit>
338 <trans-unit id="_shortcut.image" approved="yes">
339 <source>EXT:context_help/cshimages/page_shortcut.gif</source>
340 <target>EXT:context_help/cshimages/page_shortcut.gif</target>
341 </trans-unit>
342 <trans-unit id="shortcut.image_descr" approved="yes">
343 <source>Select a page to shortcut to by the Element Browser.</source>
344 <target>Select a page to shortcut to by the Element Browser.</target>
345 </trans-unit>
346 <trans-unit id="keywords.description" approved="yes">
347 <source>Enter keywords for the page separated by commas. You may also use short phrases.</source>
348 <target>Enter keywords for the page separated by commas. You may also use short phrases.</target>
349 </trans-unit>
350 <trans-unit id="keywords.details" approved="yes">
351 <source>Most TYPO3 websites use these keywords in a meta-tag on the page, but you have to setup the appropriate TypoScript template yourself.
352
353 To optimize your page for search engines like google you should not use more than 3 to 6 keywords. You should make sure that the keywords can be found in the content of the page.
354
355 Note that also search engine extensions for TYPO3 (e.g. Indexed search) can be configured to make use of the keywords.
356
357 In TYPO3, the keywords can also be used to create a menu of related pages. Create a content element of type 'Sitemap' and then choose the menu type &lt;i&gt;Related pages (based on keywords)&lt;/i&gt;.</source>
358 <target>Most TYPO3 websites use these keywords in a meta-tag on the page, but you have to setup the appropriate TypoScript template yourself.
359
360 To optimize your page for search engines like google you should not use more than 3 to 6 keywords. You should make sure that the keywords can be found in the content of the page.
361
362 Note that also search engine extensions for TYPO3 (e.g. Indexed search) can be configured to make use of the keywords.
363
364 In TYPO3, the keywords can also be used to create a menu of related pages. Create a content element of type 'Sitemap' and then choose the menu type &lt;i&gt;Related pages (based on keywords)&lt;/i&gt;.</target>
365 </trans-unit>
366 <trans-unit id="_keywords.seeAlso" approved="yes">
367 <source>pages:description</source>
368 <target>pages:description</target>
369 </trans-unit>
370 <trans-unit id="description.description" approved="yes">
371 <source>Enter a short description of the page. It will be displayed in the result lists of search engines.</source>
372 <target>Enter a short description of the page. It will be displayed in the result lists of search engines.</target>
373 </trans-unit>
374 <trans-unit id="description.details" approved="yes">
375 <source>Most TYPO3 websites insert this description in a meta-tag on the page, but you have to configure this yourself in your TypoScript template.
376
377 Search engines will display the description in their result list. Thus, the text should be short (about 160 characters maximum), and it's wording should make sense when it shows up in the result list.
378
379 Also, the description will be displayed if you create a content element of type 'Sitemap' and then choose the menu type &lt;i&gt;Menu of subpages to these pages (with abstract)&lt;/i&gt;.
380
381 &lt;b&gt;Note:&lt;/b&gt; Some search engines only use the description if the text is not found elsewhere in the content. So do not just repeat yourself.
382 </source>
383 <target>Most TYPO3 websites insert this description in a meta-tag on the page, but you have to configure this yourself in your TypoScript template.
384
385 Search engines will display the description in their result list. Thus, the text should be short (about 160 characters maximum), and it's wording should make sense when it shows up in the result list.
386
387 Also, the description will be displayed if you create a content element of type 'Sitemap' and then choose the menu type &lt;i&gt;Menu of subpages to these pages (with abstract)&lt;/i&gt;.
388
389 &lt;b&gt;Note:&lt;/b&gt; Some search engines only use the description if the text is not found elsewhere in the content. So do not just repeat yourself.
390 </target>
391 </trans-unit>
392 <trans-unit id="_description.seeAlso" approved="yes">
393 <source>pages:keywords
394 pages:abstract</source>
395 <target>pages:keywords
396 pages:abstract</target>
397 </trans-unit>
398 <trans-unit id="abstract.description" approved="yes">
399 <source>Enter an abstract of the contents. It may be displayed in an overview of articles.</source>
400 <target>Enter an abstract of the contents. It may be displayed in an overview of articles.</target>
401 </trans-unit>
402 <trans-unit id="abstract.details" approved="yes">
403 <source>An abstract is a short description of the page content, that might be a little longer than the one in the &lt;i&gt;Description&lt;/i&gt; field.
404
405 Other than the description, the abstract is not meant for display in search engine result lists, but for use in your own project exclusively.
406
407 By default, TYPO3 lets you create a content element of type &lt;i&gt;Sitemap&lt;/i&gt; and then choose &lt;i&gt;Menu of subpages to these pages (with abstract)&lt;/i&gt; to create an overview of articles. If an abstract is available it will be used instead of the description.
408
409 &lt;b&gt;Note:&lt;/b&gt; You do not have to enter the text of the description into the &lt;i&gt;Abstract field&lt;/i&gt; again.
410
411 Of course, admins can make custom use of this field via their TypoScript templates.</source>
412 <target>An abstract is a short description of the page content, that might be a little longer than the one in the &lt;i&gt;Description&lt;/i&gt; field.
413
414 Other than the description, the abstract is not meant for display in search engine result lists, but for use in your own project exclusively.
415
416 By default, TYPO3 lets you create a content element of type &lt;i&gt;Sitemap&lt;/i&gt; and then choose &lt;i&gt;Menu of subpages to these pages (with abstract)&lt;/i&gt; to create an overview of articles. If an abstract is available it will be used instead of the description.
417
418 &lt;b&gt;Note:&lt;/b&gt; You do not have to enter the text of the description into the &lt;i&gt;Abstract field&lt;/i&gt; again.
419
420 Of course, admins can make custom use of this field via their TypoScript templates.</target>
421 </trans-unit>
422 <trans-unit id="_abstract.seeAlso" approved="yes">
423 <source>pages:description</source>
424 <target>pages:description</target>
425 </trans-unit>
426 <trans-unit id="backend_layout.description" approved="yes">
427 <source>Select a backend layout for this particular page only.</source>
428 <target>Select a backend layout for this particular page only.</target>
429 </trans-unit>
430 <trans-unit id="backend_layout.details" approved="yes">
431 <source>If you have created any additional backend layouts you can select them here to have the page module render the columns of this page with the selected layout.
432
433 Usually it will reflect the frontend layout in a way so that you will be able to recognize easily to which area of the page the content belongs.
434
435 You can select nothing or "none" to get the default column view of the page module for this page.
436
437 If you select a layout or "none", it will override any settings that might have been inherited from pages in the rootline of the current page.
438
439 The selection is &lt;b&gt;NOT&lt;/b&gt; inherited automatically by subpages - use &lt;b&gt;Backend Layout (subpages of this page)&lt;/b&gt; if you want to achieve this.
440 </source>
441 <target>If you have created any additional backend layouts you can select them here to have the page module render the columns of this page with the selected layout.
442
443 Usually it will reflect the frontend layout in a way so that you will be able to recognize easily to which area of the page the content belongs.
444
445 You can select nothing or "none" to get the default column view of the page module for this page.
446
447 If you select a layout or "none", it will override any settings that might have been inherited from pages in the rootline of the current page.
448
449 The selection is &lt;b&gt;NOT&lt;/b&gt; inherited automatically by subpages - use &lt;b&gt;Backend Layout (subpages of this page)&lt;/b&gt; if you want to achieve this.
450 </target>
451 </trans-unit>
452 <trans-unit id="_backend_layout.seeAlso" approved="yes">
453 <source>pages:backend_layout_next_level</source>
454 <target>pages:backend_layout_next_level</target>
455 </trans-unit>
456 <trans-unit id="backend_layout_next_level.description" approved="yes">
457 <source>Select a backend layout for all subpages of this page.</source>
458 <target>Select a backend layout for all subpages of this page.</target>
459 </trans-unit>
460 <trans-unit id="backend_layout_next_level.details" approved="yes">
461 <source>If you have created any additional backend layouts you can select them here to have the page module render the columns of the subpages of this page with the selected layout.
462
463 Usually it will reflect the frontend layout in a way so that you will be able to recognize easily to which area of the page the content belongs.
464
465 You can select nothing or "none" to get the default column view of the page module for the subpages.
466
467 If you select a layout or "none", it will override any settings that might have been inherited from pages in the rootline of the current page.
468
469 The selection is inherited automatically by all subpages - so you don't have to set it seperately for each of them.</source>
470 <target>If you have created any additional backend layouts you can select them here to have the page module render the columns of the subpages of this page with the selected layout.
471
472 Usually it will reflect the frontend layout in a way so that you will be able to recognize easily to which area of the page the content belongs.
473
474 You can select nothing or "none" to get the default column view of the page module for the subpages.
475
476 If you select a layout or "none", it will override any settings that might have been inherited from pages in the rootline of the current page.
477
478 The selection is inherited automatically by all subpages - so you don't have to set it seperately for each of them.</target>
479 </trans-unit>
480 <trans-unit id="_backend_layout_next_level.seeAlso" approved="yes">
481 <source>pages:backend_layout</source>
482 <target>pages:backend_layout</target>
483 </trans-unit>
484 <trans-unit id="newUntil.description" approved="yes">
485 <source>Enter the 'expiry date' of the page.</source>
486 <target>Enter the 'expiry date' of the page.</target>
487 </trans-unit>
488 <trans-unit id="newUntil.details" approved="yes">
489 <source>The 'expiry date' of the page has no effect on the display of the webpage. This value is rather for internal use meant as a reminder of the date when the content of this page should be revised. So if the content of the page will be outdated at a certain point in time, you could set this value to that approximate date.
490 In order to obtain an overview of the expiry dates of pages, use the 'Pagetree overview' in the 'Web&gt;Info' module.</source>
491 <target>The 'expiry date' of the page has no effect on the display of the webpage. This value is rather for internal use meant as a reminder of the date when the content of this page should be revised. So if the content of the page will be outdated at a certain point in time, you could set this value to that approximate date.
492 In order to obtain an overview of the expiry dates of pages, use the 'Pagetree overview' in the 'Web&gt;Info' module.</target>
493 </trans-unit>
494 <trans-unit id="newUntil.syntax" approved="yes">
495 <source>See Page / Start (click below)</source>
496 <target>See Page / Start (click below)</target>
497 </trans-unit>
498 <trans-unit id="_newUntil.seeAlso" approved="yes">
499 <source>pages:starttime</source>
500 <target>pages:starttime</target>
501 </trans-unit>
502 <trans-unit id="lastUpdated.description" approved="yes">
503 <source>Enter the time and date of the most recent update of this page.</source>
504 <target>Enter the time and date of the most recent update of this page.</target>
505 </trans-unit>
506 <trans-unit id="lastUpdated.details" approved="yes">
507 <source>How the value of this field is used is determined by the TypoScript template of the website. First of all a 'Last updated' notice needs to be inserted on the pages and secondly the template must be configured to use this value.
508 The most common use which is found in the standard templates will automatically display the last update time and date &lt;em&gt;unless&lt;/em&gt; this field specifies a value in which case this value is inserted.</source>
509 <target>How the value of this field is used is determined by the TypoScript template of the website. First of all a 'Last updated' notice needs to be inserted on the pages and secondly the template must be configured to use this value.
510 The most common use which is found in the standard templates will automatically display the last update time and date &lt;em&gt;unless&lt;/em&gt; this field specifies a value in which case this value is inserted.</target>
511 </trans-unit>
512 <trans-unit id="lastUpdated.syntax" approved="yes">
513 <source>Format is HH:MM DD-MM-YYYY.
514 If you insert eg. a 'd' the current time and date is inserted. You can also append any value in the field with eg. '+10' which will add 10 days to the current value.</source>
515 <target>Format is HH:MM DD-MM-YYYY.
516 If you insert eg. a 'd' the current time and date is inserted. You can also append any value in the field with eg. '+10' which will add 10 days to the current value.</target>
517 </trans-unit>
518 <trans-unit id="nav_hide.description" approved="yes">
519 <source>With this option the page will be hidden in navigation menus in the frontend. The page can still be viewed if linked by its ID directly.</source>
520 <target>With this option the page will be hidden in navigation menus in the frontend. The page can still be viewed if linked by its ID directly.</target>
521 </trans-unit>
522 <trans-unit id="_nav_hide.seeAlso" approved="yes">
523 <source>pages:nav_title</source>
524 <target>pages:nav_title</target>
525 </trans-unit>
526 <trans-unit id="nav_title.description" approved="yes">
527 <source>Alternative title for menu items in the frontend. This value takes precedence over the page title if this value is filled in.</source>
528 <target>Alternative title for menu items in the frontend. This value takes precedence over the page title if this value is filled in.</target>
529 </trans-unit>
530 <trans-unit id="content_from_pid.description" approved="yes">
531 <source>If set, this is an alternative page id from where Content Elements will be selected instead of Content Elements from the current page.
532 Depends on template implementation whether this applies.</source>
533 <target>If set, this is an alternative page id from where Content Elements will be selected instead of Content Elements from the current page.
534 Depends on template implementation whether this applies.</target>
535 </trans-unit>
536 <trans-unit id="urltype.description" approved="yes">
537 <source>Set the URL prefix.</source>
538 <target>Set the URL prefix.</target>
539 </trans-unit>
540 <trans-unit id="shortcut_mode.description" approved="yes">
541 <source>Select a shortcut mode. By default the shortcut page type must have a page id to jump to. Alternative methods are to go to the first subpage of a page or to a random subpage.</source>
542 <target>Select a shortcut mode. By default the shortcut page type must have a page id to jump to. Alternative methods are to go to the first subpage of a page or to a random subpage.</target>
543 </trans-unit>
544 <trans-unit id="mount_pid.description" approved="yes">
545 <source>Mount this page id. If set it means that the subpages of this page comes from the mounted page instead.</source>
546 <target>Mount this page id. If set it means that the subpages of this page comes from the mounted page instead.</target>
547 </trans-unit>
548 <trans-unit id="mount_pid.details" approved="yes">
549 <source>In the frontend this is done by adding a new variable, &amp;MP, to the parameters which links the mounted branch to the main branch by pairing page ids.</source>
550 <target>In the frontend this is done by adding a new variable, &amp;MP, to the parameters which links the mounted branch to the main branch by pairing page ids.</target>
551 </trans-unit>
552 <trans-unit id="_mount_pid.seeAlso" approved="yes">
553 <source>pages:mount_pid_ol</source>
554 <target>pages:mount_pid_ol</target>
555 </trans-unit>
556 <trans-unit id="mount_pid_ol.description" approved="yes">
557 <source>If set, the mount point is "overlaid" by the mounted page. It will look like if the mount point does not exist and the mounted page is inserted in its position instead.</source>
558 <target>If set, the mount point is "overlaid" by the mounted page. It will look like if the mount point does not exist and the mounted page is inserted in its position instead.</target>
559 </trans-unit>
560 <trans-unit id="_mount_pid_ol.seeAlso" approved="yes">
561 <source>pages:mount_pid</source>
562 <target>pages:mount_pid</target>
563 </trans-unit>
564 <trans-unit id="title.description.+" approved="yes">
565 <source>This is normally shown in the website navigation.</source>
566 <target>This is normally shown in the website navigation.</target>
567 </trans-unit>
568 <trans-unit id="TSconfig.details.+" approved="yes">
569 <source>&lt;strong&gt;Example:&lt;/strong&gt;
570 Normally the 'Web&gt;Page' module lets you create content in four columns, Left, Normal, Right, Border. However most websites use only a single or two columns. So some of these content columns are just taking up space and may even be confusing to users.
571 If you enter this string in the 'TSconfig' field, the 'Web&gt;Page' module will allow you to work only in the 'Normal' and 'Border' column!
572
573 &lt;em&gt;mod.web_layout.tt_content.colPos_list = 0,3&lt;/em&gt;
574
575 (Must be entered in a single line!)</source>
576 <target>&lt;strong&gt;Example:&lt;/strong&gt;
577 Normally the 'Web&gt;Page' module lets you create content in four columns, Left, Normal, Right, Border. However most websites use only a single or two columns. So some of these content columns are just taking up space and may even be confusing to users.
578 If you enter this string in the 'TSconfig' field, the 'Web&gt;Page' module will allow you to work only in the 'Normal' and 'Border' column!
579
580 &lt;em&gt;mod.web_layout.tt_content.colPos_list = 0,3&lt;/em&gt;
581
582 (Must be entered in a single line!)</target>
583 </trans-unit>
584 <trans-unit id="l18n_cfg.description" approved="yes">
585 <source>Affect availability of pages in the various languages.</source>
586 <target>Affect availability of pages in the various languages.</target>
587 </trans-unit>
588 <trans-unit id="l18n_cfg.details" approved="yes">
589 <source>&lt;b&gt;Hide default translation of page&lt;/b&gt;
590 If set the page is only available in one of the translations. So any attempt to access the page in the default language will show an error message.
591
592 &lt;b&gt;Hide page if no translation for current language exists&lt;/b&gt;
593 If set the page access will be blocked with an error message if there is no translation in the current language. By default access to a non-translated page will just show the default language content.</source>
594 <target>&lt;b&gt;Hide default translation of page&lt;/b&gt;
595 If set the page is only available in one of the translations. So any attempt to access the page in the default language will show an error message.
596
597 &lt;b&gt;Hide page if no translation for current language exists&lt;/b&gt;
598 If set the page access will be blocked with an error message if there is no translation in the current language. By default access to a non-translated page will just show the default language content.</target>
599 </trans-unit>
600 </body>
601 </file>
602 </xliff>