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.

Notă

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 Fișier de limbă de bază monolingvă within Weblate, though the naming might vary in your paradigm.

Additionally this workflow can be extended by utilizing Fișier de limbaj intermediar to include strings provided by developers, but not to be used as is in the final strings.

Automatic detection

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

Comments 3

Context 4

Location 5

Flags 8

Additional states 6

GNU gettext

bilingual

yes

yes

yes

yes

yes 9

needs editing

Monolingual gettext

mono

yes

yes

yes

yes

yes 9

needs editing

XLIFF

both

yes

yes

yes

yes

yes 10

needs editing, approved

Java properties

both

no

yes

no

no

no

mi18n lang files

mono

no

yes

no

no

no

Proprietăți GWT

mono

yes

yes

no

no

no

Joomla translations

mono

no

yes

no

yes

no

Qt Linguist .ts

both

yes

yes

no

yes

yes 10

needs editing

Android string resources

mono

yes

yes 7

no

no

yes 10

Apple iOS strings

bilingual

no

yes

no

no

no

Șiruri PHP

mono

no 11

yes

no

no

no

JSON files

mono

no

no

no

no

no

JSON i18next files

mono

yes

no

no

no

no

go-i18n JSON files

mono

yes

no

no

no

no

ARB File

mono

yes

yes

no

no

no

WebExtension JSON

mono

yes

yes

no

no

no

.XML resource files

mono

no

yes

no

no

yes 10

CSV files

both

no

yes

yes

yes

no

needs editing

YAML files

mono

no

yes

no

no

no

Ruby YAML files

mono

yes

yes

no

no

no

DTD files

mono

no

no

no

no

no

Flat XML files

mono

no

no

no

no

yes 10

Windows RC files

mono

no

yes

no

no

no

Excel Deschidere XML

mono

no

yes

yes

yes

no

needs editing

Fișiere de metadate ale magazinului de aplicații

mono

no

no

no

no

no

Subtitle files

mono

no

no

no

yes

no

HTML files

mono

no

no

no

no

no

OpenDocument Format

mono

no

no

no

no

no

IDML Format

mono

no

no

no

no

no

INI translations

mono

no

no

no

no

no

Inno Setup INI translations

mono

no

no

no

no

no

TermBase eXchange format

bilingual

no

yes

no

no

yes 10

Fișiere text

mono

no

no

no

no

no

Stringsdict format

mono

yes

yes

no

no

no

Fluent format

mono

no 12

yes

no

no

no

1

See Bilingual and monolingual formats

2

Plurals are necessary to properly localize strings with variable count.

3

Comments 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 „Not translated” and „Translated”.

7

XML comment placed before the <string> element, parsed as a developer comment.

8

See Personalizarea comportamentului cu ajutorul stegulețelor

9(1,2)

The gettext type comments are used as flags.

10(1,2,3,4,5,6)

The flags are extracted from the non-standard attribute weblate-flags for all XML based formats. Additionally max-length:N is supported through the maxwidth 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

Plurals are handled in the syntax of the strings and not exposed as plurals in Weblate.

Șiruri de caractere numai pentru citire

Nou în versiunea 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 Personalizarea comportamentului cu ajutorul stegulețelor.

GNU gettext

Cel mai utilizat format pentru traducerea de software liber.

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 Configurația componentei

Masca de fișier

