Project

General

Profile

Actions

Feature #17538

closed

Why not a native lang support ?

Added by Popy no-lastname-given over 17 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2007-08-16
Due date:
% Done:

0%

Estimated time:
PHP Version:
4.3
Tags:
Complexity:
Sprint Focus:
Needs Decision

Description

For now the only way to make multilang website is to
1) Creat languages records
2) Translate pages & content
3) Modify the TS Template to add a language switch for each lang

From my point of view, the third step should not be. We can use the L get parameter to load the language record wich has the same id, ald get from it others informations, like language key, instead of reading it in the template (of course template should handle default language, but the propreties will be overriden by language record values)

By the way, the L get var can become a "system" var, so should be added in "cHash excluded parameters" and the sys_langage_uid added in the hash array (@see TSFE->getHash) to have a nice language system, without cHashes and cache problems.

I attach an example extension, wich define a ux_tslib_fe to realize it.

(issue imported from #M6163)


Files

T3X_belink_syslang-1_0_0-z-200708161700.t3x (7.71 KB) T3X_belink_syslang-1_0_0-z-200708161700.t3x Administrator Admin, 2007-08-16 17:00
6163.patch (3.79 KB) 6163.patch Administrator Admin, 2010-11-17 16:20

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Task #62856: L parameter strong defaultClosed2014-11-11

Actions
Related to TYPO3 Core - Feature #84581: Create a backend module to create site configurationsClosedBenni Mack2018-04-03

Actions
Actions

Also available in: Atom PDF