Skip to content

docs: improve translation visibility and lower barrier to entry#7034

Open
Abhi-d-gr8 wants to merge 2 commits intoOSGeo:mainfrom
Abhi-d-gr8:feat/7006-translations-visibility
Open

docs: improve translation visibility and lower barrier to entry#7034
Abhi-d-gr8 wants to merge 2 commits intoOSGeo:mainfrom
Abhi-d-gr8:feat/7006-translations-visibility

Conversation

@Abhi-d-gr8
Copy link
Contributor

This PR addresses #7006 by improving documentation to encourage translation contributions.

Changes

  • README.md: Added Weblate translation status badge and highlighted translations in Contributing section
  • CONTRIBUTING.md: Added dedicated Translations section with step-by-step guide for beginners
  • locale/README.md: Completely rewritten to be welcoming and beginner-friendly, with technical details separated for developers

Motivation

Translation activity has been minimal except for French and Swedish. These changes aim to:

  • Make translations more visible to potential contributors
  • Lower the barrier to entry by emphasizing "no coding required"
  • Provide clear, friendly onboarding instructions
  • Highlight contributor recognition

Fixes #7006

@github-actions github-actions bot added vector Related to vector data processing Python Related code is in Python C Related code is in C translation Message translation related module docs markdown Related to markdown, markdown files tests Related to Test Suite CMake labels Feb 3, 2026
Add Weblate badge, dedicated Translations section in CONTRIBUTING.md,
and rewrite locale/README.md to be beginner-friendly.

Addresses OSGeo#7006
@Abhi-d-gr8 Abhi-d-gr8 force-pushed the feat/7006-translations-visibility branch from 0a95f6b to e11fc32 Compare February 3, 2026 23:48
@Abhi-d-gr8
Copy link
Contributor Author

Apologies for the inconvenience @echoix . I accidentally included commits from another branch (I guess during the compare and pull request). I have force-pushed to clean it up, and the PR now only contains the relevant documentation changes.

@echoix
Copy link
Member

echoix commented Feb 4, 2026

I didn't post any review comments yet, so it really doesn't matter. I didn't have time to read either

Copy link
Member

@echoix echoix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall I like the tone, it is positive and convincing, almost like an advertisement ;)

The readme in locale/ folder still contains the needed older info, and updated, except for some few points which were not true anymore before this change, and needs to be true now

If someone else wants to read after that to see how it fits with our other guidelines, the greater picture, I'd appreciate, but once the little points addressed, I plan on having this merged anyways, it's really close

locale/README.md Outdated
@@ -1,24 +1,36 @@
# HOWTO translate GRASS GIS messages
# Contributing to GRASS GIS Translations
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Contributing to GRASS GIS Translations
# Contributing to GRASS Translations

In 8.5, and since somewhere in spring, GRASS GIS was renamed, or rebranded as GRASS; it isn't only a GIS

locale/README.md Outdated
# Contributing to GRASS GIS Translations

## Where to translate user message
**Welcome!** Thank you for your interest in helping translate GRASS GIS.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Welcome!** Thank you for your interest in helping translate GRASS GIS.
**Welcome!** Thank you for your interest in helping translate GRASS.

locale/README.md Outdated
Comment on lines 23 to 24
- Email the development mailing list at `grass-dev@lists.osgeo.org`
([subscribe here](https://lists.osgeo.org/mailman/listinfo/grass-dev))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The discourse subsection grass developers replaced the grass-dev mailing list. All the content was migrated to there.

### Quick start

**Please help us translate all the GRASS messages!!**
1. **Create an account** at [OSGeo Weblate](https://weblate.osgeo.org/)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Validate with your experience on if it is enough or the correct steps. When going in private navigation, I don't see a way to create the account on the Weblate sign in page, on my phone anyways.


Translations are automatically submitted to the GRASS repository as pull requests.
For help or questions, join the
[GRASS development community on Discourse](https://discourse.osgeo.org/c/grass/developer/61)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@petrasovaa wasn't there an old translation mailing list? Should we migrate it too? Just thinking about it, as we're linking to the grass-dev list equivalent on discourse.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, good catch, it even has posts from 2025!

https://lists.osgeo.org/pipermail/grass-translations/

The trend was to replace these with user or dev discussions, but I one can make an argument for a separate list.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, I need to checks with PSC again, but I think we are moving away from it, so I wouldn't add it here.

@Abhi-d-gr8
Copy link
Contributor Author

I'm glad you liked the tone @echoix , so should I commit the suggestions you made , or should I wait for others to give their opinions or anything you want me to do ...

@echoix
Copy link
Member

echoix commented Feb 4, 2026

The ones you know, make them, but maybe there will be nothing to change after that

You can also report issues, plan new features,
or explore <https://grass.osgeo.org/get-involved/>.

## Translations
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would move this after AI policy. And I would shorten it, it should mainly point to the locale/README. So e.g. you don't need here getting started and the "why translate" seems excessive (and too obviously AI-generated).

[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.5176030.svg)](https://doi.org/10.5281/zenodo.5176030)
[![Discourse](https://img.shields.io/badge/discourse-forum-blue?logo=discourse)](https://discourse.osgeo.org/c/grass/62)
[![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/OSGeo/grass/main?labpath=doc%2Fexamples%2Fnotebooks%2Fjupyter_example.ipynb)
[![Translation status](https://weblate.osgeo.org/widget/grass-gis/svg-badge.svg)](https://weblate.osgeo.org/engage/grass-gis/)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is weird, the website states:

The translation project for GRASS GIS currently contains 0 strings for translation. It is being translated into 31 languages. Overall, these translations are 100.0% complete.

Any idea what's going on?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very weird indeed, I see the same, but not in the images of other badges.

I even tried in private navigation, in case it considered only my logged in language preferences.

**Please help us translate all the GRASS messages!!**
1. **Create an account** at [OSGeo Weblate](https://weblate.osgeo.org/)
2. **Choose your language** at the [GRASS GIS project page](https://weblate.osgeo.org/projects/grass-gis/)
3. **Start translating** directly in your browser - no software installation needed!
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe at least linking weblate user documentation? This seems rather brief.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

C Related code is in C CMake docs markdown Related to markdown, markdown files module Python Related code is in Python tests Related to Test Suite translation Message translation related vector Related to vector data processing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feat] Incite collaborators to participate translations in their languages

4 participants