Created attachment 186487 [details] My autocorrect settings - not the double-quote area A few days ago, it somehow happened that my autocorrect got configured to replace simple double-quotes with an x character. I failed to notice this because the buttons don't seem to indicate that fact, and the text beside them looks a bit ambiguous, see screenshot. Anyway, now I was typing away and my double-quotes were all becoming x's! I finally figured it out, but it was not easy to pull myself out of this hole.
Sure it is, reset your profile ;-)
The big button labelled "Default" is not comforting you?
(In reply to Heiko Tietze from comment #2) > The big button labelled "Default" is not comforting you? No, because it seems like the current choice is double-quotes, not 'x's.
We could replace the current button label ' and " by the text "Start/End quote".
(In reply to Heiko Tietze from comment #4) > We could replace the current button label ' and " by the text "Start/End > quote". That would be a significant improvement. I would also consider differentiating between the chosen character and its Unicode hexadecimal value, using one or more of: * putting it in a (non-editable?) tiny text box * more space between them * different font
Code pointer: Remove the two GtkLabels and change the caption of the GtkButtons in cui/uiconfig/ui/applylocalizedpage.ui
The glyph on the button comes from the localization, but the replacement is the os/DE UI font or by fallback. So more spacing can be added to simply separate the button from the assigned Unicode glyph and its UNICODE. It could also be bolded when assigned and not the 'Default' label. And finally when set other than 'Default' the *color* of the resulting glyph and code value could be changed per SC/AC to a highlighted/selected value.
(In reply to V Stuart Foote from comment #7) > The glyph on the button comes from the localization, but the replacement is > the os/DE UI font or by fallback. Yes, I gathered as much. The thing is, the user is likely to assume that the glyph on the button is the currently-chosen opening quote or double-quote. > So more spacing can be added to simply separate the button from the assigned > Unicode glyph and its UNICODE. I meant spacing from the Unicode hex value; spacing from what's currently the button is not (?) important, since it's obvious that the button and text outside the button are two separate things.
(In reply to Eyal Rozenberg from comment #8) > (In reply to V Stuart Foote from comment #7) > > The glyph on the button comes from the localization, but the replacement is > > the os/DE UI font or by fallback. > > Yes, I gathered as much. The thing is, the user is likely to assume that the > glyph on the button is the currently-chosen opening quote or double-quote. > Don't see any obvious way to avoid that--it follows the locale and is decoration applied to the button. > > So more spacing can be added to simply separate the button from the assigned > > Unicode glyph and its UNICODE. > > I meant spacing from the Unicode hex value; spacing from what's currently > the button is not (?) important, since it's obvious that the button and text > outside the button are two separate things. Possible I think, IIUC the text is a simple table lookup of the Unicode glyph assigned, and its Unicode name (not-localizable I'll add now). But should be able to isolate the name from the glyph and manipulate the two strings.