[TASK] Add XLIFF Core files
[Packages/TYPO3.CMS.git] / typo3 / sysext / context_help / locallang_csh_fe_users.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="username.description">
7 <source>Enter the username of the website user. This is needed to login.</source>
8 <target approved="yes">Enter the username of the website user. This is needed to login.</target>
9 </trans-unit>
10 <trans-unit id="username.syntax">
11 <source>A username is required and must be in lowercase without spaces in it. The username must be unique among other usernames in the page where it's saved. If it is not unique a number will be prepended automatically.</source>
12 <target approved="yes">A username is required and must be in lowercase without spaces in it. The username must be unique among other usernames in the page where it's saved. If it is not unique a number will be prepended automatically.</target>
13 </trans-unit>
14 <trans-unit id="_username.seeAlso">
15 <source>Creating Frontend Users and Groups | http://typo3.org/documentation/document-library/doc_tut_quickstart/Create_users_group/</source>
16 <target approved="yes">Creating Frontend Users and Groups | http://typo3.org/documentation/document-library/doc_tut_quickstart/Create_users_group/</target>
17 </trans-unit>
18 <trans-unit id="password.description">
19 <source>Enter the password for the username above. This is needed to login.</source>
20 <target approved="yes">Enter the password for the username above. This is needed to login.</target>
21 </trans-unit>
22 <trans-unit id="password.syntax">
23 <source>A password is required and must be in lowercase without spaces in it.</source>
24 <target approved="yes">A password is required and must be in lowercase without spaces in it.</target>
25 </trans-unit>
26 <trans-unit id="usergroup.description">
27 <source>Select a user group for the username.</source>
28 <target approved="yes">Select a user group for the username.</target>
29 </trans-unit>
30 <trans-unit id="usergroup.details">
31 <source>When a user logs in he is able to view all content which is access restricted to the user &lt;em&gt;group(s)&lt;/em&gt; the user is a member of. Therefore the user login primarily makes sense with regard to the member groups.</source>
32 <target approved="yes">When a user logs in he is able to view all content which is access restricted to the user &lt;em&gt;group(s)&lt;/em&gt; the user is a member of. Therefore the user login primarily makes sense with regard to the member groups.</target>
33 </trans-unit>
34 <trans-unit id="lockToDomain.description">
35 <source>Enter the host name from which the user is forced to login.</source>
36 <target approved="yes">Enter the host name from which the user is forced to login.</target>
37 </trans-unit>
38 <trans-unit id="lockToDomain.details">
39 <source>A TYPO3 system may have multiple domains pointing to it. Therefore this option secures that users can login only from a certain host name.</source>
40 <target approved="yes">A TYPO3 system may have multiple domains pointing to it. Therefore this option secures that users can login only from a certain host name.</target>
41 </trans-unit>
42 <trans-unit id="lockToDomain.syntax">
43 <source>Either a domain name, "www.typo3.com" or an IP address, "10.34.222.83"</source>
44 <target approved="yes">Either a domain name, "www.typo3.com" or an IP address, "10.34.222.83"</target>
45 </trans-unit>
46 <trans-unit id="_lockToDomain.seeAlso">
47 <source>fe_groups:lockToDomain</source>
48 <target approved="yes">fe_groups:lockToDomain</target>
49 </trans-unit>
50 <trans-unit id="name.description">
51 <source>Enter the regular name of the user, both first- and surname.</source>
52 <target approved="yes">Enter the regular name of the user, both first- and surname.</target>
53 </trans-unit>
54 <trans-unit id="address.description">
55 <source>Enter the street address of the user.</source>
56 <target approved="yes">Enter the street address of the user.</target>
57 </trans-unit>
58 <trans-unit id="www.description">
59 <source>Enter the homepage URL</source>
60 <target approved="yes">Enter the homepage URL</target>
61 </trans-unit>
62 <trans-unit id="title.description">
63 <source>Enter the job title, eg. 'Director' or 'Accountant'.</source>
64 <target approved="yes">Enter the job title, eg. 'Director' or 'Accountant'.</target>
65 </trans-unit>
66 <trans-unit id="company.description">
67 <source>Enter the name of the company in which the user is employed.</source>
68 <target approved="yes">Enter the name of the company in which the user is employed.</target>
69 </trans-unit>
70 <trans-unit id="image.description">
71 <source>Insert a photo of the user.</source>
72 <target approved="yes">Insert a photo of the user.</target>
73 </trans-unit>
74 <trans-unit id="disable.description">
75 <source>This option will temporarily disable the user from logging in.</source>
76 <target approved="yes">This option will temporarily disable the user from logging in.</target>
77 </trans-unit>
78 <trans-unit id="_disable.seeAlso">
79 <source>fe_users:starttime,fe_users:endtime</source>
80 <target approved="yes">fe_users:starttime,fe_users:endtime</target>
81 </trans-unit>
82 <trans-unit id="starttime.description">
83 <source>Enter the date from which the account is active.</source>
84 <target approved="yes">Enter the date from which the account is active.</target>
85 </trans-unit>
86 <trans-unit id="starttime.syntax">
87 <source>The syntax is dd-mm-yy, but you can just enter a "d" in the field to insert todays date. Or "d+10" to insert the date 10 days from now etc.
88 The field will re-format any input to fit the format it understands so you can just experiment and you will be able to clearly see how dates should be entered.</source>
89 <target approved="yes">The syntax is dd-mm-yy, but you can just enter a "d" in the field to insert todays date. Or "d+10" to insert the date 10 days from now etc.
90 The field will re-format any input to fit the format it understands so you can just experiment and you will be able to clearly see how dates should be entered.</target>
91 </trans-unit>
92 <trans-unit id="_starttime.seeAlso">
93 <source>fe_users:disable,fe_users:endtime</source>
94 <target approved="yes">fe_users:disable,fe_users:endtime</target>
95 </trans-unit>
96 <trans-unit id="endtime.description">
97 <source>Enter the date from which the account is disabled.</source>
98 <target approved="yes">Enter the date from which the account is disabled.</target>
99 </trans-unit>
100 <trans-unit id="endtime.syntax">
101 <source>See "Start"</source>
102 <target approved="yes">See "Start"</target>
103 </trans-unit>
104 <trans-unit id="_endtime.seeAlso">
105 <source>fe_users:disable,fe_users:starttime</source>
106 <target approved="yes">fe_users:disable,fe_users:starttime</target>
107 </trans-unit>
108 <trans-unit id="lastlogin.description">
109 <source>This field shows the user's last log in date.</source>
110 <target approved="yes">This field shows the user's last log in date.</target>
111 </trans-unit>
112 <trans-unit id="TSconfig.description">
113 <source>Enter additional TSconfig for the user (advanced).</source>
114 <target approved="yes">Enter additional TSconfig for the user (advanced).</target>
115 </trans-unit>
116 <trans-unit id="TSconfig.details">
117 <source>This field allows you to enter TypoScript style configuration values for the user. Currently there are no system defined keys. If there ever will be, they will be described in detail in the administrative documentation.
118
119 The primary use of this field (as well as the 'sister'-field in the Website usergroup table) is for custom purposes. In this case, you should use the root-key "user" for your customly defined values. Thus you don't risk any future system keys to interfere with your configuration.
120
121 You access the values of the configuration from your frontend plugins by calling the function &lt;em&gt;$GLOBALS["TSFE"]-&gt;fe_user-&gt;getUserTSconf()&lt;/em&gt; which will return an array with the valuetree in it.
122
123 &lt;b&gt;Warning:&lt;/b&gt; You should use Website user/group TSconfig in your PHP-scripts ONLY if your resulting content is NOT being cached! So call it from TypoScript USER_INT cObjects or disable caching from your PHP-code by calling &lt;em&gt;$GLOBALS["TSFE"]-&gt;set_no_cache();&lt;/em&gt;
124
125 &lt;b&gt;TSconfig from Website usergroups:&lt;/b&gt;
126 Notice that the configuration from the field TSconfig in the member groups of the user is accumulated and prepended to the TSconfig of the user before it's parsed. This means for instance that a key defined in the TSconfig of the user (this field) will override the same key defined in the last (bottom) usergroup in the list which will again override the same key defined in the first (top) usergroup in the list.
127
128 &lt;b&gt;Example:&lt;/b&gt;
129 Let's imagine you want to define for a user that his name is printed in the bottom of the webpages when he is logged in. First of all you must write a PHP-function and insert the result from it as a USER_INT cObject in the bottom of the page. But your function needs to know, whether or not this user is configured to have his name printed. So you decide to use a custom TSconfig key, 'user.printUserName':
130
131 &lt;em&gt;In the TSconfig field of the user or usergroup:&lt;/em&gt;
132
133 user.printUserName = 1
134
135
136 &lt;em&gt;In your PHP-function:&lt;/em&gt;
137
138 $userTSConfig = $GLOBALS["TSFE"]-&gt;fe_user-&gt;getUserTSconf();
139 if ($userTSConfig["user."]["printUserName"]) {
140 return $GLOBALS["TSFE"]-&gt;fe_user-&gt;user["name"];
141 }</source>
142 <target approved="yes">This field allows you to enter TypoScript style configuration values for the user. Currently there are no system defined keys. If there ever will be, they will be described in detail in the administrative documentation.
143
144 The primary use of this field (as well as the 'sister'-field in the Website usergroup table) is for custom purposes. In this case, you should use the root-key "user" for your customly defined values. Thus you don't risk any future system keys to interfere with your configuration.
145
146 You access the values of the configuration from your frontend plugins by calling the function &lt;em&gt;$GLOBALS["TSFE"]-&gt;fe_user-&gt;getUserTSconf()&lt;/em&gt; which will return an array with the valuetree in it.
147
148 &lt;b&gt;Warning:&lt;/b&gt; You should use Website user/group TSconfig in your PHP-scripts ONLY if your resulting content is NOT being cached! So call it from TypoScript USER_INT cObjects or disable caching from your PHP-code by calling &lt;em&gt;$GLOBALS["TSFE"]-&gt;set_no_cache();&lt;/em&gt;
149
150 &lt;b&gt;TSconfig from Website usergroups:&lt;/b&gt;
151 Notice that the configuration from the field TSconfig in the member groups of the user is accumulated and prepended to the TSconfig of the user before it's parsed. This means for instance that a key defined in the TSconfig of the user (this field) will override the same key defined in the last (bottom) usergroup in the list which will again override the same key defined in the first (top) usergroup in the list.
152
153 &lt;b&gt;Example:&lt;/b&gt;
154 Let's imagine you want to define for a user that his name is printed in the bottom of the webpages when he is logged in. First of all you must write a PHP-function and insert the result from it as a USER_INT cObject in the bottom of the page. But your function needs to know, whether or not this user is configured to have his name printed. So you decide to use a custom TSconfig key, 'user.printUserName':
155
156 &lt;em&gt;In the TSconfig field of the user or usergroup:&lt;/em&gt;
157
158 user.printUserName = 1
159
160
161 &lt;em&gt;In your PHP-function:&lt;/em&gt;
162
163 $userTSConfig = $GLOBALS["TSFE"]-&gt;fe_user-&gt;getUserTSconf();
164 if ($userTSConfig["user."]["printUserName"]) {
165 return $GLOBALS["TSFE"]-&gt;fe_user-&gt;user["name"];
166 }</target>
167 </trans-unit>
168 <trans-unit id="TSconfig.syntax">
169 <source>TypoScript syntax, without conditions and constants.</source>
170 <target approved="yes">TypoScript syntax, without conditions and constants.</target>
171 </trans-unit>
172 <trans-unit id="_TSconfig.seeAlso">
173 <source>TSconfig for TSFE | http://typo3.org/documentation/document-library/doc_core_tsconfig/TCEMAIN/
174 pages:TSconfig,
175 fe_groups:TSconfig,
176 be_users:TSconfig,
177 be_groups:TSconfig</source>
178 <target approved="yes">TSconfig for TSFE | http://typo3.org/documentation/document-library/doc_core_tsconfig/TCEMAIN/
179 pages:TSconfig,
180 fe_groups:TSconfig,
181 be_users:TSconfig,
182 be_groups:TSconfig</target>
183 </trans-unit>
184 <trans-unit id=".description">
185 <source>A website login user.</source>
186 <target approved="yes">A website login user.</target>
187 </trans-unit>
188 <trans-unit id=".details">
189 <source>These are users with a username and password who are allowed specific access to otherwise restricted areas on your website.</source>
190 <target approved="yes">These are users with a username and password who are allowed specific access to otherwise restricted areas on your website.</target>
191 </trans-unit>
192 <trans-unit id="_.seeAlso">
193 <source>fe_groups
194 be_users</source>
195 <target approved="yes">fe_groups
196 be_users</target>
197 </trans-unit>
198 <trans-unit id="_.image">
199 <source>EXT:context_help/cshimages/feusers_1.png,
200 EXT:context_help/cshimages/feusers_2.png,</source>
201 <target approved="yes">EXT:context_help/cshimages/feusers_1.png,
202 EXT:context_help/cshimages/feusers_2.png,</target>
203 </trans-unit>
204 <trans-unit id=".image_descr">
205 <source>Part of the form for editing a frontend user.
206 A typical login box (standard) on the website where frontend users can login.</source>
207 <target approved="yes">Part of the form for editing a frontend user.
208 A typical login box (standard) on the website where frontend users can login.</target>
209 </trans-unit>
210 </body>
211 </file>
212 </xliff>