po/*.po

Fișier de limbă de bază monolingvă

Empty

Șablon pentru traduceri noi

po/messages.pot

Formatul fișierului

Gettext PO file

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 Configurația componentei

Masca de fișier

po/*.po

Fișier de limbă de bază monolingvă

po/en.po

Șablon pentru traduceri noi

po/messages.pot

Formatul fișierului

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.

Vezi și

XML Localization Interchange File Format (XLIFF) specification

Translation states

Schimbat în versiunea 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.

Whitespace and newlines 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.

De exemplu:

    <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 Personalizarea comportamentului cu ajutorul stegulețelor) 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 Gestionarea fonturilor).

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 Configurația componentei for bilingual XLIFF

Masca de fișier

localizations/*.xliff

Fișier de limbă de bază monolingvă

Empty

Șablon pentru traduceri noi

localizations/en-US.xliff

Formatul fișierului

XLIFF Translation File

Typical Weblate Configurația componentei for monolingual XLIFF

Masca de fișier

localizations/*.xliff

Fișier de limbă de bază monolingvă

localizations/en-US.xliff

Șablon pentru traduceri noi

localizations/en-US.xliff

Formatul fișierului

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.

Notă

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 Configurația componentei

Masca de fișier

src/app/Bundle_*.properties

Fișier de limbă de bază monolingvă

src/app/Bundle.properties

Șablon pentru traduceri noi

Empty

Formatul fișierului

Java Properties (ISO-8859-1)

mi18n lang files

Nou în versiunea 4.7.

File format used for JavaScript localization by mi18n. Syntactically it matches Java properties.

Typical Weblate Configurația componentei

Masca de fișier

*.lang

Fișier de limbă de bază monolingvă

en-US.lang

Șablon pentru traduceri noi

Empty

Formatul fișierului

mi18n lang file

Proprietăți GWT

Native GWT format for translations.

GWT properties are usually used as monolingual translations.

Typical Weblate Configurația componentei

Masca de fișier

src/app/Bundle_*.properties

Fișier de limbă de bază monolingvă

src/app/Bundle.properties

Șablon pentru traduceri noi

Empty

Formatul fișierului

GWT Properties

INI translations

Nou în versiunea 4.1.

INI file format for translations.

INI translations are usually used as monolingual translations.

Typical Weblate Configurația componentei

Masca de fișier

language/*.ini

Fișier de limbă de bază monolingvă

language/en.ini

Șablon pentru traduceri noi

Empty

Formatul fișierului

INI File

Notă

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

Nou în versiunea 4.1.

Formatul de fișier Inno Setup INI pentru traduceri.

Inno Setup INI translations are usually used as monolingual translations.

Notă

The only notable difference to INI translations is in supporting %n and %t placeholders for line break and tab.

Typical Weblate Configurația componentei

Masca de fișier

language/*.islu

Fișier de limbă de bază monolingvă

language/en.islu

Șablon pentru traduceri noi

Empty

Formatul fișierului

Inno Setup INI File

Notă

Only Unicode files (.islu) are currently supported, ANSI variant (.isl) is currently not supported.

Joomla translations

Nou în versiunea 2.12.

Native Joomla format for translations.

Joomla translations are usually used as monolingual translations.

Typical Weblate Configurația componentei

Masca de fișier

language/*/com_foobar.ini

Fișier de limbă de bază monolingvă

language/en-GB/com_foobar.ini

Șablon pentru traduceri noi

Empty

Formatul fișierului

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 Configurația componentei when using as bilingual

Masca de fișier

i18n/app.*.ts

Fișier de limbă de bază monolingvă

Empty

Șablon pentru traduceri noi

i18n/app.de.ts

Formatul fișierului

Qt Linguist Translation File

Typical Weblate Configurația componentei when using as monolingual

Masca de fișier

i18n/app.*.ts

Fișier de limbă de bază monolingvă

i18n/app.en.ts

Șablon pentru traduceri noi

i18n/app.en.ts

Formatul fișierului

Qt Linguist Translation File

Android string resources

Android specific file format for translating applications.

Android string resources are monolingual, the Fișier de limbă de bază monolingvă is stored in a different location from the others res/values/strings.xml.

Typical Weblate Configurația componentei

Masca de fișier

res/values-*/strings.xml

Fișier de limbă de bază monolingvă

res/values/strings.xml

Șablon pentru traduceri noi

Empty

Formatul fișierului

Android String Resource

Notă

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

Apple iOS strings

Apple specific file format for translating applications, used for both iOS and iPhone/iPad application translations.

Apple iOS strings are usually used as bilingual translations.

Typical Weblate Configurația componentei

Masca de fișier

Resources/*.lproj/Localizable.strings

Fișier de limbă de bază monolingvă

Resources/en.lproj/Localizable.strings or Resources/Base.lproj/Localizable.strings

Șablon pentru traduceri noi

Empty

Formatul fișierului

iOS Strings (UTF-8)

Șiruri PHP

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 Configurația componentei

Masca de fișier

lang/*/texts.php

Fișier de limbă de bază monolingvă

lang/en/texts.php

Șablon pentru traduceri noi

lang/en/texts.php

