Hi I'm trying to find out whether OpenOffice.org1.0 for Linux is already able to replace Winword for someone (not me) who is writing mostly in Japanese, but also in German. My first impression is, that it might be usable but that there are still some problems left. I'd like to ask for similar or different experiences/opinions. First a small bug: If you activate kinput2 with Shift-Space you should be able to write in Japanese (of course started with LC_CTYPE = ja_JP and correct XMODIFIERS setting) directly, but you can't. You have to change manually to the Japanese font first. And back after you have deactivated kinput2. Japanese input with kinput2 works only over the spot. OpenOffice doesn't work well with kinput/canna (which one I don't know). Quite often they crash. One example: If I press HOME the "auxiliary control" window opens. Normally I can close it with Ctrl-g or backspace. Only backspace works correctly. If I press Ctrl-g the window closes, but kinput/canna don't work anymore. Sometimes OpenOffice crashes after about 15 seconds (enough time to safe your file). This happens with several other combinations too. I tested the German and the Japanese versions of OpenOffice on notebooks with SuSE 7.1 and 7.3 (later I will also try it on my desktop with SuSE 8.0). Thanks in advance for any comment Gerhard Schuck geschu@ma5.seikyou.ne.jp
I wrote in my previous mail:
Japanese input with kinput2 works only over the spot.
That's wrong. Actually it is on the spot, I think. But what disturbs me, is the little window right under the input zone which is always in your sight, when you are writing. It should be in the status bar. Gerhard Schuck geschu@ma5.seikyou.ne.jp
Gerhard Schuck
I wrote in my previous mail:
Japanese input with kinput2 works only over the spot.
That's wrong. Actually it is on the spot, I think. But what disturbs me, is the little window right under the input zone which is always in your sight, when you are writing. It should be in the status bar.
This seems to be a matter of taste. I happen to like the little indicator window close to the cursor. Therefore it would be best if the position of this window were configurable. Indeed there is a X-resource option to choose the position of this indicator window: Kinput2*modeLocation: bottomleft
From the man page of kinput2:
modeLocation
This resource specifies the location of status
widget in case of over-the-spot type conversion.
Unless client specifies the location explicitly,
the location of the status widget is determined by
this resource. If the value of this resource is
``topleft'', the widget is placed at the top left
of the client window. You can also specify
``topright'', ``bottomleft'' and ``bottomright''.
If the value is ``tracktext'', the widget is
placed just under the cursor position, and moves
according to the cursor. However, if the region
available for conversion is too small, status is
placed at the bottom left of the client area. If
the value is ``none'', the status widget will
never appear.
The default is ``tracktext''.
Unfortunately many applications ignore this setting.
For example this setting works for kterm, rxvt, mlterm, Qt3
applications with "over the spot" style, ...
But it is ignored by Mozilla, OpenOffice, (X)Emacs, ...
--
Mike Fabian
Gerhard Schuck
First a small bug: If you activate kinput2 with Shift-Space you should be able to write in Japanese (of course started with LC_CTYPE = ja_JP and correct XMODIFIERS setting) directly, but you can't. You have to change manually to the Japanese font first.
I don't think this is a bug. Japanese input immediately works, i.e. the indicator window pops up and you can enter Japanese, but of course it is not correctly displayed when you use a font which doesn't contain Japanese characters, then you just see boxes.
And back after you have deactivated kinput2.
You don't have to do that if the font you use for Japanese also contains all the other characters you need. Most Japanese fonts contain at least ASCII as well, i.e. you can continue to use the Japanese font for English if you want. Some fonts like Bitstream Cyberbit or MS Arial Unicode contain most of Unicode 2.0, i.e. you can continue using such fonts for German as well if you like. If you want a different font style, you have to switch fonts of course, that can't be helped. [...]
OpenOffice doesn't work well with kinput/canna (which one I don't know). Quite often they crash. One example: If I press HOME the "auxiliary control" window opens. Normally I can close it with Ctrl-g or backspace. Only backspace works correctly. If I press Ctrl-g the window closes, but kinput/canna don't work anymore. Sometimes OpenOffice crashes after about 15 seconds (enough time to safe your file). This happens with several other combinations too.
I tested the German and the Japanese versions of OpenOffice on notebooks with SuSE 7.1 and 7.3 (later I will also try it on my desktop with SuSE 8.0).
Add the following to /usr/X11R6/lib/X11/app-defaults/Kinput2
!! Don't give input focus to the windows of kinput2, they don't need input focus
!! it just causes problems if they get input focus.
!!
!! For example, if you use kinput2 with Canna and open the 'auxShell' window
!! by pressing the 'insert' key a window pops up where special symbols
!! can be selected. If this window gets focus, the selected symbol will not
!! appear in the application until the application gets focus again. This is
!! quite confusing.
!! And there are even some applications where the selected symbol will never appear,
!! not even when the application gets focus again. Gvim currently behaves
!! like that and XIM in Gvim may even become completely unusable after one of
!! the kinput2 windows got focus, making it necessary to restart Gvim to be able
!! to use XIM again.
!!
!! I found no reason why one of kinput2's windows should need input focus.
!!
*SeparateConversion.input: false
*selectionShell.input: false
*auxShell.input: false
and restart kinput2 (restart X11 if in doubt). This solves the problem
you describe.
These app-default settings are already included in SuSE Linux 8.0, but
not yet in 7.3 and 7.1.
--
Mike Fabian
On Tue, 28 May 2002 12:32:09 +0200
Mike Fabian
Gerhard Schuck
writes: [...]
First a small bug: If you activate kinput2 with Shift-Space you should be able to write in Japanese (of course started with LC_CTYPE = ja_JP and correct XMODIFIERS setting) directly, but you can't. You have to change manually to the Japanese font first.
I don't think this is a bug. Japanese input immediately works, i.e. the indicator window pops up and you can enter Japanese, but of course it is not correctly displayed when you use a font which doesn't contain Japanese characters, then you just see boxes.
I'm not shure but I still think it should change to the default asian language font (and back) automatically like in Winword. ...
OpenOffice doesn't work well with kinput/canna (which one I don't know). Quite often they crash. One example: If I press HOME the "auxiliary control" window opens. Normally I can close it with Ctrl-g or backspace. Only backspace works correctly. If I press Ctrl-g the window closes, but kinput/canna don't work anymore. Sometimes OpenOffice crashes after about 15 seconds (enough time to safe your file). This happens with several other combinations too.
I tested the German and the Japanese versions of OpenOffice on notebooks with SuSE 7.1 and 7.3 (later I will also try it on my desktop with SuSE 8.0).
Add the following to /usr/X11R6/lib/X11/app-defaults/Kinput2
...
*SeparateConversion.input: false *selectionShell.input: false *auxShell.input: false
and restart kinput2 (restart X11 if in doubt). This solves the problem you describe.
These app-default settings are already included in SuSE Linux 8.0, but not yet in 7.3 and 7.1.
Problem solved! Thanks Gerhard Schuck geschu@ma5.seikyou.ne.jp
participants (2)
-
Gerhard Schuck
-
Mike Fabian