[TYPO3-v4] Minutes from the 3rd meeting of the 4.6 Release Team

[Ernesto Baschny [cron IT]]

Dmitry Dulepov schrieb am 05.04.2011 13:55:

> Oliver Hader wrote:
>> ** Manage Reference Index =>  Update part, will be available from
>>     Reports as a link but should be encapsulated or rewritten as a
>>     scheduler task too
> 
> This does not seem right. "Reports" implies that it only shows data.
> Moving "Update" there is not what the user would expect from reports.
> Reports are static, displayable. Update is dynamic, it is action in the
> background.

Just a link in the reports to the action. Same for the report about the
"insecure password" which provides a link to the form where you can
change the password. I think having those links to the "how to solve
this issue" directly in the Reports is very user-friendly (instead of
writing "Go to Database, Manager Reference Index, and click on
Reconstruct to solve this problem" => simple provide the proper link!

Having this as a "task" sounds like a good plan, the link would then
simply fire up this task. I just wonder what the result of a "task" can
be, because currently the result from "cleanup" is to display the result
of "what was done". Can a task also output this? If its run through the
scheduler, where is this information displayed?

>>  Why would you either deactivate or delete some currently logged in
>>    user? When you are being hacked? Then it should not be so prominent
> 
> We do it from time to time when editors do not work for a certain period
> of time. It happens quite often.

I think it is about "currently logged in users" view. If he is
"currently logged in" is is working (or its a hacker). The question in
Olly's list is "why would you need that" in this view? I would also say
that it's useless.

>> XLIFF vs. locallang.xml
>> -----------------------
>>
>> In general "XLIFF" is the abbreviation of "XML Localization Interchange
>> File Format". Since the current solution for translating language labels
>> in TYPO3 is an individual solution which cannot be extended easily,
>> there is one initiative to switch from the known locallang.xml structure
>> to the XLIFF standard.
> 
> I see a danger in it. Since we cannot change old versions, it means that
> we will have to keep two translation server around:
> - for translating extensions in LLXML format for TYPO3 4.5 (which is LTS!)
> - for translating extensions in XLIFF format
> 
> Also any extension that uses XLIFF become incompatible with earlier
> TYPO3 versions.
> 
> No idea how to solve that.

If there could be a mapping from the XLIFF translated strings to
locallang files, I see no problem to migrate the translation
infrastructure to XLIFF, but still provide the old locallang files to
older installations.

Cheers,
Ernesto