Formatul fișierului

PHP strings

Laravel PHP șiruri de caractere

Schimbat în versiunea 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',
];

JSON files

Nou în versiunea 2.0.

Schimbat în versiunea 2.16: Since Weblate 2.16 and with translate-toolkit at-least 2.2.4, nested structure JSON files are supported as well.

Schimbat în versiunea 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:

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": ""
  }
}

Sugestie

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 Configurația componentei

Masca de fișier

langs/translation-*.json

Fișier de limbă de bază monolingvă

langs/translation-en.json

Șablon pentru traduceri noi

Empty

Formatul fișierului

JSON nested structure file

JSON i18next files

Schimbat în versiunea 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.

Notă

Weblate supports the i18next JSON v3 format. The v2 and v1 variants are mostly compatible, with exception of how plurals are handled.

Example file:

{
  "hello": "Hello",
  "apple": "I have an apple",
  "apple_plural": "I have {{count}} apples",
  "apple_negative": "I have no apples"
}

Typical Weblate Configurația componentei

Masca de fișier

langs/*.json

Fișier de limbă de bază monolingvă

langs/en.json

Șablon pentru traduceri noi

Empty

Formatul fișierului

i18next JSON file

go-i18n JSON files

Nou în versiunea 4.1.

go-i18n translations are monolingual, so it is recommended to specify a base file with (what is most often the) English strings.

Notă

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 Configurația componentei

Masca de fișier

langs/*.json

Fișier de limbă de bază monolingvă

langs/en.json

Șablon pentru traduceri noi

Empty

Formatul fișierului

go-i18n JSON file

ARB File

Nou în versiunea 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 Configurația componentei

Masca de fișier

lib/l10n/intl_*.arb

Fișier de limbă de bază monolingvă

lib/l10n/intl_en.arb

Șablon pentru traduceri noi

Empty

Formatul fișierului

ARB file

WebExtension JSON

Nou în versiunea 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.

Notă

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": "",
    "description": "Description"
  },
  "try": {
    "message": "",
    "description": "Description"
  },
  "thanks": {
    "message": "",
    "description": "Description"
  }
}

Typical Weblate Configurația componentei

Masca de fișier

_locales/*/messages.json

Fișier de limbă de bază monolingvă

_locales/en/messages.json

Șablon pentru traduceri noi

Empty

Formatul fișierului

WebExtension JSON file

.XML resource files

Nou în versiunea 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 Configurația componentei

Masca de fișier

Resources/Language.*.resx

Fișier de limbă de bază monolingvă

Resources/Language.resx

Șablon pentru traduceri noi

Empty

Formatul fișierului

.NET resource file

CSV files

Nou în versiunea 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 Fișier de limbă de bază monolingvă when your files are monolingual (see Bilingual and monolingual formats).

Atenționare

The CSV format currently automatically detects the dialect of the CSV file. In some cases the automatic detection might fail and you will get mixed results. This is especially true for CSV files with newlines in the values. As a workaround it is recommended to omit quoting characters.

Example file:

Thank you for using Weblate.,Děkujeme za použití Weblate.

Typical Weblate Configurația componentei for bilingual CSV

Masca de fișier

locale/*.csv

Fișier de limbă de bază monolingvă

Empty

Șablon pentru traduceri noi

locale/en.csv

Formatul fișierului

CSV file

Typical Weblate Configurația componentei for monolingual CSV

Masca de fișier

locale/*.csv

Fișier de limbă de bază monolingvă

locale/en.csv

Șablon pentru traduceri noi

locale/en.csv

Formatul fișierului

Simple CSV file

Vezi și

CSV

YAML files

Nou în versiunea 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 Configurația componentei

Masca de fișier

translations/messages.*.yml

Fișier de limbă de bază monolingvă

translations/messages.en.yml

Șablon pentru traduceri noi

Empty

Formatul fișierului

YAML file

Vezi și

YAML, Ruby YAML files

Ruby YAML files

Nou în versiunea 2.9.

Ruby i18n YAML files with language as root node.

Example Ruby i18n YAML file:

cs:
  weblate:
    hello: ""
    orangutan: ""
    try: ""
    thanks: ""

Typical Weblate Configurația componentei

Masca de fișier

translations/messages.*.yml

Fișier de limbă de bază monolingvă

translations/messages.en.yml

Șablon pentru traduceri noi

Empty

Formatul fișierului

Ruby YAML file

Vezi și

YAML, YAML files

DTD files

Nou în versiunea 2.18.

Example DTD file:

<!ENTITY hello "">
<!ENTITY orangutan "">
<!ENTITY try "">
<!ENTITY thanks "">

Typical Weblate Configurația componentei

Masca de fișier

locale/*.dtd

Fișier de limbă de bază monolingvă

locale/en.dtd

Șablon pentru traduceri noi

Empty

Formatul fișierului

DTD file

Flat XML files

Nou în versiunea 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 Configurația componentei

Masca de fișier

locale/*.xml

Fișier de limbă de bază monolingvă

locale/en.xml

Șablon pentru traduceri noi

Empty

Formatul fișierului

Flat XML file

Vezi și

Flat XML

Windows RC files

Schimbat în versiunea 4.1: Support for Windows RC files has been rewritten.

Notă

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 Configurația componentei

Masca de fișier

lang/*.rc

Fișier de limbă de bază monolingvă

lang/en-US.rc

Șablon pentru traduceri noi

lang/en-US.rc

Formatul fișierului

RC file

Vezi și

Windows RC files

Fișiere de metadate ale magazinului de aplicații

Nou în versiunea 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 Configurația componentei

Masca de fișier

fastlane/android/metadata/*

Fișier de limbă de bază monolingvă

fastlane/android/metadata/en-US

Șablon pentru traduceri noi

fastlane/android/metadata/en-US

Formatul fișierului

App store metadata files

Sugestie

In case you don’t want to translate certain strings (for example changelogs), mark them read-only (see Personalizarea comportamentului cu ajutorul stegulețelor). This can be automated by the Editare în masă.

Subtitle files

Nou în versiunea 3.7.

Weblate poate traduce diverse fișiere de subtitrare:

  • SubRip subtitle file (*.srt)

  • MicroDVD subtitle file (*.sub)

  • Advanced Substation Alpha subtitles file (*.ass)

  • Substation Alpha subtitle file (*.ssa)

Typical Weblate Configurația componentei

Masca de fișier

path/*.srt

Fișier de limbă de bază monolingvă

path/en.srt

Șablon pentru traduceri noi

path/en.srt

Formatul fișierului

SubRip subtitle file

Vezi și

Subtitles

Excel Deschidere XML

Nou în versiunea 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

Nou în versiunea 4.1.

Notă

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.

Vezi și

HTML

Fișiere text

Nou în versiunea 4.6.

Notă

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.

Există trei variante ale acestui format:

  • Fișier text simplu

  • Fișier text DokuWiki

  • Fișier text MediaWiki

OpenDocument Format

Nou în versiunea 4.1.

Notă

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.

IDML Format

Nou în versiunea 4.1.

Notă

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

Nou în versiunea 4.5.

TBX is an XML format for the exchange of terminology data.

Typical Weblate Configurația componentei

Masca de fișier

tbx/*.tbx

Fișier de limbă de bază monolingvă

Empty

Șablon pentru traduceri noi

Empty

Formatul fișierului

TermBase eXchange file

Stringsdict format

Nou în versiunea 4.8.

Notă

Support for this format is currently in beta, feedback from testing is welcome.

XML based format used by Apple which is able to store plural forms of a string.

Typical Weblate Configurația componentei

Masca de fișier

Resources/*.lproj/Localizable.stringsdict

Fișier de limbă de bază monolingvă

Resources/en.lproj/Localizable.stringsdict or Resources/Base.lproj/Localizable.stringsdict

Șablon pentru traduceri noi

Empty

Formatul fișierului

Stringsdict file

Fluent format

Nou în versiunea 4.8.

Notă

Support for this format is currently in beta, feedback from testing is welcome.

Fluent is a monolingual text format that focuses on asymmetric localization: a simple string in one language can map to a complex multi-variant translation in another language.

Typical Weblate Configurația componentei

Masca de fișier

locales/*/messages.ftl

Fișier de limbă de bază monolingvă

locales/en/messages.ftl

Șablon pentru traduceri noi

Empty

Formatul fișierului

Fluent file

Sprijinirea altor 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.