RFC Multi-language site support

cobalt-org / cobalt.rs

Static site generator written in Rust

cobalt-org.github.io/

Apache License 2.0

1.35k stars 103 forks source link

RFC Multi-language site support #392

Open epage opened 6 years ago

epage commented 6 years ago

Challenges / Requirements

Design

pickfire commented 6 years ago

GNU GetText style _ for i18n?

ErichDonGubler commented 6 years ago

@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.

Keats commented 6 years ago

Note that I've written a RFC for i18n in Gutenberg: https://github.com/Keats/gutenberg/pull/111 Not implemented yet but is similar to the approach Hugo is using, which is quite good IMO

pickfire commented 6 years ago

@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

hello.en.md - Hello, world!
hello.zh_CN.md - 你好，世界！

hello.md - { _hello }
po/en.po - hello "Hello, world!"
po/zh_CN.po - hello "你好，世界！"

ErichDonGubler commented 6 years ago

@Keats: I much appreciated the RFC for i18n support in Gutenberg! It seems well-designed, and where the inspiration came from seems well-proven. :)

Keats commented 6 years ago

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. The shared approach is interesting but then end users have to deal with gettext translations manually or upload them to some services like Transifex and it's not super user friendly (still need a way to deal with translations in templates though).

ail3ngrimaldi commented 1 month ago

I would really like to contribute, especially on this issue. Do you think you could guide me somehow? I'm a beginner in Rust.

epage commented 1 month ago

The problem is we first need to come up with a design

We'd need an understanding of the requirements. What do people expect out of this? What assumptions can be made?
It'd help to look at how other SSG's support multi-lingual sites (config fields, source layout, output layout) so we can learn from them. Even better to do a comparative analysis
With the above two, we need at least one design proposal and to iterate on it.