-
Notifications
You must be signed in to change notification settings - Fork 965
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
Theme translations #2396
Comments
While this is true if you want to use the I implemented a more complex version of this for tabi: see the PR and the docs for end-users. In short:
|
I mean, that's fair: you could do it manually, but it's still suboptimal that zola offers its own translation system and themes can't leverage that at all. Plus, eventually zola will have Fluent support, which will make it even more important to expose this to themes. |
I don't really want to add more with the basic translation system since it's meant to be replaced. Although at the same time it seems fluent is going to be superseded by something else (MF2)? |
Documentation issue
Summary
While it's clear that the translation system will be reworked eventually (#1058), right now a problem that exists is the fact that themes can't easily be translated. For example, if a theme includes custom translations that it wants to use via the
trans
template, these have to be included by the parentconfig.toml
and can't be included directly as part of the theme.Proposed solution
For now, probably the easiest method would be to simply copy the
translations
andlanguages.*.translations
keys fromtheme.toml
into the existing theme configs so that they can be combined with theconfig.toml
keys.The text was updated successfully, but these errors were encountered: