GRASS messages translation - Revision history

Neteler: /* Add Weblate generated translation badge to README files */ Adding new translators

2025-06-22T16:09:22Z

Add Weblate generated translation badge to README files: Adding new translators

← Older revision		Revision as of 16:09, 22 June 2025
Line 68:		Line 68:
	Then click on the <code>+</code> button to add a language. You have to do it for each component.		Then click on the <code>+</code> button to add a language. You have to do it for each component.

	==== ~~Add~~ Weblate generated translation badge to README files ====		==== Adding Weblate generated translation badge to README files ====

	We may consider to add a translation status badge, pointing to [https://weblate.osgeo.org/projects/grass-gis/ Weblate], to the server README.md on GitHub:		We may consider to add a translation status badge, pointing to [https://weblate.osgeo.org/projects/grass-gis/ Weblate], to the server README.md on GitHub:
Line 77:		Line 77:

	Yet a TODO.		Yet a TODO.

			==== Adding new translators: giving credit ====

			New translators need to be added here:
			https://github.com/OSGeo/grass/blob/main/translators.csv

	=== Weblate: technical background on the installation ===		=== Weblate: technical background on the installation ===

Neteler: + Add translation badge to README files

2025-06-20T15:15:54Z

+ Add translation badge to README files

← Older revision		Revision as of 15:15, 20 June 2025
Line 67:		Line 67:

	Then click on the <code>+</code> button to add a language. You have to do it for each component.		Then click on the <code>+</code> button to add a language. You have to do it for each component.

			==== Add Weblate generated translation badge to README files ====

			We may consider to add a translation status badge, pointing to [https://weblate.osgeo.org/projects/grass-gis/ Weblate], to the server README.md on GitHub:

			<syntaxhighlight lang="markdown">
			[![Translation status](https://weblate.osgeo.org/widgets/grass-gis/-/svg-badge.svg)](https://weblate.osgeo.org/engage/grass-gis/?utm_source=widget)
			</syntaxhighlight>

			Yet a TODO.

	=== Weblate: technical background on the installation ===		=== Weblate: technical background on the installation ===

Neteler: /* Files to be edited */ Add support for a new language

2025-06-03T16:02:34Z

Files to be edited: Add support for a new language

← Older revision		Revision as of 16:02, 3 June 2025
Line 61:		Line 61:

	'''We highly recommend to use our Weblate server: https://weblate.osgeo.org/projects/grass-gis/'''!		'''We highly recommend to use our Weblate server: https://weblate.osgeo.org/projects/grass-gis/'''!

			==== Add support for a new language ====

			Go to any component, e.g. grasslibs - https://weblate.osgeo.org/projects/grass-gis/grasslibs/

			Then click on the <code>+</code> button to add a language. You have to do it for each component.

	=== Weblate: technical background on the installation ===		=== Weblate: technical background on the installation ===

Neteler: /* Weblate: technical background on the installation */ GRASS GIS related Weblate troubleshooting

2023-10-09T16:31:37Z

Weblate: technical background on the installation: GRASS GIS related Weblate troubleshooting

← Older revision		Revision as of 16:31, 9 October 2023
Line 69:		Line 69:

	For technical background on the OSGeo Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate .		For technical background on the OSGeo Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate .

			For GRASS GIS related Weblate troubleshooting, see the discussion in this OSGeo-SAC ticket: https://trac.osgeo.org/osgeo/ticket/2981

	'''Weblate Troubleshooting:'''		'''Weblate Troubleshooting:'''

Neteler: added osgeoweblate fork URL: https://github.com/osgeoweblate/grass/tree/weblate-grass-gis-grasslibs

2023-10-09T08:50:23Z

added osgeoweblate fork URL: https://github.com/osgeoweblate/grass/tree/weblate-grass-gis-grasslibs

← Older revision		Revision as of 08:50, 9 October 2023
Line 64:		Line 64:
	=== Weblate: technical background on the installation ===		=== Weblate: technical background on the installation ===

	'''How it works:''' when a developer makes a GRASS GIS repo commit on GitHub, GitHub then calls the [https://github.com/OSGeo/grass/pull/3065#issuecomment-1716446226 webhook] on Weblate which triggers a refresh of Weblate's git ~~copy~~ of the GRASS GIS repo.		'''How it works:''' when a developer makes a GRASS GIS repo commit on GitHub, GitHub then calls the [https://github.com/OSGeo/grass/pull/3065#issuecomment-1716446226 webhook] on Weblate which triggers a refresh of Weblate's git fork of the GRASS GIS repo (check at https://github.com/osgeoweblate/grass/tree/weblate-grass-gis-grasslibs).

	For pushing translations back to GitHub, there is a setting in Weblate for that which defaults to 24 hrs (accumulates translations over a day). Then a pull request with the translations will be opened in the GRASS GIS GitHub repo.		For pushing translations back to GitHub, there is a setting in Weblate for that which defaults to 24 hrs (accumulates translations over a day). Then a pull request with the translations will be opened in the GRASS GIS GitHub repo.

Neteler: Weblate troubleshooting requires administrator rights

2023-09-22T06:21:24Z

Weblate troubleshooting requires administrator rights

← Older revision		Revision as of 06:21, 22 September 2023
Line 75:		Line 75:
	a conflict or whatever reason:		a conflict or whatever reason:

	Log into Weblate and check on <https://weblate.osgeo.org/projects/grass-gis/#repository>		Log into Weblate (requires administrator rights) and check on <https://weblate.osgeo.org/projects/grass-gis/#repository>
	click on the "Manage" -> "Repository Maintenance". Therein choose "Update" button,		click on the "Manage" -> "Repository Maintenance". Therein choose "Update" button,
	"Update with merge without fast-forward". If successful, this will create		"Update with merge without fast-forward". If successful, this will create

Neteler: update Weblate Troubleshooting

2023-09-14T12:56:39Z

update Weblate Troubleshooting

← Older revision		Revision as of 12:56, 14 September 2023
Line 70:		Line 70:
	For technical background on the OSGeo Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate .		For technical background on the OSGeo Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate .

	'''Troubleshooting:'''		'''Weblate Troubleshooting:'''

	In case the Weblate's git copy of the GRASS GIS repo does ~~not~~ update due to a conflict or whatever reason:		In case the Weblate's git copy of the GRASS GIS repo does no longer update due to
			a conflict or whatever reason:

	Log into Weblate and check on https://weblate.osgeo.org/projects/grass-gis/#repository		Log into Weblate and check on <https://weblate.osgeo.org/projects/grass-gis/#repository>
	~~and~~ choose "Update with merge without fast-forward". If successful, this will create another pull request in the GRASS GIS repo.		click on the "Manage" -> "Repository Maintenance". Therein choose "Update" button,
			"Update with merge without fast-forward". If successful, this will create
			another pull request in the GRASS GIS repo (trigger with "Push" button).

	=== Continuing an existing translation ===		=== Continuing an existing translation ===

Neteler: /* Weblate: technical background on the installation */

2023-09-13T16:51:31Z

Weblate: technical background on the installation

← Older revision		Revision as of 16:51, 13 September 2023
Line 62:		Line 62:
	'''We highly recommend to use our Weblate server: https://weblate.osgeo.org/projects/grass-gis/'''!		'''We highly recommend to use our Weblate server: https://weblate.osgeo.org/projects/grass-gis/'''!

	==== Weblate: technical background on the installation ====		=== Weblate: technical background on the installation ===

	'''How it works:''' when a developer makes a GRASS GIS repo commit on GitHub, GitHub then calls the [https://github.com/OSGeo/grass/pull/3065#issuecomment-1716446226 webhook] on Weblate which triggers a refresh of Weblate's git copy of the GRASS GIS repo.		'''How it works:''' when a developer makes a GRASS GIS repo commit on GitHub, GitHub then calls the [https://github.com/OSGeo/grass/pull/3065#issuecomment-1716446226 webhook] on Weblate which triggers a refresh of Weblate's git copy of the GRASS GIS repo.

Neteler: + Weblate: technical background on the installation

2023-09-13T16:50:34Z

+ Weblate: technical background on the installation

← Older revision		Revision as of 16:50, 13 September 2023
Line 42:		Line 42:
	=== Files to be edited ===		=== Files to be edited ===

	==== GRASS GIS 8 ====		==== GRASS GIS 8 translations ====
	In GRASS GIS 8, we have only 3 types of .po files per language (the files are stored in the source code, in directory locale/po/):		In GRASS GIS 8, we have only 3 types of .po files per language (the files are stored in the source code, in directory locale/po/):

Line 62:		Line 62:
	'''We highly recommend to use our Weblate server: https://weblate.osgeo.org/projects/grass-gis/'''!		'''We highly recommend to use our Weblate server: https://weblate.osgeo.org/projects/grass-gis/'''!

	For technical background on the Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate		==== Weblate: technical background on the installation ====

			'''How it works:''' when a developer makes a GRASS GIS repo commit on GitHub, GitHub then calls the [https://github.com/OSGeo/grass/pull/3065#issuecomment-1716446226 webhook] on Weblate which triggers a refresh of Weblate's git copy of the GRASS GIS repo.

			For pushing translations back to GitHub, there is a setting in Weblate for that which defaults to 24 hrs (accumulates translations over a day). Then a pull request with the translations will be opened in the GRASS GIS GitHub repo.

			For technical background on the OSGeo Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate .

			'''Troubleshooting:'''

			In case the Weblate's git copy of the GRASS GIS repo does not update due to a conflict or whatever reason:

			Log into Weblate and check on https://weblate.osgeo.org/projects/grass-gis/#repository
			and choose "Update with merge without fast-forward". If successful, this will create another pull request in the GRASS GIS repo.

	=== Continuing an existing translation ===		=== Continuing an existing translation ===

Neteler: /* GRASS GIS 8 */ For technical background on the Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate

2023-09-11T15:31:00Z

GRASS GIS 8: For technical background on the Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate

← Older revision		Revision as of 15:31, 11 September 2023
Line 60:		Line 60:
	where "LANG" in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: <tt>grasswxpy_pl.po</tt> for Polish.		where "LANG" in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: <tt>grasswxpy_pl.po</tt> for Polish.

	We highly recommend to use our Weblate server: https://weblate.osgeo.org/projects/grass-gis/		'''We highly recommend to use our Weblate server: https://weblate.osgeo.org/projects/grass-gis/'''!

			For technical background on the Weblate installation, see https://wiki.osgeo.org/wiki/SAC:Weblate

	=== Continuing an existing translation ===		=== Continuing an existing translation ===