tlayh / xliff-translationtool Goto Github PK

If an XLIFF file has been translated once into e.g. DE and saved to typo3conf/l10n/, the extension always opens that generated file when you return to edit the terms.

If we add new translation definitions to the original file locallang.xlf in our extension, the XLIFF Translation Tool doesn't see them.

It would be great if this could be repaired so that e.g. the original file is aways read in, with translations from the typo3conf/l10n/ file if available and if not, then showing the source text from the original xlf file.

Is there any chance you could change this over the next couple of days? Email me if you need to.

Many thanks!

If a file like fr.locallang.xml is selected to translate, a second language prefix is added and the new file looks like: fr.fr.locallang.xml

The extensions own locallang files are xml, should be xlf

There are three file templates, that are used to generate the xlf files, hide this files!

Add configuration to make the extensions that can be translated accessible depending on the backend user rights, so that editors can only translate specified extensions and languages.

Allow the user to filter the list of languages to only have already (possibly partially) translated languages

set the default selection to local extensions and display the translatable extensions directly

It is possible that files can not be read if they are symlinked.

Should appear under backend modules.

Overall error handling has to be better with more clear messages.