[TYPO3-translators] Translation of localconf.php

Otto van Bruggen otto at webspinnerij.nl
Fri Aug 8 13:51:50 CEST 2008


Hi,

In that case it might be wise to ask individual extension developers to make
their extension available in the xml format.
 
> Otto van Bruggen wrote:
>> Thanks for answering.
>> Not as an offence, but why are these extensions on the translation server?
> 
> Because I need Quixplorer to manage files.

I tried to mail the adres brunn at mail.dk but it returned as it doesn't seem
to exist. Do you happen to know the extension maker so I can ask to update.
 
>> Furthermore, There are around 10 extensions on the translation server
>> without any field to be translated. Result for a user is not logical since
>> he/she gets a translation not available sign.
> 
> They are necessary for TYPO3. Translation tool simply lists all extensions. It
> is not possible to hide any of them.
> 
>> Is it an idea to have only extension on the translation server witch meet
>> some criteria like:
>> - It must have fields to translate
>> - It must be converted to locallang.xml
> 
> Not possible, sorry. This way you will have to exclude even "cms" extension
> and TYPO3 will not run at all.

I find it hard to agree on this last point.
Cms is translated so no problem.

I someone asks you to add a extension is is done instantly.
There is to my opinion a difference between core extensions and others.
So why not take a look if it is even possible to translate.

Regards Otto



More information about the TYPO3-translators mailing list