https://bugs.documentfoundation.org/show_bug.cgi?id=155274
Eyal Rozenberg <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected], | |sahil.gautam.extern@allotro | |pia.de --- Comment #12 from Eyal Rozenberg <[email protected]> --- (In reply to Heiko Tietze from comment #11) > We discussed the topic in the design meeting. I don't think you did. The minutes indicate you discussed bug 159227. My concrete suggestions here were not discussed, nor were the implications on most-recently-added special chars. > The use case is valid, actually both, and sometimes you want to remember a > glyph for a certain font, for example when picking special symbols, and > sometimes you want to insert glyphs that are available in most fonts and > direct formatting is not needed. It's stronger than that. Usually (although certainly not always) - it is important for there _not_ to be DF. It's not just unneeded, it's detrimental. That's why this bug suggests that both use cases be supported, but the default be no-DF. > Some ideas come in mind: My suggestions were apparently not discussed, unfortunately. > a) have a global option, That doesn't agree with the legitimacy/viability of both use-cases. Unless you mean a global option for whether the default is with-DF or without-DF? Please elaborate. > b) do some smart comparison and use the current font if the glyph code > pointer and the name match the stored item No no no, this would offer almost no improvement over the current state of affairs, because I would still get DF I did not ask for nor expect. As Heiko often reminds me, being overly Smart is usually a bad thing. > (and perhaps showing an infobar > if the stored glyph is not available for the current font), An infobar is too animated and distracting, especially on a dialog rather than the document window. Also, the "current font (face)" in the context of the dialog is not the font face where the cursor is at (not to mention that that's actually at least 3 font faces: Western, RTL-CTL, CJK). Rather, the current font (face) is the one that's selected in the drop-down in the dialog. The user sees that and is can't be assumed to also keep in mind the three fonts (or more than three, in the future) at the cursor. Considering that fact, the visual indication we might want to consider is making the glyphs available in the current font face (or set-of-font-faces) be black/full-intensity, and make the missing glyphs appear gray and/or have a dotted background etc. I'm not so sure about this idea though. It's a bit too complex, and I think my suggestions below make things clearer. > c) introduce another command that allows the user to either store with the > font "Add to favorites with font" or to remember just the unicode pointer > per "Add to favorites" (or with different labels). Reminding you of my suggestions a-minus-2) A checkbox for whether to insert with a DF'ed choice of font or not; when unselected, the font selection dialog is grayed-out. a minus 1) The default chosen entry in the font selection drop-down is a non-font, e.g. "(current font)" or "fonts at cursor" or "(no font specified)". This will also let us allow for actually having a set of current fonts. See also https://bugs.documentfoundation.org/show_bug.cgi?id=151215#c19 about how the current font face may involve lots of fonts. -- You are receiving this mail because: You are the assignee for the bug.
