Skip to content
New issue

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

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

Already on GitHub? # to your account

Multi-language support #24

Closed
geoffreymcgill opened this issue May 27, 2021 · 7 comments
Closed

Multi-language support #24

geoffreymcgill opened this issue May 27, 2021 · 7 comments
Assignees
Labels
Milestone

Comments

@geoffreymcgill
Copy link
Collaborator

geoffreymcgill commented May 27, 2021

Originally posted by @slimooo in #18

See also

@DannyBen
Copy link

DannyBen commented Jul 23, 2021

I would like to drop the RTL bomb.... 💣

I know that RTL languages (Hebrew, Arabic) are usually neglected by most software vendors due to probably less demand, and more complexity in UI terms - but I think that if the UI is thoughtfully prepared, it should be a matter of strapping a <body class='rtl' direction='rtl'> to it, and then it should be easy to support RTL (which of course entails having the lefthand sidebar on the right).

Whatever the future holds for this localization feature - if RTL support finds its way in, I am happy to assist (both in RTL terms, and if needed, in localization concepts and planning).

@fabriciomurta
Copy link
Contributor

Well, I saw this bomb falling! 💥

From my experience, this would mean a complete rewrite of the CSS styling and many HTML. As you said yourself, even right sidebars may become left sidebars when RTL is in place. So I believe translation for LTR languages should be dealt in separate steps from actual RTL implementation. That's not just a matter of placing strings over placeholders, but a complete layout revamp.

One important aspect to have it well implemented and maintained is an actual audience to report the layout issues as they rise. :)

I mean, it would be worth its own dedicated issue.

@DannyBen
Copy link

Yeah, possibly.

From my experience - and the many days I spent dealing with such issues - I want to mention just a couple of key point that might help.

  1. Tables, columns, flexboxes, "float lefts" - are all automatically organized in reverse order once wrapped inside a container with direction='rtl' - so dealing with this is usually just minor adjustments.
  2. The other aspect is CSS elements that received explicit float, align, or uneven padding/margin. For these, I usually do something like this (SCSS):
.col { 
  .ltr & { float:left; }
  .rtl & { float:right; }
}

Anyways - when the time comes, give me a call.

@geoffreymcgill
Copy link
Collaborator Author

RTL is certainly something I'm interested in supporting. I love the challenge. We have been involved in other large projects in the past with the requirement, so it's not completely foreign nor off our radar.

It's on my list, but... we will likely need to add to our UI team before we can tackle RTL support.

@vmohir
Copy link

vmohir commented Mar 18, 2022

This should be really easy by using CSS logical properties as Retype is using utility classes. Even there are tools to automatically convert a CSS code to logical properties. You'll lose IE support though.

@geoffreymcgill geoffreymcgill added this to the v3.0 milestone Mar 15, 2023
@geoffreymcgill
Copy link
Collaborator Author

Retype v3.0 will include support for changing the interface language. Currently 24 languages are supported.

See the following docs for the translations:
https://retypeapp.github.io/retype-translations/

The source repo is available at:
https://github.com/retypeapp/retype-translations

RTL is not support. Hopefully one day.

@geoffreymcgill
Copy link
Collaborator Author

The new locale project configuration is now available in Retype v3.0, see docs.

The Retype Translation repo is available at https://retypeapp.github.io/retype-translations/.

Hope this helps.

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

No branches or pull requests

4 participants