+[2016-10-08T21:52:31Z]Ademanosfameron: hrm that's a very interesting idea, thanks. For the moment I've semi-required duplication, each translated page is a stub with front matter declaring the language, and an include_relative to the "base" page... seems like it'll work but I haven't fleshed it out completely yet +[2016-10-08T21:53:10Z]Ademana symlink might be a huge improvement though, not certain if that'll fly on github pages (is git aware of symlinks?) but it's worth a shot +[2016-10-08T22:01:24Z]osfameronnot sure, not tried, but let us know *if* it works :D +[2016-10-08T22:01:31Z]osfameronI suspect that duplication is the way to go though tbh +[2016-10-08T22:02:11Z]osfameronbut I've not done i18n with jekyll personally, there may be better practices
not sure, not tried, but let us know *if* it works :D
+[2016-10-09T07:50:22Z]gynterAdeman: https://github.com/gynter/gynter.github.io +[2016-10-09T07:50:23Z]jekyllrbTitle: GitHub - gynter/gynter.github.io: Homepage of Günter Kits (at github.com) +[2016-10-09T07:51:25Z]gynterThis explains it a bit: https://talk.jekyllrb.com/t/two-languages-on-the-same-site-how-to-disadvantages/1150 +[2016-10-09T07:51:26Z]jekyllrbTitle: Two languages on the same site: how to? Disadvantages? - Help - Jekyll Talk (at talk.jekyllrb.com) +[2016-10-09T07:51:47Z]gynterhttps://talk.jekyllrb.com/t/two-languages-on-the-same-site-how-to-disadvantages/1150/2?u=gynter