Added $Id$ keywords, cleaned up comment tags
[Packages/TYPO3.CMS.git] / typo3 / sysext / lang / locallang_csh_em.php
1 <?php
2 /**
3 * Default TCA_DESCR for "_MOD_tools_em"
4 * TYPO3 CVS ID: $Id$
5 */
6
7 $LOCAL_LANG = Array (
8 'default' => Array (
9 'emconf_shy.alttitle' => 'Shy',
10 'emconf_shy.description' => 'If set, the extension will normally be hidden in the EM because it might be a default extension or otherwise something which is not so important.',
11 'emconf_shy.details' => 'Use this flag if an extension is of \93rare interest\94 (which is not the same as un-important - just an extension not sought for very often...)
12 It does not affect whether or not it\'s enabled. Only display in EM.
13 Normally \93shy\94 is set for all extensions loaded by default according to TYPO3_CONF_VARS.',
14 'emconf_category.alttitle' => 'Category',
15 'emconf_category.description' => 'Which category the extension belongs to.',
16 'emconf_category.details' => '<b>be:</b> Backend (Generally backend oriented, but not a module)
17
18 <b>module:</b> Backend modules (When something is a module or connects with one)
19
20 <b>fe:</b> Frontend (Generally frontend oriented, but not a \93true\94 plugin)
21
22 <b>plugin:</b> Frontend plugins (Plugins inserted as a \93Insert Plugin\94 content element)
23
24 <b>misc:</b> Miscellaneous stuff (Where not easily placed elsewhere)
25
26 <b>example:</b> Example extension (Which serves as examples etc.)',
27 'emconf_dependencies.alttitle' => 'Dependencies of other extensions?',
28 'emconf_dependencies.description' => 'This is a list of other extension keys which this extension depends on being loaded BEFORE it self.',
29 'emconf_dependencies.details' => 'The EM will manage that dependency while writing the extension list to localconf.php',
30 'emconf_conflicts.alttitle' => 'Conflicts with other extensions?',
31 'emconf_conflicts.description' => 'List of extension keys of extensions with which this extension does not work (and so cannot be enabled before those other extensions are un-installed)',
32 'emconf_priority.alttitle' => 'Requested Loading priority',
33 'emconf_priority.description' => 'This tells the EM to try to put the extensions as the very first in the list. Default is last.',
34 'emconf_module.alttitle' => 'Backend modules included',
35 'emconf_module.description' => 'If any subfolders to an extension contains backend modules, those foldernames should be listed here.',
36 'emconf_module.details' => 'It allows the EM to know about the existence of the module, which is important because the EM has to update the conf.php file of the module in order to set the correct TYPO3_MOD_PATH constant.',
37 'emconf_state.alttitle' => 'Development state',
38 'emconf_state.description' => 'Which development state the extension is in.',
39 'emconf_state.details' => '<b>alpha</b>
40 Very initial development. May do nothing at all.
41
42 <b>beta</b>
43 Under current development. Should work partly but is not finished yet.
44
45 <b>stable</b>
46 Stable and used in production.
47
48 <b>experimental</b>
49 Nobody knows if this is going anywhere yet... Maybe still just an idea.
50
51 <b>test</b>
52 Test extension, demonstrates concepts etc.',
53 'emconf_internal.alttitle' => 'Internally supported in core',
54 'emconf_internal.description' => 'This flag indicates that the core source code is specifically aware of the extension.',
55 'emconf_internal.details' => 'In order words this flag should convey the message that \93this extension could not be written without some core source code modifications\94.
56
57 An extension is not internal just because it uses TYPO3 general classes eg. those from t3lib/.
58 True non-internal extensions are characterized by the fact that they could be written without making core source code changes, but relies only on existing classes in TYPO3 and/or other extensions, plus its own scripts in the extension folder.',
59 'emconf_clearCacheOnLoad.alttitle' => 'Clear cache when installed',
60 'emconf_clearCacheOnLoad.description' => 'If set, the EM will request the cache to be cleared when this extension is installed.',
61 'emconf_modify_tables.alttitle' => 'Existing tables modified',
62 'emconf_modify_tables.description' => 'List of tablenames which are only modified - not fully created - by this extension.',
63 'emconf_modify_tables.details' => 'Tables from this list found in the ext_tables.sql file of the extension ',
64 '.alttitle' => 'EM',
65 '.description' => 'The Extension Manager (EM)',
66 '.details' => 'TYPO3 can be extended in nearly any direction without loosing backwards compatibility. The Extension API provides a powerful framework for easily adding, removing, installing and developing such extensions to TYPO3. This is in particular powered by the Extension Manager (EM) inside TYPO3.
67
68 \93Extensions\94 is a term in TYPO3 which covers two other terms, plugins and modules.
69
70 A plugin is something that plays a role on the website itself. Eg. a board, guestbook, shop etc. It is normally enclosed in a PHP class and invoked through a USER or USER_INT cObject from TypoScript. A plugin is an extension in the frontend.
71
72 A module is a backend application which has it\'s own position in the administration menu. It requires backend login and works inside the framework of the backend. We might also call something a module if it exploits any connectivity of an existing module, that is if it simply adds itself to the function menu of existing modules. A module is an extension in the backend.',
73 'emconf_private.alttitle' => 'Private',
74 'emconf_private.description' => 'If set, this version is not shown in the public list in the online repository.',
75 'emconf_private.details' => '"Private" uploads requires you to manually enter a special key (which will be shown to you after an upload has been completed) to be able to import and view details for the uploaded extension.
76 This is nice when you are working on something internally which you do not want others to look at.
77 You can set and clear the private flag every time you upload your extension.',
78 '_emconf_private.seeAlso' => '_MOD_tools_em:emconf_download_password',
79 'emconf_download_password.alttitle' => 'Download password',
80 'emconf_download_password.description' => 'Additional password required for download of private extensions.',
81 'emconf_download_password.details' => 'Anybody who knows the "special key" assigned to the private upload will be able to import it. Specifying an import password allows you to give away the download key for private uploads and also require a password given in addition. The password can be changed later on.',
82 '_emconf_download_password.seeAlso' => '_MOD_tools_em:emconf_private',
83 'emconf_type.alttitle' => 'Installation type',
84 'emconf_type.description' => 'The type of the installation',
85 'emconf_type.details' => 'The files for an extension are located in a folder named by the extension key. The location of this folder can be either inside typo3/sysext/, typo3/ext/ or typo3conf/ext/. The extension must be programmed so that it does automatically detect where it is located and can work from all three locations.
86
87 <b>Local location \93typo3conf/ext/\94:</b> This is where to put extensions which are local for a particular TYPO3 installation. The typo3conf/ dir is always local, containing local configuration (eg. localconf.php), local modules etc. If you put an extension here it will be available for this TYPO3 installation only. This is a \93per-database\94 way to install an extension.
88
89 <b>Global location \93typo3/ext/\94:</b> This is where to put extensions which are global for the TYPO3 source code on the web server. These extensions will be available for any TYPO3 installation sharing the source code.
90 When you upgrade your TYPO3 source code you probably want to copy the typo3/ext/ directory from the former source to the new source, overriding the default directory. In this way all global extension you use will be installed inside the new sourcecode. After that you can always enter TYPO3 and upgrade the versions if needed.
91 This is a \93per-server\94 way to install an extension.
92
93 <b>System location \93typo3/sysext/\94:</b> This is system default extensions which cannot and should not be updated by the EM.
94
95
96 <b>Loading precedence</b>
97 Local extensions take precedence which means that if an extension exists both in typo3conf/ext/ and typo3/ext/ the one in typo3conf/ext/ is loaded. Likewise global extension takes predence over system extensions. This means that extensions are loaded in the order of priority local-global-system.
98 In effect you can therefore have - say - a \93stable\94 version of an extension installed in the global dir (typo3/ext/) which is used by all your projects on a server sharing source code, but on a single experimental project you can import the same extension in a newer \93experimental\94 version and for that particular project the locally available extension will be used instead.
99 ',
100 'emconf_doubleInstall.alttitle' => 'Installed twice or more?',
101 'emconf_doubleInstall.description' => 'Tells you if the extensions is installed in more than one of the System, Global or Local locations.',
102 'emconf_doubleInstall.details' => 'Because an extension can reside at three locations, System, Global and Local, this indicates if the extension is found in other locations than the current. In that case you should be aware which one of the extensions is loaded!',
103 'emconf_rootfiles.alttitle' => 'Root files',
104 'emconf_rootfiles.description' => 'List of the files in the extension folder. Does not list files in subfolders.',
105 'emconf_dbReq.alttitle' => 'Database requirements',
106 'emconf_dbReq.description' => 'Shows you the requirements to the database tables and fields, if any.',
107 'emconf_dbReq.details' => 'This will read from the files ext_tables.sql and ext_tables_static+adt.sql and show you which tables, fields and static tables are required with this extension.',
108 'emconf_dbStatus.alttitle' => 'Database requirements status',
109 'emconf_dbStatus.description' => 'Displays the current status of the database compared to the extension requirements.',
110 'emconf_dbStatus.details' => 'If the extension is loaded which will display and error message if some tables or fields are not present in the database as they should be!',
111 'emconf_flags.alttitle' => 'Flags',
112 'emconf_flags.description' => 'A list of special codes which tells you something about what parts of TYPO3 the extension touches.',
113 'emconf_flags.details' => 'This is a list of the flags:
114
115 <b>Module:</b> A true backend main/sub module is found to be added.
116
117 <b>Module+:</b> The extension adds itself to the function menu of an existing backend module.
118
119 <b>loadTCA:</b> The extension includes a function call to t3lib_div::loadTCA for loading a table. This potentially means that the system is slowed down, because the full table description of some table is always included. However there probably is a good reason for this to happen. Probably the extension tries to manipulate the TCA-config for an existing table in order to extend it.
120
121 <b>TCA:</b> The extension contains configuration of a table in $TCA.
122
123 <b>Plugin:</b> The extension adds a frontend plugin to the plugin list in Content Element type "Insert Plugin".
124
125 <b>Plugin/ST43:</b> TypoScript rendering code for the plugin is added to the static template "Content (default)". "Plugin" and "Plugin/ST43" are commonly used together.
126
127 <b>Page-TSconfig:</b> Default Page-TSconfig is added.
128
129 <b>User-TSconfig:</b> Default User-TSconfig is added.
130
131 <b>TS/Setup:</b> Default TypoScript Setup is added.
132
133 <b>TS/Constants:</b> Default TypoScript Constants is added.
134 ',
135 'emconf_conf.description' => 'Shows if the extension has a template for further lowlevel configuration.',
136 'emconf_TSfiles.alttitle' => 'Static TypoScript files',
137 'emconf_TSfiles.description' => 'Shows which TypoScript static files may be present',
138 'emconf_TSfiles.details' => 'If the files ext_typoscript_constants.txt and/or ext_typoscript_setup.txt is found in the extension folder their are included in the hierarchy of all TypoScript templates in TYPO3 right after the inclusion of other static templates.',
139 'emconf_locallang.alttitle' => 'locallang-files',
140 'emconf_locallang.description' => 'Shows which files named "locallang.php" are present in the extension folder (recursive search). Such files are usually used to present an array $LOCAL_LANG with labels for the application in the system languages.',
141 'emconf_moduleNames.alttitle' => 'Backend Module names',
142 'emconf_moduleNames.description' => 'Shows which module names was found inside the extension.',
143 'emconf_classNames.alttitle' => 'PHP Class names',
144 'emconf_classNames.description' => 'Shows which PHP-classes were found in .php and .inc files.',
145 'emconf_errors.alttitle' => 'Errors',
146 'emconf_errors.description' => 'Displays if any serious errors with the extension was discovered.',
147 'emconf_NSerrors.alttitle' => 'Namespace errors',
148 'emconf_NSerrors.description' => 'Certain naming convensions apply to extensions. This displays any violations found.',
149 'emconf_NSerrors.details' => 'The naming convensions are defined in the "Inside TYPO3" document. To make naming as simple as possible, try to avoid underscores in your extension keys.',
150 ),
151 );
152 ?>