Project

General

Profile

Actions
Copy link

Bug #105270

closed

Problem on https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.3/Deprecation-99882-SiteLanguageTypo3LanguageSetting.html

Added by Markus A 20 days ago. Updated 20 days ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Documentation
Target version:
-
Start date:
2024-10-11
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
13
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Hi,

I believe there is a need to keep the typo3Language option.
Scenario:
Client A:
Languages: German (locale: de_DE) and English (locale: en_US)
Client B:
Languages: Dutch (locale: nl_NL) and Dutch English (locale: en_US)

Dutch English requires an English locale, and en_NL is not a default locale on Linux systems, so we chose en_US.

In this scenario, we need to configure typo3Language to load the correct en_nl.locallang.xlf. Otherwise, Dutch English will use the en.locallang.xlf file.

Regards

Related issues 1 (1 open — 0 closed)

Is duplicate of TYPO3 Core - Feature #103887: Site config / Site language based language file handling for FRONTEND required since deprecation of "typo3Language" - controlling it by locale only is not enough in every use caseNew2024-05-23

Actions
Actions
Copy link
 #1

Updated by Garvin Hicking 20 days ago

  • Is duplicate of Feature #103887: Site config / Site language based language file handling for FRONTEND required since deprecation of "typo3Language" - controlling it by locale only is not enough in every use case added
Actions
Copy link
 #2

Updated by Garvin Hicking 20 days ago

  • Status changed from New to Closed

Thanks for taking the time to submit this issue and argue with your usage scenario. Please see the issue https://forge.typo3.org/issues/103887 which is about the same topic, maybe you can add your thoughts there.

Closing the issue due to being a duplicate here.

Actions
Copy link

Also available in: Atom PDF