pt-BR translation completed for Zammad UI — a few items need reviewer input

Lobby
1

Hi @mgruner and everyone,

I’m Igor (@igoraraujocosta on this Weblate instance, GitHub and Crowdin).
I run Zammad in production for my field service team and maintain the
pt-BR translation of InvenTree at 100% on Crowdin.

I recently completed and standardized the Brazilian Portuguese translation
across the whole Zammad project: stable, development, and both Hosted
Extensions components are now at 100% (up from ~83% on stable). I also
standardized terminology that was inconsistent in the existing corpus
(e.g. “ticket” appeared as ticket/tíquete/chamado) and fixed a few real
defects along the way — including 10 corrupted placeholders and one string
with an inverted meaning (“Not Assigned” was translated as “Assigned”).

Two things I couldn’t finish without help:

  1. 45 approved strings in stable (+3 in development) still carry the
    old terminology. Weblate correctly protects approved strings from
    uploads, so these are stuck inconsistent with the rest. I have the
    full list (current vs. proposed) ready to share.

  2. Glossary: I submitted 8 corrections as suggestions (my account
    can only suggest, not edit glossary terms directly) — still pending
    review.

I submitted a request through the contact form a while back but haven’t
heard back yet, so I wanted to also try here. Could someone either apply
the pending changes, or point me to how I could get reviewer rights for
pt-BR? I’d like to keep maintaining the language — next up is reviewing
the ~4,600 unreviewed strings and then the documentation project.

Happy to share files or answer any questions here or by email.

Thanks for maintaining such a great project and translation infrastructure!

2

Next time, please do not force notifications on others by mentioning them directly, please.

1 Like
3

Sorry about that. I’ll keep that in mind for next time.
Thanks for the advice!

1 Like
4

@igoraraujocosta thank you so much for reaching out, and for your contributions so far. I just granted you reviewer permission, which allows you to edit the glossary, and also mark strings as reviewed, freezing them for regular translators.
Again, thanks a lot for your help. Please feel free to reach out anytime if we can help you with something.

1 Like
5

Hi Martin,

Thank you so much for granting me reviewer permission — it’s already made
a real difference. I’ve been using it to properly review and standardize
the whole pt-BR content, not just approve what was already there.

Status update:

  • Hosted Extensions (stable + development): 100% translated and approved.
  • Zammad stable: 100% translated, and I’m working through a full review
    of the ~4,600 previously-unreviewed strings — currently past 1,500
    approved and climbing steadily. This isn’t just rubber-stamping: I’ve
    found and fixed a significant number of real errors along the way —
    mistranslations, leftover English fragments, broken grammar, and quite
    a few internal inconsistencies (the same term translated 3 different
    ways in different places). Portuguese turned out to have accumulated
    a lot of drift over time from multiple contributors without a shared
    standard, so this cleanup was overdue.
  • Zammad development: same approach starting now that it’s unlocked again.
  • Glossary: fully corrected and standardized.
  • User documentation (latest + pre-release): 100% translated and approved.
  • Admin documentation: intentionally saved for last, since it’s by far
    the largest piece (~5,400 strings) — I’ll get to it once stable/dev
    are fully reviewed.

I noticed there’s an “Addons (Internal)” project on Weblate with German at 85% but no Portuguese (Brazil) language enabled yet. Could you add pt-BR there so I can start translating it too?

Thanks again for your trust and support — happy to keep going as long
as it’s useful.

6

Thanks a lot for the update @igoraraujocosta. Awesome! We’ll check the translated docs and take them online.

Addons (Internal) is not for public and should not be visible any more.

1 Like
7

Thanks Martin.
I’m close to finishing the admin-doc translation work. I’ve noticed a recurring issue: whenever I try to download a translation file from Weblate, the corresponding component locks up right after (“Could not merge the repository” / merge conflict). This happened with zammad pre-release, more recently with admin documentation, and just now with “New Documentation at next.zammad.org” as well. It seems tied to an automatic repo sync hitting a conflict, not something I’m doing on my end, but wanted to flag the pattern in case it needs a manual git rebase/push fix on the backend.

Once the merge issue is resolved, I’ll be starting work on “New Documentation”. I will keep you posted on progress there too.

8

Hi @mgruner
Quick update — the recurring lock issue happened again, this time right after downloading the New Documentation (zammad-org) .po file for review. Same pattern as before: download → “Could not merge the repository” conflict shortly after. Wanted to keep you posted since it’s now happened three times across different components (zammad pre-release, admin documentation, and now new documentation).

9

100% done!

ll keep this under continuous review: whenever the docs get updated or new content is added, I’ll go through the corresponding translation to keep it error-free and in sync with the English source.
Let me know if anything comes up.

Thanks again!

1 Like
10

Thanks for the hint about the error. We don’t have a clue yet, and will first try updating Weblate.

And thank you so much for your contributions!