Formate të mbuluar kartelash

Weblate supports a wide range of translation formats. Each format is slightly different and provides a different set of capabilities.

Ndihmëz

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.

• Burime vargjesh Android
• Vargje Apple iOS
• Kartela tejtëdhënash shitoreje aplikacionesh
• Kartelë ARB
• Kartela CSV
• Kartela DTD
• Excel Open XML
• Kartelë XML e sheshtë
• Fluent format
• GNU gettext
• go-i18n JSON files
• gotext JSON files
• Veti GWT
• Kartela HTML
• i18next JSON files
• Format IDML
• Përkthime INI
• Inno Setup INI translations
• Veti Java
• Përkthime Joomla
• Kartela JSON
• Vargje PHP Lavarel
• Markdown files
• mi18n lang files
• Format OpenDocument
• Vargje PHP
• Qt Linguist .ts
• ResourceDictionary files
• RESX .NET resource files
• Kartela Ruby YAML
• Stringsdict format
• Kartela titrash
• TermBase eXchange format
• Kartela tekst
• JSON WebExtension
• Kartela Windows RC
• XLIFF
• Kartela YAML

Shihni edhe

Translation Related File Formats

Pikasje e vetvetishme

Weblate tries to detect file format during Adding translation projects and components. The detection might be wrong for different variants of the same serialization format (JSON, YAML, properties) or file encoding, so please verify that Format kartelash is correct before creating the component.

Translation types capabilities

Capabilities of all supported formats

Format	Linguality [1]	Shumësa [2]	Descriptions [3]	Kontekst [4]	Vendndodhje [5]	Flags [8]	Additional states [6]
GNU gettext	dygjuhëshe	po	po	po	po	po [9]	lyp përpunim
Monolingual gettext	mono	po	po	po	po	po [9]	lyp përpunim
XLIFF	të dyja	po	po	po	po	po	lyp përpunim, i miratuar
Veti Java	të dyja	no	po	no	no	no
mi18n lang files	mono	no	po	no	no	no
Veti GWT	mono	po	po	no	no	no
Përkthime Joomla	mono	no	po	no	po	no
Qt Linguist .ts	të dyja	po	po	no	po	po	lyp përpunim
Burime vargjesh Android	mono	po	po [7]	no	no	po
Vargje Apple iOS	të dyja	no	po	no	no	no
Vargje PHP	mono	no [10]	po	no	no	no
Kartela JSON	mono	no	no	no	no	no
i18next JSON files	mono	po	no	no	no	no
go-i18n JSON files	mono	po	po	no	no	no
gotext JSON files	mono	po	po	no	po	no
Kartelë ARB	mono	po	po	no	no	no
JSON WebExtension	mono	po	po	no	no	no
RESX .NET resource files	mono	no	po	no	no	po
ResourceDictionary files	mono	no	no	no	no	po
Kartela CSV	të dyja	no	po	po	po	no	lyp përpunim
Kartela YAML	mono	no	no	no	no	no
Kartela Ruby YAML	mono	po	no	no	no	no
Kartela DTD	mono	no	no	no	no	no
Kartelë XML e sheshtë	mono	no	no	no	no	po
Kartela Windows RC	mono	no	po	no	no	no
Excel Open XML	mono	no	po	po	po	no	lyp përpunim
Kartela tejtëdhënash shitoreje aplikacionesh	mono	no	no	no	no	no
Kartela titrash	mono	no	no	no	po	no
Kartela HTML	mono	no	no	no	no	no
Markdown files	mono	no	no	no	no	no
Format OpenDocument	mono	no	no	no	no	no
Format IDML	mono	no	no	no	no	no
Përkthime INI	mono	no	no	no	no	no
Inno Setup INI translations	mono	no	no	no	no	no
TermBase eXchange format	dygjuhëshe	no	po	no	no	po
Kartela tekst	mono	no	no	no	no	no
Stringsdict format	mono	po	no	no	no	no
Fluent format	mono	no [11]	po	no	no	no

[1]

Shihni Formate dygjuhësh dhe njëgjuhësh

[2]

See Pluralized strings

[3]

See Përshkrim vargu burim

[4]

See Kontekst

[5]

See Vendndodhje vargu burim

[6]

See String states

[7]

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

[8]

See Flamurka përkthimi.

[9] (1,2)

The gettext type comments are used as flags.

[10]

The plurals are supported only for Laravel which uses in string syntax to define them, see Localization in Laravel.

[11]

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

Formate dygjuhësh dhe njëgjuhësh

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 Vargje Apple iOS). 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 Burime vargjesh Android). 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 Kartelë njëgjuhëshe gjuhe bazë within Weblate, though the naming might vary in your paradigm.

Additionally this workflow can be extended by utilizing Kartelë gjuhe ndërmjetëse to include strings provided by developers, but not to be used as is in the final strings.

String states

Many file formats only differentiate «Untranslated» and «Translated» strings. With some formats it is possible to store more fine-grained state information, such as «Needs editing» or «Approved».

Përshkrim vargu burim

Source string descriptions can be used to pass additional info about the string to translate.

Several formats have native support for providing additional info to translators (for example XLIFF, GNU gettext, JSON WebExtension, Kartela CSV, Excel Open XML, Qt Linguist .ts, go-i18n JSON files, gotext JSON files, Kartelë ARB, RESX .NET resource files). Many other formats extract closest comment as source string description.

Shpjegim

The Shpjegim on strings can be stored and parsed from a few file formats.

Currently supported only in TermBase eXchange format.

Vendndodhje vargu burim

Location of a string in source code might help proficient translators figure out how the string is used.

This information is typically available in bilingual formats where strings are extracted from the source code using tools. For example GNU gettext and Qt Linguist .ts.

Flamurka përkthimi

Translation flags allow customizing Weblate behavior. Some formats support defining those in the translation file (you can always define them in the Weblate interface, see Customizing behavior using flags).

This feature is modelled on flags in GNU gettext.

Additionally, for all XML based format, the flags are extracted from the non-standard attribute weblate-flags. Additionally max-length:N is supported through the maxwidth attribute as defined in the XLIFF standard, see Specifying translation flags.

Shihni edhe

Customizing behavior using flags, PO files documentation

Kontekst

Context is used to differentiate identical strings in a bilingual format 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).

For monolingual formats the string identifier (often called key) can serve the same purpose and additional context is not necessary.

Pluralized strings

Plurals are necessary to properly localize strings with variable count. The rules depend on a target language and many formats follow CLDR specification for that.

Ndihmëz

Pluralizing strings need proper support from the application framework as well. Choose native format of your platform such as GNU gettext, Burime vargjesh Android or Stringsdict format.

Vargje vetëm për lexim

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 Burime vargjesh Android), but can be emulated in others by adding a read-only flag, see Customizing behavior using flags.

Supporting other formats

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.

Shihni edhe

Translation Related File Formats