From d9b07c4ec5c84128390679e75e5d5f5af41e6352 Mon Sep 17 00:00:00 2001
From: Georg Ringer <georg.ringer@gmail.com>
Date: Fri, 7 Aug 2015 21:18:01 +0200
Subject: [PATCH] [TASK] Remove usage of EXT:lang/4.5
Migrate the translations to the files where those belong
Change-Id: I999fa1ad32afbbb6e33a5b0cc48a3ac9a8515eeb
Resolves: #68855
Releases: master
Reviewed-on: http://review.typo3.org/42393
Reviewed-by: Morton Jonuschat <m.jonuschat@mojocode.de>
Tested-by: Morton Jonuschat <m.jonuschat@mojocode.de>
Reviewed-by: Andreas Fernandez <typo3@scripting-base.de>
Tested-by: Andreas Fernandez <typo3@scripting-base.de>
---
typo3/sysext/core/ext_tables.php | 5 -
.../sysext/lang/4.5/locallang_csh_corebe.xlf | 11 --
typo3/sysext/lang/4.5/locallang_csh_pages.xlf | 148 ------------------
typo3/sysext/lang/locallang_csh_corebe.xlf | 2 +-
typo3/sysext/lang/locallang_csh_pages.xlf | 84 +++++-----
5 files changed, 42 insertions(+), 208 deletions(-)
delete mode 100644 typo3/sysext/lang/4.5/locallang_csh_corebe.xlf
delete mode 100644 typo3/sysext/lang/4.5/locallang_csh_pages.xlf
diff --git a/typo3/sysext/core/ext_tables.php b/typo3/sysext/core/ext_tables.php
index 772b44bcfcb9..52ad1f774c41 100644
--- a/typo3/sysext/core/ext_tables.php
+++ b/typo3/sysext/core/ext_tables.php
@@ -140,11 +140,6 @@ $GLOBALS['TBE_STYLES'] = array(
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addLLrefForTCAdescr('_MOD_web_info', 'EXT:lang/locallang_csh_web_info.xlf');
// Web > Func
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addLLrefForTCAdescr('_MOD_web_func', 'EXT:lang/locallang_csh_web_func.xlf');
-// Labels for TYPO3 4.5 and greater.
-// These labels override the ones set above, while still falling back to the original labels
-// if no translation is available.
-$GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride']['EXT:lang/locallang_csh_pages.xlf'][] = 'EXT:lang/4.5/locallang_csh_pages.xlf';
-$GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride']['EXT:lang/locallang_csh_corebe.xlf'][] = 'EXT:lang/4.5/locallang_csh_corebe.xlf';
/**
* Backend sprite icon-names
diff --git a/typo3/sysext/lang/4.5/locallang_csh_corebe.xlf b/typo3/sysext/lang/4.5/locallang_csh_corebe.xlf
deleted file mode 100644
index 52e3b46d1db9..000000000000
--- a/typo3/sysext/lang/4.5/locallang_csh_corebe.xlf
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xliff version="1.0" xmlns:t3="http://typo3.org/schemas/xliff">
- <file t3:id="1415814844" source-language="en" datatype="plaintext" original="messages" date="2011-10-17T20:22:33Z" product-name="lang">
- <header/>
- <body>
- <trans-unit id="new_regular.image_descr">
- <source>The selection of records a user can create on this particular page. The selection depends on the user's permissions and the page type. For example a Folder page type can contain any kind of record while regular pages can contain only some types (like Content Elements).</source>
- </trans-unit>
- </body>
- </file>
-</xliff>
diff --git a/typo3/sysext/lang/4.5/locallang_csh_pages.xlf b/typo3/sysext/lang/4.5/locallang_csh_pages.xlf
deleted file mode 100644
index 28d7c025cfe8..000000000000
--- a/typo3/sysext/lang/4.5/locallang_csh_pages.xlf
+++ /dev/null
@@ -1,148 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xliff version="1.0" xmlns:t3="http://typo3.org/schemas/xliff">
- <file t3:id="1415814845" source-language="en" datatype="plaintext" original="messages" date="2011-10-17T20:22:33Z" product-name="lang">
- <header/>
- <body>
- <trans-unit id=".description">
- <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>
- </trans-unit>
- <trans-unit id=".details" xml:space="preserve">
- <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.
-
-<b>The Pagetree</b>
-The pages are organized in a tree structure that reflects the organization of your website.
-
-<b>UID, PID and the Pagetree Root</b>
-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.
-
-<b>Storage of Database Records</b>
-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>
- </trans-unit>
- <trans-unit id="_.seeAlso" xml:space="preserve">
- <source>xMOD_csh_corebe:pagetree,
-tt_content,
-About pages | https://docs.typo3.org/typo3cms/GettingStartedTutorial/GeneralPrinciples/PageTree/</source>
- <note from="developer">A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note>
- </trans-unit>
- <trans-unit id="_.image" xml:space="preserve">
- <source>EXT:lang/cshimages/pages_1.png,
-EXT:lang/cshimages/pages_2.png,</source>
- <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
- </trans-unit>
- <trans-unit id=".image_descr" xml:space="preserve">
- <source>The most basic fields on a page are the Disable Page option, the Type of page ("doktype") and the Page Title.
-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>
- </trans-unit>
- <trans-unit id="title.description">
- <source>Enter the title of the page or folder. This field is required.</source>
- </trans-unit>
- <trans-unit id="title.details" xml:space="preserve">
- <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.
-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.
-You can use any characters in the Page Title.</source>
- </trans-unit>
- <trans-unit id="_title.image">
- <source>EXT:lang/cshimages/pages_3.png</source>
- <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
- </trans-unit>
- <trans-unit id="title.image_descr">
- <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>
- </trans-unit>
- <trans-unit id="doktype.description">
- <source>Page Type determines whether the page is normal webpage, a shortcut to another webpage, or used in other internal ways.</source>
- </trans-unit>
- <trans-unit id="doktype.details" xml:space="preserve">
- <source>'Standard' is the most common Page Type and is used for normal webpages.
-'Folder' is a page type which is not shown as a webpage; instead, it stores records of your choice.
-'Recycler' is a garbage can. Pages and records in a recycler are not visible in the frontend.
-
-<b>Notice</b> 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.'
-
-<b>$PAGES_TYPES [Technical]</b>
-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>
- </trans-unit>
- <trans-unit id="_doktype.seeAlso" xml:space="preserve">
- <source>be_groups:pagetypes_select,
-About $PAGES_TYPES | https://docs.typo3.org/typo3cms/CoreApiReference/PageTypes/</source>
- <note from="developer">A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note>
- </trans-unit>
- <trans-unit id="_doktype.image">
- <source>EXT:lang/cshimages/pages_4.png</source>
- <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
- </trans-unit>
- <trans-unit id="doktype.image_descr">
- <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>
- </trans-unit>
- <trans-unit id="TSconfig.description">
- <source>Page TSConfig.</source>
- </trans-unit>
- <trans-unit id="TSconfig.details" xml:space="preserve">
- <source>'TypoScript' is a concept for entering values in a hierarchical structure that is used to create templates for TYPO3 websites.
-The same principles of storing a hierarchy of values is also used to configure various Backend functionality such as Modules and the RTE.
-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>Info' Module (requires the "info_pagetsconfig" extension to be installed).</source>
- </trans-unit>
- <trans-unit id="TSconfig.syntax" xml:space="preserve">
- <source>Basic TypoScript Syntax <em>without</em> 'Constants.'
-
-It is recommended that only admin users have access to this field!</source>
- </trans-unit>
- <trans-unit id="_TSconfig.seeAlso" xml:space="preserve">
- <source>_MOD_web_info:tsconfig_hierarchy,
-More about Page TSconfig | https://docs.typo3.org/typo3cms/TSconfigReference/PageTsconfig/</source>
- <note from="developer">A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note>
- </trans-unit>
- <trans-unit id="_TSconfig.image">
- <source>EXT:lang/cshimages/pages_5.png</source>
- <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
- </trans-unit>
- <trans-unit id="TSconfig.image_descr">
- <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>
- </trans-unit>
- <trans-unit id="php_tree_stop.description">
- <source>Stops backend rendering of the page tree in navigation and lists.</source>
- </trans-unit>
- <trans-unit id="php_tree_stop.details" xml:space="preserve">
- <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.
-
-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>
- </trans-unit>
- <trans-unit id="_php_tree_stop.seeAlso">
- <source>_MOD_web_info:pagetree_overview</source>
- <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
- </trans-unit>
- <trans-unit id="_php_tree_stop.image" xml:space="preserve">
- <source>EXT:lang/cshimages/pages_8.png,
-EXT:lang/cshimages/pages_6.png,
-EXT:lang/cshimages/pages_7.png</source>
- <note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
- </trans-unit>
- <trans-unit id="php_tree_stop.image_descr" xml:space="preserve">
- <source>Here the "Stop page tree" option is enabled.
-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.
-If you click the red "+" the page will be mounted temporarily in the navigation frame.</source>
- </trans-unit>
- <trans-unit id="storage_pid.description">
- <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>
- </trans-unit>
- <trans-unit id="storage_pid.details" xml:space="preserve">
- <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 configured to look elsewhere.
-
-A General Record Storage Page is typically a page of the "Folder" type.</source>
- </trans-unit>
- <trans-unit id="_storage_pid.seeAlso">
- <source>The Storage Folder | https://docs.typo3.org/typo3cms/GettingStartedTutorial/GeneralPrinciples/SpecialPages/Index.html#folders</source>
- </trans-unit>
- <trans-unit id="editlock.description">
- <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>
- </trans-unit>
- <trans-unit id="fe_login_mode.description">
- <source>The Login Behavior allows the logins and other related featured to be disabled for this page.</source>
- </trans-unit>
- <trans-unit id="fe_login_mode.details" xml:space="preserve">
- <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.
-
-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>
- </trans-unit>
- </body>
- </file>
-</xliff>
diff --git a/typo3/sysext/lang/locallang_csh_corebe.xlf b/typo3/sysext/lang/locallang_csh_corebe.xlf
index d2c2e1cd6c4f..bc39e1f79c9b 100644
--- a/typo3/sysext/lang/locallang_csh_corebe.xlf
+++ b/typo3/sysext/lang/locallang_csh_corebe.xlf
@@ -317,7 +317,7 @@ xMOD_csh_corebe:new_pages</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="new_regular.image_descr">
- <source>The selection of records a user can create on this particular page. The selection depends on the users permissions and the page type. For example a SysFolder page type can contain any kind of record while regular pages can contain only some types (like content elements).</source>
+ <source>The selection of records a user can create on this particular page. The selection depends on the user's permissions and the page type. For example a Folder page type can contain any kind of record while regular pages can contain only some types (like Content Elements).</source>
</trans-unit>
<trans-unit id="new_pages.alttitle">
<source>Create new page wizard</source>
diff --git a/typo3/sysext/lang/locallang_csh_pages.xlf b/typo3/sysext/lang/locallang_csh_pages.xlf
index c0344274e657..3f00b550d41d 100644
--- a/typo3/sysext/lang/locallang_csh_pages.xlf
+++ b/typo3/sysext/lang/locallang_csh_pages.xlf
@@ -4,19 +4,19 @@
<header/>
<body>
<trans-unit id=".description">
- <source>A 'Page' record usually represents a webpage in TYPO3. All pages have an id-number by which they can be linked and referenced. The 'Page' record does not itself contain the content of the page - for this purpose you should create 'Page content' records (Content Elements).</source>
+ <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>
</trans-unit>
<trans-unit id=".details" xml:space="preserve">
- <source>The pages table is the very backbone in TYPO3. All records editable by the mainstream modules in TYPO3 must 'belong' to a page. It's exactly like files and folders on your computers harddrive.
+ <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.
-<b>The page tree</b>
-The pages are organized in a tree structure which is not only a very handy way of organizing in general but also a optimal reflection of how you should organize the pages on your website. And thus you'll normally find that the page tree is a reflection of the website navigation itself.
+<b>The Page Tree</b>
+The pages are organized in a tree structure that reflects the organization of your website.
-<p>uid, pid and the pagetree root</b>
-Technically all database elements has a field 'uid' which is a unique identification number. Further they must have a field 'pid' which holds the uid-number of the page (page id) to which they belong. If the 'pid' field is zero the record is found in the so called 'root'. Only administrators are allowed access to the root and furthermore table records must be configured to either belonging to a page or being found in the root.
+<b>UID, PID and the page tree root</b>
+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.
-<b>Storage of database records</b>
-Depending on the 'Type' of the page, it may also represent a general storage for database elements in TYPO3. In that case it is not necessarily available as a webpage but only internally in the page tree as a place to store items such as users, subscriptions etc. Such pages are typically of the type "SysFolder".</source>
+<b>Storage of Database Records</b>
+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 page tree as a place to store items such as users, subscriptions, etc. Such pages are typically of the type "Folder".</source>
</trans-unit>
<trans-unit id="_.seeAlso" xml:space="preserve">
<source>xMOD_csh_corebe:pagetree,
@@ -30,36 +30,36 @@ EXT:lang/cshimages/pages_2.png,</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id=".image_descr" xml:space="preserve">
- <source>The most basic fields of a page is the hidden flag, the type of page ("doktype") and the page title. Other fields are also available but typically added by extensions in TYPO3.
-Pages are arranged in a page tree in TYPO3. The page from the editing form in the previous screenshot was the "Intro" page from this page tree. As you can see it belongs in the root of the page tree and has a number of "child" pages under it.</source>
+ <source>The most basic fields on a page are the 'Disable Page' option, the 'Type' of page ("doktype") and the 'Page Title'.
+Pages are arranged in a page tree in TYPO3. The page from the editing form in the previous screenshot was the "Intro" page from this page tree. As you can see it belongs in the root of the page tree and has a number of subpages pages under it.</source>
</trans-unit>
<trans-unit id="title.description">
- <source>Enter the title of the page or folder. You must enter a page title. The field is required.</source>
+ <source>Enter the title of the page or folder. This field is required.</source>
</trans-unit>
<trans-unit id="title.details" xml:space="preserve">
- <source>The page title is used to represent the page visually in the system, for example in the page tree. Also the page title is used by default for navigation links on webpages.
-You can always change a page title without affecting links to a page. This is because pages are always referenced by their "uid" number, not their title.
-You can use any characters in the page title.</source>
+ <source>The 'Page Title' is used to represent the page visually in the system, for example in the page tree. Also the 'Page Title' is used by default for navigation links on webpages.
+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.
+You can use any characters in the 'Page Title'.</source>
</trans-unit>
<trans-unit id="_title.image">
<source>EXT:lang/cshimages/pages_3.png</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="title.image_descr">
- <source>The field for the page title has a little "required" icon next to it; You must supply a page title and you cannot save the new page unless you enter a title for it.</source>
+ <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>
</trans-unit>
<trans-unit id="doktype.description">
- <source>Select the page type. This affects whether the page represents a visible webpage or is used for other purposes.</source>
+ <source>The page type determines whether the page is normal webpage, a shortcut to another webpage, or used in other internal ways.</source>
</trans-unit>
<trans-unit id="doktype.details" xml:space="preserve">
- <source>The 'Standard' type represents a webpage.
-'SysFolder' represents a non-webpage - a folder acting as a storage for records of your choice.
-'Recycler' is a garbage bin.
+ <source>'Standard' is the most common page type and is used for normal webpages.
+'Folder' is a page type which is not shown as a webpage; instead, it stores records of your choice.
+'Recycler' is a garbage can. Pages and records in a recycler are not visible in the frontend.
-<b>Notice:</b> 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).
+<b>Notice</b> 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.'
<b>$PAGES_TYPES [Technical]</b>
-The restrictions that apply to each page type is defined in the global array $PAGES_TYPES. Here it is defined which tables are allowed on a page. When extensions adds tables to TYPO3 they may need to register their tables in $PAGES_TYPES so they can be created on standard pages.</source>
+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>
</trans-unit>
<trans-unit id="_doktype.seeAlso" xml:space="preserve">
<source>be_groups:pagetypes_select,
@@ -71,20 +71,20 @@ About $PAGES_TYPES | https://docs.typo3.org/typo3cms/CoreApiReference/PageTypes/
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="doktype.image_descr">
- <source>This snippet of the page tree shows regular pages which usually have the yellow icons in top of this screenshot. You also see a Garbage bin page. Any records stored in a garbage bin should be regarded as waste and therefore not shown on the website etc. Finally the gray folders are "SysFolders". They cannot be viewed as regular webpages but serve as storage pages for database records of some kind.</source>
+ <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>
</trans-unit>
<trans-unit id="TSconfig.description">
- <source>Page TypoScript configuration.</source>
+ <source>Page TSconfig.</source>
</trans-unit>
<trans-unit id="TSconfig.details" xml:space="preserve">
- <source>Basically 'TypoScript' is a concept for entering values in a tree-structure. This is known especially in relation to creating templates for TYPO3 websites.
-However the same principle for entering the hierarchy of values is used here to configure various features in relation to the backend, functions in modules, the Rich Text Editor etc.
-The resulting 'TSconfig' for a page is actually an accumulation of all 'TSconfig' values from the root of the page tree and outwards to the current page. And thus all subpages are affected as well. A print of the page TSconfig is available from the 'Page TSconfig' menu in the 'Web>Info' module (requires the extension "info_pagetsconfig" to be installed).</source>
+ <source>'TypoScript' is a concept for entering values in a hierarchical structure that is used to create templates for TYPO3 websites.
+The same principles of storing a hierarchy of values is also used to configure various Backend functionality such as Modules and the RTE.
+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>Info' Module (requires the "info_pagetsconfig" extension to be installed).</source>
</trans-unit>
<trans-unit id="TSconfig.syntax" xml:space="preserve">
- <source>Basic TypoScript syntax <em>without</em> 'Conditions' and 'Constants'.
+ <source>Basic TypoScript Syntax <em>without</em> 'Constants.'
-It's recommended that only admin-users are allowed access to this field!</source>
+It is recommended that only admin users have access to this field!</source>
</trans-unit>
<trans-unit id="_TSconfig.seeAlso" xml:space="preserve">
<source>_MOD_web_info:tsconfig_hierarchy,
@@ -96,17 +96,15 @@ More about Page TSconfig | https://docs.typo3.org/typo3cms/TSconfigReference/Pag
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="TSconfig.image_descr">
- <source>Page TSconfig customizing the Rich Text Editors behaviour in this branch of the page tree. The cool thing about Page TSconfig is that the configuration is specific for that page and subpages since the configuration settings are inherited down the page tree.</source>
+ <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>
</trans-unit>
<trans-unit id="php_tree_stop.description">
<source>Stops backend rendering of the page tree in navigation and lists.</source>
</trans-unit>
<trans-unit id="php_tree_stop.details" xml:space="preserve">
- <source>If you set this flag the page tree in the navigation frame will not expand that branch. Rather you will see a red "+" which indicates that the tree stopped here due to this flag being set.
+ <source>If you enable this option, the page tree will not expand that branch. Instead you will see a red "+" which indicates that the page tree stops here because the Stop Page Tree option is enabled.
-The point with this flag is to prevent descendence into a branch that might have an unusual amount of subpages (hundreds).
-
-You can click the red "+" and the page will become a temporary mount point in the navigation frame.</source>
+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>
</trans-unit>
<trans-unit id="_php_tree_stop.seeAlso">
<source>_MOD_web_info:pagetree_overview</source>
@@ -119,31 +117,31 @@ EXT:lang/cshimages/pages_7.png</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="php_tree_stop.image_descr" xml:space="preserve">
- <source>Here the "Stop page tree" flag is set. It is a palette field under "TSconfig".
-In the pagetree the setting is reflected with the red "+" and it is not possible to expand that branch of the tree.
-If you click the red "+" you will get the page mounted temporarily in the navigation frame.</source>
+ <source>Here the "Stop page tree" option is enabled.
+In the page tree, this setting is reflected with the red "+" and the Expand/Collapse page tree icon will be disabled for that branch of the tree.
+If you click the red "+" the page will be mounted temporarily in the navigation frame.</source>
</trans-unit>
<trans-unit id="storage_pid.description">
- <source>A General Storage Folder is meant to be a global page for storage of general database elements of a website. That could be for templates, frontend users etc. which does not really relate to a single page but more to the whole site.</source>
+ <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>
</trans-unit>
<trans-unit id="storage_pid.details" xml:space="preserve">
- <source>It is recommended that applications support "General Storage pages" so that they look for records in the sites general storage folder by default and that they should be specifically configured to look elsewhere.
+ <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 configured to look elsewhere.
-A General Record Storage Page is typically a page of the "SysFolder" type.</source>
+A General Record Storage Page is typically a page of the "Folder" type.</source>
</trans-unit>
<trans-unit id="_storage_pid.seeAlso">
<source>The Storage Folder | https://docs.typo3.org/typo3cms/GettingStartedTutorial/GeneralPrinciples/SpecialPages/Index.html#folders</source>
</trans-unit>
<trans-unit id="editlock.description">
- <source>If set, non-Admin users cannot edit the page properties or any records on the page (except subpages). They cannot create new records or pages on the page either.</source>
+ <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>
</trans-unit>
<trans-unit id="fe_login_mode.description">
- <source>The Login Mode disables the ability to "be logged in" at this page.</source>
+ <source>The Login Behavior allows the logins and other related featured to be disabled for this page.</source>
</trans-unit>
<trans-unit id="fe_login_mode.details" xml:space="preserve">
- <source>Usually, if the user logs into TYPO3's Frontend the session gets carried around and for each page that user visits, it's calculated whether there is content that the user can see.
+ <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.
-By disabling the login, this check does not happen anymore. So the content is the same for all states whether logged in or not or for different FE user groups. This again results in being able to send cache headers.</source>
+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>
</trans-unit>
</body>
</file>
--
GitLab