Open hunvreus opened 7 years ago
By the way, the site we're gonna be testing it against is at https://github.com/Wiredcraft/1912pike.
(now available at http://{branch}.1912pike.wiredcraft.jekyllpro.com) - see https://github.com/Wiredcraft/jekyllpro/issues/26 for more details
@hunvreus can this be closed, I believed we used another approach in the end.
You can safely ignore the stuff above.
However;
When the language is not default, you need to save the language as categories:
in the YAML front matter as well. For example;
title: Non default language post
lang: en
categories: en
If a post has no translation yet, we should allow the use to change the language and have the language bar enabled.
This ticket is broken in 2 parts. Only act on the first one for now;
[ ] Test that all translated content is in the
{lang/}
subfolder; I can't remember for example if we store the posts inzh/_posts
or_posts/zh
(for example with Chinese). It should bezh/_posts
.[ ] (OPTIONAL) Renamed
lang
attribute and rely on subfolder; I did some more testing over the weekend and I think the best and most flexible approach is to use the subfolder to specify the language. That means the yaml front matter should omitlang: zh
for example, and rely on the fact that the entry is in thezh/
subfolder or has an explicitcategory: zh
attribute. I understand this may break a bunch of things (like the translation links in the edit form) so hold off for now if it's more work than 10 to 20 minutes. We probably need to discuss it a bit more anyway.