GNOME Bugzilla – Bug 406520
Scripts combo box incorrectly identified as languages combo box
Last modified: 2010-05-29 02:49:56 UTC
Please describe the problem: In the detailed font settings dialog, there is a combo box that contains a list of scripts for which fonts may be configured. However, the corresponding label reads “For language:”, suggesting that it is a language list (rather than a script list). This creates inconsistencies. Steps to reproduce: 1. Launch Epiphany. 2. Choose Edit → Preferences. 3. On the “Fonts & Style” page, click the “Detailed Font Settings...” button. Actual results: The label at the topmost combo box reads “For language:”. Expected results: I would expect the label at the topmost combo box to read something to the effect of “For script:”. Does this happen every time? Yes. Other information: This mismatch creates not only an obvious logical contradiction. In some languages this may pose translation problems; e. g. in Russian, the words “script” (“письменность”) and “language” (“язык”) are of different gender, so the script names have to be unnaturally inflexed to avoid even more inconsistency.
Heh, to be honest I'd better remove that dialog. Really is there a valuable usecase where it is required? Probably it can be moved to plugin. Also I wonder if the button to edit css is really needed on that tab.
Created attachment 94837 [details] [review] Changes 'For language' to 'For script' Here's a trivial patch (untested) that changes the label 'For language:' to 'For script:'. This could be a short-term solution until the font dialog gets a redesign.
'Script' isn't really correct either, since e.g. 'Eastern European' uses latin script just like 'Western European'. Anyway, string freeze -> 2.22.
chpe, can I commit this now?
Reinout: see comment 3: 'script' isn't the best choice either. Maybe 'Script or Language' ?
How about "alphabet"?
(In reply to comment #6) > How about "alphabet"? Many of those aren’t alphabets.
Such as?
Don't be pedantic, guys. Close this as is, it's not the biggest problem ever being :)
(In reply to comment #8) > Such as? At least the Chinese script is by no means an alphabet. The case with languages such as Arabic is not quite clear to me. Maybe “For text written in” or “For text that uses”? This is clear and accurate, but I’m unsure if this is a good option for translators. (In reply to comment #9) > Don't be pedantic, guys. Close this as is, it's not the biggest problem ever > being :) I don’t see why this bug should not be allowed to live in Bugzilla until it is meaningfully resolved. It’s marked as ‘minor’ and nobody demands its immediate resolution. We strive for perfection, no? :-)
We're getting again near to string freeze for 2.22, what should we do with this?
I’d suggest just sticking to the “script” terminology. It is clearly the original purpose of this combo box (see the “Other Scripts” item), and the European entries can be explained by saying that e.g. “Eastern European script” is “one of the scripts used in Eastern Europe”. Makes some sense to me :-)
How do pango guys tell different languages writing? scripts?
We don't allow scripts preferences now.