Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

Chinese words are not suggested properly when using Zhuyin keyboard in iOS #9918

Open
AnandRaj32 opened this issue Mar 10, 2020 · 5 comments

Comments

@AnandRaj32
Copy link

AnandRaj32 commented Mar 10, 2020

Description

Unable to input the Chinese words to the UITextField. A Chinese word can be represented by one to four symbols in Zhuyin.

For example:ㄊㄞˊ => 台

But when I try to type in, I unable to get a word in the suggestions in iOS.

In my scenario, I have handled the UITextField typed text on my side. So I have return false in ShouldCharactersChange event. If I have returned true in ShouldCharactersChange event, the keyboard suggested properly.

Steps to Reproduce

  1. In iOS settings, go to "General -> Keyboards -> Add New Keyboard...". Select "Chinese (Traditional) -> Zhuyin".
  2. Type ㄊㄞ and no words will be suggested.

Expected Behavior

The Chinese words should be suggested based on the symbols.

Actual Behavior

No words suggested.

Basic Information

  • Version with issue: 4.4.991640
  • Platform Target Frameworks: Xamarin.Forms.iOS
    • iOS: 13.1
  • Affected Devices: All devices

Screenshots

KeyboardIssue

Reproduction Link

Custom_Sample

Video

@jfversluis
Copy link
Member

Hey @AnandRaj32! Thanks for this! I see what is happening, but I found that whenever I unhook your event handler Handle_ShouldChangeCharacters the suggestions work just fine. So it looks like something is happening in your code in the event handler that triggers this? Is that something you are seeing as well?

@jfversluis jfversluis added the s/needs-info ❓ A question has been asked that requires an answer before work can continue on this issue. label Mar 19, 2020
@jfversluis jfversluis moved this from New to Needs Info in Triage Mar 19, 2020
@AnandRaj32
Copy link
Author

@jfversluis Thanks for the update!
I have already told that If we return true in ShouldCharacterChanged event the keyboard suggested properly. If I have returned false only the keyboard not shown properly.

We have handled the text in our side, so only we returned false in ShouldCharacter changed event. Please let me know if you need any other details.

@PureWeen PureWeen moved this from Needs Info to New in Triage Apr 3, 2020
@kingces95 kingces95 removed the s/needs-info ❓ A question has been asked that requires an answer before work can continue on this issue. label Apr 4, 2020
@kingces95 kingces95 moved this from New to Ready For Work in Triage Apr 4, 2020
@samhouts samhouts moved this from Ready For Work to Needs Estimate in Triage Apr 10, 2020
@samhouts samhouts added this to Backlog in Accessibility Apr 10, 2020
@samhouts samhouts added a/l10n and removed s/unverified New report that has yet to be verified a/a11y 🔍 labels Jun 10, 2020
@samhouts samhouts removed this from Backlog in Accessibility Jun 10, 2020
@samhouts samhouts added this to the 5.0.0 milestone Aug 13, 2020
@samhouts samhouts added this to To do in vNext+1 (5.0.0) Aug 14, 2020
@samhouts samhouts removed this from the 5.0.0 milestone Nov 2, 2020
@jasonyslai
Copy link

Hi, any updates?

@jasonyslai
Copy link

hi @jfversluis , will it have a schedule to solve this issue or on MAUI?

@jfversluis
Copy link
Member

Hey @jasonyslai! I've put it on our todo list to give this another look. If you have any additional info that would be very much appreciated :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Triage
  
Needs Estimate
Development

No branches or pull requests

5 participants