Date: prev next · Thread: first prev next last
August 2018 Archives by date, by thread · List index


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

Cor Nouws <cno@nouenoff.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cno@nouenoff.nl

--- Comment #6 from Cor Nouws <cno@nouenoff.nl> ---
(In reply to Buovjaga from comment #3)

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

It does capture any word, if you turn off Automatic Spell Checking

(In reply to Heiko Tietze from comment #4)
Issue here is that non-standard characters like # or _ are not taken into
the auto completion but stripped off. You can type tipof... and add the
hashtag later. 

It would definitely be possible to add exceptions for special characters that
should be included/start/tailing. If it's worth, is always hard to say.

My take is to keep autocompletion 

Word Completion

as it is but introduce editing capabilities 

and this would be an option that works too. But if one starts editing a list,
then one can also use AutoCorrect > Replace..

 and permanency for the list, 

Permanency cross session, or only cross document? The latter should work if
there is no tick in the fifth checkbox.

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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.