Project

General

Profile

Actions

Bug #36512

closed

Extension Manager doesn't show default labels if no translation is found

Added by Aske Ertmann about 12 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Extension Manager
Target version:
Start date:
2012-04-24
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.7
PHP Version:
5.3
Tags:
Complexity:
easy
Is Regression:
No
Sprint Focus:

Description

After downloading translations in Danish for the Extension Module multiple labels are missing. I know they haven't been translated on the translation.typo3.org server, but the default label should be shown if there's no translation for the label. I think it's an issue between how the translation server works and how the XLIFF translation is handled. Because the translation server needs all the keys in order to allow for editing of labels, but in TYPO3 it only checks if the key exists, and not if the key actually has been filled out..

Example of empty XLIFF key (missing the target with the translated key)

      <trans-unit id="availableExtensions" xml:space="preserve">
        <source>Available Extensions</source>
      </trans-unit>

Example of empty XML key

      <label index="availableExtensions"/>

I'm not sure if this is a more general issue or only an issue with handling of labels in the EM.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #32203: Language Labels in new Extension Manager show no textClosed2011-11-30

Actions
Actions #1

Updated by Wouter Wolters over 9 years ago

  • Status changed from New to Needs Feedback
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.9)?

Actions #2

Updated by Wouter Wolters about 9 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or 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

Also available in: Atom PDF