TYPO3 v15 dev-main snapshot ()
This commit is contained in:
@@ -0,0 +1,260 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
|
||||
<file source-language="en" datatype="plaintext" original="EXT:reports/Resources/Private/Language/locallang_reports.xlf" date="2011-10-17T20:22:35Z" product-name="reports">
|
||||
<header/>
|
||||
<body>
|
||||
<trans-unit id="status_ok">
|
||||
<source>OK</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_wrongValue">
|
||||
<source>Wrong value detected</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_info">
|
||||
<source>Information</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_insecure">
|
||||
<source>Insecure</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_disabled">
|
||||
<source>Disabled</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_enabled">
|
||||
<source>Enabled</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_enabledPermanently">
|
||||
<source>Enabled permanently</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_enabledTemporarily">
|
||||
<source>Enabled temporarily</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_empty">
|
||||
<source>Empty</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_none">
|
||||
<source>None</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_connectionFailed">
|
||||
<source>Connection Failed</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_checkFailed">
|
||||
<source>Check Failed</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_updateComplete">
|
||||
<source>Update Complete</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_updateIncomplete">
|
||||
<source>Update Incomplete</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_problemNotification">
|
||||
<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_allNotification">
|
||||
<source>This report contains all System Status Notifications from your TYPO3 installation. Please check the %sstatus report%s for more information.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_typo3">
|
||||
<source>TYPO3 System</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_system">
|
||||
<source>System</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_security">
|
||||
<source>Security</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_configuration">
|
||||
<source>Configuration</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_referenceIndex">
|
||||
<source>Reference Index</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_fal">
|
||||
<source>File Abstraction Layer</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_missingFiles">
|
||||
<source>Files flagged as missing</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_missingFilesCount">
|
||||
<source>%1$s files</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_missingFilesMessage">
|
||||
<source>These files are flagged as missing. Restore the files and run the indexer to reset the missing flag.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_memcachedConfiguration">
|
||||
<source>Memcached Configuration</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_CreatedFilePermissions">
|
||||
<source>Permissions of created files</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_CreatedFilePermissions.writable">
|
||||
<source>Files created by TYPO3 are configured to be world writable. 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']['SYS']['fileCreateMask']. This can be set in the install tool.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_CreatedDirectoryPermissions">
|
||||
<source>Permissions of created directories</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_CreatedDirectoryPermissions.writable">
|
||||
<source>Directories created by TYPO3 are configured to be world writable. 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']['SYS']['folderCreateMask']. This can be set in the install tool.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_MysqlDatabaseCharacterSet">
|
||||
<source>MySQL Database Character Set</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_MysqlDatabaseCharacterSet_CheckFailed">
|
||||
<source>Checking database character set failed, got key "%1$s" instead of "character_set_database"</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_MysqlDatabaseCharacterSet_Unsupported">
|
||||
<source>Your default database uses character set "%1$s", but only "utf8", "utf8mb3" or "utf8mb4" is supported with TYPO3.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_MysqlDatabaseCharacterSet_Ok">
|
||||
<source>Your default database uses utf-8. All good.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_MysqlDatabaseCharacterSet_Info">
|
||||
<source>Your default database uses a different charset, but all tables uses utf-8. All good. But consider fixing your database collation and check the table creation settings.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_MysqlDatabaseCharacterSet_MixedCollations">
|
||||
<source>Your default database is set to create tables with character set "%1$s", but contains tables or columns with different collations. Please fix these tables to avoid "illegal mix of collations" errors.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_encryptedConnectionStatus">
|
||||
<source>Encrypted backend connection (HTTPS)</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_encryptedConnectionStatus_insecure">
|
||||
<source>Your backend access is not secured using HTTPS but relies on HTTP which sends all your data (including login passwords) over an insecure connection. All modern web sites should rely on HTTPS and only sites secured differently, for instance some intranet installations may use HTTP only.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_lockSslStatus">
|
||||
<source>Backend only accessible through HTTPS</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_lockSslStatus_insecure">
|
||||
<source><![CDATA[It is highly recommended to activate the option (<code>$GLOBALS['TYPO3_CONF_VARS']['BE']['lockSSL']</code>).]]></source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_trustedHostsPattern">
|
||||
<source>Trusted Hosts Pattern</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_encryptionKey">
|
||||
<source>Encryption Key</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_fileDenyPattern">
|
||||
<source>File Deny Pattern</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_htaccessUploadProtection">
|
||||
<source>.htaccess Upload Protection</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_exceptionHandler">
|
||||
<source>Exception Handler / Error Reporting</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_exportedFiles">
|
||||
<source>XML/T3D export files</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_exceptionHandler_warningMessage">
|
||||
<source>Display Errors is set to 1 - errors will be displayed with the DebugExceptionHandler including stack traces.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_exceptionHandler_errorMessage">
|
||||
<source>Debug Exception Handler enabled in Production Context - will show full error messages including stack traces.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_exportedFiles_warningMessage">
|
||||
<source>The following exported files were found:</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_exportedFiles_warningRecommendation">
|
||||
<source>It is recommended to delete exported files to avoid possible disclosure of exported data to backend users with lower/different access rights than user(s) who originally created the export(s).</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_installTool">
|
||||
<source>Install Tool</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_phpModules">
|
||||
<source>PHP Modules</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_phpModulesMissing">
|
||||
<source>One or more modules are missing.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_phpModulesList">
|
||||
<source>The following PHP module(s) is/are missing: %s.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_phpModulesInfo">
|
||||
<source>You need to install and enable these modules to let TYPO3 function correctly.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_phpModulesGroup">
|
||||
<source>one of: %s</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_phpModulesPresent">
|
||||
<source>All required modules are installed.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_installEnabledTemporarily">
|
||||
<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_updateTaskTitle">
|
||||
<source>System Status Update</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_updateTaskDescription">
|
||||
<source>Runs a system status check and sends notifications if problems have been found.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_updateAdditionalInformation">
|
||||
<source>Send notification to: %s</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_updateTaskField_notificationEmails">
|
||||
<source>Notification Email Addresses (one per line)</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_updateTaskField_notificationEmails_invalid">
|
||||
<source>Empty or invalid notification email addresses.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_updateTaskField_notificationAll">
|
||||
<source>Always send notification mail (not only on errors or warnings)</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_updateTask_email_subject">
|
||||
<source>System Status Notification for site %s</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_updateTask_email_site">
|
||||
<source>Site</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_updateTask_email_issues">
|
||||
<source>Issues</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_xclassUsage">
|
||||
<source>XCLASS used</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_xclassUsageFound">
|
||||
<source>Your system registers XCLASS</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_xclassUsageFound_message">
|
||||
<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">
|
||||
<source>%2$s registers an XCLASS of %1$s</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing">
|
||||
<source>Image Processing</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing_webp">
|
||||
<source>WebP support and availability</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing_disabled">
|
||||
<source>Image processing via ImageMagick/GraphicsMagick is disabled</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing_webp_not_configured">
|
||||
<source>WebP image generation is not enabled in $TYPO3_CONF_VARS[GFX][imagefile_ext]. No WebP image files will be generated.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing_webp_available">
|
||||
<source>WebP image generation is not enabled in $TYPO3_CONF_VARS[GFX][imagefile_ext], but it is supported by ImageMagick/GraphicsMagick.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing_webp_not_available">
|
||||
<source>WebP image generation is enabled in $TYPO3_CONF_VARS[GFX][imagefile_ext], but it is NOT supported by ImageMagick/GraphicsMagick. Please update your system environment or disable webp support in TYPO3 Configuration.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing_webp_available_and_configured">
|
||||
<source>WebP image generation is enabled in $TYPO3_CONF_VARS[GFX][imagefile_ext] and supported by ImageMagick/GraphicsMagick — Everything is configured correctly.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing_avif">
|
||||
<source>AVIF support and availability</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing_avif_not_configured">
|
||||
<source>AVIF image generation is not enabled in $TYPO3_CONF_VARS[GFX][imagefile_ext]. No AVIF image files will be generated.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing_avif_available">
|
||||
<source>AVIF image generation is not enabled in $TYPO3_CONF_VARS[GFX][imagefile_ext], but it is supported by ImageMagick/GraphicsMagick.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing_avif_not_available">
|
||||
<source>AVIF image generation is enabled in $TYPO3_CONF_VARS[GFX][imagefile_ext], but it is NOT supported by ImageMagick/GraphicsMagick. Please update your system environment or disable AVIF support in TYPO3 Configuration.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_imageprocessing_avif_available_and_configured">
|
||||
<source>AVIF image generation is enabled in $TYPO3_CONF_VARS[GFX][imagefile_ext] and supported by ImageMagick/GraphicsMagick — Everything is configured correctly.</source>
|
||||
</trans-unit>
|
||||
<trans-unit id="status_problem_notification_cli_disclaimer">
|
||||
<source>This report was generated from the Command Line Interface (CLI) context. The PHP settings and modules might differ from the ones defined for the webserver process, for example when using a different php.ini file. In case of problems, always compare the report with the one generated via the backend report module.</source>
|
||||
</trans-unit>
|
||||
</body>
|
||||
</file>
|
||||
</xliff>
|
||||
Reference in New Issue
Block a user