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

Some keys can not be tapped on non English keyboard. #31

Open
lestathc opened this issue Feb 25, 2016 · 5 comments
Open

Some keys can not be tapped on non English keyboard. #31

lestathc opened this issue Feb 25, 2016 · 5 comments

Comments

@lestathc
Copy link

Hi,

I tried the EarlGrey, if you want to test non-English app, some keys can not be tapped, like "space". I tried with "fr", the space key should be "espace".

Besides of that, EarlGrey is great, thanks for making this.

@lestathc lestathc changed the title Some keys can not be tapped on non English key Keyboard. Some keys can not be tapped on non English keyboard. Feb 28, 2016
@tirodkar
Copy link
Collaborator

@lestathc you should be able to type any language string using grey_replaceText() now. Please do give it a try.

@KazuCocoa
Copy link
Contributor

In my case, I could put some Japanese into search field with grey_replaceText() .

@Usipov
Copy link

Usipov commented Aug 8, 2017

I have added support for Сyrillic letters in my fork of this repo.
This was done as a proof of concept only.
I will probably refactor this code to make support for different languages more scalable and then merge the fork back. I just have no time for this at the moment

You may take a look at this PR: https://github.com/Usipov/EarlGrey/pull/1/files

@tirodkar
Copy link
Collaborator

tirodkar commented Aug 8, 2017

That's super awesome. I was planning to do the following to add support:

  • Allow custom gShiftLabels to be set, with an override option.
  • Allow custom modifier key identifiers - space, delete return etc.
  • Allow custom more, numbers & more, letters & Next Keyboard key identifiers.
  • Allow the ability for checking capitalization with the custom language.

Would that satisfy all the requirements?

@Usipov
Copy link

Usipov commented Aug 9, 2017

@tirodkar, no, there is one more thing to be done.
Some characters require a long tap gesture followed by swipe gesture (see the screenshot below).

Also it is sometimes useful to type Cyrillic and Latin characters in a same test.
For example, the registration form may require an email and a password to be typed in English and a user's name to be typed in Russian
So I think, that override options can be less useful than simple extension points

simulator screen shot 9 aug 2017 10 17 16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants