Gettext without headers: all translations marked fuzzy

[rix0rrr]

Describe the issue

We are using Hosted Weblate.

Because we're noticing that when we are running gettext update commands locally (using pybabel, in case that matters), there are frequent merge conflicts in the time stamps that are in the .po file headers.

So I thought I would be clever and run pybabel with --omit-header, so it doesn't emit the magic msgid "" entry that has the metadata headers attached.

It looks like in response, Weblate has marked all my translations fuzzy, completely reordered all translations in the file, and has replaced them with the original English versions. I had to do some git trickery to get back to a workable state.

This was a surprise to me. Is this expected?

I already tried

• I've read and searched the documentation.
• I've searched for similar issues in this repository.

Steps to reproduce the behavior

Have a number of .po files translated via Weblate.

Then run:

pybabel extract -F babel.cfg -o messages.pot . --no-location --sort-output --omit-header
pybabel update -i messages.pot -d translations -N  --no-wrap --omit-header

Specifically, you can see the change I made in this PR: hedyorg/hedy#4304

Expected behavior

I expected fewer conflicts. Instead I got more :).

Screenshots

No response

Exception traceback

No response

How do you run Weblate?

weblate.org service

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

[github-actions]

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.

In case your question is already answered, making a donation is the right way to say thank you!

[nijel]

It is not expected to mark existing strings as fuzzy. It would be great if you would include links to the problematic commits. I've quickly looked into hedyorg/hedy#4297, and I don't see anything problematic there. What I can see is adding of fuzzy translations matching source, what was done by the “Prefill translation with source” add-on. For example in hedyorg/hedy@c5b6485

[rix0rrr]

Here is the commit where Weblate starts marking a bunch of translations as fuzzy: hedyorg/hedy@93f65c1

Which follows right on the heels of hedyorg/hedy@27f41d8 where I remove all the headers from po files.

[nijel]

It is not changing existing translations to be fuzzy, it adds missing strings as fuzzy. This is done by add-on, which you have installed. See https://docs.weblate.org/en/latest/admin/addons.html#prefill-translation-with-source

[github-actions]

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!