Project

General

Profile

Actions

Feature #14173

closed

remove dependency on static_info_tables for $GLOBALS['TSFE']->sys_language_uid

Added by Martin Kutschker over 20 years ago. Updated over 16 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Backend API
Target version:
-
Start date:
2004-05-17
Due date:
% Done:

0%

Estimated time:
PHP Version:
4
Tags:
Complexity:
Sprint Focus:

Description

The dependency is a) unnecssary and has b) a rather highy performance penalty by using an additional SQL query.

I suggest adding a Typo3-to -iso mapping to the Core, probably in t3lib_cs:

var $isoCodeArray = array(
'dk' => 'da',
'de' => '',
'no' => '',
'it' => '',
'fr' => '',
'es' => '',
'nl' => '',
'cz' => 'cs',
'pl' => ',
'si' => 'sl',
'fi' => '',
'tr' => '',
'se' => 'sv',
'pt' => '',
'ru' => '',
'ro' => ',
'ch' => 'zh-Hans,
'sk' => '',
'lt' => '',
'is' => '',
'hr' => '',
'hu' => '',
'gl' => '',
'th' => '',
'gr' => '',
'hk' => 'zh-Hant',
'eu' => '',
'bg' => '',
'br' => 'pt-br',
'et' => '',
'ar' => '',
'he' => ,
'ua' => 'uk',
);

The current static_info_tables is broken anyway, because eg Brazialian Prortuguese is mapped to pt instead of pt-br.
(issue imported from #M101)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #14702: Typo3 shouldn't use country codes for specifying languageClosedRené Fritz2005-04-25

Actions
Actions #1

Updated by Robert Lemke over 20 years ago

Hey René, this seems like your favourite topic ...

Actions #2

Updated by Martin Kutschker over 19 years ago

The mentioned array exists in TYPO3:

t3lib_cs->isoArray

Actions #3

Updated by René Fritz over 19 years ago

I'm not shure if we should change the behaviour of iso codes languages etc.
I think we should do the cleanup in TYPO3 V. 5 when we're doing some major changes anyway.

Actions #4

Updated by Ingo Renner over 17 years ago

is present in source

Actions

Also available in: Atom PDF