|
Bugzilla – Full Text Bug Listing |
| Summary: | change "Installation Settings" string to "Summary" | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Ludwig Nussel <lnussel> |
| Component: | YaST2 | Assignee: | YaST Team <yast-internal> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jreidinger, lnussel, wimer |
| Version: | Leap 42.3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| URL: | https://trello.com/c/EZgGZfG9 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | German screenshot | ||
|
Description
Ludwig Nussel
2017-02-03 10:07:03 UTC
Ken - as this change will affect also SLE, what is your view about this change? Please notice that his might have quite some impact on documentation and SDB/Wiki. Actually, the current design assumes that the titles will be longer and therefor flow over more than one line. In general it might not be bad to rethink the text in the ui but it would be better to look into this as a bigger issue with the proper process and documentation to understand the scope of the changes across the entire ui. A current screenshot (the original one got rotated away) https://openqa.opensuse.org/tests/392307#step/installation_overview/2 Well yes, it is two long words. But I don't understand the problem. Does it look plain wrong in a certain language? Can it be worked around by adding a space or a line break in the translation? Otherwise this looks like much work for dubious gain. QUESTION: are there languages in which this string is one long word? If so, changing the string to something shorter does indeed seem like a logical plan. If not, we should leave it as is. Change for the sake of change in a system which has existed for a long time and is well known by our users would decrease the usability of the product. Created attachment 722700 [details]
German screenshot
Maybe it should be translated to "Zusammenfassung der Installation". Even longer but has spaces. Ok, looks like German is a mess: ./po/control.de.po:msgid "Installation Summary" ./po/control.de.po-msgstr "Installationsüberblick" ./po/storage.de.po:msgid "Installation Summary" ./po/storage.de.po-msgstr "Installationszusammenfassung" ./po/qt-pkg.de.po:msgid "Installation Summary" ./po/qt-pkg.de.po-msgstr "Zusammenfassung" ./po/ncurses-pkg.de.po:msgid "Installation Summary" ./po/ncurses-pkg.de.po-msgstr "Installationsüberblick" storage/sv.po:msgid "Installation Summary" storage/sv.po-msgstr "Installationssammanfattning" control/af.po:msgid "Installation Summary" control/af.po-msgstr "Installasie-opsomming" control/da.po:msgid "Installation Summary" control/da.po-msgstr "Installationssammendrag" control/nb.po:msgid "Installation Summary" control/nb.po-msgstr "Installasjonssammendrag" control/nds.po:msgid "Installation Summary" control/nds.po-msgstr "Installatschoonsmodus" control/nl.po:msgid "Installation Summary" control/nl.po-msgstr "Installatieoverzicht" control/nn.po:msgid "Installation Summary" control/nn.po-msgstr "Installasjonssamandrag" What is the status of this? It's been in NEEDINFO for 3+ weeks; it is unclear to me who should supply what information. Considering that the problem does seem to exist in many languages it does seem like an improvement. We need to weigh the effort of changing this in QA, the documentation and screenshots and make the change when we are sure that everything can be changed at once. OK then; since this appears to be an issue for multiple teams and departments, this sounds more like a feature request to me so it can properly be coordinated. Anyway, we surely don't want to do this right now during the late Beta phase of SP3; this would break a lot of tests, I assume, and I don't know the impact on the doc team (do they make new screenshots anyway? No idea). Looks indeed as a good idea that would NOT need FATE at all. If it was earlier ... So, we can IMO change it in TW, but not in SLE 12 SP3 as the docu and translations are involved too. Now tracking in Trello to integrate this task in our scrum team workflow: https://trello.com/c/EZgGZfG9 Hmm, looking at it again... Installation Summary is "more correct" than just "Summary" What about fixing it for translations only? We should add a comment that translators need to use only "Summary" in case the translation is too long (and one word only). And we could actually handle this in the code :) We could have both strings and decide depending on the space and the length of strings (and available spaces). A real responsive content :D I'm not in the mood for bike shedding today. Please just do what you think is the right thing to do. Remember that simpler is usually better. The user is in the installer of an operating system - a fact they will not forget. It should be clear to them that it is the summary of the installation. The extra text will not help the user to understand anything in this UI. Guys you're making me cry :) On Monday morning!
One talks about a bike shed while we are talking about installation.
The other forgets about translations.
Obviously making something shorter is usually better, but for instance in
Czech, just "summary" tells basically nothing and the translation will be
most probably horrible, believe me, I've seen it.
If we use "Summary" as a string marked for translation, then we might need
to add a comment like this:
"Translators: Use 'Installation Summary' or similar if just 'Summary'
does not tell enough"
And now what happens if "Summary" is used at some other place but it's NOT
"Installation Summary"? Yast code contains "Summary" 7.000-times, I can't
find if it's used as a translatable string now.
The /problem/ is a bit more complex than you might think...
This is automated batch bugzilla cleanup. The openSUSE 42.3 changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE (At this moment openSUSE Leap 15.1, 15.0 and Tumbleweed) please feel free to reopen this bug against that version (!you must update the "Version" component in the bug fields, do not just reopen please), or alternatively create a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime |