Fixes and changes to Lokalize, request for feedback

[fin-w at tutanota.com]

Hi all,

I'm happy to devote some time to fixing issues you have with Lokalize. I welcome your feedback and can try to implement things you would like to see changed in the program. Please do message me and I can take a look if I have the time and resources.

Right now, I'm interested to change the layout and formatting of the translation memory view. I'd like to know what you all think of this as a new layout, where in this example Cymraeg is the target language (top lines) and English is the source language:
 <https://invent.kde.org/-/project/2339/uploads/a61607f9c078fabdce00e25db9d15125/Screenshot_20240723_004807.png>

For reference, here is the old layout with the same data:

 <https://invent.kde.org/-/project/2339/uploads/298a07a103a102154541db6ec0add8ab/Screenshot_20240723_003516.png>


You can read more about the merge request here https://invent.kde.org/sdk/lokalize/-/merge_requests/133

You can see below a screenshot of crowdin.com's translation editor, which lays out translation memory data under the strings to translate in a similar fashion to what my merge request is doing: <https://invent.kde.org/-/project/2339/uploads/a61607f9c078fabdce00e25db9d15125/Screenshot_20240723_004807.png>

I'm interested to do this because I find the current translation memory cluttered and confusing, and because putting the metadata on the bottom line allows me to focus on what's most important first (source and target strings). I'd like to hear from other translators who use this tool though too to see what you think, and if you think it should be different to what I'm proposing.

Thanks,
Finley


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20240725/c389c17f/attachment.htm>