9.26 and uim?

Hi,

I just started using uim anthy to type japanese.  It works nicely both in gtk 
and Qt apps, except Opera (and OOo).  I can use it in the URL field, but it 
keeps turning it off after every character, apparently because it pops up the 
(in this case not) "useful" menu of probable completions (usually just

prepending a "g " for google).

But in both simple and multiline text areas it is completely ignored.  Do I 
need anything else, like uim-xim, (which is flaky -- hangs or crashes and 
freezez emacs -- and/or I haven't understood how to use it)?  Or is this a bug?

coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer

-- 
lerne / learn / apprends / lär dig / ucz się    Esperanto:

Daniel Pfeiffer <occitan@esperanto.org> writes:

> Hi,
>
> I just started using uim anthy to type japanese.  It works nicely both
> in gtk and Qt apps, except Opera (and OOo).  I can use it in the URL
> field, but it keeps turning it off after every character, apparently
> because it pops up the (in this case not) "useful" menu of
probable
> completions (usually just prepending a "g " for google).

Yes, that is annoying.  Luckily, there's not all that much use for
"international" characters in urls yet...

>
> But in both simple and multiline text areas it is completely ignored.
> Do I need anything else, like uim-xim, (which is flaky -- hangs or
> crashes and freezez emacs -- and/or I haven't understood how to use
> it)?  Or is this a bug?

Unless someone has made big changes to the code since I wrote it a few
years back, we're pretty much just depending on Qt's input method
events.  So I would expect that if it works in other qt apps, it
should work in opera as well.  Unless Qt is doing something special in
their text widgets to support uim, which they don't do for other
widgets.

It's probably worth a bug report either way.

Hi Eirik,

la 03.04.2008 09:39 Eirik Byrkjeflot Anonsen skribis:
> Daniel Pfeiffer <occitan@esperanto.org> writes:

>> I just started using uim anthy to type japanese.  It works nicely both
>> in gtk and Qt apps, except Opera (and OOo).  I can use it in the URL
>> field, but it keeps turning it off after every character, apparently
>> because it pops up the (in this case not) "useful" menu of
probable
>> completions (usually just prepending a "g " for google).
> 
> Yes, that is annoying.  Luckily, there's not all that much use for
> "international" characters in urls yet...

Just used that field for testing.  But do follow any 日本語 link in Wikipedia

if you want to see international URLs.  It's never been a problem in Opera.

>> But in both simple and multiline text areas it is completely ignored.
>> Do I need anything else, like uim-xim, (which is flaky -- hangs or
>> crashes and freezez emacs -- and/or I haven't understood how to use
>> it)?  Or is this a bug?
> 
> Unless someone has made big changes to the code since I wrote it a few
> years back, we're pretty much just depending on Qt's input method
> events.  So I would expect that if it works in other qt apps, it
> should work in opera as well.  Unless Qt is doing something special in
> their text widgets to support uim, which they don't do for other
> widgets.
> 
> It's probably worth a bug report either way.

I just wanted to write one, and tried it on the bug report form -- it worked 
:-)  And it's even stopped turning itself off in the URL field :-)  Apparently 
Opera is a little shy and took some getting used to uim...  Btw. just updated 
to 9.27 and it still works.  有難う！

coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer

-- 
lerne / learn / apprends / lär dig / ucz się    Esperanto:

Daniel Pfeiffer <occitan@esperanto.org> writes:

