lfeditor issueshttps://gitlab.sgalinski.de/typo3/lfeditor/-/issues2024-03-22T10:24:03Zhttps://gitlab.sgalinski.de/typo3/lfeditor/-/issues/75allow my_ext/ext_localconf.php for language override configuration2024-03-22T10:24:03ZDavid Menzelallow my_ext/ext_localconf.php for language override configurationRight now, the LFEditor can be configured to override the language files. The path can be set in the extension configuration but only relative to the root folder public/...
Would it be possible to allow to set those override declaration...Right now, the LFEditor can be configured to override the language files. The path can be set in the extension configuration but only relative to the root folder public/...
Would it be possible to allow to set those override declarations in an extension specific `ext_localconf.php` file?
documention: https://docs.typo3.org/m/typo3/reference-coreapi/11.5/en-us/ExtensionArchitecture/FileStructure/ExtLocalconf.html
`It should contain additional configuration of `$GLOBALS['TYPO3_CONF_VARS']`.`
Which is for example:
```
$GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride']['EXT:news/Resources/Private/Language/locallang.xlf'][0] = 'EXT:my_ext/Resources/Private/Language/override_ext_news_locallang.xlf';
```
Maybe if the editor prefixes the path with `EXT:` and sets a path like `EXT:my_ext/ext_localconf.php`?
Right now the file path for those overrides points to `public/typo3conf/LFEditor/Configuration.php` and LFEditor has to be installed. If you have LFEditor just as an dev requirement installed, that doesn't work because the production system doesn't know to look in this file for the additional configuration.
Is that possible?https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/72avoid creating of CDATA[] sections and use escaped content instead2024-03-05T15:27:30ZDavid Menzelavoid creating of CDATA[] sections and use escaped content insteadUsing CDATA sections for the content is not recommended according to the official documentation:
https://docs.oasis-open.org/xliff/v1.2/xliff-profile-html/xliff-profile-html-1.2-cd02.html#General_CDATA
The current version 2.1 also recom...Using CDATA sections for the content is not recommended according to the official documentation:
https://docs.oasis-open.org/xliff/v1.2/xliff-profile-html/xliff-profile-html-1.2-cd02.html#General_CDATA
The current version 2.1 also recommends to avoid it:
http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html#d0e8112
Special characters should be encoded as HTML entities like described here in the best practice examples:
https://www.w3.org/TR/xml-i18n-bp/#AuthCDATA
So, by default, I would suggest not to use the CDATA section and special characters should be escaped.
However, the user should have the option to use the CDATA section if needed. Maybe with a checkbox to activate/add the CDATA section to individual fields?https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/71option to allow translation services (e.g. Google Translate, Deepl, ...) for ...2024-03-05T12:59:11ZDavid Menzeloption to allow translation services (e.g. Google Translate, Deepl, ...) for key translationsIf you have a lot of translation keys it could take some time to translate every key manually.
It would save time, if an editor has the possibility to translate a key via the Deepl API, Google Translate API or other services, just by pr...If you have a lot of translation keys it could take some time to translate every key manually.
It would save time, if an editor has the possibility to translate a key via the Deepl API, Google Translate API or other services, just by pressing a button.
Maybe translate the complete language file in one go or each key individually one by one, depending if a localization exists or if just some keys needs to be translated. Then the editor only needs to proof read and maybe make minor adjustments.
I saw this feature in this extension: https://extensions.typo3.org/extension/datamints_locallang_builderhttps://gitlab.sgalinski.de/typo3/lfeditor/-/issues/70Allow non-admin users to edit certain extensions/files only2024-03-05T11:38:38ZDavid MenzelAllow non-admin users to edit certain extensions/files onlyHi,
it is possible to restrict the display of language files to selected extensions. However, this seems to apply to both admins and none-admins (editors).
Is it currently possible to separate the display of extensions in the language e...Hi,
it is possible to restrict the display of language files to selected extensions. However, this seems to apply to both admins and none-admins (editors).
Is it currently possible to separate the display of extensions in the language editor for admins and non-admin users?
If an extension has several language files, e.g
```
locallang_backend.xlf
locallang_frontend.xlf
locallang_tca.xlf
```
would it be possible that editors can only edit `locallang_frontend.xlf` and not the other two language files?
A similar option exists in the extension translate_locallang, where you can add specific extensions for none-admin users AND add specific files:
```
# cat=basic//7; type=string; label=Allowed extensions for non-admin users (wildcard patterns, comma separated, e.g. acme_*)
allowedExts = *
# cat=basic//8; type=string; label=Allowed filenames for non-admin users (comma separated, empty=all)
allowedFiles =
```
Unfortunately, this extension does not have the option of a tree view, which is very useful for keeping an overview in the LFEditor.
So, as summary:
Is it possible to restrict extensions and their files to none-admin users and if not possible, is such a feature possible to integrate?https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/36[TASK] Add support for 11.42022-07-18T16:05:49ZAttila Glück[TASK] Add support for 11.4https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/33ext_conf_template.txt -- pathAdditionalConfiguration = '' (important for TYPO...2024-01-03T18:39:42ZHenri Nathansonext_conf_template.txt -- pathAdditionalConfiguration = '' (important for TYPO3 12)I suggest this value to be deleted or at least be set to '' as default. If set, it triggers some weird checkings in ConfigurationService.php. For our case /typo3conf/ was not writetable and /LFEditor/ was set as symlink to get the overri...I suggest this value to be deleted or at least be set to '' as default. If set, it triggers some weird checkings in ConfigurationService.php. For our case /typo3conf/ was not writetable and /LFEditor/ was set as symlink to get the overriden data out of the way of automated deployment. Anyway, the checking for /typo3conf/ seems to be unnecessary and it is triggered by this constant value set.https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/22FEATURE: enable extension key whitelist2019-06-12T13:52:07ZfgFEATURE: enable extension key whitelistHi,
instead of only blacklisting extension keys and preg_match'ing them (/typo3conf/ext/lfeditor/Classes/Utility/Functions.php:100), it would be nice to have a whitelist as well.
Thx,
FrankHi,
instead of only blacklisting extension keys and preg_match'ing them (/typo3conf/ext/lfeditor/Classes/Utility/Functions.php:100), it would be nice to have a whitelist as well.
Thx,
Frankhttps://gitlab.sgalinski.de/typo3/lfeditor/-/issues/16Make save location for language files configurable (TYPO3 12)2024-01-03T18:39:04ZRyan KlarhölterMake save location for language files configurable (TYPO3 12)Similar to my previous issue (https://gitlab.sgalinski.de/typo3/lfeditor/issues/15): It would be useful to be able to change the location of the language files that are created when I use the override mode (default is “typo3conf/LFEditor...Similar to my previous issue (https://gitlab.sgalinski.de/typo3/lfeditor/issues/15): It would be useful to be able to change the location of the language files that are created when I use the override mode (default is “typo3conf/LFEditor/” – I would like to change it to a directory outside the DocumentRoot), because „typo3conf/“ will be overwritten automatically by my deployment setup.https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/15Make configuration file location configurable2018-12-06T15:57:48ZRyan KlarhölterMake configuration file location configurableWhen I use the override mode the locations of the new created files are saved in “AdditionalConfiguration.php”. That’s bad in my case, because this file is under version control and will be overwritten with each release. It would be usef...When I use the override mode the locations of the new created files are saved in “AdditionalConfiguration.php”. That’s bad in my case, because this file is under version control and will be overwritten with each release. It would be useful to be able to change that file (via a TypoScript constant, e. g. to “AdditionalConfiguration/LfeditorConfiguration.php”).https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/10Conversion tool from XML to XLIFF2022-08-09T13:32:57ZFabian GalinskiConversion tool from XML to XLIFFTicket on Forge: https://forge.typo3.org/issues/78277
Author: Anonym
Description:
Translations written to typo3conf/LFEditor are written to a single XML file, even where the base file in the extension is in XLIFF format.
If the (non-...Ticket on Forge: https://forge.typo3.org/issues/78277
Author: Anonym
Description:
Translations written to typo3conf/LFEditor are written to a single XML file, even where the base file in the extension is in XLIFF format.
If the (non-admin) client user edits translations - which happens in “override mode” - then there is no easy way that I can find to get those translations back into the extension.
A feature in the extension for this would be great: either a conversion tool, or a revision to the “extension mode” so that files in typo3conf/LFEditor can be fed back into the extension file structure.https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/7Needs a possibility to search for extension in the "Select language file" list2023-08-02T16:57:28ZFabian GalinskiNeeds a possibility to search for extension in the "Select language file" listTicket on Forge: https://forge.typo3.org/issues/66226Ticket on Forge: https://forge.typo3.org/issues/66226https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/6Move/Copy Constant Between Files2024-01-03T18:38:49ZFabian GalinskiMove/Copy Constant Between FilesTicket on Forge: https://forge.typo3.org/issues/66187
Implementation of a possibility to move/copy a constant from one file to an another.Ticket on Forge: https://forge.typo3.org/issues/66187
Implementation of a possibility to move/copy a constant from one file to an another.https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/5System wide search for language constants2023-08-02T16:57:34ZFabian GalinskiSystem wide search for language constantsTicket on Forge: https://forge.typo3.org/issues/65808
Author: Damjan Komlenac
Description:
Search for language keys and translations within all language files in TYPO3 system.Ticket on Forge: https://forge.typo3.org/issues/65808
Author: Damjan Komlenac
Description:
Search for language keys and translations within all language files in TYPO3 system.https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/4User limitation on extensions2024-01-03T18:38:46ZFabian GalinskiUser limitation on extensionsTicket on Forge: https://forge.typo3.org/issues/65807
Author: Damjan Komlenac
Description:
Chose extensions which can be edited by certain users.Ticket on Forge: https://forge.typo3.org/issues/65807
Author: Damjan Komlenac
Description:
Chose extensions which can be edited by certain users.https://gitlab.sgalinski.de/typo3/lfeditor/-/issues/3Extension/Language/Function Access Management2022-08-09T13:33:35ZFabian GalinskiExtension/Language/Function Access ManagementTicket on Forge: https://forge.typo3.org/issues/65103
Author: Stefan Galinski
Description:
Integration into the backend user/groupTicket on Forge: https://forge.typo3.org/issues/65103
Author: Stefan Galinski
Description:
Integration into the backend user/grouphttps://gitlab.sgalinski.de/typo3/lfeditor/-/issues/2Editor should track changes made to default language2024-01-03T18:38:43ZFabian GalinskiEditor should track changes made to default languageTicket on Forge: https://forge.typo3.org/issues/63563
Author: Markus Klein
Description:
Like llxmltranslate, lfeditor should track changes made to the default language.
So if one changes a label in the default language, translators ge...Ticket on Forge: https://forge.typo3.org/issues/63563
Author: Markus Klein
Description:
Like llxmltranslate, lfeditor should track changes made to the default language.
So if one changes a label in the default language, translators get a notification that they have to update the translation as well.