Translators: What could improve your QoL when translating Cockpit? What's missing?

[Venefilyn]

Hi everyone!

I've been improving our translation workflow within Cockpit to make it easier for developers to see changes, but while doing so we have also been discussing a bit about improving translation context and information for translators. To see what is most valuable to translators before committing to anything, we'd love to hear from you!

Some questions you could answer

• Have you seen something in other projects that were helpful or generally increased your confidence in your translation?
• Has the context for individual strings in Weblate been enough to understand the usage of the string?
• How valuable are screenshots to seeing context? (Some strings got a screenshots added manually by myself, but I also have an RFE to add our pixel test images to Weblate automatically, would that be helpful?)
• Has there been some strings you couldn't translate accurately due to surrounding context changing the string?

If you got more general things to mention or things that are good, do highlight that as well! 🙏

[yurchor]

Hi,

• Remmina has different categories for strings.
• Sure
• Definitely, yes. Everything is valuable to understand the context
• Yes. Alphabetical sorting is not my friend. ;)

Best regards,
Ukrainian translator

[Venefilyn]

Thanks for responding!

Remmina has different categories for strings.
Ah so stuff like label: Button you mean?

https://hosted.weblate.org/translate/remmina/-/en_US/?q=label:%22Button%22

Yes. Alphabetical sorting is not my friend. ;)

What do you mean by alphabetical sorting?

[yurchor]

• Yes.

• Some projects avoid grouping messages by parts of the interface and just sort them alphabetically.

[ema-pe]

Hi, I've recently joined as an Italian translator so I'm new, but:

• No, nothing came to my mind.
• Almost everything is fine. In some cases (especially with arguments like $0), it is not completely clear what the argument refers to, so a comment or some additional context could help. I solved this by manually checking the source string in the code through the "Details" section.
• I haven't translated any string with an attached screenshot, but I'm sure it would help!
• No, I don't think so. The only thing I noticed is that for some extremely technical words/strings, a bit of context could be helpful (as example when referring to a specific filesystem).

[Venefilyn]

Hi, I've recently joined as an Italian translator so I'm new, but:

Thanks for your work! Which is more valuable as you get to see things as a first-time contributor! :D

Almost everything is fine. In some cases (especially with arguments like $0), it is not completely clear what the argument refers to, so a comment or some additional context could help. I solved this by manually checking the source string in the code through the "Details" section.

Ofc! So more context around certain translations with arguments would make it easier to handle. We might be able to do /translation/source string descriptions similar to how Remmina has it here if that helps?

https://hosted.weblate.org/translate/remmina/remmina/en_US/?sort_by=-priority%2Cposition&checksum=49a9b421397bf7a2

No, I don't think so. The only thing I noticed is that for some extremely technical words/strings, a bit of context could be helpful (as example when referring to a specific filesystem).

Would that be stuff surrounding btrfs etc? Do you have any specific strings I can look at?

[ema-pe]

Hi, I've recently joined as an Italian translator so I'm new, but:

Thanks for your work! Which is more valuable as you get to see things as a first-time contributor! :D

Almost everything is fine. In some cases (especially with arguments like $0), it is not completely clear what the argument refers to, so a comment or some additional context could help. I solved this by manually checking the source string in the code through the "Details" section.

Ofc! So more context around certain translations with arguments would make it easier to handle. We might be able to do /translation/source string descriptions similar to how Remmina has it here if that helps?

https://hosted.weblate.org/translate/remmina/remmina/en_US/?sort_by=-priority%2Cposition&checksum=49a9b421397bf7a2

Yes, something like this could definitely be helpful: https://hosted.weblate.org/translate/remmina/remmina/en_US/?checksum=b886c04ae5c9c834

No, I don't think so. The only thing I noticed is that for some extremely technical words/strings, a bit of context could be helpful (as example when referring to a specific filesystem).

Would that be stuff surrounding btrfs etc? Do you have any specific strings I can look at?

See this string as an example: the only possible translation is to copy the source string, and it should not be localized at all. Or look at this one: I understood that it must surely refer to a technical concept and not literally a pizza, but maybe some context or a message from the developers could help.