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


Den 18 april 2012 18:19 skrev Johnny Rosenberg <gurus.knugum@gmail.com>:
Den 18 april 2012 02:12 skrev Thomas Taylor <linxt@comcast.net>:
On Tue, 17 Apr 2012 10:48:22 +0100
Séamas Ó Brógáin <sob@iol.ie> wrote:

Doug:

Using the compose key, the default settings are:

   dash (em rule)      ---
   en rule:            --.







How do you do that if your system (openSuSE 12.1) only allows two (2) key
composition?

Thanks, Tom

I have had OpenSUSE some years back (I think it was 11.3 or
something), but unfortunately I didn't test this…
However, this page doesn't say anything about that the compose key
behaviour is depending on your GNU/Linux-distribution, so I thought
this was true for all of them.

Forgot to include the link to ”this page”… sorry… :D
Here it is:
http://www.hermit.org/Linux/ComposeKeys.html

Maybe it's a Gnome thing and you have the KDE version of OpenSUSE?
Well, I don't think so, but I use Gnome only, so I don't know.


Best regards

Johnny Rosenberg
ジョニー・ローゼンバーグ

-- 
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.