https://bugs.documentfoundation.org/show_bug.cgi?id=151122
--- Comment #50 from Manu <[email protected]> --- (In reply to Eyal Rozenberg from comment #49) > Also, many features or behaviors in LO are not > perfect when first released, and feedback from users makes them improve in > later releases. Of course we need something "decent" enough to actually be > committed in the first place. I would like this to be true, but there are other examples of bugs that have been created by an improvement (real-time preview in calc for example), and when a performance problem appears, we cannot disable the improvement, and no correction is made because it is considered specific to certain documents. At least don't forget a new parameter to disable the new system, because we never know what the user will encounter in reality. > > But if we want more simple, there is the character list the user set in a > > textbox. > Assume the user has not typed in any characters; they are just about to do > so. Or they are editing a style. What would you use then? Your understanding is not what I suggest. In the new system, we need a full specifications saying which character codes are associated with each language. That's a long work to do, and it will be certainly constantly criticized by a user who want more or differently. With my suggestion, the user write himself the list of characters that represent his needs. These characters are easy to find: on the keyboard, in the special character dialogbox, in wikipedia (alphabet of the targeted language), on unicode website. If you want, in the parameters, fonts paragraph, we could see: [X] activate the new font list presentation (disabled = standard A-Z list) (Y) first group with fonts that support all these characters: __________ (Z) first group with fonts that support the select language So when X is enabled, we can select the method: either Y or Z. In the two cases Y or Z, the result will be a font list with 2 groups. For example if the textbox is ÇÑÃÕÅßIJŐĞŊŮĆŞΞѢЁЪЂ we could see: --- fonts supporting user's choice fontEUROPE fontCYR --- other fonts fontEN(only) fontGRE(only) fontEURnotCYR fontCYRnotEUROPE With choice Y, we can set many different alphabets, and with choice Z the method is user-friendly. For example: --- fonts supporting "language" fontHEB --- other fonts fontEN(only) fontGRE(only) fontCYR(only) fontOTHER(not HEB) > That suggestion _will_ actually require some dynamic recomputation > (especially if I selected a lot of text on multiple pages); and while it > might be simpler to implement and does not require familiarity with > languages - it is _quite_ complicated for the user, who will have absolutely > no idea what's going on with the partitioned list, which will keep changing > for them. What you explain, the selection of text, is what is already in function. The selected text is used for the lorem ipsum in the textbox for rendering a preview before validating the Characters dialogbox. At the present moment, only one line is displayed. As the new enhancement (list partition) will change the dialogbox, I suggested to add a few more lines (maybe 3 or 5) in order to see more in the preview, and extensibility of the dialogbox in order to see really well the shapes without the need of a microscope (see my other comment above). I hope it helps. -- You are receiving this mail because: You are the assignee for the bug.
