Project

General

Profile

Actions
Copy link

Bug #31806

closed

translation files are not being loaded in fileadmin

Added by Christian Seifert about 13 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Xavier Perseguers
Category:
Localization
Target version:
-
Start date:
2011-11-14
Due date:
% Done:

0%

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

Description

I have the following TS object and a multilingual site offering an English and German version:

lib {
siteTitle = TEXT
siteTitle {
data = LLL:fileadmin/labels/locallang.xml:sitetitle.value
...
}
}

So, depending on the chosen language, the sitetitle should change. For common locallang.xml files it does what it's expected to do. Now I grabes the extdeveval extensions and created to xliff files into "fileadmin/labels/":
- locallang.xlf
- de.locallang.xlf

Now, TYPO3 tries to read out the locallang.xlf file, what works perfectly. Unfortunately the German version "de.locallang.xlf" won't be loaded at all. It isn't even possible to fetch the path of the "de.locallang.xlf", because of it is not in on of the expected directories of (ext,sysext,typo3conf,...).

Might it be possible to load translation files independent of their location? Else I can only use xliff in extensions, but for consistency reasons it's much nicer using it at all.

Best regards
Christian

Actions
Copy link
 #1

Updated by Xavier Perseguers over 11 years ago

  • Project changed from 1937 to TYPO3 Core
Actions
Copy link
 #2

Updated by Riccardo De Contardi over 9 years ago

  • Category set to Localization
  • Status changed from New to Needs Feedback
  • TYPO3 Version set to 6.2
  • Is Regression set to No

this is the test I have done with TYPO3 6.2.12, tell me if it is sufficient:

1) I created in the root a "Website language" record, named "english"
2) I assume my default language (0) is italian.
3) TS Setup:

config.linkVars = L
config.uniqueLinkVars = 1
config.sys_language_overlay = content_fallback
config.language = it
config.locale_all = it_IT
config.htmlTag_langKey = it-IT
config.sys_language_uid = 0

[globalVar = GP:L = 1]
config.language = en
config.locale_all = en_EN
config.htmlTag_langKey = en-EN
config.sys_language_uid = 1
[global]

lib {
 siteTitle = TEXT
 siteTitle {
 data = LLL:fileadmin/labels/locallang.xlf:sitetitle.value
 wrap = <h2>|</h2>
 } 
}

page = PAGE
page.11 < lib.siteTitle

3) in /fileadmin/labels/ I created 2 file languages:
- locallang.xlf
- it.locallang.xlf

(If I remember correctly, this is the right way to do it since...4.7?)

the content of the files:
locallang.xlf

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<xliff version="1.0">
    <file source-language="en" datatype="plaintext" original="messages" date="2015-05-23T22:02:23Z">
        <header/>
        <body>
        <trans-unit id="sitetitle.value" xml:space="preserve">
            <source>Title in English</source>
        </trans-unit>
        </body>
    </file>
</xliff>

it.locallang.xlf

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<xliff version="1.0">
    <file source-language="en" target-language="it" datatype="plaintext" original="messages" date="2015-05-23T22:02:23Z">
        <header />
        <body>
        <trans-unit id="sitetitle.value" xml:space="preserve">
            <source>Title in English</source>
            <target>Titolo in italiano</target>
        </trans-unit>
        </body>
    </file>
</xliff>

4) I create the "english" version of the home page

RESULT: the standard page (http://mytypo3site.it/index.php?id=1) shows "Titolo in italiano" while the translated version (http://mytypo3site.it/index.php?id=1&L=1) shows "title in english".

Is this sufficient or should I perform more tests?

Actions
Copy link
 #3

Updated by Christian Seifert over 9 years ago

This ticket is from the year 2011 and I used TYPO3 4.6. I think, this ticket can be closed.

Actions
Copy link
 #4

Updated by Riccardo De Contardi over 9 years ago

  • Status changed from Needs Feedback to Closed

closed upon request of the reporter;

If you experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions
Copy link

Also available in: Atom PDF