Project

General

Profile

Actions

Bug #16191

closed

class.t3lib_div.php >>>"lang " BUG, lang system bug

Added by rob over 17 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Category:
Extension Manager
Target version:
-
Start date:
2007-07-29
Due date:
% Done:

0%

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

Description

all extension have this problem, both ext and sysext. the I make a example of tt_news, then you can understand well.
first I have write and save the ts that 'config.language = ch'

BUG show:
when yong de language packs in typo3. example with "root/typo3conf/l10n/ch" and "tt_news". If the document "root/typo3conf/ext/tt_news/pi/locallang.xml" have the code

<languageKey index="ch" type="array">
</languageKey>

however I have translated the "root/typo3conf/l10n/ch" well. the document is "root/typo3conf/l10n/ch/tt-news/pi/cn.locallang.xml", the typo3 system used language "default".

when used the II-XMLtranslation Extension, the FE show good, because II_XML del the code " <languageKey index="ch" type="array"></languageKey>" of "root/typo3conf/ext/tt_news/pi/locallang.xml". This time the document "root/typo3conf/ext/tt_news/pi/locallang.xml" is changed. when I copy "root/typo3conf/l10n/ch" and give another one. His typo3 will not work in "ch" language.

In fact, when the variable "ch" of "root/typo3conf/ext/tt_news/pi/locallang.xml" like that, " <languageKey index="ch" type="array"></languageKey>" , the typo3 should to seach "root/typo3conf/l10n/ch" , but now typo3 not work as this.

the bug document is class.t3lib_div.php

(issue imported from #M6044)


Related issues 1 (0 open1 closed)

Has duplicate TYPO3 Core - Bug #16562: translate system bugClosedOliver Hader2007-07-28

Actions
Actions #1

Updated by rob over 17 years ago

NOW THE ONLY WAY TO USE LANGUAGE FOR EVERYBADY IS THAT DEL ALL CODE OF "<languageKey index="ch" type="array"></languageKey>" IN LOCALLANG.XML OF EXTENSION.

Actions #2

Updated by Dmitry Dulepov over 16 years ago

This is not a bug, it is a error in the extension. TYPO3 never declared that external file takes precedence. In fact, translations in the extension takes precedence if it exists (even empty).

According to TYPO3 policy extensions should not have translations in them at all. All translations should be moved to the separate file and combined to language packs by translation server.

The bug report can be closed. It not a bug in TYPO3 core.

Actions #3

Updated by Christian Kuhn over 15 years ago

Resolved, no change required:

As Dmitry mentioned, all translations should be done in separate files.

Actions #4

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF