[i18n] Please use Fluent for localization

[alerque]

Dissatisfied with other current static site generators (I currently have Hexo, Hugo, Jekyll, & custom sites deployed) I was poking around the field and ran across this project. I'm actually pretty excited about it, but for my use cases internationalization is pretty much the biggest stumbling block. I see this project is only just starting to dabble in it. Please please consider using Fluent for all localization except perhaps Markdown body content. This is something most other site generators get wrong. Most of them try to use YAML or JSON key/value lists to localize the generated site UI. That approach simply isn't good enough.

I might even be able to contribute some to implementing this. The Rust bindings for Fluent are quite good and I've done some work with them before.

[Keats]

That's the plan: #1040

[alerque]

Oh awesome, that looks promising! I had searched issues but not PRs.

[alerque]

So what's the status on localization with Fluent? I've been waiting for any progress on this issue to review whether I can reasonably start migrating sites. Given that the related PR was also closed without being merged it seems like maybe there has been no progress, maybe even the priority has slipped. Is there another issue I'm missing where localization (and specifically via Fluent) is being tracked?

[Keats]

https://zola.discourse.group/t/rfc-internationalization-system-rework/546/4 and #1148

[alerque]

I'd like to request this issue be re-opened per my comment on the related Tera issue, to track progress until Fluent can be used by default to handle localization in Zola based sites without needing to code, compile, and plumb your own toolchain.

[alerque]

Kind of a side show, but tera-cli now (HEAD) has support for Fluent localizations as a data provider for filling out templates. I'm currently using tera to pre-process some things before passing them to zola. This works (ish) but is a build-system spaghetti mess. I'm still looking forward to first class support in Zola itself.

[Keats]

It looks like fluent is not going to be potentially maintained? projectfluent/fluent#358 I don't know what is MF2 except some standard effort

[clarfonthey]

Hmm, that is weird, especially considering how the Rust compiler itself is using Fluent now. Maybe worth seeing what direction they go in following this.

[heyakyra]

Fluent is stable. MF2 seems to basically be a re-implementation of the same concepts but not actually ready to be used, while Fluent is already good-to-go.

[alerque]

It looks like fluent is not going to be potentially maintained?

Mozilla has added two external community contributors (myself and another guy) with ownership status for the Rust crates and access to the repos. We've cut releases for all the unreleased development work from the past couple years, merged a bevy of PRs that have been outstanding for a while, and started digging into some long standing niggly issues. A couple original devs are also still actively involved. While it might have been ambiguous for a while while Mozilla decided how they were going to handle things, I don't think its fair any more to characterize Fluent as "potentially unmaintained" any more.

And again in relation to MF2 the latter is conceptually similar but also not currently implemented anywhere. It's a draft spec that just posted a tech preview, not a working library. It will have implementations in the future, but it isn't viable today. Also there will be migration paths for people that do decide to switch and probably also interop libraries for folks that prefer one or the other but want to interact. There is cross over in the dev teams too (you'll find my name in MF2 spec contributors and there are people even more deeply involved in both).

[alerque]

Also even if you don't use it directly, referencing i18n-embed would be smart as an implementation that would parallel some of the asset handling code Zola would probably want.