Weblate/Documentation — Tamazight (Central Atlas) @ Hosted Weblate: How to handle renaming translation files?

Source change

English

Tamazight (Central Atlas)

Needs editing

Skip

	English	Tamazight (Central Atlas)	Actions
	For monolingual translations, Weblate can find the previous string by ID, so it shows the differences automatically.
	Why does Weblate still show old translation strings when I've updated the template?
	Weblate does not try to manipulate the translation files in any way other than allowing translators to translate. So it also does not update the translatable files when the template or source code have been changed. You simply have to do this manually and push changes to the repository, Weblate will then pick up the changes automatically.
	It is usually a good idea to merge changes done in Weblate before updating translation files, as otherwise you will usually end up with some conflicts to merge.
	:ref:`translations-update`, :ref:`updating-target-files`, :doc:`/devel/gettext`, :doc:`/devel/sphinx`
	How to handle renaming translation files?	Tisuɣal
	When renaming files in the repository, it can happen that Weblate sees this as removal and adding of the files. This can lead to losing strings history, comments and suggestions.
	To avoid that, perform renaming in following steps:
	Lock the translation component in :ref:`manage-vcs`.
	Commit pending changes in :ref:`manage-vcs`.
	Merge Weblate changes to the upstream repository.

Loading…

None

String updated in the repository

English

Tamazight (Central Atlas) 7 characters edited Current translation Needs editing

a year ago

None

Source string changed

English 30 characters edited

a year ago

Source and translation do not both end with a question mark

English	Tamazight (Central Atlas)
translation		Weblate
translations		Weblate

rst-text

a year ago

2 days ago

a year ago

docs/locales/tzm/LC_MESSAGES/docs.po, string 7465