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

Alignment of language selection dialog in About>Translate #1713

Closed
VaishSiddharth opened this issue Jul 13, 2018 · 20 comments
Closed

Alignment of language selection dialog in About>Translate #1713

VaishSiddharth opened this issue Jul 13, 2018 · 20 comments

Comments

@VaishSiddharth
Copy link
Contributor

Summary:

The drop down menu in translate does not looks good.

Steps to reproduce:

  1. Go to About
  2. Tap on Translate
  3. See the drop down menu

Device and Android version:

Xiaomi Mi A1 (Android 8.0.0, API 26), with 2.7.2-debug-master~fa6353b3

Screen-shots:

screenshot_20180714-010003

Would you like to work on the issue?

I will try to fix this issue

@VaishSiddharth
Copy link
Contributor Author

@nicolas-raoul This issue need to be worked on i hope.

@nicolas-raoul
Copy link
Member

nicolas-raoul commented Jul 15, 2018 via email

@VaishSiddharth
Copy link
Contributor Author

VaishSiddharth commented Jul 15, 2018

@nicolas-raoul There is some text which is right aligned so it should be aligned to the left side.
screenshot_20180715-231905
The word (Kazakh) is not aligned properly. I mean its too much on the left side this should also be properly aligned.
screenshot_20180715-231955

@nicolas-raoul
Copy link
Member

I believe that each language should be shown in its natural alignment, so RTL is the best for RTL languages.
https://ux.stackexchange.com/a/67082/5179 seem to agree. On the other side, the language selection at https://www.wikipedia.org is all LTR so I am not sure what to think.

@VaishSiddharth
Copy link
Contributor Author

@nicolas-raoul I think it looks synchronized if we align all languages LTR otherwise its looks as if its an issue rather than intentionally done. May be centrally aligned solves this confusion.

@nicolas-raoul
Copy link
Member

I agree that centrally aligned may be the best.

@nicolas-raoul
Copy link
Member

The consensus at https://ux.stackexchange.com/q/119565/5179 seems to be:

  • If the app is currently in LTR, then align all language items (including the ones about languages that are usually RTL) to the left.
  • If the app is currently in RTL, then align all language items (including the ones about languages that are usually LTR) to the right.

@nicolas-raoul nicolas-raoul changed the title Drop down list in About->translate is not synchronized Alignment of language selection dialog in About>Translate Jul 18, 2018
@misaochan
Copy link
Member

If the app is currently in LTR, then align all language items (including the ones about languages that are usually RTL) to the left.

Sounds like the best solution to me. I agree with the poster who said that left-aligning RTL languages for very short phrases isn't usually an issue.

@VaishSiddharth
Copy link
Contributor Author

@misaochan So should i align all the languages to the left?

@misaochan
Copy link
Member

Lets wait for @nicolas-raoul to get back to us, shall we? :)

@nicolas-raoul
Copy link
Member

@VaishSiddharth could you please implement as described in my comment #1713 (comment) ? Thanks! :-)

@VaishSiddharth
Copy link
Contributor Author

@nicolas-raoul @misaochan Please have a look at the screenshots. Should i send a pull request?

screenshot_20180719-224008
screenshot_20180719-224017

@misaochan
Copy link
Member

I think @nicolas-raoul meant that the alignment should depend on the alignment of the language that the user is currently using? However, IMO your current code is an improvement to the existing state anyway, as the lack of alignment makes scanning the dropdown list really difficult. So you could submit a PR with that first, but we can keep this issue open so that an enhancement for RTL languages can be put in later.

@VaishSiddharth
Copy link
Contributor Author

@misaochan Ok

@VaishSiddharth
Copy link
Contributor Author

@misaochan By mistake I have commited this improvement with a branch which I had already used in a Pull request previously #1695. Please tell me what to do. Should I make a new pull request now? Or add in the description of that pull request about this improvement.

@misaochan
Copy link
Member

I would make a new PR, as they are fixing very different issues.

@VaishSiddharth
Copy link
Contributor Author

@misaochan Do I have to do anything?

@misaochan
Copy link
Member

misaochan commented Jul 24, 2018

Yes, please separate your PRs based on the issue they are solving. So these improvements should not be in #1695 . There are a number of ways to do this - for instance, you could use git cherry-pick on another branch and then resubmit your #1695 PR via that branch with only the relevant commits, and then do the same for the commits fixing this issue (with a different PR). Or you could just keep #1695 and revert the irrelevant commits.

@VaishSiddharth
Copy link
Contributor Author

@misaochan Ok I will do it.

@VaishSiddharth
Copy link
Contributor Author

@misaochan I have created a new PR please have a look.

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

No branches or pull requests

3 participants