Tracking changes to already translated strings

[raphaelarias]

Thanks for the work on this! I noticed a potential area for improvement that could enhance the workflow for managing translations.

Currently, when a string is updated but already exists in the metadata, it gets skipped during the translation process—even if the string's content has changed. To force a new translation, it requires manually removing the entry from the metadata, which can be error-prone and time-consuming.

Proposed Solution:

• Introduce a hashing mechanism to track the translated string's state.
• If the hash of the current string (e.g., its content or checksum) differs from the stored hash in the metadata, the system could automatically trigger a re-translation.

This approach could:

• Ensure translations stay up to date when strings are modified.
• Remove the need for manual metadata edits, reducing the risk of mistakes.
• Provide a more seamless experience for developers and translators.

What do you think? I'd be happy to discuss further or help brainstorm implementation ideas if this seems like a valuable addition! If you would like I can also submit a PR.

[robisim74]

Hi @raphaelarias, I like your proposal.

A PR is welcome!