<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.0">
	<file source-language="en" datatype="plaintext" original="messages" date="2011-10-17T20:22:35Z" product-name="reports">
		<header/>
		<body>
			<trans-unit id="status_report_title" xml:space="preserve">
				<source>Status Report</source>
			</trans-unit>
			<trans-unit id="status_report_description" xml:space="preserve">
				<source>Get a status report about your site's operation and any detected problems.</source>
			</trans-unit>
			<trans-unit id="status_report_explanation" xml:space="preserve">
				<source>Here you can find a short overview of your site's parameters as well as any problems detected with your installation. It may be useful to copy and paste this information into support requests filed on TYPO3's support mailinglists and project issue trackers.</source>
			</trans-unit>
			<trans-unit id="status_ok" xml:space="preserve">
				<source>OK</source>
			</trans-unit>
			<trans-unit id="status_insecure" xml:space="preserve">
				<source>Insecure</source>
			</trans-unit>
			<trans-unit id="status_disabled" xml:space="preserve">
				<source>Disabled</source>
			</trans-unit>
			<trans-unit id="status_enabled" xml:space="preserve">
				<source>Enabled</source>
			</trans-unit>
			<trans-unit id="status_enabledPermanently" xml:space="preserve">
				<source>Enabled permanently</source>
			</trans-unit>
			<trans-unit id="status_enabledTemporarily" xml:space="preserve">
				<source>Enabled temporarily</source>
			</trans-unit>
			<trans-unit id="status_empty" xml:space="preserve">
				<source>Empty</source>
			</trans-unit>
			<trans-unit id="status_none" xml:space="preserve">
				<source>None</source>
			</trans-unit>
			<trans-unit id="status_connectionFailed" xml:space="preserve">
				<source>Connection Failed</source>
			</trans-unit>
			<trans-unit id="status_updateComplete" xml:space="preserve">
				<source>Update Complete</source>
			</trans-unit>
			<trans-unit id="status_updateIncomplete" xml:space="preserve">
				<source>Update Incomplete</source>
			</trans-unit>
			<trans-unit id="status_problemNotification" xml:space="preserve">
				<source>One or more problems were detected with your TYPO3 installation. Please check the %sstatus report%s for more information.</source>
			</trans-unit>
			<trans-unit id="status_typo3" xml:space="preserve">
				<source>TYPO3 System</source>
			</trans-unit>
			<trans-unit id="status_system" xml:space="preserve">
				<source>System</source>
			</trans-unit>
			<trans-unit id="status_security" xml:space="preserve">
				<source>Security</source>
			</trans-unit>
			<trans-unit id="status_configuration" xml:space="preserve">
				<source>Configuration</source>
			</trans-unit>
			<trans-unit id="status_referenceIndex" xml:space="preserve">
				<source>Reference Index</source>
			</trans-unit>
			<trans-unit id="status_memcachedConfiguration" xml:space="preserve">
				<source>Memcached Configuration</source>
			</trans-unit>
			<trans-unit id="status_PhpSafeMode" xml:space="preserve">
				<source>PHP safe_mode</source>
			</trans-unit>
			<trans-unit id="status_PhpMagicQuotesGpc" xml:space="preserve">
				<source>PHP magic_quotes_gpc</source>
			</trans-unit>
			<trans-unit id="status_CreatedFilePermissions" xml:space="preserve">
				<source>Permissions of created files</source>
			</trans-unit>
			<trans-unit id="status_CreatedFilePermissions.writable" xml:space="preserve">
				<source>Files created by TYPO3 are configured to be world writeable. Depending on your server configuration, this can be a security risk. It is usually better to configure the create mask to not allow writing to files by "others". A sane default is often '0660' for $GLOBALS['TYPO3_CONF_VARS']['BE']['fileCreateMask']. This can be set in the install tool.</source>
			</trans-unit>
			<trans-unit id="status_CreatedDirectoryPermissions" xml:space="preserve">
				<source>Permissions of created directories</source>
			</trans-unit>
			<trans-unit id="status_CreatedDirectoryPermissions.writable" xml:space="preserve">
				<source>Directories created by TYPO3 are configured to be world writeable. Depending on your server configuration, this can be a security risk. It is usually better to configure the create mask to not allow writing to directories by "others". A sane default is often '2770' for $GLOBALS['TYPO3_CONF_VARS']['BE']['folderCreateMask']. This can be set in the install tool.</source>
			</trans-unit>
			<trans-unit id="status_adminUserAccount" xml:space="preserve">
				<source>Admin User Account</source>
			</trans-unit>
			<trans-unit id="status_encryptionKey" xml:space="preserve">
				<source>Encryption Key</source>
			</trans-unit>
			<trans-unit id="status_saltedPasswords" xml:space="preserve">
				<source>Backend user password hashes</source>
			</trans-unit>
			<trans-unit id="status_saltedPasswords_infoText" xml:space="preserve">
				<source>During the configuration check of saltedpasswords the following issues have been found:</source>
			</trans-unit>
			<trans-unit id="status_saltedPasswords_notInstalled" xml:space="preserve">
				<source>The saltedpasswords extension is not installed. The passwords are only hashed with md5 which is considered to be insecure. Install and configure the saltedpasswords extension and run the scheduler task to convert all passwords to salted hashes.</source>
			</trans-unit>
			<trans-unit id="status_saltedPasswords_notAllPasswordsHashed" xml:space="preserve">
				<source>Some backend user passwords are found to be only md5 hashed. Run the scheduler task to convert all passwords to salted hashes.</source>
			</trans-unit>
			<trans-unit id="status_fileDenyPattern" xml:space="preserve">
				<source>File Deny Pattern</source>
			</trans-unit>
			<trans-unit id="status_htaccessUploadProtection" xml:space="preserve">
				<source>.htaccess Upload Protection</source>
			</trans-unit>
			<trans-unit id="status_installToolPassword" xml:space="preserve">
				<source>Install Tool Password</source>
			</trans-unit>
			<trans-unit id="status_installTool" xml:space="preserve">
				<source>Install Tool</source>
			</trans-unit>
			<trans-unit id="status_phpVersion" xml:space="preserve">
				<source>PHP Version</source>
			</trans-unit>
			<trans-unit id="status_phpTooOld" xml:space="preserve">
				<source>Your PHP installation is too old.</source>
			</trans-unit>
			<trans-unit id="status_phpMemory" xml:space="preserve">
				<source>PHP Memory Limit</source>
			</trans-unit>
			<trans-unit id="status_phpMemoryRecommendation" xml:space="preserve">
				<source>Depending on your configuration, TYPO3 can run with a %1$s PHP memory limit. However, a %2$s PHP memory limit or above is recommended, especially if your site uses additional extensions.</source>
			</trans-unit>
			<trans-unit id="status_phpMemoryRequirement" xml:space="preserve">
				<source>Depending on your configuration, TYPO3 can run with a %1$s PHP memory limit. However, a %2$s PHP memory limit or above is required especially if your site uses additional extensions.</source>
			</trans-unit>
			<trans-unit id="status_phpMemoryEditLimit" xml:space="preserve">
				<source>Increase the memory limit by editing the memory_limit parameter in the file %s and then restart your web server (or contact your system administrator or hosting provider for assistance).</source>
			</trans-unit>
			<trans-unit id="status_phpMemoryContactAdmin" xml:space="preserve">
				<source>Contact your system administrator or hosting provider for assistance with increasing your PHP memory limit.</source>
			</trans-unit>
			<trans-unit id="status_phpMemoryUnlimited" xml:space="preserve">
				<source>unlimited</source>
			</trans-unit>
			<trans-unit id="status_phpPeakMemory" xml:space="preserve">
				<source>PHP peak memory usage</source>
			</trans-unit>
			<trans-unit id="status_phpPeakMemoryTooHigh" xml:space="preserve">
				<source>During a request %2$s of the memory limit was used. On %4$s a request to %5$s used %1$s of %3$s.</source>
			</trans-unit>
			<trans-unit id="status_phpPeakMemoryClearFlag" xml:space="preserve">
				<source>Clear this flag</source>
			</trans-unit>
			<trans-unit id="status_phpRegisterGlobals" xml:space="preserve">
				<source>PHP Register Globals</source>
			</trans-unit>
			<trans-unit id="status_phpRegisterGlobalsEnabled" xml:space="preserve">
				<source>%s is enabled. TYPO3 requires this configuration directive to be disabled.</source>
			</trans-unit>
			<trans-unit id="status_phpRegisterGlobalsSecurity" xml:space="preserve">
				<source>Your site may not be secure when %s is enabled.</source>
			</trans-unit>
			<trans-unit id="status_phpRegisterGlobalsHowToChange" xml:space="preserve">
				<source>how to change configuration settings</source>
			</trans-unit>
			<trans-unit id="status_phpRegisterGlobalsPHPManual" xml:space="preserve">
				<source>The PHP manual has instructions for %s.</source>
			</trans-unit>
			<trans-unit id="status_webServer" xml:space="preserve">
				<source>Web Server</source>
			</trans-unit>
			<trans-unit id="status_webServer_infoText" xml:space="preserve">
				<source>For your Web Server some notifications have been found:</source>
			</trans-unit>
			<trans-unit id="status_webServer_threadStackSize" xml:space="preserve">
				<source><![CDATA[Fluid uses complex regular expressions which require a lot of stack space during the first processing.
On Windows the default stack size for Apache is a lot smaller than on unix.
You can increase the size to 8MB (default on unix) by adding to the httpd.conf:
<br />&lt;IfModule mpm_winnt_module&gt;
<br />ThreadStackSize 8388608
<br />&lt;/IfModule&gt;
<br />Restart Apache after this change.]]></source>
			</trans-unit>
			<trans-unit id="status_phpModules" xml:space="preserve">
				<source>PHP Modules</source>
			</trans-unit>
			<trans-unit id="status_phpModulesMissing" xml:space="preserve">
				<source>One or more modules are missing.</source>
			</trans-unit>
			<trans-unit id="status_phpModulesList" xml:space="preserve">
				<source>The following PHP module(s) is/are missing: %s.</source>
			</trans-unit>
			<trans-unit id="status_phpModulesInfo" xml:space="preserve">
				<source>You need to install and enable these modules to let TYPO3 function correctly.</source>
			</trans-unit>
			<trans-unit id="status_phpModulesGroup" xml:space="preserve">
				<source>one of: %s</source>
			</trans-unit>
			<trans-unit id="status_phpModulesPresent" xml:space="preserve">
				<source>All required modules are installed.</source>
			</trans-unit>
			<trans-unit id="status_installEnabledTemporarily" xml:space="preserve">
				<source>The Install Tool is temporarily enabled. Delete the file "%s" when you have finished setting up TYPO3. If not used the Install Tool will be disabled automatically in %s minutes.</source>
			</trans-unit>
			<trans-unit id="status_configuration_DeprecationLog" xml:space="preserve">
				<source>Deprecation Log</source>
			</trans-unit>
			<trans-unit id="status_configuration_DeprecationLogEnabled" xml:space="preserve">
				<source>The deprecation log tracks whether old APIs are being used in extensions. Depending on the extensions you use and whether they use deprecated APIs it can happen that the log takes up quite some space over time. The more space it takes up, the more it may affect your installation's performance. It is recommended to disable deprecation log in production environments.</source>
			</trans-unit>
			<trans-unit id="status_configuration_DeprecationLogFile" xml:space="preserve">
				<source>You can find the deprecation log file at %s.</source>
			</trans-unit>
			<trans-unit id="status_configuration_DeprecationLogSize" xml:space="preserve">
				<source>Your deprecation log file currently takes up %s.</source>
			</trans-unit>
			<trans-unit id="status_configuration_DeprecationLogDeleteLink" xml:space="preserve">
				<source>Delete deprecation log file.</source>
			</trans-unit>
			<trans-unit id="status_configuration_DeprecationLogDeletedSuccessful" xml:space="preserve">
				<source>The deprecation log file was successfully deleted.</source>
			</trans-unit>
			<trans-unit id="status_configuration_DeprecationLogDeletionFailed" xml:space="preserve">
				<source>The deprecation log file could not be deleted!</source>
			</trans-unit>
			<trans-unit id="status_configuration_PhpSafeModeEnabled" xml:space="preserve">
				<source>PHP INI setting safe_mode "On" is deprecated since PHP 5.3 and is not supported by TYPO3 anymore.</source>
			</trans-unit>
			<trans-unit id="status_configuration_PhpMagicQuotesGpcEnabled" xml:space="preserve">
				<source>PHP INI setting magic_quotes_gpc "On" is deprecated since PHP 5.3. You are advised to set it to "Off" until it gets completely removed.</source>
			</trans-unit>
			<trans-unit id="status_updateTaskTitle" xml:space="preserve">
				<source>System Status Update</source>
			</trans-unit>
			<trans-unit id="status_updateTaskDescription" xml:space="preserve">
				<source>Runs a system status check and sends notifications if problems have been found.</source>
			</trans-unit>
			<trans-unit id="status_updateTaskField_notificationEmail" xml:space="preserve">
				<source>Notification Email Address</source>
			</trans-unit>
			<trans-unit id="status_updateTaskField_notificationEmails" xml:space="preserve">
				<source>Notification Email Addresses (one per line)</source>
			</trans-unit>
			<trans-unit id="status_updateTaskField_notificationEmail_invalid" xml:space="preserve">
				<source>Empty or invalid notification email address.</source>
			</trans-unit>
			<trans-unit id="status_updateTaskField_notificationEmails_invalid" xml:space="preserve">
				<source>Empty or invalid notification email addresses.</source>
			</trans-unit>
			<trans-unit id="status_updateTask_email_subject" xml:space="preserve">
				<source>System Status Notification for site %s</source>
			</trans-unit>
			<trans-unit id="status_updateTask_email_site" xml:space="preserve">
				<source>Site</source>
			</trans-unit>
			<trans-unit id="status_updateTask_email_issues" xml:space="preserve">
				<source>Issues</source>
			</trans-unit>
			<trans-unit id="status_oldXclassUsage" xml:space="preserve">
				<source>Old XCLASS method used</source>
			</trans-unit>
			<trans-unit id="status_oldXclassUsageFound" xml:space="preserve">
				<source>Old XCLASS method is used in %d cases:</source>
			</trans-unit>
			<trans-unit id="status_oldXclassUsageFound_message" xml:space="preserve">
				<source>The old XCLASS registration does not work since TYPO3 CMS version 6.0. This is not necessarily a bad thing, the registration might be done by an extension author to keep compatibility with older TYPO3 CMS versions. Please check the affected extension for TYPO3 CMS 6.0 compatibility to verify whether this is a problem for you.</source>
			</trans-unit>
			<trans-unit id="status_xclassUsage" xml:space="preserve">
				<source>XCLASS used</source>
			</trans-unit>
			<trans-unit id="status_xclassUsageFound" xml:space="preserve">
				<source>Your system registers XCLASS</source>
			</trans-unit>
			<trans-unit id="status_xclassUsageFound_message" xml:space="preserve">
				<source>XCLASS can overwrite methods or classes of the core or other extensions. This is not necessarily a bad thing, but those XCLASS might break during extension or core upgrades. You should keep an eye on extension compatibility and make sure the intended functionality is still given after updates.</source>
			</trans-unit>
			<trans-unit id="status_xclassUsageFound_message_detail" xml:space="preserve">
				<source>%2s registers an XCLASS of %1s</source>
			</trans-unit>
		</body>
	</file>
</xliff>
