TYPO3 Core

This was already reported in #86914 but rejected.
I do not agree with that decision, maybe i can convince you to to change your mind.

In my setups, i strive for having configuration settings centralized. I extend the site configuration and site language depending on the project requirements.
Thus the page IDs for e.g. record storages and detail views go in there, so i can use them everywhere.

For "simple" setups, a lot of settings can go into settings block of a site config and are thus available as TypoScript constants. But when they need to be language specific, i can not access them this way and would like to use stdWrap data functions. Hence it would really help if settings accept stdWrap.

Example: while the website is build as single tree, some records are not translatable and created independently in different storage dirs. I would like to save this in the siteLanguage and access it via https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Functions/Data.html?highlight=sitelanguage#sitelanguage

https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Seo/XmlSitemap.html#xmlsitemapdataproviders

pid = TEXT
pid.data = siteLanguage:record_storage_pid