[Libreoffice-ux-advise] [Bug 118399] Word Completion should collect any string regardless of correctness according to spellchecker

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

Buovjaga <todventtu@suomi24.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needsUXEval
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org
            Summary|Word Completion doesn't     |Word Completion should
                   |capture words starting with |collect any string
                   |the pound/hash symbol (#)   |regardless of correctness
                   |                            |according to spellchecker
                 OS|Windows (All)               |All
           Severity|minor                       |enhancement

--- Comment #3 from Buovjaga <todventtu@suomi24.fi> ---
Thanks and this is absolutely the place to discuss it because reports need to
have clear steps - references to features are not enough.

The problem for me (and apparently the actual root problem here) was that I
tried with "todayilearned" and its #-version and neither was saved. Welp,
luckily I happened to try with a real Finnish word as the default document
language was Finnish and it worked!

I did a new test from scratch with English (USA) for the document language, but
"todayilearned" was still not captured. I tried with a real English word
"completion" and it was captured.

So in essence your suggestion is: capture any word, even though your language
dictionary considers it nonsense. Delegating to UX team.

Tested with
Arch Linux 64-bit
Version: 6.2.0.0.alpha0+
Build ID: bd394492c165d27c96a44495d9ca694a242acb8f
CPU threads: 8; OS: Linux 4.17; UI render: default; VCL: gtk3; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded
Built on July 11th 2018

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