Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for non english numbers in BitNumberField component #8551

Open
1 task done
ShahryarSaljoughi opened this issue Sep 8, 2024 · 1 comment
Open
1 task done

Comments

@ShahryarSaljoughi
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

The BitNumberField won't accept Persian numbers as valid digits.

More context on the problem:

There are several Language Packs available for Persian.
Let's say I have not passed in any format to the Format parameter. Hence, the underlying input element has a type=numeric attribute (based on your current implemnetation).
Now whether the input works as expected depends on the current language selected (Look at the image below too):

  • English (last item in picture) <-- works
  • Persian (First item in picture) <-- works
  • Persian (Iranian Standard Persian keyboard) <-- doesn't work
  • Persian (Persian (Standard) Keyboard) <-- doesn't work
    image

The problem occurs only if I use the top row keys of keyboard for entering numbers (not the numeric pad on the right-side of physical keyboards)

Describe the solution you'd like

I have the idea of mapping the literal strings like ("۱", "۲", "۳", ...) to their equivalent English characters.
I can see that this idea is not aligned with the fact that your implementation so far is not bound to any specific culture and this solution won't scale to a generic solution suitable for all cultures.
Given all the nice multi-lingual capabilities, I hope finding some more robust solution.

Additional context

Though suggested by numerous resources that setting lang attribute will help the problem, I tested and can verify that it won't help the described problem.

@msynk
Copy link
Member

msynk commented Sep 8, 2024

@ShahryarSaljoughi Thanks for contacting us. We're investigating this issue.
We'll let you know if it's possible to work on this issue.

@msynk msynk moved this to Investigating in Support tracking Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Investigating
Development

No branches or pull requests

2 participants