[Libreoffice-ux-advise] [Bug 114899] VIEWING: smarter positioning of deleted text in track changes mode ( considering word boundaries)

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=114899

--- Comment #1 from Heiko Tietze <tietze.heiko at gmail.com> ---
Created attachment 138949
  --> https://bugs.documentfoundation.org/attachment.cgi?id=138949&action=edit
How LibO, GDocs, and MSO shows changes

Attachment shows how LibO. GDocs, and MSO handles changes (second line for LibO
shows how the actual request could be improved).

Your banana/havana is only part of the question. We should consider
addition/deletion/replacement of single/multiple letters at the
beginning/middle/end of a word. And the question is also where the changed
letter is placed - before or after the new.

My take considering readability and least changes to the text:

Beginning, single & multiple letters: just add, or insert right of the replaced
letters (He -> -H-She)
End, single & multiple letters: just add, or insert left of the replaced
letters (him -> her-im- | steps -> stepz-s- compare GDocs and LibO in the
attachment)
Middle, single letter: insert and place the new letter right of the replaced
(behind -> be-h-kind)
Middle, multiple letters: replace the full word and show the new right-hand
(queit -> -queit-quiet | quite -> -quiet-quite) (here I would go further than
MSO just to make the algorithm simpler)
In case of addition/deletion of single and multiple contiguous letters I would
just do the changes but when more than one letter is changed on different
positions the full word should be replaced (Havana -> Havan+n+a | Hawana ->
Ha-w-vana vs. Hawana -> -Hawana-Havanna 

On the other what we have works not that bad for me. We should also consider
the input that might become strange; that needs some testing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.