> Hi Eirik,
>
> la 03.04.2008 09:39 Eirik Byrkjeflot Anonsen skribis:
>> Daniel Pfeiffer <occitan@esperanto.org> writes:
>
>>> I just started using uim anthy to type japanese.  It works nicely
both
>>> in gtk and Qt apps, except Opera (and OOo).  I can use it in the
URL
>>> field, but it keeps turning it off after every character,
apparently
>>> because it pops up the (in this case not) "useful" menu
of probable
>>> completions (usually just prepending a "g " for google).
>>
>> Yes, that is annoying.  Luckily, there's not all that much use for
>> "international" characters in urls yet...
>
> Just used that field for testing.  But do follow any ���{�� link in
> Wikipedia if you want to see international URLs.  It's never been a
> problem in Opera.

As long as the server and opera agrees on the encoding...  Of course,
these days it should always be utf-8, but it used to be somewhat
arbitrary...


>
>>> But in both simple and multiline text areas it is completely
ignored.
>>> Do I need anything else, like uim-xim, (which is flaky -- hangs or
>>> crashes and freezez emacs -- and/or I haven't understood how to
use
>>> it)?  Or is this a bug?
>>
>> Unless someone has made big changes to the code since I wrote it a few
>> years back, we're pretty much just depending on Qt's input method
>> events.  So I would expect that if it works in other qt apps, it
>> should work in opera as well.  Unless Qt is doing something special in
>> their text widgets to support uim, which they don't do for other
>> widgets.
>>
>> It's probably worth a bug report either way.
>
> I just wanted to write one, and tried it on the bug report form -- it
> worked :-)  And it's even stopped turning itself off in the URL field
> :-)  Apparently Opera is a little shy and took some getting used to
> uim...  Btw. just updated to 9.27 and it still works.  �L��I

�ǂ��������܂����B

But that is annoying (to us programmers).  Programs aren't supposed to
just suddenly start working for no good reason :)

On Fri, 04 Apr 2008 17:14:04 +0900, Eirik Byrkjeflot Anonsen  
<eirik@opera.com> wrote:

Ｊｕｓｔ a side note.

> Daniel Pfeiffer <occitan@esperanto.org> writes:
>
>> Hi Eirik,
>>
>> la 03.04.2008 09:39 Eirik Byrkjeflot Anonsen skribis:
>>> Daniel Pfeiffer <occitan@esperanto.org> writes:
>>
>>>> I just started using uim anthy to type japanese.  It works
nicely both
>>>> in gtk and Qt apps, except Opera (and OOo).  I can use it in
the URL
>>>> field, but it keeps turning it off after every character,
apparently
>>>> because it pops up the (in this case not) "useful"
menu of probable
>>>> completions (usually just prepending a "g " for
google).
>>>
>>> Yes, that is annoying.  Luckily, there's not all that much use for
>>> "international" characters in urls yet...
>>
>> Just used that field for testing.  But do follow any 日本語 link in
>> Wikipedia if you want to see international URLs.  It's never been a
>> problem in Opera.
>
> As long as the server and opera agrees on the encoding...  Of course,
> these days it should always be utf-8, but it used to be somewhat
> arbitrary...
>
>
>>
>>>> But in both simple and multiline text areas it is completely
ignored.
>>>> Do I need anything else, like uim-xim, (which is flaky -- hangs
or
>>>> crashes and freezez emacs -- and/or I haven't understood how to
use
>>>> it)?  Or is this a bug?
>>>
>>> Unless someone has made big changes to the code since I wrote it a
few
>>> years back, we're pretty much just depending on Qt's input method
>>> events.  So I would expect that if it works in other qt apps, it
>>> should work in opera as well.  Unless Qt is doing something special
in
>>> their text widgets to support uim, which they don't do for other
>>> widgets.
>>>
>>> It's probably worth a bug report either way.
>>
>> I just wanted to write one, and tried it on the bug report form -- it
>> worked :-)  And it's even stopped turning itself off in the URL field
>> :-)  Apparently Opera is a little shy and took some getting used to
>> uim...  Btw. just updated to 9.27 and it still works.  有難う！
>
> どういたしました。
>
> But that is annoying (to us programmers).  Programs aren't supposed to
> just suddenly start working for no good reason :)
>
> eirik

ja.wikipedia.org always uses UTF-8 even now.
On my Linux(Fedora) box, I use scim+anthy and Opera, as well as OOo with  
no problem.
I don't try uim for a long, so I can't help you much, but now your Opera  
seems to be working properly now :)

--