Downloading and uploading translations
You can export files from a translation, make changes, and import them again. This allows working offline, and then merging changes back into the existing translation. This works even if it has been changed in the meantime.
Not
Available options might be limited by access control settings.
Downloading translations
From the project or component dashboard, translatable files can be downloaded in the Files menu.
The first option is to download the file in the original format as it is stored in the repository. In this case, any pending changes in the translation are getting committed and the up-to-date file is yield without any conversions.
You can also download the translation converted into one of the widely used localization formats. The converted files will be enriched with data provided in Weblate; such as additional context, comments or flags. Several file formats are available via the Files ↓ Customize download menu:
gettext PO
Gettext uzantılı XLIFF
XLIFF 1.1
TermBase eXchange
Çeviri belleği takası
gettext MO (yalnızca çeviri gettext PO kullanıyorsa kullanılabilir)
CSV
Excel Open XML
JSON (yalnızca tek dilli çeviriler için kullanılabilir)
Android dizge kaynağı (yalnızca tek dilli çeviriler için kullanılabilir)
iOS dizgeleri (yalnızca tek dilli çeviriler için kullanılabilir)
İpucu
The content available in the converted files differs based on file format features, you can find overview in Çeviri türü yetenekleri.
Uploading translations
When you have made your changes, use Upload translation in the Files menu.
Desteklenen dosya biçimleri
Any file in a supported file format can be uploaded, but it is still recommended to use the same file format as the one used for translation, otherwise some features might not be translated properly.
Ayrıca bakınız
Desteklenen dosya biçimleri, Downloading and uploading translations
Import methods
Çeviri dosyaları yüklenirken şu seçenekler sunulur:
- Çeviri olarak eklensin (
translate) Imported strings are added as translations to existing strings. This is the most common usecase, and the default behavior.
Only translations are used from the uploaded file and no additional content.
- Öneri olarak eklensin (
suggest) Imported strings are added as suggestions, do this when you want to have your uploaded strings reviewed.
Only translations are used from the uploaded file and no additional content.
- Düzenlenmesi gerekli çeviri olarak eklensin (
fuzzy) Imported strings are added as translations needing edit. This can be useful when you want translations to be used, but also reviewed.
Only translations are used from the uploaded file and no additional content.
- Var olan çeviri dosyası değiştirilsin (
replace) Existing file is replaced with new content. This can lead to loss of existing translations, use with caution.
- Kaynak dizgeler güncellensin (
source) Updates source strings in bilingual translation file. This is similar to what PO dosyalarını POT ile eşleştirerek güncelleme (msgmerge) does.
Bu seçenek yalnızca bazı dosya biçimleri için kullanılabilir.
- Yeni dizgeler eklensin (
add) Adds new strings to the translation. It skips the one which already exist.
In case you want to both add new strings and update existing translations, upload the file second time with Add as translation.
This option is available only with Dizge yönetimi turned on.
Yüklenen dosyadan yalnızca kaynak, çeviri ve anahtar (bağlam) kullanılır.
Conflicts handling
Defines how to deal with uploaded strings which are already translated.
Düzenlenmesi gerekli dizgeler
There is also an option for how to handle strings needing edit in the imported file. Such strings can be handle in one of the three following ways: “Do not import”, “Import as string needing edit”, or “Import as translated”.