Implement Bulk Translation Interface for Localization Keys (Considering User Feedback)

[hesspavel]

Hi everyone,

We're reaching out regarding feedback received through a LinkedIn comment (by Liam Goldfinch) about the translation workflow based on the current screenshot interface.

The feedback highlights that currently, translating strings seems to require going into each translation independently and then tagging them with the localization key. This can be time-consuming for large batches of strings.

Considering this valuable feedback, we'd like to gauge user interest in a bulk translation interface.

Similar Interface to KX13:

This interface would allow users to translate multiple strings at once, with the localization key automatically implied by the parent type. This would significantly streamline the translation process, especially for projects with a large volume of strings.

Benefits:

• Increased Efficiency: Translating multiple strings simultaneously saves time.
• Improved Workflow: Automating localization key tagging reduces manual steps.
• Consistency: Bulk translation helps maintain consistency across translations.

Open Discussion:

We're open to discussing the feasibility and implementation details of a bulk translation interface. Please share your thoughts and experiences with the current translation workflow.

Is a bulk translation interface something you'd find valuable?

Call to Action:

Your feedback is important to us. Please leave a comment below to share your thoughts and experiences.

Additionally:

If you have any specific suggestions for the bulk translation interface, feel free to share them as well. You can mention the specific screenshots that led to the initial feedback.

[hesspavel]

We have implemented bulk editing in #12 and #13.

[liamgold]

Great to see this be implemented, thanks!