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.

Sign up for GitHub

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

Jump to bottom

Internationalization #134

Closed
vladwing opened this issue Feb 11, 2017 · 4 comments
Closed

Internationalization #134

vladwing opened this issue Feb 11, 2017 · 4 comments

Comments

@vladwing
Copy link

I see there is no documented way for providing internationalization/localization to tera. Is there a recommended way? If not, what do others use in this case?
@clarfonthey
Copy link
Contributor

Internationalisation is a problem that tera itself doesn't solve; I'd recommend looking at crates like l20n.

@Keats
Copy link
Owner

Keats commented Feb 13, 2017

There's no de-facto solution for i18n/l20n in Rust as far as I'm aware. Once there is one, I'll add support directly in Tera if needed

@kennytm kennytm mentioned this issue Jan 28, 2018
Closed
@Keats Keats mentioned this issue Aug 6, 2018
Closed
@Keats
Copy link
Owner

Keats commented May 1, 2019

Note that I'll probably add fluent to Zola but I'm not sure it will be something solved in Tera itself. If it is easy enough to add, I can just point to the implementation there instead.

@Keats
Copy link
Owner

Keats commented Dec 7, 2019

That can be added as a filter outside of Tera itself.

@Keats Keats closed this as completed Dec 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Keats @vladwing @clarfonthey