Hi all,
Recently I moved from using the version of LibreOffice supplied by my
package manager (aptitude) to the one provided on the LibreOffice
website (currently I am running 3.5.4). So far all is well, but I
noticed one difference that I'd really like to change.
I've set up Capslock to be used as the compose key on my system (Debian
GNU/Linux with KDE). That works just fine for all applications, but not
so anymore for the version of LibreOffice I've installed outside of the
package manager. There it seems the compose key is ignored completely.
If I type Stra<CAPSLOCK>sse I get the intended Straße in all apps, but
LibreOffice gives me Strae.
Can anyone advise me on how to fix this behavior? I use a lot of special
characters when writing and I write a lot for my work, so it would
really make a difference for me if I can use the compose key again in
LibreOffice. But I'd prefer to not go back to the version provided by
the package manager, because I need some recently added features that
are not in there.
Your help would be appreciated.
Grx HdV
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-users] Compose key is being ignored · J.A. de Vries
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.