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

Please consider full i18n #103

Open
mhf-ir opened this issue Dec 3, 2019 · 2 comments
Open

Please consider full i18n #103

mhf-ir opened this issue Dec 3, 2019 · 2 comments
Labels
feature New feature or request text
Milestone

Comments

@mhf-ir
Copy link

mhf-ir commented Dec 3, 2019

If planing for world class UI library please consider fully i18n.
https://mhf-ir.github.io/i18nplease/

btw you're start great job. ❤️

@hecrj hecrj added the feature New feature or request label Dec 4, 2019
@hecrj hecrj added this to the 1.0.0 milestone Dec 4, 2019
@hecrj
Copy link
Member

hecrj commented Dec 4, 2019

Thank you!

Support for internationalization is planned (we have parts of it in the roadmap).

A first step towards this goal would be to render text properly in iced_wgpu (see #33). This is quite a big step, as the current font parsing and text rendering ecosystem in Rust is not very mature. However, I think we will slowly get there!

An alternative short-term-wise would be to build a renderer on top of some 3rd party library that handles text shaping and font fallback correctly.

@cguentherTUChemnitz
Copy link

Does this really need to be part of the ui-framework like iced? Wouldn't it be already sufficient to wrap the strings before putting into iced with an i18n implementation:
https://github.com/longbridgeapp/rust-i18n

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

No branches or pull requests

3 participants