-
Notifications
You must be signed in to change notification settings - Fork 92
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
[static_comments] localization messages #304
Comments
If you have your own custom theme, you can add the messages to the theme's translation files ( |
I think it looks in the theme only. |
Is there an example somewhere in what format this needs to be added? A pointer to relevant Babel documentation (I see that the project is using Babel but have never used it myself) would be fine. Thanks |
The project doesn't use babel, or at least not for translations. Translations have to be available in the theme folder(s) in The easiest way to add translations is probably to create a "dummy" theme which inherits from the theme you're using, and add translations there (and add nothing else). You don't have to provide all translations, Nikola will go through the theme chain and load all missing translations from the themes lower in the chain... |
The documentation mentions that for static comments some localization messages are necessary:
"Finally, you need to add support for some additional messages."
but fails to mention how and where to add them. I also didn't find a pointer in the nikola handbook. My current solution was to remove the localization from the jinja template.
Otherwise: Thanks for the good work, I was able to convert an existing WP blog with all comments.
The text was updated successfully, but these errors were encountered: