-
Notifications
You must be signed in to change notification settings - Fork 103
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
RFC Multi-language site support #392
Comments
GNU GetText style |
@pickfire: That's definitely a necessary part of the complete picture! Another thing that would be really important is to have a way of relating localizations of the same content to each other, with a default language as fallback for nonexistent localizations. Hugo does a good job presenting an end-user spec here: https://gohugo.io/content-management/multilingual/ Those are the two main parts needed to fulfill this use case for static sites. A little static JavaScript could be used in tandem with the aforementioned information to redirect users to the correct localization for a page -- not necessary, but an interesting feature to build on top of the previous two. |
Note that I've written a RFC for i18n in Gutenberg: getzola/zola#111 |
@Keats The one I was talking about are most possible in the alternatives section though where we use one file to do multiple language, I didn't thought of separating the file though. So now I guess we have something like: split
share
|
@Keats: I much appreciated the RFC for i18n support in Gutenberg! It seems well-designed, and where the inspiration came from seems well-proven. :) |
There is no tool/library for i18n in pure Rust as far as I know though, there's a couple of gettext crate but nothing really good apparently. |
I would really like to contribute, especially on this issue. Do you think you could guide me somehow? I'm a beginner in Rust. |
The problem is we first need to come up with a design
|
Challenges / Requirements
Design
The text was updated successfully, but these errors were encountered: