Weblate - Revision history

Karellen: Converted to redirect

2022-04-11T23:21:44Z

Converted to redirect

← Older revision		Revision as of 23:21, 11 April 2022
Line 1:		Line 1:
	~~= Best practices =~~		#REDIRECT [[Language_portal]]
	[[~~Translations#Submit_your_add-on_or_skin_for_translation\|Submit your add-on or skin for translation~~]]
	~~<br/><br/>~~
	* Only change the content of en_gb source language file.
	~~:Never change anything in other language files, as Weblate will handle syncing and maintaining of all strings for all languages.~~
	~~<br/>~~
	* If you have an open Weblate pull request, always merge that pull request before any other.<br/>
	~~:Failing to do so could result in merge conflicts at Weblate.<br/>~~
	~~:Also merge any open Weblate pull request before changing or adding translations to en_gb source file.~~
	~~<br/>~~
	* If doing a minor change for an existing source language (en_gb) string, Weblate will most likely treat this as a completely new string.<br/>
	~~:That means that all existing translations will get removed for that string.<br/>~~
	~~:So be careful before you change existing strings.~~
	~~<br/>~~
	* Sometimes Weblate will add commented out translations at the end of language files.<br/>
	~~:These '''should not''' be removed and are harmless.<br/>~~
	~~:They are kept as part of translation memory and will benefit translators in a number of ways.~~

	~~= Workflows and scripts =~~
	~~We offer several workflows to help integrate Weblate translations into your add-ons.~~

	~~== sync-addon-metadata-translations.yml ==~~
	~~This workflow will sync metadata (description, summary, disclaimer etc.) between addon.xml and the language files.<br/>~~
	~~It will add this metadata from addon.xml to each language file to allow translation at Weblate.<br/>~~
	~~Whenever changes are done to either addon.xml or any language file, the workflow will run and sync changes both ways.<br/>~~
	~~Either a pull request or direct commit can be created.~~

	~~An '''''amt-sync''''' branch is created by the workflow where changes are pushed before a pull request is created.<br/>~~
	~~Once the pull request is merged the branch can be safely deleted.<br/>~~
	~~Make sure branch protection is disabled for ''amt-sync'' branch and that force pushing is allowed.~~

	~~''This workflow is required for proper Weblate translations.''~~

	~~== increment_version.py ==~~
	~~This workflow will bump the version number in your addon.xml file whenever changes are done to the language files.<br/>~~
	~~It can be configured to create a changelog entry as well.<br/>~~
	~~Either a pull request or direct commit can be created.~~

	~~An '''''inc-ver''''' branch is created by the workflow where changes are pushed before a pull request is created.<br/>~~
	~~Once the pull request is merged the branch can be safely deleted.<br/>~~
	~~Make sure branch protection is disabled for ''inc-ver'' branch and that force pushing is allowed.~~

	~~= Weblate configuration and add-ons =~~
	~~The text in your Weblate pull request or direct commit can be changed exactly as you see fit.~~

	~~We enable several add-ons for your component(s) at Weblate.<br/>~~
	~~Most of them will be enabled with default configuration, but some of them can be configured to your preference.~~

	~~==Squash Git commits==~~
	~~This add-on will squash all Weblate commits into a single one.<br/>~~
	~~But it can also create one commit per language or per file if wanted.~~

	~~==Customize gettext output==~~
	~~Default for this add-on is to only wrap lines at newlines.<br/>~~
	~~But it can also wrap lines at 77 characters and at newlines or do no line wrapping.~~

Gade: /* Best practices */

2022-04-05T08:53:29Z

Best practices

← Older revision		Revision as of 08:53, 5 April 2022
Line 1:		Line 1:
	= Best practices =		= Best practices =
	[[Translations#Submit_your_add-on_or_skin_for_translation\|Submit your add-on or skin for translation]]		[[Translations#Submit_your_add-on_or_skin_for_translation\|Submit your add-on or skin for translation]]

	~~Only change the content of en_gb source language file.<br/>~~
	~~Never change anything in other language files, as Weblate will handle syncing and maintaining of all strings for all languages.~~
	<br/><br/>		<br/><br/>
	If you have an open Weblate pull request, always merge that pull request before any other.<br/>		* Only change the content of en_gb source language file.
	Failing to do so could result in merge conflicts at Weblate.<br/>		:Never change anything in other language files, as Weblate will handle syncing and maintaining of all strings for all languages.
	Also merge any open Weblate pull request before changing or adding translations to en_gb source file.		<br/>
	~~<br/>~~<br/>		* If you have an open Weblate pull request, always merge that pull request before any other.<br/>
	If doing a minor change for an existing source language (en_gb) string, Weblate will most likely treat this as a completely new string.<br/>		:Failing to do so could result in merge conflicts at Weblate.<br/>
	That means that all existing translations will get removed for that string.<br/>		:Also merge any open Weblate pull request before changing or adding translations to en_gb source file.
	So be careful before you change existing strings.		<br/>
	~~<br/>~~<br/>		* If doing a minor change for an existing source language (en_gb) string, Weblate will most likely treat this as a completely new string.<br/>
	Sometimes Weblate will add commented out translations at the end of language files.<br/>		:That means that all existing translations will get removed for that string.<br/>
	These '''should not''' be removed and are harmless.<br/>		:So be careful before you change existing strings.
	They are kept as part of translation memory and will benefit translators in a number of ways.		<br/>
			* Sometimes Weblate will add commented out translations at the end of language files.<br/>
			:These '''should not''' be removed and are harmless.<br/>
			:They are kept as part of translation memory and will benefit translators in a number of ways.

	= Workflows and scripts =		= Workflows and scripts =

Gade: /* Best practices */

2022-03-22T10:51:15Z

Best practices

← Older revision		Revision as of 10:51, 22 March 2022
Line 12:		Line 12:
	That means that all existing translations will get removed for that string.<br/>		That means that all existing translations will get removed for that string.<br/>
	So be careful before you change existing strings.		So be careful before you change existing strings.
			<br/><br/>
			Sometimes Weblate will add commented out translations at the end of language files.<br/>
			These '''should not''' be removed and are harmless.<br/>
			They are kept as part of translation memory and will benefit translators in a number of ways.

	= Workflows and scripts =		= Workflows and scripts =

Gade: /* Best practices */

2022-03-22T10:48:42Z

Best practices

← Older revision		Revision as of 10:48, 22 March 2022
Line 4:		Line 4:
	Only change the content of en_gb source language file.<br/>		Only change the content of en_gb source language file.<br/>
	Never change anything in other language files, as Weblate will handle syncing and maintaining of all strings for all languages.		Never change anything in other language files, as Weblate will handle syncing and maintaining of all strings for all languages.
			<br/><br/>
	If you have an open Weblate pull request, always merge that pull request before any other.<br/>		If you have an open Weblate pull request, always merge that pull request before any other.<br/>
	Failing to do so could result in merge conflicts at Weblate.<br/>		Failing to do so could result in merge conflicts at Weblate.<br/>

Gade: /* Best practices */

2022-03-22T10:48:14Z

Best practices

← Older revision		Revision as of 10:48, 22 March 2022
Line 8:		Line 8:
	Failing to do so could result in merge conflicts at Weblate.<br/>		Failing to do so could result in merge conflicts at Weblate.<br/>
	Also merge any open Weblate pull request before changing or adding translations to en_gb source file.		Also merge any open Weblate pull request before changing or adding translations to en_gb source file.
			<br/><br/>
			If doing a minor change for an existing source language (en_gb) string, Weblate will most likely treat this as a completely new string.<br/>
			That means that all existing translations will get removed for that string.<br/>
			So be careful before you change existing strings.

	= Workflows and scripts =		= Workflows and scripts =

Gade: /* Weblate configuration and add-ons */

2022-03-18T01:13:38Z

Weblate configuration and add-ons

← Older revision		Revision as of 01:13, 18 March 2022
Line 36:		Line 36:
	The text in your Weblate pull request or direct commit can be changed exactly as you see fit.		The text in your Weblate pull request or direct commit can be changed exactly as you see fit.

	We enable several add-ons for your component(s) at Weblate.		We enable several add-ons for your component(s) at Weblate.<br/>
	Most of them will be enabled with default configuration, but some of them can be configured to your preference.		Most of them will be enabled with default configuration, but some of them can be configured to your preference.

Gade: /* increment_version.py */

2022-03-18T01:12:36Z

increment_version.py

← Older revision		Revision as of 01:12, 18 March 2022
Line 29:		Line 29:
	Either a pull request or direct commit can be created.		Either a pull request or direct commit can be created.

	An '''''inc-ver''''' branch is created by the workflow where changes are pushed to before a pull request is created.<br/>		An '''''inc-ver''''' branch is created by the workflow where changes are pushed before a pull request is created.<br/>
	Once the pull request is merged the branch can be safely deleted.<br/>		Once the pull request is merged the branch can be safely deleted.<br/>
	Make sure branch protection is disabled for ''inc-ver'' branch and that force pushing is allowed.		Make sure branch protection is disabled for ''inc-ver'' branch and that force pushing is allowed.

Gade: /* sync-addon-metadata-translations.yml */

2022-03-18T01:11:33Z

sync-addon-metadata-translations.yml

← Older revision		Revision as of 01:11, 18 March 2022
Line 18:		Line 18:
	Either a pull request or direct commit can be created.		Either a pull request or direct commit can be created.

	An '''''amt-sync''''' branch is created by the workflow where changes are pushed to before a pull request is created.<br/>		An '''''amt-sync''''' branch is created by the workflow where changes are pushed before a pull request is created.<br/>
	Once the pull request is merged the branch can be safely deleted.<br/>		Once the pull request is merged the branch can be safely deleted.<br/>
	Make sure branch protection is disabled for ''amt-sync'' branch and that force pushing is allowed.		Make sure branch protection is disabled for ''amt-sync'' branch and that force pushing is allowed.

Gade: /* Squash Git commits */

2022-03-17T21:25:56Z

Squash Git commits

← Older revision		Revision as of 21:25, 17 March 2022
Line 40:		Line 40:

	==Squash Git commits==		==Squash Git commits==
	This add-on will squash all Weblate commits into ~~one~~ single one.<br/>		This add-on will squash all Weblate commits into a single one.<br/>
	But it can also create one commit per language or per file if wanted.		But it can also create one commit per language or per file if wanted.

Gade at 21:25, 17 March 2022

2022-03-17T21:25:04Z

← Older revision		Revision as of 21:25, 17 March 2022
Line 2:		Line 2:
	[[Translations#Submit_your_add-on_or_skin_for_translation\|Submit your add-on or skin for translation]]		[[Translations#Submit_your_add-on_or_skin_for_translation\|Submit your add-on or skin for translation]]

	Only change the content of en_gb source language file.		Only change the content of en_gb source language file.<br/>
	Never change anything in other language files, as Weblate will handle syncing and maintaining of all strings for all languages.		Never change anything in other language files, as Weblate will handle syncing and maintaining of all strings for all languages.

	If you have an open Weblate pull request, always merge that pull request before any other.		If you have an open Weblate pull request, always merge that pull request before any other.<br/>
	Failing to do so could result in merge conflicts at Weblate.		Failing to do so could result in merge conflicts at Weblate.<br/>
	Also merge any open Weblate pull request before changing or adding translations to en_gb source file.		Also merge any open Weblate pull request before changing or adding translations to en_gb source file.

Line 13:		Line 13:

	== sync-addon-metadata-translations.yml ==		== sync-addon-metadata-translations.yml ==
	This workflow will sync metadata (description, summary, disclaimer etc.) between addon.xml and the language files.		This workflow will sync metadata (description, summary, disclaimer etc.) between addon.xml and the language files.<br/>
	It will add this metadata from addon.xml to each language file to allow translation at Weblate.		It will add this metadata from addon.xml to each language file to allow translation at Weblate.<br/>
	Whenever changes are done to either addon.xml or any language file, the workflow will run and sync changes both ways.		Whenever changes are done to either addon.xml or any language file, the workflow will run and sync changes both ways.<br/>
	Either a pull request or direct commit can be created.		Either a pull request or direct commit can be created.

	An '''''amt-sync''''' branch is created by the workflow where changes are pushed to before a pull request is created.		An '''''amt-sync''''' branch is created by the workflow where changes are pushed to before a pull request is created.<br/>
	Once the pull request is merged the branch can be safely deleted.		Once the pull request is merged the branch can be safely deleted.<br/>
	Make sure branch protection is disabled for ''amt-sync'' branch and that force pushing is allowed.		Make sure branch protection is disabled for ''amt-sync'' branch and that force pushing is allowed.

Line 25:		Line 25:

	== increment_version.py ==		== increment_version.py ==
	This workflow will bump the version number in your addon.xml file whenever changes are done to the language files.		This workflow will bump the version number in your addon.xml file whenever changes are done to the language files.<br/>
	It can be configured to create a changelog entry as well.		It can be configured to create a changelog entry as well.<br/>
	Either a pull request or direct commit can be created.		Either a pull request or direct commit can be created.

	An '''''inc-ver''''' branch is created by the workflow where changes are pushed to before a pull request is created.		An '''''inc-ver''''' branch is created by the workflow where changes are pushed to before a pull request is created.<br/>
	Once the pull request is merged the branch can be safely deleted.		Once the pull request is merged the branch can be safely deleted.<br/>
	Make sure branch protection is disabled for ''inc-ver'' branch and that force pushing is allowed.		Make sure branch protection is disabled for ''inc-ver'' branch and that force pushing is allowed.

Line 40:		Line 40:

	==Squash Git commits==		==Squash Git commits==
	This add-on will squash all Weblate commits into one single one.		This add-on will squash all Weblate commits into one single one.<br/>
	But it can also create one commit per language or per file if wanted.		But it can also create one commit per language or per file if wanted.

	==Customize gettext output==		==Customize gettext output==
	Default for this add-on is to only wrap lines at newlines.		Default for this add-on is to only wrap lines at newlines.<br/>
	But it can also wrap lines at 77 characters and at newlines or do no line wrapping.		But it can also wrap lines at 77 characters and at newlines or do no line wrapping.