-
-
Notifications
You must be signed in to change notification settings - Fork 178
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
i18n: add translation for default taxonomies #528
Comments
A few minutes ago, I also recognized this. Thanks for reporting. I'll make the appropriate changes to the theme. |
For the new feature to look nice, my life and coding partner @Xarkam added the following to layout/partials/content-footer.html. This looks fine and allows a content item to belong to more than one category.
This visually gives this for my work-in-progress website: Just be careful about font awesome 5 vs 6 we use. |
The fix has landed in master, but I want to fix some stuff first before the next official release. In the meanwhile you could check out the translation. I hope Google Translate and DeepL did their job well. |
I just added a comment to the commit, great work with a small wording fix please for fr language. |
Hello,
In addition to tags taxonomy, I configured categories taxonomy in my website, and copied layout/partials/tags.html to layout/partials/categories.html, replacing "tags" by "categories" and "tag" by "category".
Then I noticed than in French, we don't use the same word for "category" as in English, unlike "tag" where we also use "tag".
My question is about the pages that lists all pages of a given tag/category: the layout/partials/_taxonomy.html template is used. I would like to get the "tag"/"category" word present in title in my display language, so changed line 7 to the following, adding "i18n":
Then in every .toml language file (I guess really in each...) I would need to declare a new term else there is no word displayed:
Is this the right way to achieve what I'd like to do?
Thanks
The text was updated successfully, but these errors were encountered: