Missing, a string is considered translated as soon as a element Needing edit if there is a target present: new, needs-translation, “Needs edit” state in Weblate (the following states are used to flag the string as The state attribute in the file is partially processed and mapped to the XLIFF enriched by XLIFF 1.2 Representation Guide for Gettext PO to support plurals.Ĭhanged in version 3.3: Weblate ignored the state attribute prior to the 3.3 release. Standard XLIFF supporting placeables and other XML elements. Simple XLIFF file where content of the elements is stored as plain text (all XML elements being escaped). Weblate supports XLIFF in several variants: XLIFF translation file XML Localization Interchange File Format (XLIFF) is usually used as bilingual, but Weblate supports it as monolingual as well. XML-based format created to standardize translation files, but in the end it #: 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" Plurals are handled in the syntax of the strings and not exposed as plurals in Weblate. The plurals are supported only for Laravel which uses in string syntax to define them, see Localization in Laravel. Additionally max-length:N is supported through the maxwidth attribute as defined in the XLIFF standard, see Specifying translation flags. The flags are extracted from the non-standard attribute weblate-flags for all XML based formats. The gettext type comments are used as flags. See Customizing behavior using flags ( 1, 2) XML comment placed before the element, parsed as a source string description. Īdditional states supported by the file format in addition to “Untranslated” and “Translated”. Location of a string in source code might help proficient translators figure out how the string is used. Ĭontext 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). Source string descriptions can be used to pass additional info about the string to translate. Plurals are necessary to properly localize strings with variable count. Weblate can automatically detect several widespread file formats, but thisĭetection can harm your performance and will limit features specific to givenįile format (for example automatic addition of new translations). Not to be used as is in the final strings. Intermediate language file to include strings provided by developers, but Is called Monolingual base language file within Weblate, though the naming mightĪdditionally this workflow can be extended by utilizing Some fileįormats are used in both variants, see the detailed description below.įor correct use of monolingual files, Weblate requires access to a fileĬontaining complete list of strings to translate with their source-this file Only the mapping of those to any given language (typically Android string resources). Monolingual formats identify the string by ID, and each language file contains (typical examples are GNU gettext, XLIFF or Apple iOS strings). Bilingual and monolingual formats īilingual formats store two languages in single file-source and translation Translators can additionally use whatever tools they are used to, and will more Well established format in the toolkit/platform you use. When choosing a file format for your application, it’s better to stick some
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |