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
- Kartela XML të sheshta
- Format Fluent
- Kartelë JSON Format.JS
- GNU gettext PO (Portable Object)
- Kartela JSON go-i18n
- Kartela JSON gotext
- Veti GWT
- Kartela HTML
- Kartela JSON i18next
- Format IDML
- Përkthime INI
- Përkthime Inno Setup INI
- Veti Java
- Përkthime Joomla
- Kartela JSON
- Vargje PHP Lavarel
- Kartela Markdown
- Kartela mi18n lang
- Burime Mobile Kotlin
- Format OpenDocument
- Vargje PHP
- Qt Linguist .ts
- Kartela ResourceDictionary
- Kartela burimesh .NET (RESX, RESW)
- Kartela Ruby YAML
- Format Stringsdict
- Kartela titrash
- Format TermBase eXchange
- Kartela tekst
- JSON WebExtension
- Kartela Windows RC
- XLIFF
- Kartela YAML
Shihni edhe
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¶
Format |
Linguality [1] |
Shumësa [2] |
Descriptions [3] |
Kontekst [4] |
Vendndodhje [5] |
Flags [8] |
Additional states [6] |
---|---|---|---|---|---|---|---|
dygjuhëshe |
po |
po |
po |
po |
po [9] |
lyp përpunim |
|
mono |
po |
po |
po |
po |
po [9] |
lyp përpunim |
|
të dyja |
po |
po |
po |
po |
po |
lyp përpunim, i miratuar |
|
të dyja |
no |
po |
no |
no |
no |
||
mono |
no |
po |
no |
no |
no |
||
mono |
po |
po |
no |
no |
no |
||
mono |
no |
po |
no |
po |
no |
||
të dyja |
po |
po |
no |
po |
po |
lyp përpunim |
|
mono |
po |
po [7] |
no |
no |
po |
||
të dyja |
no |
po |
no |
no |
no |
||
mono |
no [10] |
po |
no |
no |
no |
||
mono |
no |
no |
no |
no |
no |
||
mono |
po |
no |
no |
no |
no |
||
mono |
po |
po |
no |
no |
no |
||
mono |
po |
po |
no |
po |
no |
||
mono |
po |
po |
no |
no |
no |
||
mono |
po |
po |
no |
no |
no |
||
mono |
no |
po |
no |
no |
po |
||
mono |
no |
no |
no |
no |
po |
||
të dyja |
no |
po |
po |
po |
no |
lyp përpunim |
|
mono |
no |
no |
no |
no |
no |
||
mono |
po |
no |
no |
no |
no |
||
mono |
no |
no |
no |
no |
no |
||
mono |
no |
no |
no |
no |
po |
||
mono |
no |
po |
no |
no |
no |
||
mono |
no |
po |
po |
po |
no |
lyp përpunim |
|
mono |
no |
no |
no |
no |
no |
||
mono |
no |
no |
no |
po |
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 |
||
mono |
no |
no |
no |
no |
no |
||
dygjuhëshe |
no |
po |
no |
no |
po |
||
mono |
no |
no |
no |
no |
no |
||
mono |
po |
no |
no |
no |
no |
||
mono |
no [11] |
po |
no |
no |
no |
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 PO (Portable Object), 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 PO (Portable Object), JSON WebExtension, Kartela CSV, Excel Open XML, Qt Linguist .ts, Kartela JSON go-i18n, Kartela JSON gotext, Kartelë ARB, Kartela burimesh .NET (RESX, RESW)). 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 Format TermBase eXchange.
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 PO (Portable Object) 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 PO (Portable Object).
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
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 PO (Portable Object), Burime vargjesh Android or Format Stringsdict.
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