Red Hat Bugzilla – Bug 865598
String "You're all set" is idiomatic and hard to translate
Last modified: 2012-12-20 00:34:33 EST
I've made a patch which I hope captures what the string was trying to say. The language is friendly, which is good, but unfortunately may not translate well.
If this violates a string freeze for Fedora 18 Anaconda, I nominate this patch for the appropriate pre-f19 branch ('master' or wherever). :-)
I think you may have forgotten the patch.
And yeah, this would need to be an F19 thing.
Created attachment 627517 [details]
Fix problematic language in partitioning popup
Oops, sorry -- patch attached now.
Hm, I don't really like "Your storage is ready!" either. What if we just get rid of the last line from that label? I don't think it contributes all that much.
I'd be OK with dropping, but perhaps a "Please proceed." or something similar would still be useful.
I definitely agree this line is a problem, and I also agree with the idea of dropping it. I think dropping it is the best plan for a couple of reasons:
- We won't have that line become an untranslated string for non-English installs for F18 final;
- The button labels make it clear you can continue as well (the mockup is here http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Prototypes/Previews/free-space.png) ... the right-most button says 'Continue'
anaconda-18.37.3-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.37.3-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-18.37.3-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
anaconda-18.37.4-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.37.4-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.