Frequently Asked Questions (FAQ)¶
- General Questions
- Questions about extension integration
If you miss a question, please share it in the slack channel
The existing translation server will be turned off some time after Crowdin will have been announced stable.
The existing and exported translations which are downloaded within the Install Tool will be available for longer time.
If you miss an extension on Crowdin, contact the extension owner to create a project on Crowdin. It is important that they follow the description on the page Extension integration. The setup is a simple process and done within minutes.
If you are missing the support for a specific language in an extension on Crowdin please contact either the maintainer of the extension or the Crowdin initiative.
The language needs to be supported by TYPO3 itself as well, see Supported languages for a list of all languages.
If you just have setup Crowdin and you ship translated xlf files within your extension, those will be shown as well as to be translated.
You need to exlude those in your
.crowdin.yaml configuration which can be found in the extension root directory.
files: - source: /Resources/Private/Language/ translation: /%original_path%/%two_letters_code%.%original_file_name% ignore: - /Resources/Private/Language/de.*
In the long run, you should remove the translations from your extension as those will be provided by the translation server.
More information can be found in the documentation on crowdin: https://support.crowdin.com/configuration-file/
If translations exist on Pootle there is no need to retranslate everything on Crowdin again - you can import those.
Fetch translations Download the translations you need. You will need to download them directly from the TER with the following URL pattern:
<extension_key>is the full extension key,
<e>the 1st and
<x>the 2nd letter of that extension key. Finally
<lang>is the 2-lettered language identifier, e.g.
For example to download the German translations of the extension powermail:
Open and Cleanup Unzip the translations and switch to e.g.
Resources/Private/Languagewhich is the typical directory of translations. Remove the xml files as only the xlf files are important.
Match the Files The attribute
originalof the translations must match the ones of the default translations. Example: The file
Resources/Private/Language/locallang.xlfstarts with the following snippet:
<?xml version="1.0" encoding="utf-8" standalone="yes" ?> <xliff version="1.0"> <file source-language="en" datatype="plaintext" original="EXT:powermail/Resources/Private/Language/locallang.xlf">
de.locallang.xlfmust be modified and
original="messages"must be changed to
Upload the Translations Just keep on reading the next question.
Yes, you can! Switch to the settings area of your project (you need to have the proper permissions for that) and you can upload xlf files or even zip files containg the xlf files.
After triggering the upload Crowdin tries to find the matching source files and the target languages. It might be that you need to adopt both if not found automatically.