Order of strings should match template order for Fluent

[henry-torproject]

Describe the problem

I've noticed that the order of strings in translated Fluent files for Tor Browser do not match the order in the original en-US file.

Instead, it seems that the strings are ordered by when the unit was created, or the order in which strings have been translated.

E.g. if I have the original file:

message-1 = First
message-2 = Second

and on Weblate I first translate message-2 and then translated message-1, the resulting translated file is:

message-2 = Second translated
message-1 = First translated

This makes it more difficult to compare the translated files with each other, or the original en-US file.

It also means that if we makes it harder to review bulk automated change to all translations: (such as Fluent migrations because these will arrange the strings according to the template en-US file.

Describe the solution you would like

At least for the Fluent format, it would be nice if the order of strings could match the template's order.

Describe alternatives you have considered

No response

Screenshots

No response

Additional context

No response

[nijel]

This would make sense for most of monolingual formats, but there is currently no easy way to achieve this. The translate-toolkit which handles the files knows nothing about the template file, it operates on a single file only. And it has only an API to add a unit, which appends it to the end.

[github-actions]

This issue has been added to the backlog. It is not scheduled on the Weblate roadmap, but it eventually might be implemented.

In case you need this feature soon, please consider helping or push it by funding the development.