https://bugs.documentfoundation.org/show_bug.cgi?id=167015
--- Comment #9 from V Stuart Foote <[email protected]> --- (In reply to Dave Gilbert from comment #8) > No, suffers from the same original problem! > > I don't know Uno too know; but IMHO it makes sense to have simple commands > (i.e. toggle or set style) that can be composed over clever ones (i.e. > toggle and maybe change what you're editing) > OK, you are correct. I Followed your steps more carefully ;-) It would be helpful while modifying if--a text insertion with a change in DF/CS--would not affect DF/CS of adjacent words or their whitespace bounds. Just the current "word" text span being entered and not affect anything past its bounds to exclude its bounding whitespace. Seems that would match the MS formatting mentioned? The trouble occurs both with DF or CS being applied to *Modify* an existing text span. E.g. typing Alpha Charlie and reposition text cursor and insert Bravo with a DF/CS change. The word bounds (Spaces here) receive the DF or CS when it is toggled. Different to handling while *Typing* the initial text spans which allow the DF/CS toggles between any characters of the span. Likewise if making a selection, DF/CS is toggled up to the word bounds (double click) or sentence bounds (triple click) or paragraph extent (quad click). Where the DF/CS change occurs up to the selection bounds (but DF/CS then applies to the white space since they are no longer the breaks). IIUC the logic is buried in the editshell(s) and we use ICU libs to define the break iterators. But the T/M distinction is used extensively, e.g. look at how the AutoCorrect Options are configured. -- You are receiving this mail because: You are the assignee for the bug.
