Checkbox : Simplify strings available for translation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox (Legacy) |
Won't Fix
|
Medium
|
Unassigned | ||
Checkbox Provider - Base |
Won't Fix
|
Medium
|
Unassigned | ||
Ubuntu Translations |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Checbox strings are currently made in a way which required a lot of extra effort/ time from trasnlators than it could:
There are many long strings of this type:
PURPOSE:
This test will test display rotation
STEPS:
1. Open the Displays application
2. Select a new rotation value from the dropdown list
3. Click on Apply
4. Click on Restore Previous Configuration
5. Click on Apply
6. Repeat 2-5 for different rotation values
VERIFICATION:
Did the display rotation change as expected?
Consequentially translators need to translate strings PURPOSE, STEPS and VERIFICATION tens of times. Many other strings could also be reused. For example "Click on Apply" or "Click "Test"" appear very often. "Click on the bluetooth icon in menu bar" appears for almost all bluetooth tests and so on. This not only required more work from translators but also makes them less motivated as they need to translate the same strings over and over again within a short span.
If longer strings would be split up into smaller ones work load for translators could decrease required translator's work substantially (in my opinion by about 30-40%).
Changed in ubuntu-translations: | |
status: | New → Triaged |
importance: | Undecided → Medium |
summary: |
- Checkbox requires a lot of translator work + Checkbox : Simplify strings available for translation |
tags: | added: job |
Changed in checkbox-legacy: | |
status: | Triaged → Won't Fix |
Changed in plainbox-provider-checkbox: | |
status: | Triaged → Won't Fix |
Changed in ubuntu-translations: | |
status: | Triaged → Won't Fix |
Hi Andrej,
Thanks for pointing out this problem. You're more knowledgeable than I about the whole translation infrastructure and workflow, so I'd like your input on how to best tackle this problem.
Checkbox's job descriptions are included in textfiles in rfc822 format (see in /usr/share/ checkbox/ jobs for examples). Thus there are a few differences from strings included in source code. I can't, for instance, have just one PURPOSE string and reuse that easily in my job description files; at least, not without introducing an extra variable- substitution step.
So, do you know of any way to handle this with the current format we're using? could we perhaps format the description field in a way that "splits" the long description into smaller chunks?
Thanks again for your report. I'll set as importance: Medium and Incomplete for checkbox, pending your reply, but once you respond I'd be inclined to set this to either Confirmed or Triaged.