[Libreoffice-ux-advise] [Bug 78217] Autocorrect replacement table: selected text is copied in "With" field rather than "Replace" field

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=78217

--- Comment #30 from tommy27 <barta at quipo.it> ---
(In reply to comment #26)
> ...
> Behavioural functionality (only text then do this) will only lead to
> confusion, because most users will never guess why.

Let's summarize. The autocorrect replacement table may be used for 3 categories
of autocorrection:

1- real typing errors (i.e. yrllow ; yellow) comment 0

2- text snippets for formatted text + images + tables ecc. ecc. (like a table
with your name in bold italics and company logo etc. etc.) comment 13

3- text snippets for text only long phrases (i.e. asap ; as soon as possibile)
comment 8

so the problem here is: “which is the right place” we should paste a user
“selection” when opening the replacement table?

I believe that behavioural functionality would not lead to confusion at all but
will exactly do what is expected by the user in a logical way... let's see some
scenarios: 

1- user selects text but just a “single word” 
then is very likely that he selected a typing error and he wanna enter the
proper spelling, so the selection IMHO should directly go in “replace” rather
than “with”. 

Otherwise, as in 4.2.x, if the typo fills the “with” field and you have to cut
and paste into the “replace” field and then go back to “with” and type the
correct spelling.

2- user selects “formatted text + images + tables ecc. ecc.” 
is indeed very likely that he's not willing to correct a typing error but
rather enter a text snippet for formatted text etc. etc. so logical destination
is “with”

as shown (and I initially missed it), if the initial destination is “replace”
(like in the patched 4.3.x) you can't preserve formatting by moving manually to
“with” so that's why that patch has to be reverted.

3- user selects text in “a long phrase”
I see 3 different scenarios:

a- user selected a correct phrase to enter an abbreviation snippet (i.e. as
soon as possible ; asap) so that selection should go in “with”

b- however there are chances that user selected a long phrase like “as son as
possible”
in which spellchecker doesn't see errors but the content of the phrase is wrong
(“son / soon”) so in this case logical destination is “replace” and type “as
soon as possible” in the “with field”

so, bottomline is if it's technically feasible to teach LibO to guess the
correct scenario and do the right choice... 

while I suppose it can be easy to distinguish between 1 and 2, I think that it
would be probably impossible for a computer to distinguish between case 3a and
3b. 

probably the “prefill both” idea from Micheal Stahl ( comment 20 ) is the one
which is technically easier to implement.


for the moment it's better to revert patch in comment 4, than think if this
"autocorrect destination field" can be managed without breaking functionality.

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