Supported file formats
Weblate supports most translation format understood by translate-toolkit, however each format being slightly different, some issues with formats that are not well tested can arise.
Siehe auch
Bemerkung
When choosing a file format for your application, it’s better to stick some well established format in the toolkit/platform you use. This way your translators can additionally use whatever tools they are used to, and will more likely contribute to your project.
Bilingual and monolingual formats
Both monolingual and bilingual formats are supported. Bilingual formats store two languages in single file—source and translation (typical examples are GNU gettext, XLIFF or Apple iOS strings). On the other side, monolingual formats identify the string by ID, and each language file contains only the mapping of those to any given language (typically Android string resources). Some file formats are used in both variants, see the detailed description below.
For correct use of monolingual files, Weblate requires access to a file containing complete list of strings to translate with their source—this file is called Einsprachige Basis-Sprachdatei within Weblate, though the naming might vary in your paradigm.
Additionally this workflow can be extended by utilizing Zwischensprachedatei to include strings provided by developers, but not to be used as is in the final strings.
Automatische Detektion
Weblate can automatically detect several widespread file formats, but this detection can harm your performance and will limit features specific to given file format (for example automatic addition of new translations).
Translation types capabilities
Capabilities of all supported formats:
Format |
Linguality 1 |
Plurals 2 |
Descriptions 3 |
Context 4 |
Location 5 |
Flags 8 |
Additional states 6 |
---|---|---|---|---|---|---|---|
bilingual |
yes |
yes |
yes |
yes |
yes 9 |
needs editing |
|
mono |
yes |
yes |
yes |
yes |
yes 9 |
needs editing |
|
both |
yes |
yes |
yes |
yes |
yes 10 |
needs editing, approved |
|
both |
no |
yes |
no |
no |
no |
||
mono |
no |
yes |
no |
no |
no |
||
mono |
yes |
yes |
no |
no |
no |
||
mono |
no |
yes |
no |
yes |
no |
||
both |
yes |
yes |
no |
yes |
yes 10 |
needs editing |
|
mono |
yes |
yes 7 |
no |
no |
yes 10 |
||
both |
no |
yes |
no |
no |
no |
||
mono |
no 11 |
yes |
no |
no |
no |
||
mono |
no |
no |
no |
no |
no |
||
mono |
yes |
no |
no |
no |
no |
||
mono |
yes |
no |
no |
no |
no |
||
mono |
yes |
yes |
no |
no |
no |
||
mono |
yes |
yes |
no |
no |
no |
||
mono |
no |
yes |
no |
no |
yes 10 |
||
mono |
no |
no |
no |
no |
yes 10 |
||
both |
no |
yes |
yes |
yes |
no |
needs editing |
|
mono |
no |
yes |
no |
no |
no |
||
mono |
yes |
yes |
no |
no |
no |
||
mono |
no |
no |
no |
no |
no |
||
mono |
no |
no |
no |
no |
yes 10 |
||
mono |
no |
yes |
no |
no |
no |
||
mono |
no |
yes |
yes |
yes |
no |
needs editing |
|
mono |
no |
no |
no |
no |
no |
||
mono |
no |
no |
no |
yes |
no |
||
mono |
no |
no |
no |
no |
no |
||
mono |
no |
no |
no |
no |
no |
||
mono |
no |
no |
no |
no |
no |
||
mono |
no |
no |
no |
no |
no |
||
mono |
no |
no |
no |
no |
no |
||
bilingual |
no |
yes |
no |
no |
yes 10 |
||
mono |
no |
no |
no |
no |
no |
||
mono |
yes |
yes |
no |
no |
no |
||
mono |
no 12 |
yes |
no |
no |
no |
- 1
- 2
Plurals are necessary to properly localize strings with variable count.
- 3
Source string descriptions can be used to pass additional info about the string to translate.
- 4
Context is used to differentiate identical strings used in different scopes (for example Sun can be used as an abbreviated name of the day „Sunday“ or as the name of our closest star).
- 5
Location of a string in source code might help proficient translators figure out how the string is used.
- 6
Additional states supported by the file format in addition to „Untranslated“ and „Translated“.
- 7
XML comment placed before the
<string>
element, parsed as a source string description.- 8
- 9(1,2)
The gettext type comments are used as flags.
- 10(1,2,3,4,5,6,7)
The flags are extracted from the non-standard attribute
weblate-flags
for all XML based formats. Additionallymax-length:N
is supported through themaxwidth
attribute as defined in the XLIFF standard, see Specifying translation flags.- 11
The plurals are supported only for Laravel which uses in string syntax to define them, see Localization in Laravel.
- 12
Plurale werden in der Syntax der Zeichenketten behandelt und nicht als Plural in Weblate angezeigt.
Schreibgeschützte Zeichenketten
Neu in Version 3.10.
Read-only strings from translation files will be included, but
can not be edited in Weblate. This feature is natively supported by few formats
(XLIFF and Android string resources), but can be emulated in others by adding a
read-only
flag, see Anpassen des Verhaltens mit Flaggen.
GNU gettext
Most widely used format for translating libre software.
Contextual info stored in the file is supported by adjusting its headers or linking to corresponding source files.
The bilingual gettext PO file typically looks like this:
#: weblate/media/js/bootstrap-datepicker.js:1421
msgid "Monday"
msgstr "Pondělí"
#: weblate/media/js/bootstrap-datepicker.js:1421
msgid "Tuesday"
msgstr "Úterý"
#: weblate/accounts/avatar.py:163
msgctxt "No known user"
msgid "None"
msgstr "Žádný"
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
Empty |
Vorlage für neue Übersetzungen |
|
Dateiformat |
Gettext PO file |
Siehe auch
Translating software using GNU gettext, Translating documentation using Sphinx, Gettext on Wikipedia, PO Files, Aktualisieren Sie die Variable ALL_LINGUAS in der „configure“-Datei, Ausgabe von Gettext anpassen, LINGUAS-Datei aktualisieren, MO-Dateien erzeugen, PO-Dateien auf POT aktualisieren (msgmerge)
Monolingual gettext
Some projects decide to use gettext as monolingual formats—they code just the IDs in their source code and the string then needs to be translated to all languages, including English. This is supported, though you have to choose this file format explicitly when importing components into Weblate.
The monolingual gettext PO file typically looks like this:
#: weblate/media/js/bootstrap-datepicker.js:1421
msgid "day-monday"
msgstr "Pondělí"
#: weblate/media/js/bootstrap-datepicker.js:1421
msgid "day-tuesday"
msgstr "Úterý"
#: weblate/accounts/avatar.py:163
msgid "none-user"
msgstr "Žádný"
While the base language file will be:
#: weblate/media/js/bootstrap-datepicker.js:1421
msgid "day-monday"
msgstr "Monday"
#: weblate/media/js/bootstrap-datepicker.js:1421
msgid "day-tuesday"
msgstr "Tuesday"
#: weblate/accounts/avatar.py:163
msgid "none-user"
msgstr "None"
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
|
Dateiformat |
Gettext PO file (monolingual) |
XLIFF
XML-based format created to standardize translation files, but in the end it is one of many standards, in this area.
XML Localization Interchange File Format (XLIFF) is usually used as bilingual, but Weblate supports it as monolingual as well.
Weblate unterstützt XLIFF in mehreren Varianten:
- XLIFF translation file
Simple XLIFF file where content of the elements is stored as plain text (all XML elements being escaped).
- XLIFF with placeables support
Standard XLIFF supporting placeables and other XML elements.
- XLIFF mit Gettext-Erweiterungen
XLIFF enriched by XLIFF 1.2 Representation Guide for Gettext PO to support plurals.
Siehe auch
XML Localization Interchange File Format (XLIFF) specification, XLIFF 1.2 Representation Guide for Gettext PO
Translation states
Geändert in Version 3.3: Weblate ignored the state
attribute prior to the 3.3 release.
The state
attribute in the file is partially processed and mapped to the
„Needs edit“ state in Weblate (the following states are used to flag the string as
needing edit if there is a target present: new
, needs-translation
,
needs-adaptation
, needs-l10n
). Should the state
attribute be
missing, a string is considered translated as soon as a <target>
element
exists.
If the translation string has approved="yes"
, it will also be imported into Weblate
as „Approved“, anything else will be imported as „Waiting for review“ (which matches the
XLIFF specification).
While saving, Weblate doesn’t add those attributes unless necessary:
The
state
attribute is only added in case string is marked as needing edit.The
approved
attribute is only added in case string has been reviewed.In other cases the attributes are not added, but they are updated in case they are present.
That means that when using the XLIFF format, it is strongly recommended to turn on the Weblate review process, in order to see and change the approved state of strings.
Similarly upon importing such files (in the upload form), you should choose Import as translated under Processing of strings needing edit.
Siehe auch
Leerzeichen und Zeilenumbrüche in XLIFF
Generally types or amounts of whitespace is not differentiated between in XML formats.
If you want to keep it, you have to add the xml:space="preserve"
flag to
the string.
For example:
<trans-unit id="10" approved="yes">
<source xml:space="preserve">hello</source>
<target xml:space="preserve">Hello, world!
</target>
</trans-unit>
Specifying translation flags
You can specify additional translation flags (see Anpassen des Verhaltens mit Flaggen) by
using the weblate-flags
attribute. Weblate also understands maxwidth
and font
attributes from the XLIFF specification:
<trans-unit id="10" maxwidth="100" size-unit="pixel" font="ubuntu;22;bold">
<source>Hello %s</source>
</trans-unit>
<trans-unit id="20" maxwidth="100" size-unit="char" weblate-flags="c-format">
<source>Hello %s</source>
</trans-unit>
The font
attribute is parsed for font family, size and weight, the above
example shows all of that, though only font family is required. Any whitespace
in the font family is converted to underscore, so Source Sans Pro
becomes
Source_Sans_Pro
, please keep that in mind when naming the font group (see
Schriftarten verwalten).
String keys
Weblate identifies the units in the XLIFF file by resname
attribute in case
it is present and falls back to id
(together with file
tag if present).
The resname
attribute is supposed to be human friendly identifier of the
unit making it more suitable for Weblate to display instead of id
. The
resname
has to be unique in the whole XLIFF file. This is required by
Weblate and is not covered by the XLIFF standard - it does not put any
uniqueness restrictions on this attribute.
Typical Weblate Component configuration for bilingual XLIFF |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
Empty |
Vorlage für neue Übersetzungen |
|
Dateiformat |
XLIFF Translation File |
Typical Weblate Component configuration for monolingual XLIFF |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
|
Dateiformat |
XLIFF Translation File |
Java properties
Native Java format for translations.
Java properties are usually used as monolingual translations.
Weblate supports ISO-8859-1, UTF-8 and UTF-16 variants of this format. All of
them support storing all Unicode characters, it is just differently encoded.
In the ISO-8859-1, the Unicode escape sequences are used (for example zkou\u0161ka
),
all others encode characters directly either in UTF-8 or UTF-16.
Bemerkung
Loading escape sequences works in UTF-8 mode as well, so please be careful choosing the correct encoding set to match your application needs.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
Java Properties (ISO-8859-1) |
mi18n lang Dateien
Neu in Version 4.7.
Dateiformat, das für die JavaScript-Lokalisierung von mi18n verwendet wird. Syntaktisch entspricht es Java properties.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
mi18n lang file |
GWT-Eigenschaften
Native GWT format for translations.
GWT properties are usually used as monolingual translations.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
GWT Properties |
INI translations
Neu in Version 4.1.
INI file format for translations.
INI translations are usually used as monolingual translations.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
INI File |
Bemerkung
Weblate only extracts keys from sections within an INI file. In case your INI file lacks sections, you might want to use Joomla translations or Java properties instead.
Inno Setup INI translations
Neu in Version 4.1.
Inno Setup INI file format for translations.
Inno Setup INI translations are usually used as monolingual translations.
Bemerkung
The only notable difference to INI translations is in supporting %n
and %t
placeholders for line break and tab.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
Inno Setup INI File |
Bemerkung
Only Unicode files (.islu
) are currently supported, ANSI variant
(.isl
) is currently not supported.
Siehe auch
Joomla translations
Neu in Version 2.12.
Native Joomla format for translations.
Joomla translations are usually used as monolingual translations.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
Joomla Language File |
Qt Linguist .ts
Translation format used in Qt based applications.
Qt Linguist files are used as both bilingual and monolingual translations.
Typical Weblate Component configuration when using as bilingual |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
Empty |
Vorlage für neue Übersetzungen |
|
Dateiformat |
Qt Linguist Translation File |
Typical Weblate Component configuration when using as monolingual |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
|
Dateiformat |
Qt Linguist Translation File |
Siehe auch
Qt Linguist manual, Qt .ts, Bilingual and monolingual formats
Android string resources
Android specific file format for translating applications.
Android string resources are monolingual, the Einsprachige Basis-Sprachdatei is
stored in a different location from the other files – res/values/strings.xml
.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
Android String Resource |
Bemerkung
Android string-array structures are not currently supported. To work around this, you can break your string arrays apart:
<string-array name="several_strings">
<item>First string</item>
<item>Second string</item>
</string-array>
become:
<string-array name="several_strings">
<item>@string/several_strings_0</item>
<item>@string/several_strings_1</item>
</string-array>
<string name="several_strings_0">First string</string>
<string name="several_strings_1">Second string</string>
The string-array that points to the string elements should be stored in a different file, and not be made available for translation.
This script may help pre-process your existing strings.xml files and translations: https://gist.github.com/paour/11291062
Hinweis
To avoid translating some strings, these can be marked as non-translatable. This can be especially useful for string references:
<string name="foobar" translatable="false">@string/foo</string>
Apple iOS strings
File format typically used for translating Apple iOS applications, but also standardized by PWG 5100.13 and used on NeXTSTEP/OpenSTEP.
Apple iOS strings are usually used as monolingual.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
iOS Strings (UTF-8) |
PHP-Zeichenketten
PHP translations are usually monolingual, so it is recommended to specify a base file with (what is most often the) English strings.
Example file:
<?php
$LANG['foo'] = 'bar';
$LANG['foo1'] = 'foo bar';
$LANG['foo2'] = 'foo bar baz';
$LANG['foo3'] = 'foo bar baz bag';
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
|
Dateiformat |
PHP strings |
Laravel PHP-Zeichenketten
Geändert in Version 4.1.
The Laravel PHP localization files are supported as well with plurals:
<?php
return [
'welcome' => 'Welcome to our application',
'apples' => 'There is one apple|There are many apples',
];
Siehe auch
JSON files
Neu in Version 2.0.
Geändert in Version 2.16: Since Weblate 2.16 and with translate-toolkit at-least 2.2.4, nested structure JSON files are supported as well.
Geändert in Version 4.3: The structure of JSON file is properly preserved even for complex situations which were broken in prior releases.
JSON format is used mostly for translating applications implemented in JavaScript.
Weblate currently supports several variants of JSON translations:
Simple key / value files, used for example by vue-i18n or react-intl.
Files with nested keys.
JSON translations are usually monolingual, so it is recommended to specify a base file with (what is most often the) English strings.
Example file:
{
"Hello, world!\n": "Ahoj světe!\n",
"Orangutan has %d banana.\n": "",
"Try Weblate at https://demo.weblate.org/!\n": "",
"Thank you for using Weblate.": ""
}
Nested files are supported as well (see above for requirements), such a file can look like:
{
"weblate": {
"hello": "Ahoj světe!\n",
"orangutan": "",
"try": "",
"thanks": ""
}
}
Hinweis
The JSON file and JSON nested structure file can both handle same type of files. Both preserve existing JSON structure when translating.
The only difference between them is when adding new strings using Weblate.
The nested structure format parses the newly added key and inserts the new
string into the matching structure. For example app.name
key is inserted as:
{
"app": {
"name": "Weblate"
}
}
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
JSON nested structure file |
JSON i18next files
Geändert in Version 2.17: Since Weblate 2.17 and with translate-toolkit at-least 2.2.5, i18next JSON files with plurals are supported as well.
i18next is an internationalization framework written in and for JavaScript. Weblate supports its localization files with features such as plurals.
i18next translations are monolingual, so it is recommended to specify a base file with (what is most often the) English strings.
Bemerkung
Weblate unterstützt das i18next JSON-v3-Format. Die Varianten v2 und v1 sind größtenteils kompatibel, mit Ausnahme der Behandlung von Pluralformen.
The v4 variant uses different approach for storing plurals and is currently not supported.
Example file:
{
"hello": "Hello",
"apple": "I have an apple",
"apple_plural": "I have {{count}} apples",
"apple_negative": "I have no apples"
}
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
i18next JSON file |
go-i18n JSON files
Neu in Version 4.1.
go-i18n translations are monolingual, so it is recommended to specify a base file with (what is most often the) English strings.
Bemerkung
Weblate supports the go-i18n JSON v1 format, for flat JSON formats please use JSON files. The v2 format with hash is currently not supported.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
go-i18n JSON file |
ARB File
Neu in Version 4.1.
ARB translations are monolingual, so it is recommended to specify a base file with (what is most often the) English strings.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
ARB file |
WebExtension JSON
Neu in Version 2.16: This is supported since Weblate 2.16 and with translate-toolkit at-least 2.2.4.
File format used when translating extensions for Mozilla Firefox or Google Chromium.
Bemerkung
While this format is called JSON, its specification allows to include comments, which are not part of JSON specification. Weblate currently does not support file with comments.
Example file:
{
"hello": {
"message": "Ahoj světe!\n",
"description": "Description",
"placeholders": {
"url": {
"content": "$1",
"example": "https://developer.mozilla.org"
}
}
},
"orangutan": {
"message": "Orangutan has $coUnT$ bananas",
"description": "Description",
"placeholders": {
"count": {
"content": "$1",
"example": "5"
}
}
},
"try": {
"message": "",
"description": "Description"
},
"thanks": {
"message": "",
"description": "Description"
}
}
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
WebExtension JSON file |
.XML resource files
Neu in Version 2.3.
A .XML resource (.resx) file employs a monolingual XML file format used in Microsoft .NET applications. It is interchangeable with .resw, when using identical syntax to .resx.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
.NET resource file |
ResourceDictionary files
Neu in Version 4.13.
ResourceDictionary is a monolingual XML file format used to package localizable string resources for Windows Presentation Foundation (WPF) applications.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
ResourceDictionary file |
CSV files
Neu in Version 2.4.
CSV files can contain a simple list of source and translation. Weblate supports the following files:
Files with header defining fields (
location
,source
,target
,ID
,fuzzy
,context
,translator_comments
,developer_comments
). This is the recommended approach, as it is the least error prone. Choose CSV file as a file format.Files with two fields—source and translation (in this order). Choose Simple CSV file as a file format.
Headerless files with fields in order defined by the translate-toolkit:
location
,source
,target
,ID
,fuzzy
,context
,translator_comments
,developer_comments
. Choose CSV file as a file format.Remember to define Einsprachige Basis-Sprachdatei when your files are monolingual (see Bilingual and monolingual formats).
Hinweis
By default, the CSV format does autodetection of file encoding. This can be unreliable in some corner cases and causes performance penalty. Please choose file format variant with encoding to avoid this (for example CSV file (UTF-8)).
Warnung
Das CSV-Format erkennt derzeit automatisch den Dialekt der CSV-Datei. In einigen Fällen kann die automatische Erkennung fehlschlagen und Sie erhalten gemischte Ergebnisse. Dies gilt insbesondere für CSV-Dateien mit Zeilenumbrüchen in den Werten. Als Abhilfe empfiehlt es sich, die Anführungszeichen wegzulassen.
Example file:
Thank you for using Weblate.,Děkujeme za použití Weblate.
Typical Weblate Component configuration for bilingual CSV |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
Empty |
Vorlage für neue Übersetzungen |
|
Dateiformat |
CSV file |
Typical Weblate Component configuration for monolingual CSV |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
|
Dateiformat |
Simple CSV file |
Multivalue CSV file
Neu in Version 4.13.
This variant of the CSV files allows storing multiple translations per string.
Siehe auch
YAML files
Neu in Version 2.9.
The plain YAML files with string keys and values. Weblate also extract strings from lists or dictionaries.
Example of a YAML file:
weblate:
hello: ""
orangutan": ""
try": ""
thanks": ""
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
YAML file |
Siehe auch
Ruby YAML files
Neu in Version 2.9.
Ruby i18n YAML files with language as root node.
Example Ruby i18n YAML file:
cs:
weblate:
hello: ""
orangutan: ""
try: ""
thanks: ""
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
Ruby YAML file |
Siehe auch
DTD files
Neu in Version 2.18.
Example DTD file:
<!ENTITY hello "">
<!ENTITY orangutan "">
<!ENTITY try "">
<!ENTITY thanks "">
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
DTD file |
Siehe auch
Flat XML files
Neu in Version 3.9.
Example of a flat XML file:
<?xml version='1.0' encoding='UTF-8'?>
<root>
<str key="hello_world">Hello World!</str>
<str key="resource_key">Translated value.</str>
</root>
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
Flat XML file |
Siehe auch
Windows RC files
Geändert in Version 4.1: Support for Windows RC files has been rewritten.
Bemerkung
Support for this format is currently in beta, feedback from testing is welcome.
Example Windows RC file:
LANGUAGE LANG_CZECH, SUBLANG_DEFAULT
STRINGTABLE
BEGIN
IDS_MSG1 "Hello, world!\n"
IDS_MSG2 "Orangutan has %d banana.\n"
IDS_MSG3 "Try Weblate at http://demo.weblate.org/!\n"
IDS_MSG4 "Thank you for using Weblate."
END
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
|
Dateiformat |
RC file |
Siehe auch
App-Store Metadatendateien
Neu in Version 3.5.
Metadata used for publishing apps in various app stores can be translated. Currently the following tools are compatible:
The metadata consists of several textfiles, which Weblate will present as separate strings to translate.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
|
Dateiformat |
App store metadata files |
Hinweis
In case you don’t want to translate certain strings (for example changelogs), mark them read-only (see Anpassen des Verhaltens mit Flaggen). This can be automated by the Massenbearbeitung.
Subtitle files
Neu in Version 3.7.
Weblate kann verschiedene Untertiteldateien übersetzen:
SubRip subtitle file (
*.srt
)MicroDVD subtitle file (
*.sub
)Advanced Substation Alpha subtitles file (
*.ass
)Substation Alpha subtitle file (
*.ssa
)
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
|
Dateiformat |
SubRip subtitle file |
Siehe auch
Excel Open XML
Neu in Version 3.2.
Excel Open XML (.xlsx) files can be imported and exported.
When uploading XLSX files for translation, be aware that only the active
worksheet is considered, and there must be at least a column called source
(which contains the source string) and a column called target
(which
contains the translation). Additionally there should be the column called context
(which contains the context path of the translation string). If you use the XLSX
download for exporting the translations into an Excel workbook, you already get
a file with the correct file format.
HTML files
Neu in Version 4.1.
Bemerkung
Support for this format is currently in beta, feedback from testing is welcome.
The translatable content is extracted from the HTML files and offered for the translation.
Siehe auch
Textdateien
Neu in Version 4.6.
Bemerkung
Support for this format is currently in beta, feedback from testing is welcome.
The translatable content is extracted from the plain text files and offered for the translation. Each paragraph is translated as a separate string.
Dieses Format gibt es in drei Varianten:
Klartextdatei
DokuWiki-Textdatei
MediaWiki-Textdatei
Siehe auch
OpenDocument Format
Neu in Version 4.1.
Bemerkung
Support for this format is currently in beta, feedback from testing is welcome.
The translatable content is extracted from the OpenDocument files and offered for the translation.
Siehe auch
IDML Format
Neu in Version 4.1.
Bemerkung
Support for this format is currently in beta, feedback from testing is welcome.
The translatable content is extracted from the Adobe InDesign Markup Language files and offered for the translation.
TermBase eXchange format
Neu in Version 4.5.
TBX is an XML format for the exchange of terminology data.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
Empty |
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
TermBase eXchange file |
Siehe auch
Stringsdict-Format
Neu in Version 4.8.
Bemerkung
Support for this format is currently in beta, feedback from testing is welcome.
Ein von Apple verwendetes XML-basiertes Format, das mehrere Pluralformen einer Zeichenkette speichern kann.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
Stringsdict-Datei |
Siehe auch
Fluent-Format
Neu in Version 4.8.
Bemerkung
Support for this format is currently in beta, feedback from testing is welcome.
Fluent ist ein einsprachiges Textformat, das sich auf asymmetrische Lokalisierung konzentriert: Eine einfache Zeichenkette in einer Sprache kann in einer anderen Sprache eine komplexe Übersetzung mit mehreren Varianten ergeben.
Typical Weblate Component configuration |
|
---|---|
Dateimaske |
|
Einsprachige Basis-Sprachdatei |
|
Vorlage für neue Übersetzungen |
Empty |
Dateiformat |
Fluent-Datei |
Siehe auch
Unterstützung anderer Formate
Most formats supported by translate-toolkit which support serializing can be easily supported, but they did not (yet) receive any testing. In most cases some thin layer is needed in Weblate to hide differences in behavior of different translate-toolkit storages.
To add support for a new format, the preferred approach is to first implement support for it in the translate-toolkit.
Siehe auch