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

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

What GUI (Qt, GTK, X11) did you use? On my test, I have tried pure X11 
(I didn't bother to install desktop integration packages).
You can use different GUI than default with OOO_FORCE_DESKTOP variable.

As far as I remember, GTK uses different, hardcoded in source code Xcompose 
sequences. This can be changed by GTK_IM_MODULE environment variable. I have 
set it to "xim" to ensure that GTK apps uses the same sequences as other apps.
But if that's a case, then LO from repository should also be affected, which 
you claim is not. So perhaps it won't help, but you can give it a try anyway.

Apart from these three things, I am out of ideas.

Well, it seems you are on the right track here!

I tried changing my SAL_USE_VCLPLUGIN value from gen (generic X11) to
kde and gtk and voila the compose key has magically reappeared. Great!

However, now I am faced with another problem. This made me remember why
I choose "gen" in the first place. If I use either "kde" or "gtk" some
widgets (notably comboboxes and menu spearators) in the UI become very
coarse and ugly (which I could live with if necessary) and in some cases
even unusable (which is more problematic). Anyone else noticed this?

Grx HdV

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.