docs: improve translation visibility and lower barrier to entry#7034
docs: improve translation visibility and lower barrier to entry#7034Abhi-d-gr8 wants to merge 2 commits intoOSGeo:mainfrom
Conversation
Add Weblate badge, dedicated Translations section in CONTRIBUTING.md, and rewrite locale/README.md to be beginner-friendly. Addresses OSGeo#7006
0a95f6b to
e11fc32
Compare
|
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. |
|
I didn't post any review comments yet, so it really doesn't matter. I didn't have time to read either |
echoix
left a comment
There was a problem hiding this comment.
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 | |||
There was a problem hiding this comment.
| # 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. |
There was a problem hiding this comment.
| **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
| - Email the development mailing list at `grass-dev@lists.osgeo.org` | ||
| ([subscribe here](https://lists.osgeo.org/mailman/listinfo/grass-dev)) |
There was a problem hiding this comment.
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/) |
There was a problem hiding this comment.
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) |
There was a problem hiding this comment.
@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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Hm, I need to checks with PSC again, but I think we are moving away from it, so I wouldn't add it here.
|
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 ... |
|
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 |
There was a problem hiding this comment.
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).
| [](https://doi.org/10.5281/zenodo.5176030) | ||
| [](https://discourse.osgeo.org/c/grass/62) | ||
| [](https://mybinder.org/v2/gh/OSGeo/grass/main?labpath=doc%2Fexamples%2Fnotebooks%2Fjupyter_example.ipynb) | ||
| [](https://weblate.osgeo.org/engage/grass-gis/) |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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! |
There was a problem hiding this comment.
Maybe at least linking weblate user documentation? This seems rather brief.
This PR addresses #7006 by improving documentation to encourage translation contributions.
Changes
Motivation
Translation activity has been minimal except for French and Swedish. These changes aim to:
Fixes #7006