when type Japanese characters they appear not at cursor place. How to solve?

[Guest]

Hi,

There is some troubles at Japanese text input. When start to type Japanese (or Chinese) characters they appear not at cursor place, it's very inconvenient for using. How could it be solved?

Some screenshots done in demo TLF site http://labs.adobe.com/technologies/textlayout/demos/

Regards,

Ann

[longlostbigelow]

Ann,

Could you provide some more information such as what OS you are using, if you are using a browser or a stand alone version of the Player, as well as the Player version you are using.  When using a Mac, FireFox v3.0.10, this problem is not reproducible.

[Guest]

Environment:

Windows XP (also tried Windows Vista, in that case japanese characters appear in the upper left corner, but still not in place of cursor)

Firefox 3.0.10 and IE 7.0.6

Adobe Flash Player 10

For typing I've used Katakana and Hiragana japanese alphabet

It looks like the problem only of TLF cause the simple text fields under the same conditions display and print japanese symbols in the right way.

When typing hiragana using Mac all the same the characters appear below the editor like this

Regards,

Ann

[longlostbigelow]

In the Mac case, the behavior you are seeing is expected, if not desired.  When you commit the characters, by hitting the return key, the characters are then entered into the main text.  This method of input is the standard or default behavior for IME (input method editors) for both Mac and Windows.  This contrasted with Inline Input, which is when the glyphs appear directly in the text prior to committing them.  TLF does not currently support inline input.  I wonder if this is not the same problem you are having on the Windows.

[natallyk]

It would be strange if this would be the desired behavior. The problem is - the position of the "input box" on the screen is changing and is not even predictable.

I am using Windows XP.

Here it is in one position

Here I clicked on the Font drop-down - so now I have the position there, and whatever I do, it stays there.

Unless I click on Data sourse drop-down - then I have it there

This input box does not return to the editor, although after hitting Enter I do get the characters at the place of the cursor.

But it makes it basically unusable for japanese and some other languages - if there are any other controls in the application, the input box moves to them if I click there, and does not return. Besides, in many cases it overlaps already inputted text, which is very inconvenient for the user.

Where is this input box supposed to be by design, I wonder? And how do I keep it there?

Another question - is the support for inline input planned and if so, when?

[brian_thomas2]

This is not a bug. Since TLF doesn't support inline text input in the current version, you have to validate what you typed by Japanese/Chinese IME. Typed characters should be validated by pressing the enter/return key. That's how 2-byte IME works.

[natallyk]

I am sorry, I don't understand how this can be by design. I mean I understand this is how IME works - but it is still supposed to be in some defined place.

What I illustrate here is - it is impossible to understand the algorithm of placement of the "input box".

If there are any other controls in the application, the input box moves to them if I click there, and does not return to the editor if I click in the editor. Besides, in many cases it overlaps already inputted text, which is very inconvenient for the user.

Could you please answer the questions below?

Where is this input box supposed to be by design? And how do I keep it there?

Another question - is the support for inline input planned and if so, when?

[Sujko]

We have plan to implement inline input in future release.  Also, we will look into the problem.

Thank you,

Sumiko

[natallyk]

Hi,

Do you have any estimate on the date the solution will be available?

This problem is a showstopper for our application to be used in Japan.

May be we could do a short Acrobat Connect session so that I coulld demonstrate how this looks like in the application?

Thank you,

Natalia

[Sujko]

Hello,

I'll post follow up info as soon as I get.

Thank you,

Sumiko

[Guest]

We plan on having inline input supported in our 1.0 release - we know what is available now is unacceptable. But unfortunately this is one of those issues where a lot of different pieces have to move into place, so I do not expect our TLF betas to have inline input working until we're relatively close to release. There are not any specific dates I can give you, but I think I can say that inline input is probably not going to be available in TLF this year.

I wish I could promise something sooner. The best I can do is say that we understand the problem, and we have many different teams working on a solution.

[natallyk]

That means the product will not be usable in Japan for at least half a year:(

Given that, could you please give me an indication when the bug with the location of the input box will be fixed in IME mode?

As I described and illustrated with the screen shots, if there are any other controls in the application, the input box moves to them if I click there, and does not return to the editor if I click in the editor. Besides, in many cases it overlaps already inputted text, which is very inconvenient for the user.

Is this bug going to be fixed in the near future? That would make it at least somewhat usable.

Another question - AIR version now does not support Japanese/Chinese input at all, not even IME. Any indication when that will be available?

[natallyk]

Hi,

I did not get any answer on my post from August 5 on this. When will the bug with the location of the IME box be fixed?

And is there any update on the inline input implementation timeline?

For now, the product is unusable for Japaneese as well as for Chineese markets.

[Guest]

We will fix these bugs as soon as we possibly can. As I said before, I can't give you a specific date. The solution we provide should fix both problems you're reporting.

[natallyk]

Hi,

I see 2 different problems here. One is that inline input is not implemented yet.

The other is, that IME input has a bug - the placement of the input box is wrong.

I would assume, the second problem can be fixed separately from the first one and much sooner, as it is just a bug.

Is it not the case? If so, it would at least make product somewhat usable for Japaneese/Chineese languages until the inline input is implemented.

[Guest]

As far as I know, we will not be addressing that bug separately.

[Sujko]

Hi,

Thank you for checking it.  I'm afraid I don't have much news I can share at this moment.  We are working on inline text input support.

We appreciate your patient.

Sujiko

[natallyk]

Hi,

Is build 523 supposed to address this problem?

Thanks,

Natalia