[BUGFIX] High CPU load in IE8/9 when using context menu in htmlArea RTE
[Packages/TYPO3.CMS.git] / typo3 / sysext / lang / 4.5 / 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:24 UTC" product-name="lang">
4 <header/>
5 <body>
6 <trans-unit id=".description" approved="yes">
7 <source>A 'Page' record usually represents a webpage in TYPO3. All pages have an ID number (UID) by which they can be linked and referenced. The 'Page' record itself does not contain the content of the page. 'Page Content' records (Content Elements) are used for this.</source>
8 <target>A 'Page' record usually represents a webpage in TYPO3. All pages have an ID number (UID) by which they can be linked and referenced. The 'Page' record itself does not contain the content of the page. 'Page Content' records (Content Elements) are used for this.</target>
9 </trans-unit>
10 <trans-unit id=".details" approved="yes">
11 <source>The pages' table is the backbone of TYPO3. All records editable by the main modules in TYPO3 must belong to a page. It's exactly like files and folders on your computer's hard drive.
12
13 &lt;b&gt;The Pagetree&lt;/b&gt;
14 The pages are organized in a tree structure that reflects the organization of your website.
15
16 &lt;p&gt;UID, PID and the Pagetree Root&lt;/b&gt;
17 All database elements have a field 'uid' which is a unique identification number. They also have a field 'pid' (page id) which holds the ID number of the page to which they belong. If the 'pid' field is zero, the record is found in the 'root.' Only administrators are allowed access to the root. Table records must be configured to either belong to a page or be found in the root.
18
19 &lt;b&gt;Storage of Database Records&lt;/b&gt;
20 Depending on the 'Type,' a page may also represent general storage for database elements in TYPO3. In this case, it is not available as a webpage but is used internally in the Pagetree as a place to store items such as users, subscriptions, etc. Such pages are typically of the type "Folder".</source>
21 <target>The pages' table is the backbone of TYPO3. All records editable by the main modules in TYPO3 must belong to a page. It's exactly like files and folders on your computer's hard drive.
22
23 &lt;b&gt;The Pagetree&lt;/b&gt;
24 The pages are organized in a tree structure that reflects the organization of your website.
25
26 &lt;p&gt;UID, PID and the Pagetree Root&lt;/b&gt;
27 All database elements have a field 'uid' which is a unique identification number. They also have a field 'pid' (page id) which holds the ID number of the page to which they belong. If the 'pid' field is zero, the record is found in the 'root.' Only administrators are allowed access to the root. Table records must be configured to either belong to a page or be found in the root.
28
29 &lt;b&gt;Storage of Database Records&lt;/b&gt;
30 Depending on the 'Type,' a page may also represent general storage for database elements in TYPO3. In this case, it is not available as a webpage but is used internally in the Pagetree as a place to store items such as users, subscriptions, etc. Such pages are typically of the type "Folder".</target>
31 </trans-unit>
32 <trans-unit id="_.seeAlso" approved="yes">
33 <source>xMOD_csh_corebe:pagetree,
34 tt_content,
35 About pages | http://typo3.org/documentation/document-library/doc_tut_quickstart/Pagetree/</source>
36 <target>xMOD_csh_corebe:pagetree,
37 tt_content,
38 About pages | http://typo3.org/documentation/document-library/doc_tut_quickstart/Pagetree/</target>
39 </trans-unit>
40 <trans-unit id="_.image" approved="yes">
41 <source>EXT:lang/cshimages/pages_1.png,
42 EXT:lang/cshimages/pages_2.png,</source>
43 <target>EXT:lang/cshimages/pages_1.png,
44 EXT:lang/cshimages/pages_2.png,</target>
45 </trans-unit>
46 <trans-unit id=".image_descr" approved="yes">
47 <source>The most basic fields on a page are the Disable Page option, the Type of page ("doktype") and the Page Title.
48 Pages are arranged in a Pagetree in TYPO3. The page from the editing form in the previous screenshot was the "Intro" page from this Pagetree. As you can see it belongs in the root of the Pagetree and has a number of subpages pages under it.</source>
49 <target>The most basic fields on a page are the Disable Page option, the Type of page ("doktype") and the Page Title.
50 Pages are arranged in a Pagetree in TYPO3. The page from the editing form in the previous screenshot was the "Intro" page from this Pagetree. As you can see it belongs in the root of the Pagetree and has a number of subpages pages under it.</target>
51 </trans-unit>
52 <trans-unit id="title.description" approved="yes">
53 <source>Enter the title of the page or folder. This field is required.</source>
54 <target>Enter the title of the page or folder. This field is required.</target>
55 </trans-unit>
56 <trans-unit id="title.details" approved="yes">
57 <source>The Page Title is used to represent the page visually in the system, for example in the Pagetree. Also the Page Title is used by default for navigation links on webpages.
58 You can always change the Page Title without affecting links to a page. This is because pages are always referenced by ID number, not their title.
59 You can use any characters in the Page Title.</source>
60 <target>The Page Title is used to represent the page visually in the system, for example in the Pagetree. Also the Page Title is used by default for navigation links on webpages.
61 You can always change the Page Title without affecting links to a page. This is because pages are always referenced by ID number, not their title.
62 You can use any characters in the Page Title.</target>
63 </trans-unit>
64 <trans-unit id="_title.image" approved="yes">
65 <source>EXT:lang/cshimages/pages_3.png</source>
66 <target>EXT:lang/cshimages/pages_3.png</target>
67 </trans-unit>
68 <trans-unit id="title.image_descr" approved="yes">
69 <source>The field for the Page Title has a small "Required" icon next to it; You must supply a Page Title. You cannot save the new page unless you enter a title for it.</source>
70 <target>The field for the Page Title has a small "Required" icon next to it; You must supply a Page Title. You cannot save the new page unless you enter a title for it.</target>
71 </trans-unit>
72 <trans-unit id="doktype.description" approved="yes">
73 <source>Page Type determines whether the page is normal webpage, a shortcut to another webpage, or used in other internal ways.</source>
74 <target>Page Type determines whether the page is normal webpage, a shortcut to another webpage, or used in other internal ways.</target>
75 </trans-unit>
76 <trans-unit id="doktype.details" approved="yes">
77 <source>'Standard' is the most common Page Type and is used for normal webpages.
78 'Folder' is a page type which is not shown as a webpage; instead, it stores records of your choice.
79 'Recycler' is a garbage can. Pages and records in a recycler are not visible in the frontend.
80
81 &lt;b&gt;Notice&lt;/b&gt; Each page type is represented by a unique icon. The available page types can be restricted for users so all of the options described above may not be visible. Finally, some records may only be allowed on certain page types, but any record can be placed in a 'Folder.'
82
83 &lt;b&gt;$PAGES_TYPES [Technical]&lt;/b&gt;
84 The restrictions that apply to each Page Type is defined in the global array $PAGES_TYPES. When extensions add tables to TYPO3 they may need to register their tables in $PAGES_TYPES so they can be created on standard pages.</source>
85 <target>'Standard' is the most common Page Type and is used for normal webpages.
86 'Folder' is a page type which is not shown as a webpage; instead, it stores records of your choice.
87 'Recycler' is a garbage can. Pages and records in a recycler are not visible in the frontend.
88
89 &lt;b&gt;Notice&lt;/b&gt; Each page type is represented by a unique icon. The available page types can be restricted for users so all of the options described above may not be visible. Finally, some records may only be allowed on certain page types, but any record can be placed in a 'Folder.'
90
91 &lt;b&gt;$PAGES_TYPES [Technical]&lt;/b&gt;
92 The restrictions that apply to each Page Type is defined in the global array $PAGES_TYPES. When extensions add tables to TYPO3 they may need to register their tables in $PAGES_TYPES so they can be created on standard pages.</target>
93 </trans-unit>
94 <trans-unit id="_doktype.seeAlso" approved="yes">
95 <source>be_groups:pagetypes_select,
96 About $PAGES_TYPES | http://typo3.org/documentation/document-library/doc_core_api/PAGES_TYPES/</source>
97 <target>be_groups:pagetypes_select,
98 About $PAGES_TYPES | http://typo3.org/documentation/document-library/doc_core_api/PAGES_TYPES/</target>
99 </trans-unit>
100 <trans-unit id="_doktype.image" approved="yes">
101 <source>EXT:lang/cshimages/pages_4.png</source>
102 <target>EXT:lang/cshimages/pages_4.png</target>
103 </trans-unit>
104 <trans-unit id="doktype.image_descr" approved="yes">
105 <source>This snippet of the page tree shows regular pages (white icons) at the top of this screenshot. You also see a Recycler page. Any records stored in a Reycler page are considered trash and not shown on the website. The gray folders icons represent "Folders". They cannot be viewed as regular webpages but serve as storage pages for other database records.</source>
106 <target>This snippet of the page tree shows regular pages (white icons) at the top of this screenshot. You also see a Recycler page. Any records stored in a Reycler page are considered trash and not shown on the website. The gray folders icons represent "Folders". They cannot be viewed as regular webpages but serve as storage pages for other database records.</target>
107 </trans-unit>
108 <trans-unit id="TSconfig.description" approved="yes">
109 <source>Page TSConfig.</source>
110 <target>Page TSConfig.</target>
111 </trans-unit>
112 <trans-unit id="TSconfig.details" approved="yes">
113 <source>'TypoScript' is a concept for entering values in a heirarchacal structure that is used to create templates for TYPO3 websites.
114 The same principles of storing a hierarchy of values is also used to configure various Backend functionality such as Modules and the RTE.
115 The 'TSConfig' for an individual page is actually an accumulation of all 'TSConfig' values beginning from the root page and trickling downward to the current page. This means the TSConfig on the current page will affect all of its subpages as well. All TSconfig in use on a page is available from the 'Page TSconfig' menu in the 'Web&gt;Info' Module (requires the "info_pagetsconfig" extension to be installed).</source>
116 <target>'TypoScript' is a concept for entering values in a heirarchacal structure that is used to create templates for TYPO3 websites.
117 The same principles of storing a hierarchy of values is also used to configure various Backend functionality such as Modules and the RTE.
118 The 'TSConfig' for an individual page is actually an accumulation of all 'TSConfig' values beginning from the root page and trickling downward to the current page. This means the TSConfig on the current page will affect all of its subpages as well. All TSconfig in use on a page is available from the 'Page TSconfig' menu in the 'Web&gt;Info' Module (requires the "info_pagetsconfig" extension to be installed).</target>
119 </trans-unit>
120 <trans-unit id="TSconfig.syntax" approved="yes">
121 <source>Basic TypoScript Syntax &lt;em&gt;without&lt;/em&gt; 'Constants.'
122
123 It is recommended that only admin users have access to this field!</source>
124 <target>Basic TypoScript Syntax &lt;em&gt;without&lt;/em&gt; 'Constants.'
125
126 It is recommended that only admin users have access to this field!</target>
127 </trans-unit>
128 <trans-unit id="_TSconfig.seeAlso" approved="yes">
129 <source>_MOD_web_info:tsconfig_hierarchy,
130 More about Page TSconfig | http://typo3.org/documentation/document-library/doc_core_tsconfig/Page_TSconfig/</source>
131 <target>_MOD_web_info:tsconfig_hierarchy,
132 More about Page TSconfig | http://typo3.org/documentation/document-library/doc_core_tsconfig/Page_TSconfig/</target>
133 </trans-unit>
134 <trans-unit id="_TSconfig.image" approved="yes">
135 <source>EXT:lang/cshimages/pages_5.png</source>
136 <target>EXT:lang/cshimages/pages_5.png</target>
137 </trans-unit>
138 <trans-unit id="TSconfig.image_descr" approved="yes">
139 <source>Page TSConfig customizing layout labels in the Page Module. Note that the Page TSconfig is specific to that page and will be inherited by its subpages.</source>
140 <target>Page TSConfig customizing layout labels in the Page Module. Note that the Page TSconfig is specific to that page and will be inherited by its subpages.</target>
141 </trans-unit>
142 <trans-unit id="php_tree_stop.description" approved="yes">
143 <source>Stops backend rendering of the page tree in navigation and lists.</source>
144 <target>Stops backend rendering of the page tree in navigation and lists.</target>
145 </trans-unit>
146 <trans-unit id="php_tree_stop.details" approved="yes">
147 <source>If you enable this option, the Pagetree will not expand that branch. Instead you will see a red "+" which indicates that the Pagetree stops here because the Stop Page Tree option is enabled.
148
149 This option was designed to prevent the display of a branch with an unmanageable number of subpages. By clicking on the red "+" the page will become a temporary mount point in the navigation frame, thus facilitating easier navigation and editing.</source>
150 <target>If you enable this option, the Pagetree will not expand that branch. Instead you will see a red "+" which indicates that the Pagetree stops here because the Stop Page Tree option is enabled.
151
152 This option was designed to prevent the display of a branch with an unmanageable number of subpages. By clicking on the red "+" the page will become a temporary mount point in the navigation frame, thus facilitating easier navigation and editing.</target>
153 </trans-unit>
154 <trans-unit id="_php_tree_stop.seeAlso" approved="yes">
155 <source>_MOD_web_info:pagetree_overview</source>
156 <target>_MOD_web_info:pagetree_overview</target>
157 </trans-unit>
158 <trans-unit id="_php_tree_stop.image" approved="yes">
159 <source>EXT:lang/cshimages/pages_8.png,
160 EXT:lang/cshimages/pages_6.png,
161 EXT:lang/cshimages/pages_7.png</source>
162 <target>EXT:lang/cshimages/pages_8.png,
163 EXT:lang/cshimages/pages_6.png,
164 EXT:lang/cshimages/pages_7.png</target>
165 </trans-unit>
166 <trans-unit id="php_tree_stop.image_descr" approved="yes">
167 <source>Here the "Stop page tree" option is enabled.
168 In the Pagetree, this setting is reflected with the red "+" and the Expand/Collapse Pagetree icon will be disabled for that branch of the tree.
169 If you click the red "+" the page will be mounted temporarily in the navigation frame.</source>
170 <target>Here the "Stop page tree" option is enabled.
171 In the Pagetree, this setting is reflected with the red "+" and the Expand/Collapse Pagetree icon will be disabled for that branch of the tree.
172 If you click the red "+" the page will be mounted temporarily in the navigation frame.</target>
173 </trans-unit>
174 <trans-unit id="storage_pid.description" approved="yes">
175 <source>A General Record Storage Page is a global page for storing of general database elements (records) of a website. This could be for templates, frontend users, and other records that are not limited to a single page but shared across the whole website.</source>
176 <target>A General Record Storage Page is a global page for storing of general database elements (records) of a website. This could be for templates, frontend users, and other records that are not limited to a single page but shared across the whole website.</target>
177 </trans-unit>
178 <trans-unit id="storage_pid.details" approved="yes">
179 <source>It is recommended that extensions support the "General Record Storage Pages" so that the extension accesses records in this location by default when not conifgured to look elsewhere.
180
181 A General Record Storage Page is typically a page of the "Folder" type.</source>
182 <target>It is recommended that extensions support the "General Record Storage Pages" so that the extension accesses records in this location by default when not conifgured to look elsewhere.
183
184 A General Record Storage Page is typically a page of the "Folder" type.</target>
185 </trans-unit>
186 <trans-unit id="_storage_pid.seeAlso" approved="yes">
187 <source>The Storage Folder | http://typo3.org/documentation/document-library/doc_tut_ftb1/The_Storage_Folder/</source>
188 <target>The Storage Folder | http://typo3.org/documentation/document-library/doc_tut_ftb1/The_Storage_Folder/</target>
189 </trans-unit>
190 <trans-unit id="editlock.description" approved="yes">
191 <source>If set, non-admin users cannot edit the page properties or any records on the page, but may still edit subpages. They cannot create new records or pages on the page either.</source>
192 <target>If set, non-admin users cannot edit the page properties or any records on the page, but may still edit subpages. They cannot create new records or pages on the page either.</target>
193 </trans-unit>
194 <trans-unit id="fe_login_mode.description" approved="yes">
195 <source>The Login Behavior allows the logins and other related featured to be disabled for this page.</source>
196 <target>The Login Behavior allows the logins and other related featured to be disabled for this page.</target>
197 </trans-unit>
198 <trans-unit id="fe_login_mode.details" approved="yes">
199 <source>When a user logs into TYPO3's frontend, each page and/or its Content Elements can be set to restrict access based on the user's login.
200
201 By disabling logins, restrictions are removed and the content is accessible whether or not a user is logged in and regardless of Frontend usergroup settings. When logins are disabled for a page, cache headers can be sent again.</source>
202 <target>When a user logs into TYPO3's frontend, each page and/or its Content Elements can be set to restrict access based on the user's login.
203
204 By disabling logins, restrictions are removed and the content is accessible whether or not a user is logged in and regardless of Frontend usergroup settings. When logins are disabled for a page, cache headers can be sent again.</target>
205 </trans-unit>
206 </body>
207 </file>
208 </xliff>