types capabilities, Translation workflows Direct translation This is most usual setup for smaller teams, anybody can directly translate. This is also the default setup in Weblate. Any user can edit translations source language, it will be also available for translators to translate into additional languages. Development process Localization process Developers Intermediate file Monolingual base language file Translators Once you merge changes from Weblate, you might have to merge these branches (depending on your development workflow) discarding differences: See also Keeping translations same across components How to

types capabilities, Translation workflows Direct translation This is most usual setup for smaller teams, anybody can directly translate. This is also the default setup in Weblate. Any user can edit translations source language, it will be also available for translators to translate into additional languages. Development process Localization process Developers Intermediate file Monolingual base language file Translators Once you merge changes from Weblate, you might have to merge these branches (depending on your development workflow) discarding differences: git merge -s ours origin/maintenance See also Keeping translations

types capabilities, Translation workflows Direct translation This is most usual setup for smaller teams, anybody can directly translate. This is also the default setup in Weblate. Any user can edit translations source language, it will be also available for translators to translate into additional languages. Development process Localization process Developers Intermediate file Monolingual base language file Translators Once you merge changes from Weblate, you might have to merge these branches (depending on your development workflow) discarding differences: git merge -s ours origin/maintenance See also Keeping translations

types capabilities, Translation workflows Direct translation This is most usual setup for smaller teams, anybody can directly translate. This is also the default setup in Weblate. Any user can edit translations source language, it will be also available for translators to translate into additional languages. Development process Localization process Developers Intermediate file Monolingual base language file Translators Once you merge changes from Weblate, you might have to merge these branches (depending on your development workflow) discarding differences: git merge -s ours origin/maintenance See also Keeping translations

types capabilities, Translation workflows Direct translation This is most usual setup for smaller teams, anybody can directly translate. This is also the default setup in Weblate. Any user can edit translations source language, it will be also available for translators to translate into additional languages. Development process Localization process Developers Intermediate file Monolingual base language file Translators Once you merge changes from Weblate, you might have to merge these branches (depending on your development workflow) discarding differences: git merge -s ours origin/maintenance See also Keeping translations

types capabilities, Translation workflows Direct translation This is most usual setup for smaller teams, anybody can directly translate. This is also the default setup in Weblate. Any user can edit translations source language, it will be also available for translators to translate into additional languages. Development process Localization process Developers Intermediate file Monolingual base language file Translators Once you merge changes from Weblate, you might have to merge these branches (depending on your development workflow) discarding differences: git merge -s ours origin/maintenance See also Keeping translations

types capabilities, Translation workflows Direct translation This is most usual setup for smaller teams, anybody can directly translate. This is also the default setup in Weblate. Any user can edit translations source language, it will be also available for translators to translate into additional languages. Development process Localization process Developers Intermediate file Monolingual base language file Translators Once you merge changes from Weblate, you might have to merge these branches (depending on your development workflow) discarding differences: git merge -s ours origin/maintenance See also Keeping translations

types capabilities, Translation workflows Direct translation This is most usual setup for smaller teams, anybody can directly translate. This is also the default setup in Weblate. Any user can edit translations source language, it will be also available for translators to translate into additional languages. Development process Localization process Developers Intermediate file Monolingual base language file Translators Once you merge changes from Weblate, you might have to merge these branches (depending on your development workflow) discarding differences: git merge -s ours origin/maintenance See also Keeping translations

types capabilities, Translation workflows Direct translation This is most usual setup for smaller teams, anybody can directly translate. This is also the default setup in Weblate. Any user can edit translations source language, it will be also available for translators to translate into additional languages. Development process Localization process Developers Intermediate file Monolingual base language file Translators Once you merge changes from Weblate, you might have to merge these branches (depending on your development workflow) discarding differences: git merge -s ours origin/maintenance See also Keeping translations

types capabilities, Translation workflows Direct translation This is most usual setup for smaller teams, anybody can directly translate. This is also the default setup in Weblate. Any user can edit translations source language, it will be also available for translators to translate into additional languages. Development process Localization process Developers Intermediate file Monolingual base language file Translators Once you merge changes from Weblate, you might have to merge these branches (depending on your development workflow) discarding differences: See also Keeping translations same across components How to