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


On 2012-07-16 02:16, Mirosław Zalewski wrote:

I could not reproduce your issue. I am using Debian testing, amd64, KDE 4.8.4. 
I have installed LO 3.5.5 downloaded from LO page, run it and compose key 
(which is right-Ctrl here) is working fine.
If this is not architecture/LO version dependent (you did not provide 
information about it), then:

This is on a Intel 32-bits platform, using an up-to-date Debian
GNU/Linux testing with KDE 4.8.4 and LibreOffice 3.5.4 downloaded from
the website.

how did you map your compose key? In KDE system settings or through
dpkg-reconfigure keyboard-configuration command?
I have set mine through dpkg-reconfigure. I did not touch any KDE settings.

I used both KDE and dpkg-reconfigure to map the compose key to Capslock
and in *all* other applications (both GTK and QT based) that works just
fine. But somehow it doesn't in LibreOffice. It does in the version
provided by aptitude, just not in the "official" version downloaded from
the website.

Thanks for trying to help.

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


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.