In the JSON file that I read into Weblate, I have a key that is not needed for translation but contains context to where this translation can be used. It’s not ideal, but it’s how it is now.

We have web application, which does use gettext (po and pot files) for translations. We have custom script which searches our codebase (java) for strings marked for translations and generates pot (and also po) files. We have a few separate branches, which does live longer (different customers) and occasionally they get merged into main branch. We have imported branches into weblate and we are doing translations on main branch, which propagate translated strings also to other branches (weblate components).