Re: unusual characters in OOo

"hermanmeester" <[email protected]> :

>    So far I installed m17n-db, libotf, and wordcut, but for m17n-lib (which is needed by scim-m17n) my system (in the root console) says it needs:
>
> libanthy.so.0 and
> libanthydic.so.0
>
> I don't know how old that is, but is it equivalent to
>
> ftp://ftp.suse.com/pub/projects/m17n/9.1/i586/anthy-6024-1.1.i586 and/or
> ftp://ftp.suse.com/pub/projects/m17n/9.1/i586/anthy-devel-6024-1.1.i586 ?
>
> ?

Yes, you can use these anthy packages.

Actually "anthy" is a Japanese input engine, you may not need that,
but m17n-lib depends on it.

I could avoid that dependency by splitting the libraries which need
"anthy" out of the main "m17n-lib" package into a sub-package
"m17n-lib-anthy". Then one could install it only when one wants to use
the Japanese M17N-anthy input method.

But I'm not sure whether this is worth the effort. Having too many
sub-packages also increases the confusion.

>    I see that "RAW CODE" input method in the little menu (at
>    "other"); so do you mean that if you insert the code and enter,
>    the character you want will show up?

Yes.

>   Just another thing:
>
>    So basically your idea is, why not try putting everything in
>    SCIM, if one is already using that? It does sound very
>    attractive, because SCIM works really fine.

Yes, because than you can use the same methods to input *everywhere*,
you don't have to learn special input methods for OpenOffice, it's the
same as everywhere else then.

> Do you think Arabic and Hebrew can also be put in the SCIM-panel?
> (My panel also mentions Russian, and even Amharic!)

As James Su already wrote, Hebrew and Arabic input methods are already
supported by SCIM if you have scim-m17n etc... installed.

> Problem could be that Hebrew and Arabic are written from right to
> left, of course. Could this mess things up in SCIM?

No.

> I'm now typing Hebrew by pasting
>
> setxkbmap -option grp:switch,grp:shift_toggle,grp_led:scroll us,il
>
> in the shell after every reboot.

Pasting that into the shell each time sounds a bit tedious.
Why not add that to your ~/.xinitrc if you want to use that always?

If you do not have a ~/.xinitrc yet, you can copy the sample from
/etc/skel to your home directory:

    cp /etc/skel/.xinitrc.template ~/.xinitrc

and then edit it. Look for

    #
    # Add your own lines here...
    #

and insert your "setxkbmap" line there.

Of course you can also use the Hebrew keyboard in KDE, you can easily
switch between different keyboard layouts in KDE as well.

> Then, double shift gives Hebrew. It
> "overrides" SCIM (double shift turns the little scroll-lock light
> on; then you cannot use SCIM).
>
> I don't mind doing that every time, and I don't use Arabic much (for
> which I didn't have an imput method yet) so it's not really a
> priority; but would you know if ftp://ftp.suse ~ m17n/9.1/i586/ has
> any ready-to-install hebrew and arabic scim packages?

Yes, as written above, it's in scim-m17n.

> Or maybe I have to ask, where can you see easily what all these
> packages are about?

Usually you can get some information what the package does
by

    rpm -qpi package*.rpm

But the description of the scim-m17n package doesn't say much,
currently it just contains only:

    "M17N Input Method Engine for SCIM"

I should make that a bit more verbose.

> And if I add all sorts of SCIM-packages, do I have to modify the
> ~/.xim file at any time?

No.

If you install more scim packages, more input methods will appear in
the scim panel, that's all.

-- 
Mike FABIAN   <[email protected]>   http://www.suse.de/~mfabian



-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]