Skip to content

Remove Bulgarian from availabe languages#1174

Draft
wlorenzetti wants to merge 1 commit into
v.3.10.xfrom
remove_bg_as_default
Draft

Remove Bulgarian from availabe languages#1174
wlorenzetti wants to merge 1 commit into
v.3.10.xfrom
remove_bg_as_default

Conversation

@wlorenzetti

Copy link
Copy Markdown
Member

No description provided.

@wlorenzetti wlorenzetti added this to the v3.10 milestone Jul 30, 2025
@wlorenzetti wlorenzetti self-assigned this Jul 30, 2025
@wlorenzetti wlorenzetti added the i18n Edit or add translations label Jul 30, 2025
@nstoykov

nstoykov commented Jun 17, 2026

Copy link
Copy Markdown

Hi @wlorenzetti,
I understand the reasoning — based on the diff comment, bg is being disabled in g3w-admin until the g3w-client translation is complete and up to date.
I run a GIS consulting practice in Bulgaria, and we deploy G3W-Suite for several Bulgarian municipalities. Bulgarian-language UI matters a lot for our end users — most municipal staff don't work comfortably in English.
I'd like to volunteer to take ownership of the Bulgarian translation, for both g3w-client and g3w-admin:

Review and complete the existing bg locale strings in g3w-client (src/static/locales)
Keep them in sync with new strings as the client evolves
Do the same for the g3w-admin Django .po files under /g3w-admin/locale
Submit PRs against dev (or whichever branch you prefer) and keep maintaining it going forward, not just a one-off fix

Could you point me to:

The current state/completeness of the bg locale in g3w-client (so I know what's missing)
Whether you'd prefer translations via direct PR against the JSON/po files, or if there's a Transifex/Weblate project I should join instead
Any style/terminology guidelines you use for translations (so I stay consistent with existing entries)

Happy to commit to keeping this maintained long-term rather than letting it lapse again. Let me know how you'd like to proceed.

@wlorenzetti

wlorenzetti commented Jun 17, 2026

Copy link
Copy Markdown
Member Author

Hi @nstoykov, yes the disabilitation of BG is temporary..

The current state/completeness of the bg locale in g3w-client (so I know what's missing)

I must ask to client guys :)

Whether you'd prefer translations via direct PR against the JSON/po files, or if there's a Transifex/Weblate project
I should join instead

Transifex is on roadmap.. but now I prefer PR thanks.

Any style/terminology guidelines you use for translations (so I stay consistent with existing entries)

No we don't have a style/terminology by default.

Thanks in advance.
Happy G3W-SUITE mapping ;)

@Raruto

Raruto commented Jun 17, 2026

Copy link
Copy Markdown
Member

@nstoykov Don't worry, at the time being g3w-client@v4.0 didn't include Bulgarian among the available languages ​​yet.

Ref:

image

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

Labels

i18n Edit or add translations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants