Writer with autokey does not work (work very badly): f.e if I type "ip" expecting to expand into "in particolare", instead I get "ip in particola".
Also with autocorrect, if I type "ip" I get "ipin particolar", not, as expected, "in particolare"
Steps to Reproduce:
2.type a abbreviation in Writer
3.appears another word that expected
f.e. "ip in particola"
f.e. "in particolare"
User Profile Reset: Yes
OpenGL enabled: Yes
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
This bug is also in appimage of LibreOffice 126.96.36.199
Bug present also in Version: 188.8.131.52
(Build ID: 1:6.0.1~rc1-0ubuntu0.17.10.1~lo1
CPU threads: 2; OS: Linux 4.13; UI render: default; VCL: gtk3;
Locale: it-IT (en_US.UTF-8); Calc: group)
Bug: abbreviation not removed
f.e. "ip" becomes "ip in particola" as already said
How do I create such an autotext? I read this, but there is no "New" entry in the Autotext dropdown: https://help.libreoffice.org/Writer/Using_AutoText
(In reply to Buovjaga from comment #3)
> How do I create such an autotext? I read this, but there is no "New" entry
> in the Autotext dropdown: https://help.libreoffice.org/Writer/Using_AutoText
I got help in Bug 115904
- Write any text, with formatting, table, ...
- Select the text
- Press Cntl+F3
- Select a category
- Enter a name (important!)
- Click on AutoText => New
I did this for ip -> in particolare
When I type ip and press F3, I get the correct result.
Arch Linux 64-bit
Build ID: b8fe96f1da2c42c04a8094ca8c57d49763b7bded
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4;
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on March 8th 2018
Btw. I could not reproduce bug 115904, so maybe you could try it.
Autokey *is not* Libreoffice autotext: it's a external program (/app), named Autokey. I use autokey-gtk.
(In reply to Duns from comment #6)
> Autokey *is not* Libreoffice autotext: it's a external program (/app), named
> Autokey. I use autokey-gtk.
Well now you tell me. So why do you think this is a problem in LibreOffice rather than something for Autokey to solve? Why not report it to https://github.com/autokey/autokey/issues ?
Yes is a LibreOffice problem because in any other program (such Thunderbird, Calligra, OnlyOffice, Kate, Firefox, Chrome) autokey works perfectly. In LO no :)
A *temporary workaround* is a) disable autokey when I open LibreOffice and b) use LibreOffice "autocorrect".
But I hope that this problem will fixed.
You did not mention that you had posted your problem to this thread: https://groups.google.com/forum/#!topic/autokey-users/LhWVgiBsF2M
Joe gave you tasks to do, so please do them as soon as possible. Based on what Joe said, your claim "Yes is a LibreOffice problem" is definitely not a fact at this point.
You can also try running LibreOffice from the command line with
This will make it use the gtk2 backend instead of gtk3.
Unfortunately this way (SAL_USE_VCLPLUGIN=gtk libreoffice) does not works...
(In reply to Duns from comment #11)
> Unfortunately this way (SAL_USE_VCLPLUGIN=gtk libreoffice) does not works...
Ok, you could try these tips from Joe:
2) See if it's a timing issue. Turn one or two of your phrases into
macros and use type_slow() from
type them one character at a time with a delay between each character.
If that fixes it, you can experiment with the minimum time and placing
of delays to make the macro as fast as possible without failures.
If you run AutoKey manually from a terminal, you can try two diagnostic
a) Run a trace to be sure AutoKey is issuing the right keypresses, etc.
See https://github.com/autokey/autokey/wiki/Problem-Reporting-Guide for
how to run a trace and for what other information we need to help solve
Thank you, but I am not a developer, it's too complicated for me.
I see you are getting helped more and more in the Autokey list thread (and no one can reproduce the problem there), so I'm closing this.
No, no help received there has solved the problem; the problem remain.
(In reply to Duns from comment #15)
> No, no help received there has solved the problem; the problem remain.
Fine, so you can come back after trying 0.93 etc. if it still doesn't work.
OK, I will see...